Website Accessibility Audit: A Practical Guide to WCAG 2.2 Compliance for Businesses

Most businesses do not set out to exclude users. Yet without a structured website accessibility checklist, accessibility gaps accumulate quietly, in a form field missing a label, a button unreachable by keyboard, or a color combination that fails contrast standards. The consequences are real: users with disabilities encounter barriers, and businesses face compliance risk under the Americans with Disabilities Act and similar frameworks across Canada. At Brand Vision, every web design engagement builds WCAG 2.2 alignment into design and development from the start, treating accessibility as a foundation rather than a final check. This guide gives you the structured website accessibility checklist your team needs to audit, prioritize, and resolve the issues that matter most.

Why WCAG 2.2 Matters for Your Business

The What's New in WCAG 2.2 outlines how the October 2023 update to the Web Content Accessibility Guidelines adds nine new success criteria to the standard, tightening requirements for focus indicators, target size, authentication, and dragging interactions. Compliance is not optional: courts in the United States and regulators in Canada increasingly treat WCAG 2.2 as the baseline for ADA website compliance.

The business case extends beyond legal protection. The 2025 WebAIM Million report analyzed one million homepages and found that 94.8 percent had detectable WCAG 2 failures, averaging 51 accessibility errors per page. That scale of failure points to a competitive opportunity. Accessible sites load faster, rank better in organic search, and reach users across a wider range of abilities and contexts. A well-executed website accessibility checklist strengthens performance across every channel.

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.

• Perceivable: Content must be presented in ways all users can perceive, including those using screen readers or who cannot distinguish color.
• Operable: All functionality must be reachable and usable via keyboard alone, without time constraints that exclude slower users.
• Understandable: Language, navigation, and error handling must be predictable and clear, supporting users with cognitive disabilities.
• Robust: Content must be interpreted reliably by a broad range of assistive technologies, including current and future screen readers.

Building your audit process around POUR ensures that your website accessibility checklist addresses the full spectrum of user needs rather than patching isolated symptoms.

A Practical Website Accessibility Checklist by Category

Use this checklist to structure an internal audit or prepare for a professional accessibility review. The criteria below span both WCAG 2.1 and the new requirements added in WCAG 2.2. If your organization is building or redesigning a site, partnering with a structured web design agency that integrates this checklist at the design and development stage is the most efficient approach.

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 is the backbone of any website accessibility checklist. A user who cannot hold a mouse must reach every interactive element using Tab, Enter, arrow keys, and Escape alone.

• Full keyboard navigation: All links, buttons, forms, modals, and custom widgets are reachable and operable via keyboard without a mouse.
• Visible focus indicators (WCAG 2.2 SC 2.4.11): The Focus Appearance criterion requires the focus indicator area to be at least 1 CSS pixel thick along the perimeter of the component, or at least 4 CSS pixels on its shortest side, with a minimum 3:1 contrast ratio between the focused and unfocused states. Browser default outlines frequently do not satisfy these requirements and need to be replaced with custom CSS focus styles.
• 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.
• No keyboard trap: Focus does not become trapped in components like modals or date pickers. Users can always exit using Escape or Tab.
• Target size minimum (WCAG 2.2): Interactive targets are at least 24 by 24 CSS pixels, with adequate spacing, per the Target Size (Minimum) criterion. Touch interfaces benefit most from this update.
• No dragging-only interactions (WCAG 2.2): Any action achievable by dragging must also be completable with a single pointer action, per the new Dragging Movements criterion.

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.
• Descriptive page titles and headings: Each page has a unique, descriptive title tag. Headings follow a logical hierarchy (H1, H2, H3) without skipping levels, giving screen reader users an accurate outline.
• Form labels and error messages: Every form input has a visible, programmatically associated label. Error messages identify the field in error and explain how to fix it, rather than just flagging that something went wrong.
• Consistent navigation: Navigation components appear in the same position and order across pages. Labels do not change between pages without clear purpose.
• Accessible authentication (WCAG 2.2): Login and verification steps must not require users to transcribe characters, solve cognitive puzzles, or recall information. Copy-paste and password manager support are required, per the Accessible Authentication criterion.

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.
• Valid markup: HTML validates without critical errors. Duplicate IDs, missing closing tags, and malformed attributes all produce unpredictable behavior in assistive technologies.
• 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

A website accessibility checklist is most effective when paired with the right testing tools. No automated tool catches every issue, but a layered approach significantly reduces audit time and improves coverage.

• 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: Tools such as Axe DevTools and WAVE identify around 57 percent of WCAG issues automatically, according to Deque's automated accessibility coverage research. Use them to locate common failures quickly, then follow up with manual keyboard walkthroughs and screen reader testing for full coverage.

If your current site was not built with accessibility in mind, the audit process will surface structural issues that require both design and code changes. Working with a web design company that treats accessibility as a design system requirement, not a post-launch patch, produces more durable results.

How to Prioritize Fixes After Running a Website Accessibility Checklist

A completed website accessibility checklist typically reveals more issues than a single sprint can address. A structured prioritization approach prevents remediation from stalling.

Tier 1: Critical Barriers

These issues block entire categories of users and should be resolved first:

• 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 create meaningful difficulty but do not fully prevent access:

• Focus indicators that are present but fail the WCAG 2.2 minimum area requirement
• Error messages that identify errors without explaining corrections
• Page titles that are absent or non-descriptive
• Touch targets below the 24 by 24 pixel minimum

