The Accessibility Team provides accessibility expertise across the project to improve the accessibility of WordPress core and resources.
The WordPress Accessibility Coding Standards state that “All new or updated code released in WordPress must conform with the Web Content Accessibility Guidelines 2.1 at level AA.”
Find out how you can help!
- Get involved
- See the accessibility related active tickets, tasks, and useful reports
- See accessibility issues for the block editor
- Found an accessibility related bug? Create a new ticket
For questions or support related to WordPress & accessibility, please visit the WordPress Accessibility forum.
Learn how to design, develop, and write accessible code in our Handbook – best practices.
It’s also worth noting that during the meeting, our meeting note taker suffered an unexpected and unexplained data loss in Gutenberg, losing the entire post. This led to a discussion of frustrations with issues in Gutenberg where the team would really like to see a release cycle focused on polishing bugs rather than feature development. We’re aware, of course, that the Make site network uses Gutenberg trunk, which can lead to stability problems, but it exposes some of the types of frustrations people have on a daily basis that can create a bad feeling for the product. See: http://wayback.fauppsala.se:80/wayback/20210909145543/https://wordpress.slack.com/archives/C02RP4X03/p1630687004075200