Website Accessibility Audit: Complete 2026 Guide
Website Accessibility Audit: The Complete 2026 Guide to WCAG 2.2 Compliance
Everything you need to plan, execute, and act on a website accessibility audit — from automated scanning through expert remediation, legal compliance, and AI-native testing.
Webability TeamAccessibility consultants, WCAG specialists & digital compliance experts · About Webability
TL;DR — Key Takeaways- A website accessibility audit identifies WCAG 2.2, ADA, and Section 508 compliance gaps before they become lawsuits.
- Automated tools only catch ~30–40% of issues; real audits require manual expert testing and screen reader validation.
- ADA website lawsuits surged 37% in H1 2025 — with settlements averaging $50,000–$150,000 per case.
- The 6 most common failures are: low color contrast, missing alt text, empty links, missing form labels, undefined document language, empty buttons.
- A complete audit covers automated scanning, manual testing, ARIA review, keyboard navigation, and user testing with assistive technology.
- Webability provides AI-native WCAG 2.2 remediation you can deploy in under 2 minutes. Try the free scanner →
Why Your Website Accessibility Audit Can't Wait Until 2027
In the first half of 2025 alone, 2,014 ADA website accessibility lawsuits were filed in U.S. courts — a 37% increase over the same period in 2024. Illinois emerged as a new litigation hotspot with a staggering 745% spike. Meanwhile, the European Accessibility Act (EAA) became enforceable on June 28, 2025, placing millions of businesses serving EU customers under new legal obligations.
And yet, according to the 2025 WebAIM Million report, 94.8% of websites still have detectable WCAG 2 failures — averaging 51 accessibility errors per page. Only 4 out of every 100 websites are genuinely accessible.
A website accessibility audit is no longer a compliance checkbox. It is the difference between being a brand that everyone can use — and a brand that ends up as a defendant in federal court.
This guide covers everything: what an accessibility audit actually is, how to run one step-by-step, what WCAG 2.2 requires, which tools to use, what it costs, how to remediate issues, and what the future looks like for AI-driven accessibility testing.
94.8% of websites fail WCAG 2 (WebAIM 2025) 3,948 ADA website lawsuits filed in 2025 $150K Average total cost of one ADA lawsuit 1.3B People worldwide living with a disabilityWhat Is a Website Accessibility Audit?
Quick Answer — Featured SnippetA website accessibility audit is a systematic evaluation of a website against accessibility standards — primarily WCAG 2.2, the Americans with Disabilities Act (ADA), and Section 508 of the Rehabilitation Act. The audit identifies barriers that prevent people with disabilities from perceiving, navigating, and interacting with digital content, and produces a prioritized remediation roadmap. A complete audit combines automated scanning, manual expert review, and assistive technology testing.
The term "audit" encompasses several distinct activities that often get conflated:
- Automated scan: Software crawls your site and flags code-level violations (e.g., missing alt attributes, low contrast ratios).
- Manual expert review: An accessibility specialist manually tests pages against each applicable WCAG success criterion.
- Assistive technology testing: Real users or specialists test with screen readers (NVDA, JAWS, VoiceOver), voice control (Dragon NaturallySpeaking), and switch access devices.
- Conformance report (ACR/VPAT): A formal document — typically an Accessibility Conformance Report (ACR/VPAT) — describing conformance with WCAG, Section 508, and EN 301 549.
The gold standard is a hybrid audit: automated scanning to catch volume violations quickly, followed by deep manual testing to surface the issues no tool can detect — the 60–70% of failures that require human judgment.
Why Website Accessibility Audits Matter More Than Ever in 2026
The Legal Landscape Has Changed Dramatically
Three major regulatory developments have transformed website accessibility from "good practice" into an enforceable legal requirement:
| Regulation | Who It Covers | Standard Required | Key Deadline |
|---|---|---|---|
| ADA Title III | US businesses open to the public (retail, hospitality, healthcare, SaaS) | WCAG 2.1 AA (court precedent) | Enforceable now; no safe harbor |
| ADA Title II | US state & local government entities | WCAG 2.1 AA | April 2026 (< 10K population: 2027) |
| European Accessibility Act (EAA) | EU businesses & global companies serving EU customers | EN 301 549 / WCAG 2.1 AA | June 28, 2025 (enforced) |
| Section 508 | US federal agencies & contractors | WCAG 2.0 AA (EN 301 549 refresh pending) | Ongoing; ICT Refresh active |
| AODA | Ontario, Canada businesses with 50+ employees | WCAG 2.0 AA | Active enforcement |
Accessibility overlays and widgets do NOT provide legal protection. In 2025, 456 lawsuits (22.6% of all ADA web cases) specifically targeted sites using overlay tools. Courts have consistently ruled that overlays are not a substitute for code-level remediation. Learn more about ADA compliance →
The Business Case Is Equally Compelling
Beyond legal risk, accessible websites serve the $13 trillion global disability market. Users with disabilities control significant purchasing power. Accessibility improvements also deliver measurable SEO benefits: semantic HTML, descriptive alt text, logical heading hierarchies, and faster load times all contribute to higher search rankings. Read how accessibility boosts your website traffic →
Understanding WCAG 2.2: What Your Audit Must Cover
The Web Content Accessibility Guidelines (WCAG) 2.2, published by the W3C in October 2023, is the current international standard for web accessibility. It builds on WCAG 2.1 with 9 new success criteria — all while remaining fully backward-compatible.
The Four WCAG Principles (POUR)
All WCAG success criteria are organized under four principles. Every accessibility audit evaluates compliance against each:
| Principle | What It Means | Key Examples |
|---|---|---|
| Perceivable | Information must be presentable in ways users can perceive | Alt text for images, captions for video, sufficient color contrast (4.5:1 minimum) |
| Operable | UI components and navigation must be operable by all users | Full keyboard navigation, no keyboard traps, skip links, adequate focus indicators |
| Understandable | Information and operation of UI must be understandable | Readable language, predictable navigation, clear error messages, accessible forms |
| Robust | Content must be interpretable by a wide variety of user agents and AT | Valid HTML, proper ARIA roles, parsing errors resolved |
WCAG 2.2's 9 New Success Criteria — What Auditors Must Now Test
| Criterion | Level | What It Requires |
|---|---|---|
| 2.4.11 Focus Not Obscured (Min) | AA | Keyboard focus indicator must not be entirely hidden by sticky headers or overlays |
| 2.4.12 Focus Not Obscured (Enhanced) | AAA | No part of the focus indicator is obscured by author-created content |
| 2.4.13 Focus Appearance | AAA | Minimum focus indicator area: 2px perimeter with 3:1 contrast ratio vs. adjacent color |
| 2.5.7 Dragging Movements | AA | All dragging operations must have a single-pointer alternative |
| 2.5.8 Target Size (Minimum) | AA | Touch targets must be at least 24×24 CSS pixels (or have adequate spacing) |
| 3.2.6 Consistent Help | AA | If a help mechanism appears on multiple pages, it must appear in the same location |
| 3.3.7 Redundant Entry | AA | Info previously entered in a process must be auto-populated or selectable |
| 3.3.8 Accessible Authentication (Min) | AA | No cognitive function test required for authentication (e.g., no image puzzles without alternative) |
| 3.3.9 Accessible Authentication (Enhanced) | AAA | Authentication with no exception for transcription or object recognition |
For a complete breakdown of all WCAG 2.2 criteria and what they mean for your development team, see our WCAG 2.2 Complete 2026 Compliance Guide.
ℹ WCAG Conformance Levels
Level A — Minimum accessibility. Non-compliance makes content inaccessible to some users. Level AA — The legal and industry standard. Required by ADA, EAA, Section 508. Level AAA — Enhanced accessibility. Not required by law but recommended for healthcare, government, and education.
Not Sure If Your Site Is WCAG 2.2 Compliant?
Run a free instant scan with Webability's Website Accessibility Checker — identify violations in seconds, no account required.
Scan My Website Free View PricingHow to Conduct a Website Accessibility Audit: 8-Step Process
A professional-grade accessibility audit follows a structured process. Here is the methodology used by certified accessibility specialists and Webability's managed accessibility team:
-
Define Scope & Standards
Identify which pages and user flows will be audited (homepage, checkout, login, forms, PDFs, media). Confirm target standards: WCAG 2.2 Level AA is the baseline for most commercial sites in 2026. Government and healthcare should additionally reference Section 508 and EN 301 549.
-
Run Automated Scanning
Use tools like axe DevTools, WAVE, or Webability's scanner to crawl your site and generate a baseline violation report. Flag issues by severity (critical, serious, moderate, minor). Remember: automated tools catch only ~30–40% of real WCAG issues. This step is triage, not a complete audit.
-
Audit Keyboard Navigation
Disconnect your mouse. Navigate every interactive element using Tab, Shift+Tab, Enter, Space, and arrow keys. Verify focus order is logical, focus indicators are always visible (WCAG 2.4.11), no keyboard traps exist, and all functionality is operable without a mouse.
-
Screen Reader Testing
Test with NVDA + Firefox (Windows), JAWS + Chrome (enterprise Windows), and VoiceOver + Safari (macOS/iOS). Evaluate: landmark regions, heading hierarchy, image alt text quality, form label associations, dynamic content announcements via ARIA live regions, and modal dialog management.
-
Evaluate Visual Accessibility
Check all text for minimum 4.5:1 contrast ratio (3:1 for large text). Verify no information is conveyed by color alone. Test with browser zoom at 200% and 400%. Evaluate touch target sizes on mobile (minimum 24×24 CSS px per WCAG 2.5.8). Use Webability's Color Contrast Checker or AI Color Contrast Checker.
-
Review Content & Semantic Structure
Evaluate heading hierarchy (H1 → H2 → H3 with no skips), link text descriptiveness (no "click here" or "read more"), image alt text quality, language attribute (
lang="en"), table structure (headers withscope), and PDF accessibility. See our guide on best practices for alt text and using the HTML lang attribute correctly. -
Test Forms, Authentication & Dynamic Content
Every form field must have a programmatically associated label. Error messages must identify the field and describe how to fix it. Verify new WCAG 2.2 criteria: no cognitive function test in authentication (3.3.8), no redundant data entry in multi-step processes (3.3.7). Test dynamic content updates with ARIA live regions.
-
Document Findings & Build Remediation Roadmap
Categorize every finding by: WCAG criterion, impact level (critical/serious/moderate/minor), affected users, page/component location, and recommended fix. Prioritize critical and serious issues first. Produce a VPAT/ACR if required by enterprise procurement, government contracts, or EAA compliance documentation.
Automated vs. Manual Accessibility Testing: Which Do You Need?
The single most dangerous misconception in accessibility is that running an automated scan equals conducting an audit. It does not. Here is a clear breakdown:
| Factor | Automated Testing | Manual Expert Testing |
|---|---|---|
| WCAG Coverage | ~30–40% of criteria | Up to 100% of applicable criteria |
| Speed | Minutes to hours (full site) | Days to weeks |
| Cost | Free – $500/month | $1,500 – $50,000+ |
| Best For | Catching volume errors, CI/CD integration, monitoring | Pre-launch compliance, legal protection, VPATs, procurement |
| Catches | Missing alt attributes, contrast failures, empty links, missing labels, invalid ARIA | Misleading alt text, illogical heading structure, screen reader announcements, cognitive barriers, keyboard traps, context-dependent failures |
| Legal Weight | Low (not sufficient for compliance defense) | High (documented audit = evidence of good-faith effort) |
| False Positives | Possible (especially low-contrast edge cases) | Minimal (human context judgment) |
✓ Best Practice
Use both. Automate monitoring to catch regressions continuously, and invest in annual manual audits for comprehensive WCAG conformance. Integrate automated testing into your CI/CD pipeline using axe-core or Deque's CI/CD integrations. Conduct manual expert audits before major launches and annually thereafter.
The 6 Most Common Accessibility Failures Found in Audits
According to the 2025 WebAIM Million analysis of one million homepages, six issues account for the vast majority of detected WCAG failures — and they have remained the top offenders for five consecutive years:
| Failure Type | % of Sites Affected | WCAG Criterion | Quick Fix |
|---|---|---|---|
| Low color contrast text | 81.0% | 1.4.3 (AA) | Use a contrast checker; ensure 4.5:1 minimum |
| Missing alternative text on images | 54.5% | 1.1.1 (A) | Add descriptive alt attributes; use alt="" for decorative images |
| Empty links | 49.7% | 2.4.4 (AA) | Ensure all <a> tags have descriptive accessible text or aria-label |
| Missing form input labels | 45.9% | 1.3.1, 3.3.2 (A/AA) | Associate <label> to every input; use aria-label or aria-labelledby |
| Missing document language | 17.1% | 3.1.1 (A) | Add lang="en" (or appropriate language) to the <html> element |
| Empty buttons | 28.2% | 4.1.2 (A) | Add visible text or aria-label to every <button> |
Website Accessibility Audit Checklist (WCAG 2.2 Level AA)
Use this checklist as a starting point for your audit. For a full 200+ item template, see our comprehensive 2026 website accessibility checklist.
Perceivable
- All non-text content has descriptive alt text (decorative images use
alt="") - Videos have synchronized captions and/or audio descriptions
- Audio content has a text transcript available
- Color contrast for normal text is at least 4.5:1
- Color contrast for large text (18pt or 14pt bold) is at least 3:1
- Information is not conveyed by color alone
- Content is readable and functional at 200% browser zoom without horizontal scroll
- Text can be resized up to 200% without loss of content or functionality
- Images of text are avoided (except logos)
- Content does not rely on sensory characteristics (shape, size, location) alone
Operable
- All functionality is accessible via keyboard only (Tab, Enter, Space, arrow keys)
- No keyboard traps — users can navigate away from all components
- Skip navigation link is provided to bypass blocks of repeated content
- Page has a descriptive, unique
<title>element - Focus order is logical and meaningful
- Focus indicator is visible and not obscured by sticky headers (WCAG 2.4.11)
- All interactive elements have a minimum touch target of 24×24px (WCAG 2.5.8)
- Dragging interactions have a single-pointer alternative (WCAG 2.5.7)
- No content flashes more than 3 times per second
- Users have sufficient time to read and interact with content; time limits are adjustable
Understandable
- Page language is programmatically set (
langattribute on<html>) - Language changes within the page are identified with
langattribute on the relevant element - Navigation is consistent across pages
- Interactive components behave predictably (no unexpected context changes on focus)
- Form errors are identified, described, and provide correction suggestions
- Authentication does not require solving a cognitive puzzle without an alternative (WCAG 3.3.8)
- Previously entered information is auto-populated in multi-step processes (WCAG 3.3.7)
- Help mechanisms appear in a consistent location across pages (WCAG 3.2.6)
Robust
- HTML is valid and well-structured; no duplicate IDs
- All UI components have accessible names, roles, and states exposed to AT
- ARIA is used correctly; no invalid or misused ARIA roles
- Status messages are announced to assistive technology via ARIA live regions
- Custom interactive components correctly communicate their role and state
Best Website Accessibility Audit Tools in 2026
See also: Webability's expert review of the 12 best accessibility tools for websites in 2026 and our interactive Accessibility Tools Comparison.
axe DevTools Automated — Browser Extension & APIZero false positives. Deep WCAG 2.2 coverage. CI/CD integration. Industry standard for development teams.
Free core / $40+/mo Pro / WCAG 2.2 AAWAVE (WebAIM) Automated — Browser Extension & API
Visual overlays directly on your page. Excellent for training and quick triage. Free browser extension widely used by beginners.
Free extension / $3,000+/yr API / Visual feedbackGoogle Lighthouse Automated — Built into Chrome DevTools
Free and always available. Covers a subset of WCAG criteria. Good for quick developer checks. Not sufficient as a standalone audit tool.
Free / WCAG 2.1 partial / CI/CD via CLISiteimprove Enterprise Platform — Monitoring & Governance
Full site monitoring, team workflow management, compliance reporting, and issue prioritization. Best for large organizations.
Custom pricing / WCAG 2.2 AAA / EnterpriseWebability Scanner Free Instant Scan + AI Remediation
Instant WCAG scan with AI-native fixes deployed in production. One line of code. Continuous monitoring + ADA/EAA compliance reporting.
Free scan / AI-native fixes / 2-min installNVDA + JAWS + VoiceOver Screen Readers — Manual Testing
Essential for any serious audit. NVDA (free, Windows), JAWS (enterprise Windows), VoiceOver (free, macOS/iOS). Tests real AT interactions no automated tool can replicate.
Free (NVDA) / $90–$1,100/yr JAWS / ManualFor government and federal procurement, also review Section 508 compliance requirements and the W3C's full Web Accessibility Evaluation Tools list.
How Much Does a Website Accessibility Audit Cost in 2026?
Audit costs vary dramatically based on site complexity, page count, desired conformance level, and whether you need a formal VPAT/ACR for enterprise procurement.
| Audit Type | Typical Cost | Best For | Deliverable |
|---|---|---|---|
| Automated Scan (Free Tools) | $0 | Developers, initial triage | Violation report |
| Automated Platform (SaaS) | $50–$500/mo | Ongoing monitoring, SMBs | Continuous reports + monitoring |
| Manual Audit — Small Site (up to 20 pages) | $1,500–$5,000 | SMBs, startups, landing pages | Detailed findings report |
| Manual Audit — Mid-Size Site (20–100 pages) | $5,000–$15,000 | Growing businesses, SaaS apps | WCAG conformance report + VPAT |
| Enterprise Audit (100+ pages, complex apps) | $15,000–$50,000+ | Enterprise, healthcare, government | Full ACR/VPAT + remediation roadmap |
| Litigation Support Audit | $25,000–$100,000+ | Legal defense, active lawsuits | Expert witness report, legal documentation |
Compare the cost of a proactive audit against the alternative: the average total cost of a single ADA website lawsuit ranges from $50,000 to $150,000 in settlements, legal fees, remediation, and monitoring. Use our free Accessibility Cost Calculator to estimate your remediation investment.
Industry-Specific Accessibility Audit Considerations
Healthcare
Healthcare websites and patient portals face the intersection of ADA Title III, Section 508 (for federally funded providers), and HIPAA. Patients with disabilities need accessible appointment booking, medication portals, telehealth interfaces, and emergency information. Failures here are not just legal — they are patient safety issues. All forms, consent documents, and PDF health materials must be fully accessible. See our healthcare accessibility solutions.
E-Commerce & Retail
Retail sites are the single largest category of ADA website lawsuits. Product image alt text, accessible checkout flows, keyboard-navigable carousels, accessible payment forms, and screen reader-friendly product filters are all recurring failure points. A single inaccessible checkout flow can affect millions of users and represent significant revenue loss in addition to legal exposure. Learn about e-commerce accessibility →
Government & Public Sector
State and local government agencies must now achieve WCAG 2.1 AA compliance under ADA Title II, with an April 2026 deadline for large entities. Federal agencies remain under Section 508. Government sites often carry decades of legacy content — PDFs, scanned documents, and old video content — all of which require remediation. Government accessibility solutions →
SaaS & Technology
Enterprise SaaS products sold to government agencies, educational institutions, or healthcare organizations must provide a VPAT (Voluntary Product Accessibility Template). WCAG failures in core product flows — dashboards, onboarding, settings, data tables — are high-impact and can block enterprise sales cycles. Accessibility must be embedded in the product development lifecycle, not bolted on later. Technology sector accessibility →
Education
Higher education institutions receiving federal funding are covered by Section 508 and ADA. LMS platforms, course materials, and student portals must be fully accessible. Captioned video content, accessible PDFs, and keyboard-navigable course navigation are critical. Education accessibility solutions →
Finance & Banking
Banking and financial services face unique challenges: complex data tables, multi-step transaction flows, CAPTCHA on login pages (which violates WCAG 3.3.8), and time-limited session management. Accessible online banking is increasingly a regulatory expectation in both US and EU markets. Banking & finance accessibility →
After the Audit: The Remediation Process
An audit without remediation is a liability — you now have documented evidence of known failures. Here is how to move from findings to fixes:
Remediation Priority Framework
| Priority | Impact Level | Fix Timeline | Examples |
|---|---|---|---|
| P1 Critical | Completely blocks access for users with disabilities | Immediately (0–2 weeks) | No keyboard access to checkout, screen reader can't reach main content, form can't be submitted |
| P2 Serious | Creates significant barriers; workarounds are difficult | Short-term (2–6 weeks) | Low contrast text in critical UI, missing form labels, missing image alt text |
| P3 Moderate | Creates some barriers; workarounds exist | Medium-term (1–3 months) | Inconsistent focus indicators, missing skip links, generic link text |
| P4 Minor | Minor inconvenience; most users unaffected | Long-term (3–6 months) | Sub-optimal alt text, redundant ARIA, minor heading hierarchy issues |
Build Accessibility Into Your Development Workflow
True remediation is not a one-time project — it is a permanent change to how your team builds. Best-practice organizations embed accessibility at every stage: design systems include accessible components, developers run axe in CI/CD pipelines, QA checklists include keyboard and screen reader testing, and new deployments are scanned before release. For teams needing comprehensive coverage, Webability's Managed Accessibility service provides continuous AI-native remediation, monitoring, and legal documentation.
For complex document remediation, see our guide to PDF remediation for accessible documents.
AI & the Future of Accessibility Auditing
Artificial intelligence is transforming accessibility auditing in three significant ways:
1. AI-Generated Alt Text at Scale
Machine learning models can now generate contextually accurate alt text for thousands of images automatically — a capability that previously required hours of manual content review. Webability's AI Alt Text Generator demonstrates this in practice. However, AI-generated alt text still requires human review for complex, informational, or emotionally nuanced images.
2. AI-Native Code Remediation
Rather than just flagging issues, next-generation accessibility platforms use AI to generate and deploy fixes directly in production — adding ARIA attributes, correcting color contrast values, associating form labels, and improving focus management — without requiring developer intervention for every issue. Webability's AI engine applies WCAG 2.2 remediation automatically, in real time.
3. Continuous Cognitive Accessibility Monitoring
Emerging AI tools can now evaluate cognitive load, reading complexity, and plain language compliance — areas that WCAG does not fully address but that directly impact users with cognitive disabilities, ADHD, and dyslexia. How AI is transforming cognitive accessibility →
🔭 Looking Ahead: WCAG 3.0
The W3C is developing WCAG 3.0 (previously called "Silver"), which will move away from binary pass/fail criteria toward a functional outcomes model with graduated scoring. While WCAG 3.0 is still years from becoming a legal standard, accessibility teams should monitor its development and begin aligning documentation practices with outcome-based reporting.
Publish an Accessibility Statement
An accessibility statement is a public declaration of your organization's accessibility commitment, conformance status, known limitations, and contact information for users who encounter barriers. Under the EAA and many national laws, an accessibility statement is a legal requirement. Use Webability's free Accessibility Statement Generator to create a compliant statement in minutes. Learn more about Webability's own accessibility statement as an example of best practice.
Ready to Run Your Website Accessibility Audit?
Webability combines an instant free scanner with AI-native WCAG 2.2 remediation, continuous monitoring, and legal compliance documentation — deployed in under 2 minutes with a single line of code.
Start Free Scan Book a DemoFrequently Asked Questions: Website Accessibility Audits
What is a website accessibility audit?A website accessibility audit is a systematic evaluation of a website's compliance with accessibility standards — primarily WCAG 2.2, the Americans with Disabilities Act (ADA), and Section 508 of the Rehabilitation Act. It identifies barriers that prevent people with disabilities from perceiving, navigating, and interacting with digital content, and produces a prioritized remediation roadmap. A complete audit combines automated scanning, manual expert review, and testing with real assistive technologies such as screen readers and keyboard-only navigation.
How much does a website accessibility audit cost?Costs vary significantly: free automated scans are available using tools like Webability, WAVE, or axe. SaaS monitoring platforms run $50–$500/month. Professional manual audits for small sites cost $1,500–$5,000. Mid-size site audits run $5,000–$15,000. Enterprise audits covering complex applications with formal VPAT/ACR documentation can cost $15,000–$50,000 or more. Use our free cost calculator to estimate your investment.
How long does a website accessibility audit take?Automated scans complete in minutes to a few hours depending on site size. A comprehensive manual audit for a 20–50 page site typically takes 1–2 weeks. A thorough expert audit of a 50–100 page site with screen reader testing takes 2–4 weeks. Enterprise audits covering hundreds of pages, multiple user flows, and native app components can take 6–12 weeks. Remediation is a separate effort and takes additional time.
Can automated tools catch all accessibility issues?No — and this is the most important fact to understand about accessibility testing. Automated tools detect approximately 30–40% of WCAG violations. The remaining 60–70% require human judgment: evaluating whether alt text is actually meaningful and accurate, testing whether keyboard navigation is logical in context, verifying that screen reader announcements make sense, assessing cognitive load and reading complexity, and testing with real users with disabilities. Automated testing is essential for efficiency but must always be paired with manual expert review for a defensible compliance posture.
What is the difference between WCAG 2.1 and WCAG 2.2?WCAG 2.2, published October 2023, adds 9 new success criteria to WCAG 2.1 while remaining fully backward-compatible. The key additions at Level AA are: Focus Not Obscured (2.4.11), Dragging Movements (2.5.7), Target Size minimum of 24×24px (2.5.8), Consistent Help location (3.2.6), Redundant Entry prevention (3.3.7), and Accessible Authentication without cognitive puzzles (3.3.8). WCAG 2.2 also officially deprecated Criterion 4.1.1 Parsing (previously A level). Most legal standards now reference WCAG 2.1 AA, but auditing to WCAG 2.2 AA is best practice and future-proof.
Is a website accessibility audit legally required?In the US, ADA Title III applies to places of public accommodation, which courts have consistently extended to include commercial websites. There is no federal regulation specifying an exact technical standard, but WCAG 2.1 AA is the accepted benchmark in litigation. ADA Title II now mandates WCAG 2.1 AA compliance for state and local government websites, with an April 2026 deadline for most entities. The European Accessibility Act (EAA) has been enforceable since June 28, 2025, covering businesses providing digital services to EU customers. Section 508 governs federal agencies and contractors. Conducting regular audits and documenting remediation efforts constitutes a good-faith compliance defense.
How often should you audit your website for accessibility?The frequency depends on your site's update cadence. As a baseline: run automated scans at least monthly (or integrate into your CI/CD pipeline for every deployment), conduct comprehensive manual audits annually, and re-audit after any major redesign, new feature launch, CMS migration, or significant content overhaul. Sites with frequent updates — ecommerce, news, SaaS applications — benefit most from continuous automated monitoring combined with quarterly manual spot-checks of key user flows.
Do accessibility overlays and widgets make a site compliant?No. Accessibility overlays are tools that inject JavaScript to attempt to patch accessibility issues on top of an inaccessible site. They cannot replace code-level remediation and do not achieve WCAG conformance. In 2025, 456 ADA lawsuits (22.6% of all ADA web cases) targeted sites using overlay tools — demonstrating that overlays provide no legal protection. Courts and accessibility experts consistently reject overlays as a substitute for genuine accessible development. Real compliance requires fixing the underlying code.
What is a VPAT and when do I need one?A VPAT (Voluntary Product Accessibility Template) is a standardized document — completed as an Accessibility Conformance Report (ACR) — that describes how a product or website conforms to WCAG, Section 508, and EN 301 549. VPATs are typically required during enterprise procurement processes (especially for government contracts and higher education), in response to procurement questionnaires from regulated industries, and as formal documentation for EAA compliance. They are authored by trained accessibility specialists following a structured conformance evaluation methodology.
What accessibility testing should developers do before launch?Before any launch, developers should: (1) run axe DevTools or WAVE on all new pages and user flows, (2) complete keyboard-only navigation of the entire user flow, (3) test with at least one screen reader (NVDA + Chrome or VoiceOver on macOS/iOS), (4) verify all form inputs have labels, all images have appropriate alt text, and all interactive elements have visible focus indicators, (5) validate color contrast for all text elements, and (6) check mobile touch target sizes. Integrate axe-core into your CI/CD pipeline to catch regressions automatically.
The Bottom Line: Accessibility Auditing Is an Investment, Not a Cost
A website accessibility audit is the most direct path from legal exposure to legal protection — and from a site that excludes 15% of the global population to one that serves everyone. The 94.8% failure rate means your competitors are almost certainly non-compliant too. The organizations that invest in genuine accessibility auditing and remediation now will not only avoid costly litigation, they will capture the loyalty of 1.3 billion users with disabilities and establish a competitive differentiator that becomes more valuable with every new regulation.
Whether you start with a free automated scan, engage the Webability managed accessibility team for a comprehensive audit, or use our cost calculator to plan your remediation budget — the most important step is to start. Because every day a barrier exists on your website is a day someone can't use it.
Related Reading from Webability
- WCAG 2.2 Accessibility Standards: Complete 2026 Compliance Guide
- The 2026 Checklist for Website Accessibility
- Guide to Website Accessibility Compliance (WCAG 2.2) – 2026
- Master Screen Reader Testing for WCAG & UX
- 12 Best Accessibility Tools for Websites (2026 Tested)
- PDF Remediation: Your Guide to Accessible Documents
- 8 Best Practices for Alt Text: Boost SEO & Accessibility
- What is WCAG? — Webability WCAG Compliance Hub
- What is ADA? — ADA Website Compliance Guide
- European Accessibility Act (EAA) — Compliance Guide
Authoritative External Resources
Quick Questions
Tap to ask AI about this article
