ADA Guides and Checklists for ADA Website Compliance

Title III of the ADA requires places of public accommodation to provide equal access. Courts interpret that to include websites when those sites offer goods or services.

Compliance in practice usually means:

• Conformance with WCAG 2.1 Level AA
• Manual testing with keyboard and screen reader
• Ongoing monitoring

Automated scans alone are not enough. Most automated tools detect roughly 20–30% of WCAG issues. The rest require manual review.

That limitation matters. Businesses often believe installing a plugin equals compliance. It does not.

guide 1: basic wcag 2.1 aa overview for business owners

WCAG is organized around four principles:

• Perceivable
• Operable
• Understandable
• Robust

In plain language:

• Content must be visible or readable in different formats.
• Users must be able to operate the site without a mouse.
• Content must be clear and predictable.
• Code must work with assistive technologies.

Level AA is what most legal settlements require.

high-level wcag 2.1 aa checklist

Use this as a first-pass review:

• All images have meaningful alt text or empty alt for decorative images.
• Text contrast ratio is at least 4.5:1 for normal text, 3:1 for large text.
• All functionality works with keyboard only.
• Visible focus indicator appears when tabbing.
• Headings follow logical order (h1 → h2 → h3).
• Forms have programmatically associated labels.
• Error messages are clearly identified and announced.
• Videos include accurate captions.
• PDFs are tagged and accessible.
• No auto-playing content without pause controls.

This is not exhaustive. It covers the failures most often cited in complaints.

guide 2: homepage accessibility checklist

The homepage is often the first page plaintiffs test. It usually contains:

• Hero banners
• Promotional images
• Navigation menus
• Call-to-action buttons

homepage checklist

Images

• Hero images have descriptive alt text if they convey information.
• Decorative background images use CSS or empty alt attributes.

Navigation

• All menu items are reachable via keyboard.
• Dropdown menus open and close using keyboard controls.
• Skip link is present (“Skip to main content”).

Color and typography

• Body text contrast meets 4.5:1 ratio.
• Links are distinguishable from surrounding text.
• Text can resize to 200% without breaking layout.

Interactive elements

• Buttons have accessible names (“Schedule Appointment” instead of “Click Here”).
• Focus outline is visible and not removed in CSS.

Common failure: designers remove focus outlines using outline: none; and never replace them. That violates WCAG 2.4.7 (Focus Visible).

guide 3: forms and appointment booking checklist

Forms generate the highest risk because they directly affect access to services.

A 2023 demand letter sent to a Florida dental practice cited a single issue: the online booking form used placeholder text instead of labels. When users typed into the field, the placeholder disappeared. Screen readers never announced field purpose.

forms checklist

Labels

• Every input field has a <label> associated with it using the for attribute.
• Placeholder text is not used as the only label.

Instructions

• Required fields are clearly identified both visually and programmatically.

Errors

• Errors are announced to screen readers.
• Error messages explain what went wrong and how to fix it.

Keyboard

• Users can move through all fields using Tab and Shift+Tab.
• Date pickers and dropdowns are operable without a mouse.

Time limits

• Forms with timeouts provide warnings and allow extensions.

Third-party tools

• Embedded scheduling tools are tested independently.
• If an iframe is used, confirm the vendor meets WCAG 2.1 AA.

Trade-off: replacing a booking system may cost thousands of dollars. Leaving it inaccessible can trigger legal action.

guide 4: content and structure checklist

Search engines and screen readers both rely on structure.

heading structure checklist

• Only one <h1> per page describing the main topic.
• Headings follow logical order without skipping levels.
• Headings are not used purely for visual styling.

link text checklist

• Links describe destination (“Download patient intake form PDF”).
• Avoid vague text like “Click here.”

lists and tables checklist

• Lists are coded using <ul> or <ol>, not just visually styled paragraphs.
• Tables use proper header cells <th> with scope attributes.

A law firm website I reviewed in California had 18 visual headings on its homepage. Only two were coded as headings. Screen reader navigation was almost useless.

This is basic HTML. It still gets missed.

guide 5: images and media checklist

Visual content is common. It’s also a frequent source of violations.

images checklist

• Informational images include descriptive alt text.
• Charts and infographics include text alternatives explaining data.
• Decorative images use alt="".

Alt text should describe function, not appearance alone.

Bad example:
“Image of dentist.”

Better example:
“Dr. Maria Lopez performing dental implant procedure in Dallas office.”

video checklist

• Pre-recorded videos include synchronized captions.
• Captions are accurate, not auto-generated with high error rates.
• Audio descriptions are provided if visual-only information is essential.
• Auto-play videos have pause controls.

Captioning costs money. Rev.com charges about $1.50 per minute. For a 20-minute webinar, that’s $30. Businesses skip it. Plaintiffs do not.

guide 6: keyboard accessibility checklist

Many accessibility failures show up when using only the keyboard.

keyboard testing guide

1. Unplug your mouse.
2. Use Tab to move forward.
3. Use Shift+Tab to move backward.
4. Use Enter or Space to activate buttons.

Check for:

