VPATFast.com

Home / Guides / How to test accessibility

Guide · Updated November 21, 2026

How to test accessibility

Testing for an ACR: choosing the scope, keyboard and screen reader tests, 200% zoom and 320-pixel reflow, contrast checks, and what automated tools can and cannot do.

Every conclusion in an ACR should come from testing, not guesswork. This guide describes a testing method a small team can complete: set the scope first, cover most WCAG criteria with keyboard, screen reader, zoom and contrast checks, then use automated tools to catch what you missed.

Step 1: Set the scope

You do not need to test every page, but you do need to cover the paths users actually take:

  • Complete processes: sign-up, sign-in, password reset, one full run of each core feature, settings and payment. WCAG requires every page in a process to conform, so testing only one page of it does not count.
  • Representative pages: one page of each template, such as a list page, a detail page, a form page and a dashboard.
  • Shared components: navigation, dialogs, dropdown menus, date pickers, tables and notifications. A problem in one of these affects every page that uses it.

Write the scope into the product description and the evaluation methods at the top of the ACR.

Step 2: Use only the keyboard

Unplug the mouse and go through every workflow with Tab, Shift+Tab, Enter, Space and the arrow keys. This step finds more issues than any other. Check that every function works from the keyboard, focus is always visible, the focus order makes sense, and focus never gets trapped inside a component.

Step 3: Screen readers

Test with at least one combination, and two if you can:

  • NVDA (Windows, free) + Firefox or Chrome
  • JAWS (Windows, commercial) + Chrome
  • VoiceOver (built into macOS and iOS) + Safari
  • TalkBack (built into Android) + Chrome, for mobile

Listen for these: whether images and icon buttons have names, form fields have labels, error messages are announced, focus lands in the right place when a dialog opens, and the page title and heading structure are clear.

Step 4: Zoom and reflow

  • Zoom to 200% (1.4.4): at 200% browser zoom, no text or functionality may be lost.
  • Reflow (1.4.10): set the window width to 320 CSS pixels (the same as a 1280-pixel-wide screen at 400% zoom). Content should read with vertical scrolling only, without scrolling sideways at the same time. Content that needs a two-dimensional layout, such as data tables and maps, is an exception.
  • Text spacing (1.4.12): after increasing line height, paragraph spacing, letter spacing and word spacing, text must not be cut off or overlap.

Step 5: Color and contrast

  • Text contrast (1.4.3): at least 4.5:1 for normal text and 3:1 for large text. Placeholder text and light grey text (other than disabled controls, which are exempt) are common problems.
  • Non-text contrast (1.4.11): user interface elements such as input borders, icons and focus indicators need at least 3:1.
  • Not color alone (1.4.1): for example, a form error shown only by a red border, with no text or icon, does not meet this criterion.

Step 6: Automated tools

Tools such as axe DevTools, Lighthouse and WAVE quickly find missing text alternatives, missing form labels, insufficient contrast and similar issues, and they are worth running continuously in your development process. But they find only some issues. Whether the focus order makes sense, whether a text alternative is accurate, and whether a process can be completed all need human judgment. Do not fill out an ACR based on an automated score alone.

Step 7: Record the results

For each issue, write down the page or component, the WCAG criterion, what happens, who it affects and any workaround. These notes turn directly into ACR remarks; see how to write ACR remarks. Also record the test date, the product version, and the browser and assistive technology versions, and put them in the evaluation methods section of the ACR.

Next step

When testing is done, open the generator and set a conformance level for each of the nine areas based on your results. It produces an ACR draft and an accessibility statement; then add your test notes to the remarks in the .docx.

Ready to draft your ACR?

The preview is free. US$49 one-time per product to download the ACR and the statement.

Open the generator