Manual Review Process — Complete Guide

In this tutorial, you will learn about Manual Review Process. We cover key concepts, practical examples, and best practices to help you master this topic.

The manual review process in an Accessibility audit involves a trained evaluator systematically testing each page against WCAG criteria using keyboard navigation, screen readers, visual inspection, and content analysis to find issues automated tools cannot.

What You'll Learn

You will perform structured manual reviews, use evaluation checklists, document findings with evidence, and distinguish between pass, fail, and needs-review outcomes for each WCAG criterion.

Why It Matters

Manual review catches the 70 percent of accessibility issues that automated tools miss. It is the most important phase of an audit because it evaluates meaning, context, and user experience rather than just technical Compliance.

Real-World Use

An auditor manually reviews a product listing page. Automated scans passed, but manual review reveals: the sort dropdown changes focus unexpectedly, the price text uses color alone to indicate discounts, and the add-to-cart button text disappears when zoomed to 200 percent.

Manual Review Flow

flowchart TD
  A[Start Page] --> B[Keyboard Test]
  B --> C[Screen Reader Test]
  C --> D[Visual Inspection]
  D --> E[Content Review]
  E --> F[WCAG Evaluation]
  F --> G{All Criteria Checked?}
  G -->|No| B
  G -->|Yes| H[Document Findings]

Manual Review Checklist

Create a criterion-by-criterion checklist. For each criterion, define the test procedure and pass/fail criteria.

<!-- Manual review: heading structure -->
<!-- Auditor verifies heading levels are semantic and not skipped -->
<h1>Page Title</h1>
<h2>Section 1</h2>
<h3>Sub-section 1.1</h3>
<h2>Section 2</h2>
<!-- PASS: no skipped levels -->

/* Manual review: focus indicator visibility */
/* Auditor tabs through all elements and checks focus visibility */
*:focus-visible {
  outline: 2px solid #4A90D9;
  outline-offset: 2px;
  /* PASS if visible against all backgrounds */
}

/* Manual review: text spacing override test */
/* Auditor applies text-spacing bookmarklet and checks content */
.test-element {
  line-height: 1.5;
  letter-spacing: 0.12em;
  word-spacing: 0.16em;
}

// Manual review helper: check focus trapping
document.addEventListener('focusin', function(e) {
  console.log('Focus moved to:', e.target);
  // Auditor confirms focus moves in logical order
});

// Manual review: check error announcements
function showError(message) {
  var errorEl = document.getElementById('error');
  errorEl.textContent = message;
  errorEl.setAttribute('role', 'alert');
  // Auditor verifies screen reader announces this
}

Common Mistakes

• Rushing through manual review to save time
• Not using a structured checklist for each criterion
• Testing only the default page state
• Ignoring error states and edge cases
• Not documenting the specific evidence for each finding
• Forgetting to test in multiple browsers
• Confusing personal preference with WCAG violations

Practice and Challenge

Practice 1: Create a manual review checklist for criterion 1.4.3 (Contrast). Practice 2: Perform a keyboard review of a page and document findings. Practice 3: Review heading structure on a long article page. Practice 4: Test form error states with a screen reader. Practice 5: Document three findings from a visual inspection.

Challenge: Perform a complete manual review of a single web page against all WCAG AA criteria. Create a spreadsheet with columns for criterion ID, test procedure, pass/fail, evidence, and notes. Document at least 10 findings with specific evidence.

FAQ

Mini Project

Design a manual review template for a product detail page. Include: checklist items for each POUR principle, test procedures for each AA criterion, a finding documentation format with evidence fields, and a severity rating guide. Test the template on a real product page.

What's Next

Issue Documentation covers documenting and tracking audit findings.