Manual WCAG 2.1 Accessibility Audit

A full human-reviewed WCAG 2.1 Level AA audit — keyboard, screen reader, contrast, forms, ARIA — with a prioritized remediation report that your developers can actually use.

Start with a Free Automated Audit

What's Included

  • Full WCAG 2.1 Level AA review by a certified accessibility specialist
  • Keyboard navigation and screen reader testing
  • Color contrast analysis across all page and component states
  • Form, error handling, and ARIA review
  • Prioritized remediation report with code-level guidance
  • Executive summary suitable for compliance documentation and legal review

Who This Is For

  • Legal and healthcare organizations
  • Schools and universities
  • Government agencies
  • Any organization subject to ADA Title III or Section 508
Start with a Free Automated Audit

The Numbers, Plainly

Web accessibility isn't a niche concern. These numbers have been consistent for years.

95.9%

Of the top 1 million websites have detectable WCAG failures.

Source: WebAIM Million Report, 2024

4,000+

ADA website lawsuits filed in U.S. courts in 2024 alone.

Source: Seyfarth Shaw / Accessibility.Works

77%

Of ADA lawsuits in 2023 targeted companies with under $25M in revenue.

Source: AudioEye / ADA Site Compliance

$75,000

Maximum DOJ fine for a first ADA Title III violation. Subsequent violations: $150,000.

Source: DOJ ADA Title III

The Most Common Failures Are Also the Most Preventable

According to WebAIM's annual analysis of one million websites, 96.4% of all detected errors fall into six categories. These aren't obscure edge cases — they're basic oversights with real consequences.

Low Color Contrast

Found on 81% of homepages. Text that doesn't meet WCAG 1.4.3 contrast ratios is one of the first things auditors and plaintiff's attorneys look for — because it's easy to prove and impossible to argue around.

Missing Alt Text

Images without descriptive alternative text are invisible to screen reader users. It's a WCAG 1.1.1 violation and one of the most cited failures in ADA complaints.

Empty Links

A link with no discernible text gives assistive technology users zero context about where they're going. WCAG 2.4.4 requires that every link make sense on its own.

Missing Form Labels

Unlabeled form fields are unusable for screen reader users — a violation of WCAG 1.3.1 and 4.1.2. If your contact form, intake form, or booking tool isn't labeled, it's a barrier.

Missing Document Language

A missing or incorrect `lang` attribute on the HTML element causes screen readers to mispronounce or skip content. WCAG 3.1.1. One attribute.

Empty Buttons

Buttons with no accessible name are functionally invisible to users relying on keyboard navigation or assistive tech — a violation of WCAG 4.1.2.

Automated scanning catches some of these. A manual audit catches all of them — plus the failures no tool can detect.

Cases That Shaped the Landscape

These aren't cautionary tales pulled from a compliance brochure. They're the cases that established the precedents your organization operates under today.

Robles v. Domino's Pizza

The landmark that changed everything

A blind man was unable to order pizza online because Domino's website and app didn't support screen readers. The case went all the way to the U.S. Supreme Court, which declined to hear Domino's appeal — establishing that the ADA applies to websites and mobile apps. After six years of litigation across three court levels, Domino's settled in 2022.

The trigger: Missing alt text on a pizza ordering app. Six years of litigation.

National Federation of the Blind v. Target

$6 million. Class action. A household name.

Target's website was inaccessible to blind users — no alt text on product images, inaccessible checkout, broken screen reader navigation. The settlement was $6 million and required Target to bring its entire digital presence into compliance.

The trigger: Inaccessible e-commerce flow. Screen reader users couldn't complete a purchase.

NAD v. Netflix

Captions aren't optional — even on-demand.

The National Association of the Deaf sued Netflix for failing to provide closed captions on streaming content. A Massachusetts judge ruled that online services are not exempt from ADA requirements. Netflix settled for $755,000 in attorney fees and committed to captioning all content within two years.

The trigger: Missing captions on streaming content. The outcome extended ADA to digital-only services.

Conner v. Parkwood Entertainment (Beyoncé)

No organization is too big — or too small.

Beyoncé's official website was sued for being inaccessible to blind users. Settlement estimates ranged from $10,000–$50,000. The case illustrates that brand recognition offers zero legal protection.

The trigger: Inaccessible website structure. Beyoncé's team settled quickly and relaunched an accessible site.

H&R Block

Even your tax preparer isn't exempt.

H&R Block settled a DOJ-led case for $1.2 million after its website and tax preparation tools were found inaccessible to users with disabilities. The DOJ specifically cited WCAG 2.0 Level AA as the required remediation standard.

The trigger: Inaccessible web application that blocked screen reader users from completing returns online.

What Happens After a Complaint

  1. A complaint is filed — by a user, an advocacy group, or plaintiff's counsel
  2. DOJ investigation opens, or the lawsuit proceeds in federal or state court
  3. Discovery begins — your development history, audit logs, and remediation records become part of the record
  4. Settlement negotiations or trial
  5. Court-ordered WCAG compliance, plus attorney fees, plus damages

Average settlements range from $5,000 to $75,000. Legal fees frequently exceed the settlement. A manual audit costs less than either — and creates a documented record of good-faith remediation effort.

What You Walk Away With

Not a raw scan export. Not a list of criteria numbers with no context. A document built for developers, decision-makers, and — when it matters — legal teams.

Prioritized Issue Report

Every WCAG failure ranked by severity and real-world impact. Your team knows exactly what to fix first — and why.

Code-Level Remediation Guidance

Not just "this is broken." Here's the fix, written for the developer who has to implement it.

Executive Summary

Plain-language findings for stakeholders and legal counsel. Documents your remediation intent in a format that holds up in court.

Retest Eligibility

After remediation, I'll verify your fixes and update your documentation.

Prefer to hand off the fixes entirely? I can implement them directly. Ask about remediation when you request your audit.

Want to know what's actually there?

Start with a free automated audit. I'll show you what the scan finds before you decide on next steps.