Efficient Accessibility Testing

Version 2.2 of the W3C's Web Content Accessibility Guidelines (WCAG) contains 87 "success criteria", so significant resources would be required if every page of a site was to be tested against each success criterion. Fortunately this is not necessary, and there are several efficiencies to be made:

  • Only test the appropriate success criteria. The 87 success criteria are divided into three conformance levels. The Level A success criteria are the most important, so if you only need to achieve a basic level of accessibility it is only necessary to test these 32 success criteria. Most websites should aim to meet the Level AA success criteria, which requires a further 24 to be tested, but this still represents a 36% saving compared with testing all 87.

    Many of the Level AAA success criteria require coding techniques that are not part of mainstream development practice. It is rarely worth testing them unless the website has been specifically designed to meet this level.
  • Don't test every page. Most sites are based on templates, and it is usually sufficient to test one example of each template. Additional pages may be required depending on the content e.g. data tables, forms, lists, images maps etc.

    We will gladly perform an audit of your site to determine the minimum number of pages to be tested. On a typical 100 page website, we often find that it is sufficient to test just six or seven pages.
  • Lightweight test tools. Lightweight tools such as the Deque axe browser extension, Colour Contrast Analyser and single-purpose bookmarklets greatly improve the efficiency and accuracy of code inspection.
  • Expertise and experience. It takes time to learn all the web technologies such as HTML, CSS, JavaScript, ARIA, AJAX etc, to understand the rationale behind the WCAG success criteria and develop the techniques for testing them. We are already at the top of this learning curve, so our efficiency will lower your costs and shorten your timescales.