How to re-test
Anyone can repeat these checks. You do not need to write code or run scripts.
1. Free tools (10 minutes per page)
- Lighthouse (built into Chrome and Edge): open DevTools, choose Lighthouse, tick Accessibility, run. Treat anything under 100 as a prompt to look, not a verdict.
- axe DevTools (free browser extension from Deque) or Accessibility Insights for Web (free, from Microsoft): run "FastPass" or "Automated checks" on each page and application screen. Use the guided "Assessment" in Accessibility Insights for the full WCAG 2.2 AA walk-through.
- WAVE (free extension from WebAIM): shows landmarks, headings, labels and contrast on the page.
- Contrast: the browser DevTools color picker shows contrast ratios for any text.
2. Keyboard script (no tools)
- Reload the page. Press Tab once: the first stop should be "Skip to main content". Press Enter: focus moves to the main content.
- Keep pressing Tab. Every control should show a clear outline and you should always be able to see which one is focused, including when a cookie banner is at the bottom.
- Press Shift+Tab to go back. Open a dialog (for example, add a project from the calendar), check that focus is inside it, press Escape, and check focus returns to where you were.
- In the app, reorder tabs with Alt + arrow keys, move a card with Alt + arrow keys, and open the calendar item with Enter.
3. Zoom, reflow and spacing
- Set the browser window to 1280 pixels wide and zoom to 400%. The page should become a single column with no sideways scrolling (data tables may scroll inside their own box).
- Set text size to 200% in browser settings. Nothing should be cut off.
- Install the free "Text Spacing Editor" or "Web Developer" extension and apply the WCAG text spacing values. Nothing should overlap or be clipped.
- Turn on Windows High Contrast (Contrast themes) or the macOS "Increase contrast" setting and check that buttons, fields and focus outlines remain visible.
- Turn on "Reduce motion" in the operating system and reload: decorative animation should stop.
4. Screen-reader scripts (to complete the audit)
Run each flow with NVDA + Firefox and NVDA + Chrome (Windows, free), JAWS + Chrome, VoiceOver + Safari (macOS and iOS) and TalkBack + Chrome (Android). Record: could you complete the task, was every control named, and was every state and message announced?
| # | Flow | What to listen for |
|---|---|---|
| 1 | Home page: skip link, headings list, pricing switch, "idea matures" demo | Landmarks announced; switch says on or off; stage changes announced in the status line. |
| 2 | Request access form: submit empty, then with a bad email, then a good one | Error is announced immediately and focus lands on the field. |
| 3 | Cookie banner: accept, then reopen with Cookie settings | Dialog is announced; focus moves into it; closing returns focus. |
| 4 | App sign-in with a password manager, then with an emailed link | Fields named; error text announced. |
| 5 | Calendar: move through days, open an item, add a project from a day | Grid, row, column header and cell names make sense; item count is read for each day. |
| 6 | Project dialog: edit fields, add a subtask, write a comment and tag someone with @ | Suggestions announced, selection confirmed, comment saved announcement. |
| 7 | Board and Ideas: change a status without dragging; move an idea along its line | Equivalent controls found without dragging. |
| 8 | Settings: Profile, Notifications, Display (tab order), Roles table, Data and backup, Plan and account | Table headers read; Move up / Move down buttons name the item; confirmations announced. |
| 9 | Delete an item, then delete account | Confirmation dialog announced; result announced. |
| 10 | Leave the app idle for 28 minutes | Warning dialog announced; Stay signed in works. |
| 11 | Download a PDF and a Word policy document | Headings navigable; tables read with headers. |
5. Voice control
With Dragon (Windows) or Voice Control (macOS and iOS), say "click" plus the visible label of each button on the sign-in page, calendar and settings. Each visible label should work as spoken (WCAG 2.5.3 Label in Name).
6. After testing
- Record any failure in the remediation log with its criterion.
- Update the status of the matching criterion in the ACR and the known limitations in the accessibility statement.
- Repeat the keyboard, zoom and automated checks before every release.
7. Suggested schedule
Automated and keyboard checks before every release; the full guided assessment each quarter and after any redesign; an independent audit at least once a year, and before signing any contract that requires a VPAT or an ACR to be verified.