Introduction

In our context, the goal of accessibility testing is to identify barriers for users with disabilities when they use websites or apps. This includes permanent as well as temporary disabilities and impairments of senses, e.g. for elderly people (1).

Customers who run accessibility tests at test IO receive reports about lacking accessibility in their products, so that they can redesign their products in certain aspects to meet international standards and practices.

Check out the related articles at the bottom of the article to learn more about web accessibility.

Web Content Accessibility Guidelines (WCAG)

The Web Content Accessibility Guidelines (WCAG) contain checkpoints of three priority levels (2):

  • Level A covers items on web pages that must be made accessible in order for individuals with disabilities to access the content at all.

  • Level AA includes items on web pages that should be made accessible to allow a wider group of users to access the content.

  • Level AAA describes items on web pages that can be made accessible to allow the widest amount of individuals with disabilities to use the site.

The description of your accessibility test or a message from the TL in the test chat will reveal what levels are requested by the customer: A, A+AA, or A+AA+AAA.

Only checkpoints from requested levels should be tested by you; Checkpoints from levels above the requested level(s) are out of scope.

Please get familiar with the official WCAG 2.1 checkpoints from W3C and use them as a reference while testing for accessibility issues.

If you are just getting started with accessibility testing, you might feel that even our own checkpoint list is too complex in the beginning. In this case, we recommend reviewing Easy Checks provided by W3C, which are based on the official WCAG checkpoints. Note that these easy checks do not cover all checkpoints.

Testing Approach

If you are new to accessibility testing, make sure to install and configure corresponding accessibility tools and to get familiar with them before starting to test.

Use these tools to apply our recommended testing workflow:

  1. Navigate through the whole page with keyboard only.

  2. Navigate through the whole page using a screen reader.

  3. Navigate through the whole page using screen reader shortcut keys for heading, landmark, lists, and so on.

  4. Check the color contrast via contrast checker tools.

  5. Scan the website's HTML code with automated tools, which are especially helpful when you are new to the matter.

References:

  1. Introduction to Web Accessibility by W3C

  2. Web Content Accessibility Guidelines (WCAG) 2.0

  3. WCAG 2.1 checkpoints by W3C – reference to requirements and techniques

  4. Easy Checks by W3C

Did this answer your question?