Manual Accessibility Testing — Complete Guide

In this tutorial, you will learn about Manual Accessibility Testingity" >}} Testing. We cover key concepts, practical examples, and best practices to help you master this topic.

Manual accessibility testing involves a human evaluator using keyboard-only navigation, screen readers, zoom tools, and structured checklists to verify WCAG success criteria that automated tools cannot check, such as meaningful alt text and logical focus order.

What You'll Learn

You will understand the manual testing Process, create structured testing checklists, perform keyboard and screen reader tests, document findings, and distinguish issues only humans can catch.

Why It Matters

Automated tools catch only 30 percent of accessibility issues. The remaining 70 percent -- meaningful alt text, logical reading order, keyboard trap detection, screen reader announcement quality -- require human judgment.

Real-World Use

An auditor tests a checkout flow manually. Automated tools pass, but the auditor discovers: the focus order skips from email to country before ZIP code, the error summary is not announced by the screen reader, and the confirm button has insufficient contrast in its hover state.

Manual Testing Process

flowchart TD
  A[Prepare Checklist] --> B[Automated Pre-scan]
  B --> C[Keyboard-only Test]
  C --> D[Screen Reader Test]
  D --> E[Zoom Test]
  E --> F[Content Review]
  F --> G[Document Findings]
  G --> H[Verify Fixes]

Manual Testing Checklist

A structured checklist ensures consistency across test sessions. Each item references a specific WCAG criterion.

<!-- Manual test: Is the alt text meaningful? -->
<img src="chart-q4-2025.png" alt="Bar chart showing Q4 2025 revenue of 2.4 million dollars, a 15 percent increase from Q3">

<!-- A tester reads the alt text and decides if it conveys the same information as the image -->

/* Manual test: Does focus indicator have sufficient contrast? */
*:focus-visible {
  outline: 3px solid #0066cc;
  outline-offset: 2px;
  /* Manual check: visible against all background colors */
}

// Manual test helper: log focus events
document.addEventListener('focusin', (e) => {
  console.log('Focused element:', e.target.tagName, e.target.id || 'no id');
  console.log('Role:', e.target.getAttribute('role'));
});

// Tester uses this to verify focus order matches visual order

Common Mistakes

• Not using a structured checklist
• Testing only one scenario or user flow
• Assuming keyboard testing replaces screen reader testing
• Not testing in multiple browsers
• Forgetting to test error states and edge cases
• Documenting issues without enough detail to reproduce
• Testing only happy paths without error scenarios

Practice and Challenge

Practice 1: Create a manual testing checklist for a login form. Practice 2: Test a page with keyboard only and document three issues. Practice 3: Test the same page with a screen reader and find different issues. Practice 4: Zoom a page to 200 percent and check for content loss. Practice 5: Compare manual findings with automated tool results for the same page.

Challenge: Write a manual testing script for a multi-step checkout flow. Include keyboard tests, screen reader tests, zoom tests, and error state tests for each step. Execute the script and produce a findings report.

FAQ

Mini Project

Design a manual testing protocol for a dashboard application. Include sections for keyboard, screen reader, zoom, color contrast, and content review. Define pass/fail criteria for each test item. Use this protocol to test a real dashboard and produce a report.

What's Next

Keyboard Testing covers keyboard-specific accessibility testing in depth.