Accessibility related tickets, tasks, and reports

WordPress uses several separate systems for tracking issues. Issues with WordPress itself are tracked in core ticket tracking. Issues with the network of sites at The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. are tracked in the meta ticket tracker. Issues in the development of the blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. and site editors are tracked in the Gutenberg repository at GitHub.

Core tickets with a focus on accessibility

Top ↑

Gutenberg: GitHub issues with a focus on accessibility

GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. issues have two different labels.

  • The accessibility focus, representing issues that directly impact 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). (, and
  • The Needs Accessibility Feedback label, representing UXUX UX is an acronym for User Experience - the way the user uses the UI. Think ‘what they are doing’ and less about how they do it. changes seeking feedback on accessibility.

Top ↑

Accessibility tasks

Tickets that are ongoing tasks because there’s the need to find instances, touch several parts of the code base, etc. They need to be split into separate tickets for each instance. Any help welcome!

These include general, broad, issues that either require substantial refactoring or exist broadly across many aspects of the admin. All tasks use the a11y-task keyword, so they can be located easily.

Top ↑

Contribute to a task

Accessibility tasks are long-term projects, and may be completed by one or several people. A task can be in many different stages. Usually, there’s a research phase, then a development phase. This may be repeated multiple times, depending on the scope of the task. In a research phase, you identify examples of the problem in coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress., document those problems, and open new tickets for each individual problem or small group of problems.

  • Find the problem.
  • Open a ticket.
  • Add a comment to the tracking ticket with a link to the new ticket.

During the development phase, the open tickets are resolved. The ticket can be closed when you are unable to locate examples of that problem in core.

Top ↑

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 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.

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”.

Last updated: