ADA Compliant Website Design — WCAG 2.1 AA Standard on Every Build
We treat accessibility as an engineering baseline, not a compliance checkbox. Every Hawd Design build meets WCAG 2.1 Level AA as standard. For existing sites that fall short, we audit and remediate — protecting you from ADA litigation while making your site genuinely better for every user.
What Is ADA Website Compliance — and Is Your Business Required to Have It?
ADA website compliance refers to the requirement under Title III of the Americans with Disabilities Act that businesses providing public-facing services make those services accessible to people with disabilities — including through their websites. The standard applied by US courts is WCAG 2.1 Level AA (Web Content Accessibility Guidelines, version 2.1, conformance level AA), published by the W3C. A WCAG 2.1 AA-compliant website meets minimum requirements for colour contrast, keyboard navigation, screen reader compatibility, visible focus indicators, and form accessibility. Under current DOJ guidance and settled case law, most commercial websites in the US — including e-commerce, healthcare, legal, financial services, and hospitality — are subject to ADA Title III. Non-compliance exposes businesses to demand letters and federal lawsuits, with average settlement and legal costs running $25,000–$150,000+. Hawd Design builds WCAG 2.1 AA-compliant websites as standard. Standalone audits for existing sites are available from €490.
Legal Framework
Title III of the Americans with Disabilities Act requires businesses providing public-facing services to make those services accessible — including digital properties. US courts have consistently applied this to commercial websites.
Technical Standard
The Department of Justice and federal courts apply WCAG 2.1 Level AA as the operative technical standard. Meeting WCAG 2.1 AA is the legally recognised path to ADA website compliance.
Federal Procurement
Federal agencies and organisations receiving federal funding are subject to Section 508 of the Rehabilitation Act, which references the same WCAG standards. We produce VPAT / ACR documentation for procurement.
ADA Website Lawsuits — The Risk Is Real and Growing
The number of ADA Title III website accessibility lawsuits filed in US federal courts has increased significantly every year since 2017. Specialty plaintiffs' law firms have institutionalised the practice of scanning business websites for WCAG failures using automated tools — identifying dozens or hundreds of potential defendants simultaneously.
E-Commerce Businesses
Product image alt text failures, inaccessible checkout flows, and colour contrast failures in price displays are among the most common automated findings. Online retail is the highest-volume target category for ADA demand letters.
E-Commerce Web DesignHealthcare Providers
Patient portal and appointment booking inaccessibility, form label failures, and PDF accessibility are primary vectors. Healthcare websites face dual compliance requirements: ADA accessibility plus HIPAA-aware data handling.
Web Design for HealthcareLaw Firms & Professional Services
Law firm websites are disproportionately targeted by ADA litigation, partly because they are expected to understand legal obligations. Attorney biography navigation, contact form inaccessibility, and PDF accessibility are frequently cited.
Web Design for Law FirmsFinancial Services & Hospitality
Inaccessible calculator tools, PDF disclosures, and account management interfaces expose financial services firms. For hospitality businesses, online reservation systems, menu PDFs, and photo gallery accessibility are common targets.
| Scenario | Typical Cost | Outcome |
|---|---|---|
| WCAG 2.1 AA built into a new Hawd Design website | Included as standard | Full compliance from launch · no litigation exposure |
| Remediation of an existing non-compliant website | €800–€4,500 | Specific WCAG failures resolved · exposure eliminated |
| ADA demand letter — settlement + legal costs | $25,000–$150,000+ | Site may still require remediation after settlement |
| ADA litigation — defending to verdict (even when successful) | $50,000–$200,000+ | Reputational cost · plaintiff likely appeals |
Additional benefit: Accessible websites rank better in organic search, convert better on mobile, and reach a larger audience — approximately 26% of US adults have some form of disability.
What WCAG 2.1 AA Compliance Actually Requires — The Technical Checklist
WCAG 2.1 is organised around four principles: Perceivable, Operable, Understandable, and Robust. Below is a plain-language summary of the Level AA success criteria most commonly tested in ADA litigation and accessibility audits.
Information Must Be Presentable to All Users
- Colour contrast (SC 1.4.3): Normal text must have a minimum 4.5:1 contrast ratio against its background. Large text (18pt or 14pt bold) must meet 3:1. Interactive UI components must meet 3:1.
- Text alternatives (SC 1.1.1): All informative images must have descriptive alt text. Decorative images must have empty alt attributes. Complex images require a long description.
- Captions (SC 1.2.2): All pre-recorded video content must have synchronised captions. Live video must have captions where content is critical.
- Resize text (SC 1.4.4): Text must be resizable to 200% without loss of content or functionality — no horizontal scrolling required.
- Reflow (SC 1.4.10): Content must reflow to a single column at a viewport width of 320 CSS pixels — effectively a mobile-first responsiveness requirement.
- Non-text contrast (SC 1.4.11): UI component borders, focus indicators, and graphical objects must meet 3:1 contrast against adjacent colours.
- Text spacing (SC 1.4.12): Content must remain functional when line height is set to 1.5× the font size, letter spacing to 0.12em, and word spacing to 0.16em.
All Functionality Must Be Keyboard Accessible
- Keyboard accessible (SC 2.1.1): All functionality must be operable using a keyboard alone. No keyboard traps permitted.
- Focus order (SC 2.4.3): Focus order must be logical and sequential — top to bottom, left to right in standard reading order. Skip navigation links required.
- Focus visible (SC 2.4.7): All keyboard-focusable elements must have a clearly visible focus indicator. Default browser focus outlines must not be removed without providing a more visible custom alternative.
- Link purpose (SC 2.4.4): Link text must describe the destination or purpose. "Click here" and "Read more" are non-compliant without accessible names or context.
- Bypass blocks (SC 2.4.1): A "Skip to main content" link must be provided to allow keyboard users to bypass repetitive navigation.
- Pointer targets (SC 2.5.5): Interactive touch targets must be a minimum of 44×44 CSS pixels — aligned with Apple's HIG and Google Material Design.
Content and Interface Must Be Comprehensible
- Language of page (SC 3.1.1): The page
langattribute must correctly identify the language of the page content. - On focus / on input (SC 3.2.1–3.2.2): Focus events and data input must not trigger unexpected context changes — e.g., submitting a form when a select element is changed.
- Error identification (SC 3.3.1–3.3.3): Form errors must be described in text (not colour alone), associated programmatically with the relevant input, and accompanied by a suggestion for correction where possible.
- Labels or instructions (SC 3.3.2): All form inputs must have visible labels, programmatically associated via
<label for="">or ARIA.
Content Must Be Parsed Reliably by Assistive Technologies
- Parsing (SC 4.1.1): HTML must be valid and well-formed. No duplicate IDs, unclosed elements, or improperly nested tags.
- Name, Role, Value (SC 4.1.2): All UI components must have an accessible name (via
<label>,aria-label, oraria-labelledby), a role (via semantic HTML orroleattribute), and appropriate state/property values. - Status messages (SC 4.1.3): Dynamic status messages must be programmatically determinable via ARIA live regions so screen readers announce them without requiring focus change.
Accessibility Services — Audits, Remediation & New Builds
Whether you need WCAG compliance built into a new website from scratch, a formal audit of an existing site, or targeted remediation — we cover the full spectrum.
Accessibility Built Into Every New Build
Every website and e-commerce store we build meets WCAG 2.1 AA as a baseline — not as an optional add-on. There is no accessibility surcharge. It is standard.
Colour & Contrast
Colour palette tested against WCAG contrast requirements in Figma before the design is approved. All text and UI components verified.
Semantic HTML Structure
Proper heading hierarchy, landmark roles, list markup, and table structure from the outset — not bolted on after launch.
Keyboard & Screen Reader
All interactive elements keyboard-operable by design. Pre-launch testing with NVDA on Windows and VoiceOver on macOS/iOS.
- Automated audit (Axe + WAVE) — up to 20 pages
- Manual keyboard navigation test
- Screen reader test (NVDA + Chrome)
- WCAG 2.1 success criterion mapping
- Prioritised remediation report
- Accessibility Statement template
- Preliminary ACR / VPAT 2.4 structure
- Fee credited against remediation project
- Essential €800–€1,500: Contrast, alt text, form labels, skip links, focus indicators
- Extended €1,500–€3,500: Essential + ARIA roles, heading structure, keyboard trap resolution
- Full sprint €3,500–€6,000: Complete WCAG 2.1 AA pass on all pages
- Post-remediation audit to verify fixes
- Hour-by-hour scope per audit report
- Structural rebuild scoped individually
- Automated scan of all tracked URLs (Axe API)
- Monthly accessibility score reporting
- Critical WCAG failure alerts within 48 hours
- Annual full manual audit (prepaid annual plan)
- Core Web Vitals reporting included
Our Accessibility Testing Toolkit
We use a multi-layer testing methodology because no single tool catches all WCAG violations. Automated tools typically catch 30–40% of WCAG failures — manual testing is essential for the rest.
| Tool | Type | What It Tests |
|---|---|---|
| Axe (Deque) | Automated | 55+ WCAG 2.1 rules; high accuracy, low false positives |
| WAVE (WebAIM) | Automated | Visual feedback on errors, alerts, and structural elements |
| Lighthouse (Google) | Automated | Accessibility score + core violations with repair guidance |
| Colour Contrast Analyser | Manual | Precise WCAG contrast ratio verification for any colour pair |
| NVDA + Chrome | Screen reader | Real-world screen reader behaviour on Windows |
| VoiceOver + Safari | Screen reader | Real-world screen reader behaviour on macOS and iOS |
| Keyboard-only navigation | Manual | Full site navigation and form completion without mouse |
| Mobile browser testing | Manual | Touch target sizing, reflow, and focus behaviour on iOS/Android |
ADA & WCAG Compliance — Your Questions Answered
Common questions from clients evaluating ADA compliance services.
Do accessibility overlays like accessiBe or UserWay make a website ADA compliant?
No — and using them may increase your legal risk rather than reduce it. Overlay tools inject JavaScript that attempts to modify the rendered page for assistive technologies, but they do not fix the underlying HTML. Major disability advocacy organisations including the National Federation of the Blind have publicly opposed overlay tools, citing evidence that they actively interfere with screen reader software.
Multiple plaintiffs' firms have successfully argued that a website using an overlay is still non-compliant under ADA. The only reliable path to WCAG 2.1 AA compliance is fixing the underlying code.
We already passed a Lighthouse accessibility score of 95+. Are we compliant?
No. Google Lighthouse's accessibility audit catches approximately 30% of WCAG 2.1 AA failures — specifically those detectable by automated parsing. A score of 95/100 on Lighthouse means your site passes automated checks, which is a good start, but it does not mean you have no WCAG violations.
Keyboard navigation issues, screen reader compatibility problems, logical focus order failures, and many colour contrast edge cases cannot be detected by automated tools. A manual audit is required for any claim of WCAG 2.1 AA conformance.
How long does accessibility remediation take?
For essential fixes (colour contrast, alt text, form labels, skip links, focus indicators) on a standard 10–20 page website: typically 2–3 weeks from audit delivery to post-remediation verification. For extended or structural remediation, timelines depend on the volume and severity of failures identified in the audit.
We document the estimated hours for each remediation item in the audit report so you can prioritise within your budget.
Is a VPAT required for government contract procurement?
US federal agencies and many state agencies require vendors to provide a Voluntary Product Accessibility Template (VPAT) — specifically a completed Accessibility Conformance Report (ACR) — as part of procurement. We produce an ACR based on the VPAT 2.4 structure as part of our full audit deliverables. For enterprise clients with specific federal procurement requirements, we scope the ACR accordingly.
Does WCAG 2.1 AA compliance affect SEO?
Yes, positively. Many WCAG 2.1 AA requirements directly overlap with Google's quality signals: descriptive alt text supports image indexing, semantic HTML heading structure supports content comprehension, descriptive link text reduces ambiguity for crawlers, fast-loading and mobile-optimised pages improve Core Web Vitals scores, and page language declaration helps Google serve the right locale to the right searcher.
An accessible website is a technically better website — for users and for search engines.
Go Deeper on ADA & WCAG Compliance
Book a Free Consultation
Tell us your website URL and your compliance situation. We'll respond within 24 hours with a preliminary assessment and recommended next steps.
Request a Free Accessibility Audit
We'll run a free preliminary scan and respond within 1 business day.