Members of the Make WordPress Accessibility Team are volunteers working on improvements to accessibility in WordPress for people with disabilities.
Not everybody contributing to WordPress is technically minded; in fact, everyone connected with accessibility can contribute to the Accessibility Team. We particularly want to hear from people who are regular users of assistive technology (AT), as your perspective is especially valuable testing accessibility fixes for WordPress.
The Accessibility Team includes core committers, developers, testing specialists, content writers, and organizers; it could include you!
Each new version of WordPress brings accessibility improvements. The more discussion and testing we can do, the faster that rate of change can be.
Team focus areas
- WordPress core and the block editor.
- Documentation about web accessibility.
- Accessibility-ready Program.
WordPress core and the block editor
Monitor the broad accessibility of WordPress core, and any areas of WordPress not covered by another working group. Monitors and contributes to tickets in the core Trac. The general team is primarily developers and testers.
- Writing patches for accessibility trac tickets.
- Give code examples for trac tickets (the expected output).
- Help with the discussion & testing of possible solutions.
Take a look at the overview of accessibility tickets and take your pick.
We review Gutenberg accessibility-related issues, write and discuss tickets on GitHub and write code patches. We need people who know how to test for accessibility and/or use assistive technology to test existing and new functionality.
- Monitor changes to the Editor, both in Full Site Editing and in Block Editor.
- Track goals for future versions of the editor and design changes.
- Keep the team informed when major changes are planned.
Contact: Joe Dolson (@joedolson).
Documentation about web accessibility
We write documentation about accessibility for the WP Accessibility Knowledge Base and contribute to Accessibility documentation wherever needed around WordPress.org.
- Provide links to good resources and verify the existing links.
- Write explanations and general documentation.
- Write code examples.
Contact: Rian Rietveld (@rianrietveld).
Accessibility-ready Program
We review themes for the WordPress.org repo labeled with the accessibility-ready tag, new core themes, and review of the WordCamp themes, and provide assistance with accessibility issues.
Contact: Amber Hinds (@alh0319).
Need more info?
For any other questions and/or suggestions go to accessibility channel on Slack and ping any of the contacts mentioned above.
How do you get in touch?
We have a number of communication channels where you can reach out to us and contribute your thoughts and ideas. Choose the one that works best for you.
- Updates on our meetings and discussions are posted to our blog. WordPress developers also post tips and questions here. To reply to posts, you’ll need to log in to wordpress.org. If you don’t have a wordpress.org username you can register at the WordPress Support page.
- The best way to contact us is in the Slack #accessibility channel. We have biweekly meetings in Slack and weekly bug scrubs.
Come and help make WordPress more accessible for everyone. And if you’ve got some ideas about how we could better reach out to people, we’d love to hear those too.
How do I get an Accessibility Profile Badge?
The Accessibility Team has both a Contributor badge and a Team badge. The Contributor badge is for anybody who has helped improve the accessibility of any part of the WordPress core ecosystem, including the WordPress.org properties.
Learn how to get a Profile badge for the Accessibility Team.