This guide is intended to help you get started at a contributor day. If you need any help, talk to the contributor day organizer, or ask your question in the #accessibility channel on Slack.
Developers and designers who know how to contribute to core and want to take up, test, or discuss issues
Designers who want to help in discussions about making things beautiful and also accessible
Accessibility testers to help find new issues, test fixes, and discuss solutions
You can work at the accessibility table or at the core, themes or design tables. Accessibility touches many aspects of the project. All designers, developers and testers are welcome to pick up the task that fits them.
In the WordPress Slack channel #accessibility you can ask for work with priority or for help with choosing a task. The time needed for a task depends on the complexity of the issue. But testing a patch or fix, confirming a bug, or adding ideas is also useful and usually quicker.
Gutenberg is the new text editor for WordPress and it’s still in development. Gutenberg still needs a lot of accessibility improvements. Issues you can work on as a developer or designer are on the Gutenberg GitHub repo labeled with “Accessibility”.
If you know your way with assistive technology like a screen reader of can navigate with keyboard only, testing Gutenberg is also very valuable. At the moment you can install it as the plugin Gutenberg. Please read the page Gutenberg Accessibility Testing on how to do the testing best.
Accessibility issues of the website wordpress.org are listed in the meta trac, work on those tickets is appreciated.
WordPress.org is enormous, and there are always items that haven’t been tested yet. A good accessibility review on wordpress.org is still needed. If you’re an accessibility tester, please take a look at the site and it’s functionality and report any issues you find.
