By now, I’m sure you’ve noticed Twenty Sixteen has been released on Github and the theme repository to spur development and testing. If you haven’t tested the theme for accessibility, now’s the time! I mentioned it in a recent chat, and a members from the community have already tested it, but the more the merrier!
What do I test?
Test the theme according to the accessibility-ready requirements. Since this is a default theme, you should test for the recommendations too. Also, it’s a good idea to look at the applicable WCAG 2.0 requirements (Link is not the official WCAG requirements, but a more readable version), and test the theme according to those, within reason. This way, the theme can be its best accessibility-wise.
How do I test?
The accessibility-ready requirements give some information on how to test. We also have a list of tools that will help when testing.
How do I report bugs, issues or make a enhancement request?
- Create an issue on Github.
- If you can’t create an issue on Github, comment on this post.
- If you can’t do that, drop us a note on our contact form, making sure you mention Twenty Sixteen.
What information do you need to know when creating an issue?
Here’s a good format to follow when creating a bug report:
Title: Accessibility: ISSUE SUMMARY HERE What I Did: What I Expected: What Actually Happened:
I’m not a developer, how can I help?
No problem! You don’t have to be a developer to help out. Test the theme on your favorite operating system with assistive technology. This way, we get a better idea of how the theme works with different configurations. Try to break the theme! Note anything that is confusing, and makes the theme harder to use on the front end.