Introduction to Accessibility Auditing

In this tutorial, you will learn about Introduction to Accessibility Auditing. We cover key concepts, practical examples, and best practices to help you master this topic.

Accessibility auditing is the systematic evaluation of a website against WCAG success criteria using a defined methodology that combines automated scanning, manual inspection, assistive technology validation, and expert review to produce actionable remediation plans.

What You'll Learn

You will understand the difference between auditing and testing, the phases of an accessibility audit, the roles involved, and how audits drive continuous Compliance.

Why It Matters

Testing catches individual issues. Auditing evaluates compliance systematically. An audit answers the question: does this site meet WCAG AA overall? It provides the evidence needed for legal defense, VPAT creation, and stakeholder reporting.

Real-World Use

A government agency needs WCAG AA compliance documentation before launching a public portal. An accessibility audit produces a detailed report with 47 findings, a prioritized remediation plan, and a VPAT that confirms the portal meets requirements.

Audit Phases

flowchart LR
  A[Phase 1: Scope] --> B[Phase 2: Automated Scan]
  B --> C[Phase 3: Manual Review]
  C --> D[Phase 4: Screen Reader Test]
  D --> E[Phase 5: WCAG Evaluation]
  E --> F[Phase 6: Report]
  F --> G[Phase 7: Remediation]
  G --> H[Phase 8: Re-audit]

Auditing vs Testing

Testing finds bugs. Auditing evaluates compliance. Think of testing like spell-checking a document -- it finds errors. Auditing is like having an editor review the document for structure, clarity, and adherence to style guidelines.

<!-- Testing would catch: missing alt attribute -->
<img src="chart.png">

<!-- Auditing would evaluate: is this alt text meaningful? -->
<img src="chart.png" alt="Bar chart showing Q4 sales growth of 15 percent">

/* Testing catches: contrast ratio failure */
.light-gray { color: #999; }

/* Auditing evaluates: does the color scheme meet AA consistently? */
:root {
  --text: #333; /* Auditing verifies all usages */
}

// Testing script for individual issues
test('button has accessible name', () => {
  expect(button).toHaveAccessibleName();
});

// Audit methodology includes evaluation checklists
const auditChecklist = [
  { criterion: '1.1.1', check: 'All images have alt text' },
  { criterion: '1.4.3', check: 'Text contrast >= 4.5:1' },
  { criterion: '2.1.1', check: 'All functions available by keyboard' }
];

Common Mistakes

• Confusing auditing with automated testing
• Not defining the audit scope before starting
• Skipping the manual review phase
• Using outdated WCAG versions for evaluation
• Not documenting the methodology for reproducibility
• Failing to prioritize findings by severity and effort
• Not planning for re-audit after remediation

Practice and Challenge

Practice 1: List the differences between testing and auditing. Practice 2: Define the scope for auditing a blog website. Practice 3: Create an audit timeline with phases and estimated time. Practice 4: Identify which WCAG criteria require manual evaluation. Practice 5: Write an audit scope statement for a banking application.

Challenge: Create a complete audit plan for a university website. Include scope definition, methodology selection, timeline, team roles, and deliverable templates. The site has 500 pages across 10 subdomains.

FAQ

Mini Project

Create an audit brief for a SaaS dashboard application. Define the scope (what pages, what WCAG level, what assistive technologies), the methodology, the team, and the timeline. Present the brief as if proposing the audit to a client.

What's Next

Audit Types covers quick, full, and expert audit approaches.