Accessibility (WCAG) Testing Checklist
A practical, interactive checklist for auditing an application against WCAG's four core principles — Perceivable, Operable, Understandable, Robust (POUR) — covering both what an automated scanner catches and the manual passes it doesn't.
Use this tool to track your accessibility audits; progress is saved automatically in your browser's local storage.
👁️1. Perceivable — Text Alternatives & Structure
0/3
Every meaningful image has descriptive alt text; decorative images have empty alt.Example: A product photo gets `alt="Red leather wallet, front view"`; a purely decorative divider icon gets `alt=""`.
Headings follow a logical, non-skipping order (h1 → h2 → h3), not chosen for visual size.Example: A page doesn't jump from an `<h2>` section title straight to an `<h4>` subsection just because the `<h4>` looked the right font size.
Color is never the only way information is conveyed.Example: A failed form field is marked with both a red border AND an error icon/text — not red border alone, for users with color-blindness.
⌨️2. Operable — Keyboard & Focus
0/4
Every interactive element is reachable and operable using only Tab / Shift+Tab / Enter / Space.Example: A custom dropdown built from `<div>`s can be opened, navigated, and selected with no mouse at all.
A visible focus indicator is present on every focusable element — never removed with `outline: none` without a replacement.Example: Tabbing through a nav bar shows a clear outline/highlight on whichever link currently has focus.
Keyboard focus never gets trapped where Tab can't escape, except inside an intentional modal.Example: Tabbing through a dropdown menu can always reach the next page element — a genuinely open modal dialog is the one deliberate, documented exception.
A "skip to main content" link is the first focusable element on the page.Example: Pressing Tab once on page load reveals a "Skip to main content" link before the nav bar, so keyboard users don't re-tab through the header on every page.
📝3. Understandable — Forms & Errors
0/3
Every form input has a programmatically associated `<label>`, not just placeholder text.Example: An email field uses `<label for="email">Email</label>`, not just `placeholder="Email"` that disappears once typing starts.
Validation errors are announced to assistive tech and clearly associated with their field.Example: A screen reader announces "Email: invalid format" via `aria-describedby`, not just a red asterisk only a sighted user would notice.
Navigation and identification patterns stay consistent across pages.Example: The main nav bar's items appear in the same order and location on every page of the flow.
🏗️4. Robust — Semantics & ARIA
0/3
Native semantic HTML elements are used before reaching for ARIA (`<button>`, not `<div role="button">`).Example: A clickable action is a real `<button>`, which gets keyboard support, focus, and role for free — not a styled `<div onClick>`.
ARIA attributes used are valid, and roles don't contradict the native semantics.Example: A checkbox styled with CSS still exposes `role="checkbox"` and `aria-checked` reflecting its true state — not left announcing as a generic button.
Dynamic content updates (toasts, live status) are announced via an ARIA live region.Example: A "Payment submitted successfully" toast is wrapped in `aria-live="polite"` so screen-reader users hear it without needing to notice a visual popup.
🔍5. Automated & Manual Testing Process
0/4
An automated accessibility scanner (axe-core, Lighthouse, etc.) runs in CI on every build.Example: `@axe-core/playwright` runs against every page in the E2E suite, failing the build on any new serious/critical violation.
A manual keyboard-only pass is done on every new interactive feature, not just the automated scan.Example: Automated scanners catch roughly 30-40% of WCAG issues — logical tab order and true operability still need a human keyboard walkthrough.
Critical user flows are spot-checked with a real screen reader at least once per release.Example: The checkout flow is walked through with VoiceOver (Mac) or NVDA (Windows) before a major release, not just assumed to work because the automated scan passed.
Text and UI-component color contrast meets WCAG AA minimums (4.5:1 normal text, 3:1 large text/UI components).Example: Light-gray placeholder text on a white background is checked against the 4.5:1 ratio, not just "looks readable to me."
WCAG POUR Principles → Testing Map
Automated Scans Are a Floor, Not a Ceiling
Automated tools like axe-core catch real, valuable issues — but industry estimates consistently put automated coverage around 30-40% of WCAG's actual success criteria. Logical tab order, whether an error is genuinely announced at the right moment, and whether a screen reader user can actually complete a task all require a human pass. Treat the automated scan as the fast, CI-gated floor — not the whole audit.