Web accessibility testing is a subset of usability testing where the users under consideration have disabilities that affect how they use the web. Disabilities encompass a wide range of physical problems, including learning disabilities as well as difficulties with sight, hearing and movement. Assistive technology is available to enable users with disabilities to read the web. This includes but is not limited to:
- Screen reader software
- Screen magnification software
- Speech recognition software
- Special keyboard
There are about 20% of the population that has disability issues. 1 in 10 people have a severe disability; 1 in 2 people over 65 have reduced capabilities. Government agencies all over the world have come out with legalizations, which requires IT products to be accessible by disabled people. Web Accessibility Initiative published Web Content Accessibility Guidelines WCAG 2.0 as a recommendation aiming to ensure websites are accessible, usable, interoperable and optimized on websites. The WCAG 2.0 have been widely accepted as the definitive guidelines on how to create accessible websites.
Appnovation uses both industry best practices and coding best practices throughout the project development process. To ensure that the site conforms to WCAG 2.0 standards, it is essential to include accessibility in the design phase. This will help to avoid any adverse impact on the visual design and avoid any confusion for implementation. Drupal 7 Core is conformant with WCAG 2.0 guidelines, this meant that HTML markup generated from these core modules are compliant. Appnovation QA usually conduct accessibility testing to ensure any markup generated from custom Drupal modules were also compliant as well as any admin user generated content.
Who and How
Appnovation QA breakdown the accessibility testing as follows:
Utilize QA tools that can scan and evaluate compliance of the site as delivered.
Execute the content publishing workflow and ensure applicable fields and descriptions will generate compliant content. Run the evaluation tool to ensure coverage.
Evaluate the integrity of imported and migrated data to establish that the content has the required accompanying accessibility data set or identify the missing accessibility data set. Run the evaluation tool to ensure coverage.
Manual testing that follows the checklist of rules as it applies to accessibility tools and devices and observe the expected user experience.
Prelimary accessibility testing can be run on any environment throughout the development cycle. For accurate accessibility results, it's best to run accessibility testing with final content to ensure all the assistive technology is setup correctly on the website.