This information is for the Accessibility Test Team.

Our tests are divided into four groups of test types. For each group, we’ve listed some specific elements to look for in your testing. Pick the way you want to test – you don’t need to do every type of test, just what you can or want to.

  1. Keyboard testing
  2. Screen reader testing
  3. Color contrast / color blind test
  4. Code testing (for developers)

1. Keyboard only testing 1. Keyboard only testing

First, read about how to navigate a site using only your keyboard

What to test:

  • is the tab order logical, can you tab forward and backward logically
  • can you access all links and buttons you need
  • can you see where you are, while tabbing
  • can you complete the task using a keyboard only
  • do you drop out of a screen overlay and can’t you return?
  • make the window smaller until the site pops into responsive mode and test again
  • try different browsers and if you can also a tablet or mobile phone.

Top ↑

2. Screen reader testing 2. Screen reader testing

We recommend to test with the following screen reader/browser combinations:

  • VoiceOver + Safari on Mac
  • NVDA + Firefox on Windows
  • JAWS and IE 11 (no Edge yet) on Windows

ChromeVox is not included in the tests, it has too many issues at the moment to perform as a good screen reader.

What to test:

  • is the tab order logical, can you tab forward and backward logically
  • is the heading structure logical?
  • can you access all links and buttons you need
  • are there unclear links or buttons?
  • can you complete the task using the screen-reader
  • do you get stuck and don’t you know where you are?
  • where do you get stuck?
  • try the test on more than one screen reader if you can, like NVDA, Jaws, Apple Voice Over, Dragon Naturally Speaking or SuperNova. Please note with your test on which device and browser you test

Top ↑

3. Color contrast / color blind test 3. Color contrast / color blind test

  • can you see everything properly, is the contrast good enough for you?
  • if you are color blind: is there text you can’t read well?
  • you can simulate color blindness by using the Colour Contrast Analyzer

Top ↑

4. Code testing (for developers) 4. Code testing (for developers)

  • perform the keyboard testing (see 1).
  • are there major issues while validating the code with http://validator.w3.org
  • forms: does every input field have a label
  • can you see where you are, while tabbing: do all links/buttons have a .focus class with a clear focus on active
  • are all html elements used correctly, a button must be focusable by keyboard and href=”#” should be a <button>
  • color contrast: we test the color contract against WCAG 2.0 AA rules. This means the contrast ratio must be more that 4.5. You can test the HTML color code contrast of the text and background with the Contrast Checker

We want to meet the accessibility rules for WordPress theme and WCAG 2 AA. Take also a look at the Useful development tools for testing.

If you want to join the test team or have any questions: please contact us in Slack in the accessibility channel or fill out our contact form.