WP A11y Docs update February 2026

This update informs you about:

• new content;
• changes in the current team handbook;
• plans for March.

New content on wpaccessibility.org

• The way of navigating the content is now less depending on the main menu. For a better user experience, also for mobile views.
• We added the Reading guide, vistors now can find content by role or expertise instead of by topic only.

Changes in the current team handbook

The Accessibility Team Handbook now only addresses the info about the 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). (https://en.wikipedia.org/wiki/Accessibility) team itself and for the accessibility documentation we now point to the Standards and best practices in the WP Accessibility Knowledge Base. Since redirects for popular pages are not possible, some subpages will be left in place to guide users to the updated content.

Plans for March ’26

• Finish the documentation about Focus management, in the sections Frontend code and Web forms.
• Start with updating and extending the documentation for the section Content and images.
• Transfer the Accessibility team handbook to GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged by the repository owner. https://github.com/.

#wp-a11y-docs