A reliable accessibility review combines automated scans with hands-on checks. This web accessibility testing checklist gives developers and QA teams a repeatable way to test keyboard access, focus, structure, forms, images, contrast, motion, and screen-reader behavior before release—and to record what changes over time.
Overview
Accessibility testing asks whether people with different abilities can perceive, operate, understand, and interact with a website. It is not a single tool or a final-stage approval step. A page can pass an automated scan and still be difficult to use with a keyboard, screen reader, browser zoom, or reduced-motion settings.
Use this process at three levels:
- Automated testing: Scan rendered pages and components for detectable issues such as missing labels, invalid relationships, some contrast failures, and structural problems.
- Manual testing: Operate the page with a keyboard, inspect focus, review headings and landmarks, test zoom and contrast, and verify error recovery.
- Assistive-technology testing: Use a screen reader and, where practical, more than one browser and operating system combination to check how the interface is announced and operated.
Automated results are signals, not a complete accessibility verdict. Record the page, component or route, browser and assistive technology used, issue description, relevant WCAG reference, severity, owner, and retest status. WCAG references should be checked against the version your organization has selected; common examples include WCAG 2.2 success criteria such as 1.3.1 for structure, 1.4.3 for contrast, 2.1.1 for keyboard operation, 2.4.7 for focus visibility, and 3.3.1 for identifying input errors.
What to track
1. Keyboard navigation and focus
Unplug the mouse or avoid touching it and move through the page with Tab, Shift+Tab, arrow keys, Enter, and Escape where appropriate. Check that:
- Every interactive control is reachable in a logical order.
- Focus is always visible and not hidden behind a sticky header, dialog, or cookie banner.
- Menus, accordions, tabs, carousels, dialogs, and custom widgets have predictable keyboard behavior.
- A modal dialog moves focus inside when it opens, provides a clear close method, and returns focus sensibly when it closes.
- Keyboard users can reach and operate content without a keyboard trap.
Do not remove the browser’s focus outline without providing an equally clear replacement. Test focus at normal zoom and on smaller screens, where overlays and fixed elements are more likely to obscure it.
2. Headings, landmarks, and reading order
Review the page as a document before inspecting its visual design. Confirm that it has one clear page topic, headings that describe the sections below them, and no skipped level that makes the outline confusing. Check landmark regions such as header, nav, main, and footer. Use native HTML elements before adding ARIA; incorrect ARIA can create a misleading experience.
Resize the viewport or inspect the DOM and visual order to make sure content is announced in a sensible sequence. A layout that looks correct visually may still present controls or instructions in the wrong order to keyboard and screen-reader users.
3. Forms, instructions, and errors
Complete every important form using only the keyboard. Each field should have a persistent, programmatically associated label. Instructions, required-state information, input formats, and grouped controls should be available at the point of interaction. Test both valid and invalid submissions.
- Can users identify which field needs attention?
- Does the error explain what went wrong and how to fix it?
- Is the error connected to the relevant input?
- Is focus moved or directed in a way that does not disorient the user?
- Are success messages and dynamically displayed errors announced when necessary?
4. Images, audio, and other media
Classify every image as informative, decorative, functional, or complex. Informative images need concise alternative text that conveys their purpose. Decorative images should be ignored by assistive technology. An image used as a link or button needs alternative text that describes the action, not merely the file type.
Check that videos have captions and that important visual or audio information is available in another form when needed. Do not use color alone to communicate status, selection, errors, or required information.
5. Contrast, zoom, and motion
Use a contrast checker as an early filter, then inspect real states: hover, focus, disabled, error, visited, selected, and placeholder text. Test text and meaningful interface graphics against the applicable contrast requirements for your chosen WCAG target. Also test at increased browser zoom and with text enlarged. Content should remain readable and usable without unexpected overlap or loss of controls.
Enable the operating system or browser preference for reduced motion. Confirm that animations, parallax effects, auto-advancing content, and transitions are reduced or removed when the preference is honored. Motion should never be the only way to understand a change.
Common issues and suitable checks
| Issue | Testing method | Relevant WCAG area |
|---|---|---|
| Unreachable custom control | Keyboard walkthrough and DOM review | 2.1.1 Keyboard |
| Hidden or weak focus indicator | Keyboard test at desktop and mobile widths | 2.4.7 Focus Visible; check the applicable current criterion |
| Incorrect heading or landmark structure | Accessibility tree, outline, and screen reader landmarks | 1.3.1 Info and Relationships |
| Unlabeled input or unclear error | Keyboard form test and screen-reader announcement | 3.3.1 Error Identification; 3.3.2 Labels or Instructions |
| Insufficient text contrast | Contrast checker plus visual state review | 1.4.3 Contrast (Minimum) |
| Missing or unhelpful alternative text | Image inventory and screen-reader test | 1.1.1 Non-text Content |
| Motion ignores user preference | Enable reduced-motion setting and repeat key flows | 2.3.3 Animation from Interactions |
6. Screen-reader checks
Choose a representative browser and screen reader combination supported by your team, then test the highest-value flows: landing on the page, navigating headings and landmarks, opening menus or dialogs, completing a form, reading an error, and completing the primary task. Listen for duplicate announcements, missing names, incorrect roles, unexplained state changes, and content that is present visually but absent from the accessibility tree.
Screen readers differ in commands and behavior, so record the exact browser, operating system, screen reader, and version used. A focused test is more useful than claiming that every possible combination was covered.
Cadence and checkpoints
Make accessibility testing part of the development workflow rather than a quarterly surprise. Use this cadence:
- For every component: Test semantic markup, keyboard behavior, focus, labels, states, and contrast before the component enters the shared library.
- For every pull request: Run automated checks on changed routes and manually test the affected interaction, especially dialogs, forms, navigation, and dynamic content.
- Before release: Test the critical user journeys on the production-like build, including authentication, search, checkout or submission flows, error recovery, and responsive layouts.
- Monthly or quarterly: Sample important pages, review unresolved issues, rerun scans, and check whether browser, framework, component-library, or assistive-technology changes introduced regressions.
- After a redesign or dependency update: Repeat structural, keyboard, form, contrast, and screen-reader checks even if the visible change appears minor.
Automated tools are useful developer tools for repeatable regression checks, but configure them deliberately. Review false positives, test authenticated and dynamic states, and avoid treating a clean report as proof that the page is fully accessible. Keep a small regression suite of screenshots, keyboard paths, and screen-reader task notes for high-risk components.
How to interpret changes
Separate new defects from newly detected defects. A scan may report more issues because a tool was updated, a route became reachable, or a previously untested state was added. Compare results by page, component, user journey, and issue type—not only by the total count.
Prioritize problems that block a core task, prevent keyboard operation, hide essential information, create an unusable form error, or affect repeated shared components. Fix the underlying component when several pages show the same problem. Then retest the original failure and at least one related state, such as mobile layout, validation failure, or dialog closure.
For each finding, keep a short record:
- URL, component, or user journey
- Observed behavior and expected behavior
- Steps to reproduce
- Browser, operating system, and assistive technology
- Relevant WCAG criterion or internal requirement
- Owner, priority, fix date, and retest result
Use an accessibility issue tracker alongside existing QA workflows. For broader release processes, a clear reusable testing workflow can help teams standardize evidence and regression checks across different technical surfaces.
When to revisit
Revisit this checklist before every significant release and whenever a page, design system component, frontend framework, browser-support policy, or assistive-technology workflow changes. Schedule a monthly or quarterly review for high-traffic pages and critical journeys. Refresh the WCAG references, automated-tool capabilities, browser instructions, and internal acceptance criteria at least every six months or when accessibility standards are updated.
Use this release checklist as the final practical pass:
- Run automated scans on representative rendered pages and review, rather than blindly accepting, every result.
- Complete the primary journeys with a keyboard only.
- Confirm visible focus, logical order, usable dialogs, menus, tabs, and dynamic updates.
- Review headings, landmarks, reading order, labels, instructions, and error recovery.
- Check alternative text, captions, color contrast, zoom, responsive layouts, and reduced motion.
- Test the critical flows with a chosen screen reader and record the environment.
- Log defects with reproduction steps, ownership, priority, and WCAG references.
- Retest fixes in the original state and in one related regression state.
- Schedule the next review and note which browsers, tools, and assistive technologies should be reassessed.
Keep the checklist close to the code review or release process so accessibility remains a recurring quality practice. For additional developer workflow ideas, the developer tools workflow guide can help organize repeatable checks without replacing hands-on accessibility testing.