• All links and buttons reachable.
• No keyboard traps.
• Clear focus indicator.
• Modals that trap focus correctly.

Common failure: modal windows that open visually but do not shift keyboard focus inside the modal.

WCAG 2.1.1 requires all functionality to be operable through a keyboard interface.

guide 7: color contrast checklist

WCAG 2.1 AA contrast requirements:

• 4.5:1 for normal text.
• 3:1 for large text (18pt or 14pt bold).

contrast testing steps

• Use WebAIM Contrast Checker.
• Test body text against background.
• Test buttons and call-to-action text.
• Test error messages in red text.

A cosmetic dentistry site I audited in 2023 used light gray (#A0A0A0) on white. Contrast ratio around 2.7:1. Non-compliant.

After updating to darker gray, readability improved. That’s not theory. Analytics showed lower bounce rate.

guide 8: pdf accessibility checklist

PDFs are frequently overlooked.

accessible pdf checklist

• Text is selectable (not scanned image only).
• Document includes tagged structure.
• Headings are defined.
• Form fields are labeled.
• Reading order is logical.

If remediation is too expensive for legacy PDFs, convert key documents to accessible HTML pages.

Limitation: retrofitting hundreds of PDFs can cost thousands of dollars. Many organizations prioritize high-traffic documents first.

guide 9: mobile accessibility checklist

More than half of web traffic for local businesses often comes from mobile devices.

mobile checklist

• Content reflows without horizontal scrolling at 320px width.
• Buttons are large enough to tap.
• Text scales up to 200% without overlapping.
• No essential content hidden behind hover-only interactions.

WCAG 1.4.10 (Reflow) applies here.

Fixed-width layouts fail immediately on small screens with zoom enabled.

guide 10: accessibility statement checklist

An accessibility statement does not create compliance. It documents intent and process.

accessibility statement should include

• Commitment to meeting WCAG 2.1 AA.
• Date of last audit.
• Contact method for accessibility issues (email and phone).
• Process for responding to complaints.

Avoid vague language. Include real dates.

Example:

“Last audited: March 12, 2025.
Standard: WCAG 2.1 Level AA.”

Statements without real audit dates look performative.

internal workflow checklist for ongoing compliance

Accessibility fails when content updates ignore standards.

internal process checklist

• Train staff who upload content.
• Include alt text fields in CMS workflow.
• Require contrast checks before publishing graphics.
• Test new plugins before deployment.
• Schedule annual manual audits.

Accessibility is not one project. It’s maintenance.

limitations of automated accessibility tools

Automated scanners such as WAVE, Axe, and Lighthouse detect missing alt attributes and contrast errors. They do not reliably detect:

• Poorly written alt text.
• Logical heading misuse that is technically valid but confusing.
• Keyboard traps.
• Contextual comprehension issues.

Most comprehensive audits combine automated scanning with manual testing and assistive technology testing.

Blind users often use screen readers like NVDA or JAWS. Testing with these tools reveals issues scanners miss.

cost planning checklist

Budget realistically.

Typical cost ranges for small to mid-size sites:

• Manual audit: $2,500 to $7,500.
• Remediation: $3,000 to $20,000 depending on complexity.
• Annual monitoring: $1,000 to $5,000.

Demand letter settlement:

• $8,000 to $25,000 attorney fees common in smaller cases.
• Additional remediation required.

Costs vary. These ranges reflect common patterns in small business litigation contexts.

example remediation workflow

A two-location dental practice in New York received a complaint in late 2023. Issues identified:

• Missing form labels.
• Low contrast text.
• Inaccessible PDF intake form.
• No skip navigation link.

Remediation steps:

1. Conducted manual WCAG 2.1 AA audit.
2. Rebuilt booking form with proper labels.
3. Updated color palette for contrast compliance.
4. Converted PDF intake form to accessible HTML version.
5. Published accessibility statement.
6. Scheduled annual review.

The cost of remediation was lower than the settlement demand. The work could have been done before the complaint.

consolidated master ada website compliance checklist

Use this master checklist for a structured internal review.

Perceivable

• Alt text present and meaningful.
• Captions for video.
• Contrast ratios meet 4.5:1 standard.
• Content adaptable to screen readers.

Operable

• Keyboard-only navigation works site-wide.
• Focus indicator visible.
• No keyboard traps.
• Skip link present.

Understandable

• Forms labeled.
• Errors clearly identified.
• Navigation consistent across pages.
• Language declared in HTML (<html lang="en">).

Robust

• Proper semantic HTML.
• ARIA used correctly when necessary.
• Compatible with screen readers.

Document findings. Track fixes. Retest.

final operational reality

ADA website compliance is not abstract. It is technical and procedural. Most violations involve basic HTML structure, form labeling, contrast ratios, and keyboard functionality.

Free guides and checklists like the ones above cover the failures most commonly cited in complaints and settlement agreements. They do not replace a full audit. They do provide a structured baseline.

Accessibility compliance is measurable against WCAG 2.1 Level AA. Either code passes or it does not. Businesses that treat accessibility as a documented process reduce legal exposure and create websites that function for more users.

That is the operational standard.