WP A11y docs update September 2026

With:

• New and updated documentation.
• MigrationMigration Moving the code, database and media files for a website site from one server to another. Most typically done when changing hosting companies. of 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 Handbook.
• Our plans for October.
• The roadmap of the project.

New and updated documentation

In standards and best practice:

• Tables in the content in Content and images.
• Tables in front-end development in Frontend code.
• Color contrast for non-text content in Design and user experience.
• Color contrast of text against its background in Design and user experience.
• Patterns to avoid: Infinite scroll in Design and user experience; update for WordPress 7.1.

Migration of the Accessibility Team Handbook

We are moving the maintenance of the Accessibility Team Handbook over 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/ in the repo WordPress/accessibility-team-handbook, @coffee2code is helping. The reason for the migration is that more people can contribute to the content of the handbook when it’s on GitHub.

Our plans for October

We continue to work on getting the issues done in the Tracking issue Content pages: create or review or rewrite, and hopefully get the migration of the Accessibility Team Handbook finished.

The roadmap of the project

As a reminder, this is the roadmap:

• Phase 1: finish the content of the Knowledge Base, we hope to achieve this soon.
• Phase 2: Sync the content in the Knowledge Base with a new section in developer.wordpress.org called accessibility.
• Phase 3: Read through the accessibility information on wordpress.orgWordPress.org 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. https://wordpress.org/ and decide if content needs to be updated or point to Knowledge Base on developer.wordpress.org. We want to keep one source of truth to avoid duplication and outdated info.
• Phase 4: Maintenance. WordPress, web techniques, and accessibility change, we want to keep the documentation up-to-date.

Rian explains the roadmap in more detail in the interview with @mbootsman: Rian Rietveld on the Four Phases of the WP Accessibility Project.

#wp-a11y-docs