Tier 3: Polishing and Long-Term Robustness

These items improve the overall quality of accessible web design and support future-proofing:

• ARIA roles audited and redundant labels removed
• Reflow tested across zoom levels and small viewports
• Authentication flows updated to meet WCAG 2.2 accessible authentication requirements
• Dragging interactions given single-pointer alternatives

What Is New in WCAG 2.2: The Criteria Your Checklist Must Include

If your organization last conducted a website accessibility checklist review against WCAG 2.1, the 2.2 update introduces nine new success criteria. The most impactful for most business websites are:

• Focus Appearance (SC 2.4.11, AA): Focus Appearance requires focus indicators to meet minimum size (at least 1 CSS pixel along the perimeter, or 4 CSS pixels on the shortest side) and a 3:1 contrast ratio between focused and unfocused states. Many sites with technically visible focus indicators still fail on size or contrast.
• Focus Not Obscured (SC 2.4.12, AA): When a component receives keyboard focus, it must not be entirely hidden by author-created content such as sticky headers or fixed banners. Partial obscuring is permissible under this AA criterion, but complete obscuring fails.
• Target Size Minimum (SC 2.5.8, AA): Interactive targets must be at least 24 by 24 CSS pixels, or have a spacing offset of at least 24 CSS pixels from adjacent targets, per the Target Size (Minimum) criterion. This protects touch users and users with motor impairments.
• Dragging Movements (SC 2.5.7, AA): Any functionality that requires a dragging motion must also be achievable with a single pointer action, per the Dragging Movements criterion.
• Accessible Authentication Minimum (SC 3.3.8, AA): Authentication and verification steps must not require users to complete a cognitive function test such as transcribing characters or solving a puzzle, unless an alternative method is available, per the Accessible Authentication criterion.
• Redundant Entry (SC 3.3.7, A): Multi-step processes must not ask users to re-enter information they have already provided within the same session.

Incorporating all six of these into your website accessibility checklist ensures your audit reflects current compliance expectations, not outdated standards.

Building Accessible Web Design Into the Process From the Start

A website accessibility checklist used only at the end of a project will always produce more remediation work than one integrated throughout design and development. The most efficient path to WCAG 2.2 compliance runs accessibility requirements through every stage: discovery, UI UX design, component development, and QA.

At Brand Vision, our web design services validate color contrast, focus states, and target sizes during the design phase, before a single line of code is written. Our development team implements semantic HTML, tested ARIA patterns, and keyboard navigation as standard, not as an optional enhancement. Clients who have worked with us on WordPress web design and Webflow web design benefit from accessible component libraries that remain consistent across future updates.

We also published a detailed guide to accessible navigation design for complex websites, which explores how information architecture, skip links, and ARIA landmarks work together to create navigable, compliant experiences at scale.

ADA Website Compliance: Legal Context for US and Canadian Businesses

The legal environment for web accessibility has tightened considerably. Title III of the Americans with Disabilities Act has been interpreted by multiple federal courts to cover websites and digital products. Demand letters and lawsuits targeting businesses with accessibility failures have increased year over year, particularly affecting e-commerce, hospitality, education, healthcare, and financial services sectors.

In Canada, the Accessible Canada Act and Ontario Regulation 191/11 under the Accessibility for Ontarians with Disabilities Act (AODA) require organizations above certain thresholds to maintain web content conforming to WCAG 2.0 Level AA, with current guidance trending toward WCAG 2.2. If you operate across both markets, a single website accessibility checklist aligned to WCAG 2.2 AA satisfies compliance obligations in both jurisdictions.

For organizations undergoing a broader brand or digital transformation, aligning your brand strategy and digital presence simultaneously gives teams a structured moment to integrate accessibility standards across every touchpoint before launch.

Maintaining Compliance: Accessibility as an Ongoing Governance Practice

A one-time website accessibility checklist audit is a starting point, not a destination. Accessibility compliance is a continuous practice because websites change continuously: new content, new features, new templates, and CMS updates all introduce potential regressions.

Structuring ongoing accessibility governance involves several practical steps:

• Establish a baseline: Document current WCAG 2.2 conformance level by component type and page template. This baseline gives future audits a clear reference point for measuring progress.
• 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: Most accessibility regressions originate with content updates: missing alt text on new images, poor heading structure in blog posts, or unlabeled form fields added to a template. Training reduces recurring issues.
• 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 or evaluating your current digital infrastructure, a marketing consultation and audit with Brand Vision can surface accessibility gaps alongside UX, SEO, and conversion opportunities, giving stakeholders a complete picture of remediation priorities and their business impact.

A Website Accessibility Checklist as a Performance Foundation

Accessibility and performance are not competing priorities. A site that passes a thorough website accessibility checklist is faster to load, clearer to navigate, better structured for organic search, and available to a wider audience. The nine new criteria in WCAG 2.2 strengthen protections for users with motor impairments, cognitive disabilities, and those relying on authentication assistive tools, while raising the bar for the focus and target size standards many sites already struggle to meet.

The most reliable path to sustained WCAG 2.2 compliance is building a website accessibility checklist into every stage of design and development rather than treating it as a final audit. Whether you are launching a new site, redesigning an existing one, or beginning a content governance program, the standards are clear and the tools are available.

If you want a partner who integrates this website accessibility checklist discipline into every aspect of design, development, and ongoing governance, explore how Brand Vision's web design and development services can support your organization.