Accessibility related tickets, tasks, and reports

Tickets with a focus on accessibility

Top ↑

Gutenberg: GitHub issues with a focus on accessibility

Issues have accessibility label.

Top ↑

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

AccessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). ( 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 URLURL A specific web address of a website or web page on the Internet, such as a website’s URL to filterFilter Filters are one of the two types of Hooks They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output. out the closed tickets.

Top ↑

If you find an accessibility issue in WordPress coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress., or in one of the core themes, please create a new ticket and give it the focus “accessibility”.

Last updated: