Need Help With Your Brand or Website?
Branding, web design, SEO and digital marketing. Book a free consultation with our team.
Subscribe to Our Newsletter
Web Design

Website Accessibility Audit: A Practical WCAG 2.2 Checklist

Published on: April 3, 2026
Updated on: October 14, 2026

Many accessibility barriers begin with ordinary website decisions: an unlabeled form field, a button that keyboard users cannot reach, or text with insufficient contrast. A website accessibility checklist helps teams find and prioritize those barriers. Accessibility also carries legal responsibilities that depend on the organization and jurisdiction. At Brand Vision, web design is one part of that work, alongside content and interaction decisions. This guide explains the checks businesses can run and when more detailed testing is needed.

Why WCAG 2.2 Matters for Your Business

The W3C’s What's New in WCAG 2.2 explains the nine success criteria added in October 2023, covering keyboard focus, target size, authentication, help, and dragging. WCAG 2.2 is a useful audit target, but it is not automatically the legal standard for every business in the United States or Canada. The applicable requirements depend on the relevant law and organization.

The 2025 WebAIM Million report found detectable WCAG failures on 94.8 percent of one million sampled homepages, averaging 51 automated errors per page. The original figures are available in WebAIM’s archived 2025 results. Those automated findings do not establish full conformance or nonconformance for every criterion. Accessible design can reduce friction for more users, while good SEO still depends on content and technical fundamentals; accessibility alone does not guarantee higher rankings or faster pages.

woman looking at laptop

The Four Principles Behind Every Website Accessibility Checklist

WCAG 2.2 organizes all criteria under four principles, often abbreviated as POUR. Every item in a sound website accessibility checklist maps to one of these categories.

  • Make text and media available in forms people can perceive, including alternatives for non-text content.
  • Ensure people can operate controls using a keyboard and have enough time to complete tasks, with appropriate adjustments.
  • Keep navigation, instructions, and error recovery predictable and understandable.
  • Use markup that assistive technologies can interpret reliably across supported browsers and devices.

The POUR framework helps organize issues and assign owners. It is a starting point, not a substitute for checking the applicable WCAG success criteria and testing real user journeys.

A Practical Website Accessibility Checklist by Category

Use this checklist to plan an internal review, then test representative pages and workflows against the relevant success criteria. A site redesign is also a chance to coordinate inclusive content, user experience, and brand standards. Brand Vision, a branding agency can be considered alongside qualified accessibility testing and development partners when defining that scope.

Perceivable: Images, Media, and Color

  • Alt text on images: Every meaningful image carries descriptive alt text. Decorative images use empty alt attributes (alt="") so screen readers skip them without interrupting the experience.
  • Color contrast ratio: Body text must meet a minimum contrast ratio of 4.5:1 against its background. Large text (18pt or 14pt bold) requires at least 3:1. Use the WebAIM Contrast Checker to validate every text and UI combination.
  • Color independence: Information must never be conveyed by color alone. Error states, status indicators, and chart legends need text or pattern alternatives alongside color cues.
  • Captions and transcripts: Pre-recorded video includes accurate captions. Live video provides real-time captions. Audio-only content offers a text transcript.
  • Reflow at 320px: Content must reflow at 320 CSS pixels without horizontal scrolling, supporting users who zoom to 400 percent or use small screens.

Operable: Keyboard, Focus, and Interaction

Keyboard accessibility includes reaching and operating all interactive controls without a mouse. Test Tab and Shift+Tab focus order, then the keys appropriate to each component, such as Enter, Space, arrows, and Escape.

  • Full keyboard navigation: All links, buttons, forms, modals, and custom widgets are reachable and operable via keyboard without a mouse.
  • Provide a visible keyboard focus indicator under SC 2.4.7 (AA). The Focus Appearance criterion is SC 2.4.13 (AAA); it gives additional area and contrast guidance and does not mean standard browser outlines routinely fail Level AA.
  • Skip navigation link: A "Skip to main content" link appears at the top of the page, visible on focus, so keyboard users bypass repeated navigation on every page load.
  • Prevent unexpected keyboard traps. In modal dialogs, keep focus appropriately within the dialog while it is open and provide a predictable way to close it and restore focus.
  • Test pointer targets against the 24-by-24 CSS pixel baseline or applicable exceptions, including spacing and inline-text cases, under the Target Size (Minimum) criterion (SC 2.5.8, AA).
  • Offer a single-pointer alternative for actions that otherwise require dragging, except where dragging is essential, as described in the Dragging Movements criterion (SC 2.5.7, AA).
Woman writing notes

Understandable: Language, Forms, and Authentication

This section of the website accessibility checklist covers the clarity and predictability that support users with cognitive disabilities, learning differences, and limited digital literacy.

  • Page language declared: Every HTML document sets a lang attribute (e.g., lang="en") so screen readers apply the correct pronunciation rules.
  • Use a descriptive page title and a logical heading hierarchy that reflects the content. Do not mistake a preferred heading pattern for a stand-alone WCAG conformance test.
  • Associate visible labels and useful instructions with form fields. Explain what went wrong and how to correct it; consider a UX audit when repeated form errors suggest an underlying UX issue.
  • Consistent navigation: Navigation components appear in the same position and order across pages. Labels do not change between pages without clear purpose.
  • Under the Accessible Authentication criterion (SC 3.3.8, AA), avoid cognitive-function tests in authentication unless an allowed alternative or exception applies. Support password managers and pasting rather than blocking them.

Robust: Semantic Markup and ARIA

  • Semantic HTML: Use native HTML elements for their intended purpose: buttons for actions, links for navigation, lists for grouped items. Semantic structure is processed accurately by assistive technologies without additional ARIA.
  • ARIA roles and states: When native HTML is insufficient, ARIA landmarks and roles (such as role="navigation" or aria-expanded) communicate structure and state to screen readers. Review the ARIA Roles reference and apply only what is necessary; redundant ARIA attributes can create more confusion than they resolve.
  • Use valid, predictable markup, unique IDs where required, and correct programmatic names and roles. WCAG 2.2 removed the former SC 4.1.1 Parsing criterion; malformed markup can still cause other accessibility failures.
  • Status messages: Dynamic updates such as form submission confirmations or cart additions are announced to screen readers without moving focus, using ARIA live regions where appropriate.

Accessibility Testing Tools to Support Your Audit

Use automated scans to locate common failures, but verify them with keyboard, screen-reader, zoom, and human usability testing. No scanner or short checklist can certify the accessibility of an entire website.

  • W3C Easy Checks: A structured, manual starter guide from the W3C for evaluating the most impactful accessibility criteria without specialist tools.
  • WCAG 2.2 Quick Reference: The official W3C filterable checklist for all WCAG 2.2 success criteria, filterable by level and principle.
  • Browser screen readers: Test with NVDA or JAWS on Windows and VoiceOver on macOS and iOS to verify real-world screen reader compatibility before launch.
  • Keyboard-only testing: Unplug the mouse and navigate every page and form using only Tab, Shift+Tab, Enter, and Escape. This test surfaces focus order problems and keyboard traps that automated tools miss.
  • Automated scanners such as axe and WAVE help locate detectable issues. Deque's automated accessibility coverage research describes their limits; complete the audit with manual keyboard checks, assistive-technology testing, and human review.

An accessibility audit may reveal design, content, and code issues that need different owners. A Miami organization comparing project partners, for example, can ask a branding agency in Miami how it coordinates with developers and qualified testers, rather than assume a website redesign itself establishes conformance.

How to Prioritize Fixes After Running a Website Accessibility Checklist

An accessibility audit often identifies more issues than a single release can fix. Prioritize by user impact, essential tasks, severity, and the obligations that apply to the organization, and record the reason for each decision.

Tier 1: Critical Barriers

These examples often prevent people from completing essential tasks and merit urgent investigation:

  • Missing alt text on informational images
  • Forms with no labels or unusable keyboard flow
  • Text failing the 4.5:1 color contrast ratio requirement
  • Interactive elements unreachable via keyboard
  • Videos without captions

Tier 2: Significant Friction

These issues may be serious even when some users can work around them:

  • Visible focus indicators that need better contrast or clarity, with WCAG 2.2 success criteria assessed by the applicable conformance level.
  • Error messages that identify errors without explaining corrections
  • Page titles that are absent or non-descriptive
  • Small controls that fail target-size or spacing checks without a qualifying exception.

Tier 3: Polishing and Long-Term Robustness

These additional checks support ongoing quality. Escalate any of them immediately if testing shows they block an essential task:

  • ARIA roles audited and redundant labels removed
  • Reflow tested across zoom levels and small viewports
  • Recheck accessible authentication as flows change, and escalate failures that prevent users from signing in.
  • Dragging interactions given single-pointer alternatives
team working together

What Changed in WCAG 2.2: Key Criteria to Test

WCAG 2.2 added nine success criteria. The examples below highlight several of them and distinguish Level A, AA, and AAA. Use the full W3C Quick Reference for a complete level-specific review.

  • Focus Appearance is SC 2.4.13 (AAA), not SC 2.4.11 AA. Its focus-indicator area is measured against a two-CSS-pixel perimeter reference, with a 3:1 appearance contrast test and stated exceptions.
  • Focus Not Obscured (Minimum) is SC 2.4.11 (AA). A focused control must not be entirely concealed by author-created content such as a sticky header; the enhanced criterion 2.4.12 is AAA.
  • SC 2.5.8 (AA) tests targets against 24 by 24 CSS pixels, with exceptions for adequate spacing and certain other cases, as explained by the Target Size (Minimum) criterion.
  • SC 2.5.7 (AA) requires a single-pointer alternative where content uses dragging, unless essential, under the Dragging Movements criterion.
  • SC 3.3.8 (AA) limits cognitive tests for sign-in unless there is an allowed alternative or exception, per the Accessible Authentication criterion.
  • SC 3.3.7 (A) generally requires previously entered information to be reused or selectable within the same process, with limited exceptions for security, essential repetition, or invalid prior data.

These examples are not the whole WCAG 2.2 checklist. In particular, the AAA Focus Appearance criterion is a useful design goal but is not required to claim Level AA conformance.

Building Accessible Web Design Into the Process From the Start

Test accessibility throughout discovery, UI/UX design, content production, development, and QA. Research with people with disabilities can expose barriers a checklist misses; where appropriate, build research with users into task testing before committing to a design.

Teams should document who checks color contrast, focus behavior, labels, and keyboard interactions before launch. For projects involving multiple markets, a Canadian digital marketing agency can help coordinate brand and website requirements, while the organization confirms applicable accessibility rules separately. Whether the site uses WordPress web design or another platform, its components and content need their own testing.

For more on the navigation portion of an audit, our guide to accessible navigation design for complex websites covers skip links, page structure, and assistive-technology considerations. Clear accessible form microcopy also helps users understand field instructions and recover from errors.

Accessibility Requirements in the U.S. and Canada

In the United States, the ADA applies to different types of organizations in different ways. The U.S. Department of Justice’s Title II web accessibility rule specifies WCAG 2.1 Level AA for state and local government web content and mobile apps, with compliance dates extended in 2026 to April 2027 or April 2028 according to entity size. Private businesses may have obligations under ADA Title III, but the Title II rule should not be presented as a universal WCAG 2.2 mandate for them.

In Canada, requirements vary by jurisdiction and organization. Under Ontario’s AODA website accessibility requirements, designated public-sector organizations and businesses or nonprofits with at least 50 employees generally must make qualifying public websites and content meet WCAG 2.0 Level AA, subject to specified exceptions. The federal Accessible Canada Act has a separate scope for federally regulated organizations. A WCAG 2.2 AA review can go beyond some legal baselines, but one checklist cannot guarantee compliance in every jurisdiction.

When design and governance work are commissioned together, specify who owns brand decisions, technical remediation, accessibility testing, and acceptance criteria. A Chicago company comparing providers can ask a branding agency in Chicago to identify the boundaries of its work and the accessibility expertise required from other partners.

Maintaining Accessibility as an Ongoing Practice

Accessibility needs ongoing attention after the initial audit. New CMS content, product features, templates, and third-party widgets can introduce fresh barriers, even on a site that previously tested well.

Structuring ongoing accessibility governance involves several practical steps:

  • Document findings by page type, component, affected users, criterion, and the evidence available. Do not call an untested component conformant.
  • Integrate into QA: Add accessibility checks to your standard QA process for every new feature and content update. Automated scans, keyboard walkthroughs, and screen reader spot-checks should be part of every release cycle.
  • Train content editors to maintain meaningful alt text, heading structures, link descriptions, captions, and form instructions.
  • Schedule periodic full audits: Conduct a comprehensive website accessibility checklist review at minimum annually, and after any major redesign or platform migration.

If your team is planning a redesign, a marketing consultation and audit can help frame design, UX, and website priorities. A formal WCAG conformance assessment or legal opinion should be scoped separately with suitable specialists.

Turning Audit Findings Into Better Experiences

Accessibility and website performance both matter, but passing accessibility tests does not automatically improve load time or search rankings. The practical value of WCAG 2.2 is helping more people perceive content, navigate controls, understand instructions, and complete tasks.

The most durable approach is to make accessibility checks part of design, development, publishing, and ongoing QA rather than rely on a final checklist. Document outstanding issues and test fixes with the people and assistive technologies they affect.

If you are planning a more inclusive website, Brand Vision, a branding agency, can discuss the design and content scope. Businesses selecting a branding agency in the US should also confirm who will perform WCAG testing and assess applicable legal requirements.

Let’s Talk
Subscribe to Insights
Newsletter