Step 2: Select tools and get set up for testing

This page is part of a complete process to start testing the accessibility of websites and browser-based applications.

Steps to follow are:

  1. Create a test plan
  2. Select tools and get set up for testing (this page)
  3. Complete the accessibility test
  4. Document findings and assess issues

Automated testing tools can quickly identify and help fix a range of technical issues, while manual testing is essential for ensuring real-world usability for people with disabilities. Automated testing tools are limited in their capabilities and can typically only detect about a third of accessibility issues. They struggle to assess more complex or subjective aspects, such as meaningful navigation order, contextually accurate alternative text, or proper use of ARIA attributes. Many of the issues they flag also require manual review to confirm their validity or effectiveness. This makes manual testing required to ensure content is functionally and contextually accessible to all users.

The W3C provides a comprehensive list of web accessibility evaluation tools to help you choose the tools that are best for your accessibility testing.

Download, install and configure the tools and features to prepare for testing

Browser-based automated testing tools

Automated testing tools to use include:

Test Windows applications

The Accessibility Insights for Windows desktop tool can be used to test Windows applications.

Screen reader testing

Test with a screen reader to simulate your users' real-world experience. You will pick up issues that are outside the scope of automated tools.

Resources:

Accessibility features on a Mac or PC

Both Macs and PCs have built-in accessibility features.

For example:

Check your device’s system settings and your browser settings to turn on accessibility features and start using them.

Mobile and tablet testing tools

Mobiles and tablets have built-in accessibility features that help users navigate websites and web applications on their devices.

Turn on iOS (iPhone/iPad) accessibility features for manual testing

Watch the video Assistive Tech: VoiceOver on iOS for a demonstration on how to turn on VoiceOver or follow the instructions below.

  1. Enable the Accessibility shortcut for VoiceOver. Go to Settings > Accessibility > Accessibility Shortcut > Enable only VoiceOver.
  2. Turn on VoiceOver. Go to Settings > Accessibility > VoiceOver and toggle it on.
  3. To enable and disable VoiceOver, triple press the sleep/wake or home button.
  4. Turn on Zoom. Go to Settings > Accessibility > Zoom and toggle it on.
  5. Enable colour filters. Go to Settings > Accessibility > Display and Text Size > Colour Filters.
  6. If you have a switch, set up Switch Control. Go to Settings > Accessibility > Switch Control and follow the setup instructions.
  7. Turn on VoiceOver captions to check that voice access, keyboard access, and braille will work correctly.

Resources: VoiceOver getting started guide - Apple

Turn on Android accessibility features for manual testing

Watch the video Assistive Tech: TalkBack to learn how to turn on TalkBack on an android device or follow the instructions below.

  1. Enable the accessibility shortcut for TalkBack. Go to Settings > Accessibility > TalkBack > TalkBack shortcut.
  2. To enable and disable TalkBack, hold both the volume keys for 3 seconds.
  3. Enable Magnification. Go to Settings > Accessibility > Magnification and turn it on.
  4. Adjust Colour Inversion/Correction. Go to Settings > Accessibility > Visibility enhancements > Colour Inversion or Colour Correction.
  5. Set up the Accessibility Menu. Go to Settings > Accessibility > Accessibility Menu and toggle it on.
  6. Turn on TalkBack captions to check that the voice access, keyboard access, and braille will work correctly. Go to Settings > Accessibility > TalkBack > Settings > Advanced Settings > Developer Settings > Display speech output.

Android accessibility tools

Android Accessibility Suite adds further accessibility features to your Android device to help you use it without vision or with a switch device.

Google’s Accessibility Scanner scans the interface of apps on your device and can provide advice on improving their accessibility. Watch the video to learn how to use this testing tool.

Resources:

Tools for testing documents

Content should be published in HTML rather than documents, unless there is a clear user need demonstrated with customer research. Documents that are published must:

  • be tested and meet accessibility requirements (WCAG and PDF/UA).
  • include a summary of the document in HTML.

Use tool-specific built-in accessibility assessment tools for different document types to apply and test their accessibility. Find information about:

To create an accessible PDF, make the source document (e.g. Word or InDesign) accessible first, then correctly export this to PDF. The PDF will then need to be tested including tested with a screen reader, and any accessibility issues fixed before the document can be published.

Next step

Complete the accessibility test