Skip to content
Tutorials Center
My learning

Topics

Lesson 38 of 38 ยท Projects and Practice

Web Accessibility Audit Checklist

A practical WCAG 2.2 AA audit checklist and practice set: scope, sampling, tests per area, severity ratings, a report template and a final review quiz.

You have learned the principles, the markup, the testing methods and the process. This last lesson turns them into a repeatable audit you can run on any site. It also works as a final review of the track.

Step 1: define the scope

Decide what you audit and to which standard.

  • Standard: WCAG 2.2 level AA (see laws and standards).
  • Sample pages: choose key templates and journeys, not every URL: home, a content page, search and results, a form, checkout or sign-up, a page with media, an error page, and any complex widget.
  • States: logged out and logged in, open menus and dialogs, error states, empty states.
  • Environments: desktop and mobile, at least two browsers, and at least two screen reader pairings.

Step 2: the checklist

Use this grouped list. Each line is a question; a "no" is a finding. Criteria numbers help you cite the issue.

Structure and navigation

  • Page has a unique, descriptive <title> and lang (2.4.2, 3.1.1).
  • One h1, headings in logical order, headings describe sections (1.3.1, 2.4.6).
  • Landmarks used (header, nav, main, footer), labeled when repeated (1.3.1).
  • Skip link to main content (2.4.1).
  • Consistent navigation and consistent help location (3.2.3, 3.2.6).
  • More than one way to find pages (2.4.5).
  • Link text describes purpose (2.4.4).

Keyboard and focus

  • Everything operable by keyboard, no traps (2.1.1, 2.1.2).
  • Focus order logical (2.4.3); focus visible and not hidden by sticky bars (2.4.7, 2.4.11).
  • Dialogs trap and restore focus, Escape closes.
  • Keyboard shortcuts with single characters can be turned off or remapped (2.1.4).
  • Drag actions have a single-pointer alternative (2.5.7); targets at least 24 by 24 px (2.5.8).

Perception

  • Meaningful images have alt text; decorative ones alt="" (1.1.1).
  • Text contrast 4.5:1 (3:1 for large); UI parts and graphics 3:1 (1.4.3, 1.4.11).
  • Color is not the only cue (1.4.1).
  • Text resizes to 200%; reflows at 320 px; spacing overrides OK (1.4.4, 1.4.10, 1.4.12).
  • Orientation not locked (1.3.4).
  • Video has captions; audio has transcript; audio description where needed (1.2.x).
  • No autoplay audio over 3 seconds without control (1.4.2); moving content can be paused (2.2.2); no flashing above three per second (2.3.1).

Forms and interaction

  • Labels, instructions and groups (1.3.1, 3.3.2); input purpose via autocomplete (1.3.5).
  • Errors identified in text with suggestions (3.3.1, 3.3.3); prevention for important actions (3.3.4).
  • No redundant entry; authentication without cognitive tests (3.3.7, 3.3.8).
  • Status messages announced (4.1.3).
  • Time limits adjustable (2.2.1).
  • Content on hover or focus is dismissible, hoverable, persistent (1.4.13).

Robustness

  • Valid, semantic HTML; name, role and value exposed for custom widgets (4.1.2).
  • ARIA used correctly: valid attributes, no conflicts with native semantics.
  • Works with at least two screen reader and browser pairs.

Step 3: rate severity

Severity Meaning Example
Critical Blocks a task entirely for some users Checkout button unreachable by keyboard
Serious Major barrier or workaround is hard Form errors not announced
Moderate Causes difficulty but there is a workaround Poor heading order
Minor Annoyance, low impact Redundant alt text

Combine severity with how many users and pages are affected to prioritize.

Step 4: report template

For each issue, record:

TEXT
ID:            A-014
Page / state:  Checkout > payment step, error state
Criterion:     3.3.1 Error Identification (A)
Severity:      Serious
What happens:  Card number errors appear in red only; screen reader reads nothing.
Steps:         1. Leave card number empty. 2. Press Pay. 3. Listen.
Expected:      Error text linked to the field and announced.
Suggested fix: Add text message, aria-invalid, aria-describedby; focus summary.

Also include an executive summary (counts by severity, top five fixes), the scope and method, tools and versions, and positive findings: teams need to hear what already works.

Practice: a tiny audit tracker

This demo lets you log issues, rate severity and see a summary, like a lightweight version of a real audit sheet.

Audit issue tracker

Practice problems

  1. Pick any site you use. Run the 15-minute manual routine from manual testing and write three findings with criteria.
  2. Run axe on the same page and compare: which of your findings did it miss?
  3. Rewrite three vague links ("Click here", "More", "Read") from a page you know into descriptive ones.
  4. Take a carousel and list every requirement it must meet (pause, keyboard, names, reduced motion).
  5. Write accessibility acceptance criteria for a "Add to cart" button that shows a confirmation.

After the audit

Fix by priority, retest every fixed item, record the date, update your accessibility statement, and schedule the next audit (at least yearly, and after major redesigns). Keep CI checks running between audits.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. Which is the best way to choose pages to audit?

    Sampling templates and journeys covers most components efficiently, including states such as errors and open dialogs.
  2. 2. Which issue is most clearly Critical severity?

    It blocks a core task for keyboard users entirely.
  3. 3. What should every issue in a report include?

    Those fields let a developer reproduce and fix the issue and let managers prioritize.
  4. 4. How often should you audit?

    Sites change constantly, so regular audits and continuous checks prevent regressions.

Summary

  • Scope the audit by standard, pages, states and environments.
  • Use a structured checklist covering structure, keyboard, perception, forms and robustness.
  • Rate severity, write complete findings and report positive results too.
  • Re-test after fixes, update your statement and repeat on a schedule.

Next: back to the Web Accessibility track