a11y: Use `<button>` instead of `<a>` for several non-links
- Dominant language
- JavaScript
- Stars
- 338
- Forks
- 56
- Avg merge
- 24m
- Merged PRs (30d)
- 16
Description
Related: https://core.trac.wordpress.org/ticket/26504
For example [the editor tabs](https://github.com/Automattic/o2/blob/996d8de3c6525c0d02b005b795f9956624c5f1d3/inc/tpl/front-side-new-post-edit.php#L7-L8) or [the save button ](https://github.com/Automattic/o2/blob/996d8de3c6525c0d02b005b795f9956624c5f1d3/inc/tpl/front-side-new-post-edit.php#L11) should be real buttons. This would not only be semantically correct it also allows to conditionally disable one of the buttons.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start in inc/tpl/front-side-new-post-edit.php, especially the editor tabs and save control around lines 7–11. Review the related WordPress ticket for accessibility context, then identify the other non-link controls in the template. Done means those controls use button semantics and can be conditionally disabled without changing link behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- accessibility, frontend
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100