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.
When you use a text and background color combination that may be hard to read, WordPress gives you the following warning: “This color combination may be hard for people to read. Try using a brighter background color and/or a darker text color.”
We are wondering if it the team would think it would be in improvement to specifically call this out as an “Accessibility” concern. In our institution, we’ve been trying to emphasize accessibility to our content providers for years, but it’s always an uphill battle. While we love the clear/readable/plain language, we thought that maybe specifically calling this out as an accessibility concern might make people take it more seriously.
Some initial thought options included adding a small heading before it, such as “Accessibility Warning” or just adding a few words to the end “… to make the content more accessible.”