Accessibility related tickets, tasks, and reports

Tickets with a focus on accessibility Tickets with a focus on accessibility

Top ↑

Gutenberg: GitHub issues with a focus on accessibility Gutenberg: GitHub issues with a focus on accessibility

Issues have accessibility label.

Top ↑

Accessibility tasks Accessibility tasks

Tickets that are ongoing tasks because there’s the need to find instances, touch several parts of the codebase, etc. They need to be split in one ticket for each instance. Any help welcome!

Review the usage of the change event on select elements.

Other long-term tasks: General, broad, issues that would require some big refactoring and probably can’t be solved soon. Opened to start the discussion and research under a11y-task keyword.

Top ↑

Accessibility keywords Accessibility keywords

Accessibility tickets grouped by topics. We use custom keywords to keep track of some main accessibility issues. To give some background about the progress so far, these reports show all the tickets, even the closed ones. Append &status=!closed to the URL to filter out the closed tickets.

Top ↑

If you find an accessibility issue in WordPress core, or in one of the core themes, please create a new ticket and give it the focus “accessibility”.