Manual Accessibility Testing Checklist
Step-by-step verification of what automated scanners can't see (WCAG 2.2 AA).
This manual accessibility checklist is designed for web developers, QA engineers, digital product teams, and accessibility specialists seeking to eliminate barriers that automated scanning tools cannot detect. While automated checkers evaluate code patterns and color contrast, critical human experiences—including keyboard navigation traps, screen reader audio clarity, dynamic focus order, and touch target precision—require systematic manual validation.
Completing this 12-step audit typically takes between 20 and 30 minutes for a standard website. No complex hardware is needed: you can conduct the entire inspection using your everyday keyboard, a built-in screen reader (like VoiceOver or NVDA), and your browser’s native zoom controls.
Tip: Run an automated scan first to fix contrast and HTML landmark issues automatically.
Run Automated ScanStep 2: Focus Visibility
Where are you on the page? Every interactive element must display a clear, high-contrast focus indicator.
Verification Instructions
- 1Tab through the entire page and inspect the focus ring or bounding outline around every control.
- 2The focus indicator must have a minimum contrast ratio of 3:1 against adjacent colors (WCAG 2.2 AA).
- 3Verify that the focus order follows a logical reading sequence (top-to-bottom, left-to-right).
- 4Ensure sticky navigation headers, fixed banners, or floating footers do not obscure focused elements (WCAG 2.4.11).
If you lose track of which element is currently selected or if outlines are suppressed with outline: none, the site fails.
Step 3: 200% Text Resizing
Ensure content and layout remain readable and functional when users enlarge font size for low vision.
Verification Instructions
- 1In your browser settings or via Cmd/Ctrl + Plus, zoom the page viewport to 200%.
- 2Check if all body paragraphs, labels, and table content remain readable without requiring horizontal scrolling.
- 3Ensure buttons, navigation links, and badges don't truncate, overflow container cards, or overlap adjacent text.
- 4Verify that critical interactive functionality remains fully operable at 400% zoom (reflow test).
Text that is cut off, overlaps neighboring elements, or requires awkward horizontal scrolling makes the page fail.
Step 5: Descriptive Links
Link text must clearly describe destination or action when read out of context.
Verification Instructions
- 1Review all links across navigation, cards, and body text without reading surrounding paragraphs.
- 2Ensure link text explains the destination (e.g., "Download Q4 Accessibility Report" rather than just "Download").
- 3Avoid vague phrases like "Click Here", "Learn More", or "Read More" without contextual aria-labels.
- 4Verify that links opening in a new tab announce that behavior to screen readers.
Vague links force assistive technology users to read surrounding content repeatedly to deduce where the link leads.
Step 6: Screen Reader Integrity
Listen to your website. Does the structure make sense when spoken aloud by assistive software?
Verification Instructions
- 1Enable VoiceOver (macOS: Cmd+F5), NVDA (Windows: Ctrl+Alt+N), or Orca (Linux).
- 2Navigate strictly by headings (using the H shortcut) to verify a logical outline (one H1 followed by H2s and H3s).
- 3Check that all informational images have concise, meaningful alt text, and decorative icons have aria-hidden="true".
- 4Confirm that dynamic page changes or toast notifications are announced using aria-live regions.
If headings are skipped (H1 straight to H4), or images announce raw file paths like "img_1234.png", the document structure fails.
Step 7: Form Error Recovery
Forms must clearly identify errors and provide actionable suggestions for correction.
Verification Instructions
- 1Submit a form with empty required fields.
- 2Enter invalid data formats (such as a malformed email or incomplete telephone number) and submit.
- 3Check that error messages clearly describe what went wrong in plain language and how to fix it.
- 4Ensure error text is programmatically linked to the input field using aria-describedby or aria-invalid="true".
Error indicators that rely only on red borders or vague messages like "Invalid Input" without assistive tech association fail.
Step 8: Touch Target Size
Buttons and touch controls must have sufficient dimensions to prevent misclicks on touchscreens.
Verification Instructions
- 1Inspect interactive elements including navigation buttons, search toggles, and pagination links.
- 2Ensure interactive elements measure at least 24×24 CSS pixels (WCAG 2.2 AA) or 44×44 CSS pixels (AAA & mobile best practice).
- 3If targets are smaller than 44px, ensure there is sufficient padding or spacing between adjacent links.
- 4Verify that inline text links in dense paragraphs are not clumped together.
Tiny, cramped links or icons that lead to accidental misclicks fail WCAG 2.2 Target Size Minimum.
Step 9: Display Orientation
Users must be able to view and operate the website in both portrait and landscape screen orientations.
Verification Instructions
- 1Rotate your mobile device or simulate landscape and portrait orientations in browser Developer Tools.
- 2Ensure content does not get cut off, hidden behind sticky toolbars, or force artificial horizontal scrolling.
- 3Check that hamburger menus, modals, and sticky action buttons adapt smoothly in landscape mode.
- 4Verify the website never presents a message forcing users to rotate their device.
Locking screen orientation to portrait only or losing essential navigation controls in landscape mode violates WCAG 1.3.4.
Step 10: Content on Hover or Focus
Tooltips, popovers, and menus appearing on hover or focus must remain dismissible, hoverable, and persistent.
Verification Instructions
- 1Trigger a tooltip, dropdown menu, or preview card by hovering with the mouse or tabbing to the element.
- 2Press the Escape key: the dismissible content must close immediately without moving keyboard or pointer focus.
- 3Move the mouse pointer over the tooltip box itself: it must remain open without disappearing.
- 4Ensure the popover does not obscure underlying essential information or disappear unpredictably.
Tooltips that vanish when hovered directly or cannot be closed without moving the mouse fail WCAG 1.4.13.
Step 11: Motion & Animation
Animations must respect user motion preferences and avoid triggering vestibular disorders or nausea.
Verification Instructions
- 1Enable "Reduce Motion" in your operating system accessibility preferences (macOS: System Settings → Accessibility → Display).
- 2Verify that the website honors the prefers-reduced-motion CSS query by disabling or subduing large animations.
- 3Ensure any auto-advancing carousel, slideshow, or looping background video includes a prominent Pause or Stop button.
- 4Check that no content flashes or strobes more than 3 times in any 1-second period.
Forced high-motion parallax scrolling or unpausable background video carousels violate WCAG Operable guidelines.
Step 12: Audio Control
Audio must never play automatically without an immediate, accessible mechanism to pause or mute it.
Verification Instructions
- 1Load pages containing audio players, background soundtracks, or embedded video streams.
- 2If any audio starts playing automatically for longer than 3 seconds, locate the mute or pause control immediately.
- 3Ensure the audio mute button is placed near the top of the tab order and does not require a mouse to operate.
- 4Verify that the audio control works independently of the operating system's master volume.
Auto-playing background music or video ads that cannot be muted using keyboard shortcuts interfere with screen readers and fail.
Finished your manual audit?
Combine your manual checklist results with an automated scan to generate full compliance documentation.