ADA WEBSITE COMPLIANCE

Make your website accessible.
Reduce ADA website risk.

EqualAccess. finds and fixes the accessibility barriers that can prevent people with disabilities from using your website.

We combine automated analysis, expert manual testing, assistive technology, code-level remediation, verification, and clear documentation—without relying on a scanner or accessibility widget alone.

  • Manual Testing
  • Code-Level Remediation
  • Assistive Technology
  • Verification & Documentation
Tested. Remediated. Verified.
Documentation recorded
  1. 01Assess
  2. 02Manual Testing
  3. 03Code-Level Remediation
  4. 04Retest & Verify
  5. 05Documentation
Visual demo of human expert work, supported by testing tools. The example shows a keyboard barrier, missing form label, and contrast issue being corrected, retested, and documented. Scope and deliverables vary by project.

START WITH ACCESSIBILITY

ADA website compliance begins with whether people can actually use the website.

The Americans with Disabilities Act prohibits disability discrimination. For businesses open to the public, Title III requires equal access to the goods and services they offer.

DOJ’s longstanding position extends those obligations to online goods and services. Technical work focuses on removing barriers in how people access and use the website.

Official reference: DOJ guidance on web accessibility and the ADA.

Screen readers

Someone who is blind

Can important content and controls be understood and operated with a screen reader?

Keyboard access

Someone who cannot use a mouse

Can navigation, forms, menus, products, and checkout be completed with a keyboard?

Zoom & contrast

Someone with low vision

Can content be enlarged, reflowed, and understood with sufficient contrast?

Captions & media

Someone who is deaf or hard of hearing

Is important prerecorded media appropriately captioned where required?

Clear interactions

Someone with cognitive or learning disabilities

Are instructions, errors, interactions, and content understandable and predictable?

One website. Different ways to use it.
EVERYDAY ACCESSRead. Navigate.
Choose. Complete.
Keyboard Screen reader Zoom
Clear informationUnderstandable controlsAccessible next steps
A website people can use, in the way that works for them.

The goal is not simply a better scanner score.
The goal is a website people can use.

ADA ≠ WCAG

The ADA is the law.
WCAG is the technical accessibility standard.

These terms are often blended together, but they are not the same thing.

DOJ’s Title III guidance does not prescribe a detailed website technical standard for private businesses. It points to standards such as WCAG as guidance. Title II has a separate web and mobile rule for state and local governments.

WCAG—the Web Content Accessibility Guidelines—is W3C’s international technical standard for web accessibility. W3C encourages the latest version when an organization can choose its target.

Official reference: DOJ web accessibility guidance.

  1. ADA
    Civil-rights obligations

    The legal context

  2. WCAG
    Technical accessibility requirements

    A framework for evaluation

  3. Test + remediate + verify

    Practical accessibility work

Explore WCAG Compliance & Conformance

THE TECHNICAL TARGET

Use a clear accessibility standard
instead of guessing.

WCAG provides testable accessibility success criteria at Levels A, AA, and AAA. When a private organization is free to choose, WCAG 2.2 Level AA is a strong current technical target.

It builds on earlier versions and adds newer criteria. It is not a universal statutory requirement for every private-business website under ADA Title III.

  1. EARLIER WCAG 2 BASELINE2.0

    The foundation of the WCAG 2 series.

  2. BUILDS ON WCAG 2.02.1

    Adds criteria addressing mobile, low vision, and other accessibility needs.

  3. LATEST W3C RECOMMENDATION2.2

    Adds criteria for modern interactions, focus, input, and authentication.

Technical targetWCAG 2.2 AA, when appropriate

Applicable requirementConfirm the law, jurisdiction, agreement, or other requirement

Older WCAG versions remain existing standards. WCAG 2.2 removed 4.1.1 Parsing; engagements required to report against 2.0 or 2.1 may still need to address it. Read the W3C WCAG overview and WCAG 2.2 compatibility notes.

AUTOMATION + HUMAN TESTING

If accessibility were just a scan,
this would be much easier.

Automated analysis

Detect technical patterns

Find useful technical signals across the website.

Manual testing

Evaluate actual behavior

Review meaningful alt text, focus order, errors, and interactions.

Assistive technology

Understand what users receive

Evaluate names, roles, states, structure, and announcements.

User journeys

Test whether tasks can be completed

Follow the paths that matter to customers and visitors.

A much clearer accessibility picture.

Technology + human expertise

DOJ cautions that a clean automated report does not establish accessibility. W3C describes evaluation as a combination of automated testing and human judgment. See DOJ guidance and W3C conformance guidance.

THE WEBSITE EXPERIENCE

Accessibility problems can exist almost anywhere someone needs to interact.

  1. 01

    Navigation & Keyboard

    Main navigation, dropdowns, mobile menus, keyboard access, focus order, skip mechanisms, and keyboard traps.

  2. 02

    Forms & Errors

    Labels, required fields, instructions, validation, error identification, confirmation messages, and submission.

  3. 03

    Ecommerce

    Collections, filters, product options, quantity controls, cart, accounts, and checkout-related journeys.

  4. 04

    Content & Structure

    Headings, landmarks, lists, tables, links, page titles, semantic structure, and content relationships.

  5. 05

    Media

    Captions, transcripts, audio-description considerations, media controls, and prerecorded content where applicable.

Important parts of the experience
asterwyn.01 Navigation & menus
04 CLEAR CONTENT & STRUCTUREFind your everyday rhythm.
Ivory headphones in the illustrative product page
03 Product options
IvoryNavy
Cart & checkout
02 Forms & errors05 Captions & controls
Illustrative inspection map. The testing scope is agreed for your website.

Interactive Components

Modals, tabs, accordions, sliders, carousels, menus, popovers, filters, and custom controls.

Images & Icons

Alternative text, decorative images, informative graphics, icons, and visual-only information.

Visual Accessibility

Contrast, focus indicators, zoom, text spacing, reflow, responsive behavior, and information conveyed through color.

Assistive Technology

Accessible names, roles, states, values, dynamic updates, reading order, and screen-reader communication.

BEYOND INDIVIDUAL PAGES

An accessible homepage doesn’t help
if someone gets stuck at checkout.

Ecommerce: From finding the right product to receiving confirmation.

  1. 01Find product
  2. 02Choose options
  3. 03Add to cart
  4. 04Checkout
  5. 05Confirmation
Possible barriers to review
  • Inaccessible filters
  • Product swatches unavailable to keyboard users
  • Cart updates not announced
  • Inaccessible form errors
  • Poorly labelled checkout controls

Restaurant: From choosing a location to confirming a reservation.

  1. 01Find location
  2. 02Read menu
  3. 03Reserve
  4. 04Confirmation
Possible barriers to review
  • Menu PDFs
  • Navigation
  • Reservation widgets
  • Date pickers
  • Form errors

Services: From understanding an offering to submitting a request.

  1. 01Find service
  2. 02Understand offering
  3. 03Request quote
  4. 04Submit
Possible barriers to review
  • Unclear link purpose
  • Missing form labels
  • Keyboard barriers
  • Unannounced errors or confirmation

Healthcare: From finding a provider to completing a scheduling task.

  1. 01Find provider
  2. 02Read information
  3. 03Complete form
  4. 04Schedule
Possible barriers to review
  • Provider filters
  • Downloadable documents
  • Patient-facing forms
  • Third-party scheduling controls

We evaluate accessibility in the context of what your visitors are actually trying to accomplish.

WHAT THE WORK ACTUALLY LOOKS LIKE

We don’t stop at identifying the barrier.

Explore four illustrative examples, from the original barrier to the corrected component and verification.

Menu · illustrative component
BEFORE REMEDIATIONBarrier identified
AFTER RETESTINGIllustrative result: remediated & retested
EXCERPT OF THE COMPONENT CHANGE
<button aria-expanded="true"
  aria-controls="shop-links">Shop</button>

Partial markup for illustration. Complete behavior and testing depend on the component.

Conceptual comparison, not a live store or client result. Screen-reader output varies by browser and assistive technology.

A menu that works without a mouse.

Test
Open and operate the main navigation using only the keyboard, then check its name and expanded state with a screen reader.
Finding
A hover-only submenu cannot be opened from the keyboard.
User impact
Some visitors cannot reach the pages inside the menu.
Remediation
Use a native button, communicate the expanded state, and support keyboard opening, closing, and predictable focus.
Verify
Retest opening the menu, following its links, closing with Escape, and returning focus to the trigger.
Form · illustrative component
BEFORE REMEDIATIONBarrier identified
AFTER RETESTINGIllustrative result: remediated & retested
EXCERPT OF THE COMPONENT CHANGE
<label for="email">Email address</label>
<input id="email" aria-invalid="true"
  aria-describedby="email-error">

Partial markup for illustration. Complete behavior and testing depend on the component.

Conceptual comparison, not a live store or client result. Screen-reader output varies by browser and assistive technology.

An error a visitor can understand and correct.

Test
Submit a required field empty and inspect the visible label, error association, and focus behavior.
Finding
The field has no persistent label and the error is not associated with the input.
User impact
A visitor may not know what information is needed or why the form cannot continue.
Remediation
Provide a visible label, a clear error, a programmatic association, and appropriate invalid-state handling.
Verify
Retest invalid and valid entries, error correction, focus, and screen-reader output.
Product Option · illustrative component
BEFORE REMEDIATIONBarrier identified
AFTER RETESTINGIllustrative result: remediated & retested
EXCERPT OF THE COMPONENT CHANGE
<fieldset>
  <legend>Color</legend>
  <label><input type="radio" name="color"
    value="ivory" checked> Ivory</label>
</fieldset>

Partial markup for illustration. Complete behavior and testing depend on the component.

Conceptual comparison, not a live store or client result. Screen-reader output varies by browser and assistive technology.

Product options every customer can select.

Test
Use the product page with keyboard navigation and a screen reader.
Finding
Color swatches are clickable with a mouse but cannot be selected with the keyboard and do not expose their selected state.
User impact
Some customers may be unable to configure the product before adding it to the cart.
Remediation
Correct the component with appropriate interactive controls, accessible names, keyboard behavior, and programmatic selected states.
Verify
Retest product selection, Add to Cart, and related announcements with the keyboard and relevant assistive technology.
Modal · illustrative component
BEFORE REMEDIATIONBarrier identified
AFTER RETESTINGIllustrative result: remediated & retested
EXCERPT OF THE COMPONENT CHANGE
<dialog aria-labelledby="delivery-title">
  <h2 id="delivery-title">Delivery details</h2>
  <button>Close</button>
</dialog>

Partial markup for illustration. Complete behavior and testing depend on the component.

Conceptual comparison, not a live store or client result. Screen-reader output varies by browser and assistive technology.

A dialog with a clear way in and out.

Test
Open the dialog, follow the keyboard path, close it, and check where focus returns.
Finding
Focus moves behind the open dialog and the close control has no accessible name.
User impact
Visitors may lose their place or be unable to finish the task.
Remediation
Correct the dialog semantics, accessible name, focus entry, close behavior, and return path.
Verify
Retest keyboard entry, contained focus, closing, and focus returning to the original trigger.

FLEXIBLE ACROSS PLATFORMS

ADA website accessibility work is not limited to one platform.

EqualAccess. supports accessibility testing and remediation across a wide range of website technologies.

Whether your website is built on a common platform or a more custom implementation, we focus on the accessibility barriers affecting the experience and the most practical path to addressing them.

ADA WEBSITE REVIEWIllustrative
Website
yourwebsite.comExample
Platform
  • WordPress
  • Shopify
  • Custom
  • Other

Review focus

  • Accessibility barriers
  • Technical findings
  • Remediation path
  • Verification

Accessibility work can be scoped across many modern platforms.

Illustrative workflow. Scope is agreed per project.

COMMON PLATFORMS WE SUPPORT

  • Shopify
  • WordPress
  • WooCommerce
  • BigCommerce
  • Webflow
  • Squarespace
  • Wix
  • Custom Websites & Web Apps

Don’t see your platform? We may still be able to help.

Get a Free ReviewChoose a time on our calendar.

FROM FIRST REVIEW TO DOCUMENTED IMPROVEMENTS

A practical path from uncertainty
to verified improvements.

01

Assess

A clear starting point.

Identify the website, platform, important pages, templates, components, user journeys, and accessibility target. Automated analysis helps surface patterns to investigate.

OUTPUTDefined scope
Defined scope
Website & platform
Pages & templates
Critical user journeys
Target standard

Illustrative project record

The work is performed by human experts, supported by testing tools.
02

Manual Testing

Findings your team can act on.

Combine expert manual review, keyboard testing, and assistive technology with the automated findings. Prioritize barriers by user impact, important journeys, recurrence, technical dependencies, and remediation needs.

OUTPUTValidated findings & action plan
Validated findings & action plan
Reproduced barriers
Affected experiences
Technical requirements
Prioritized next steps

Illustrative project record

The work is performed by human experts, supported by testing tools.
03

Code-Level Remediation

Correct the underlying experience.

Address barriers in HTML, CSS, JavaScript, themes, templates, forms, components, and content where access and scope allow. Work directly in the site or coordinate with your developers.

OUTPUTAccessibility improvements
Accessibility improvements
Component corrections
Code & content updates
Developer coordination
Vendor limitations recorded

Illustrative project record

The work is performed by human experts, supported by testing tools.
04

Retest & Verify

Check that the change works.

Test corrected functionality again using the methods relevant to the original issue. Repeat important journeys and check for regressions in related components.

OUTPUTVerification results
Verification results
Keyboard retesting
Assistive technology review
Automated rechecks
Journey & regression checks

Illustrative project record

The work is performed by human experts, supported by testing tools.
05

Documentation

A record of the work.

Document the scope, findings, remediation, verification evidence, known limitations, and follow-up work so your team can understand the status and next steps.

OUTPUTAccessibility documentation
Accessibility documentation
Scope & findings
Remediation records
Verification evidence
Limitations & next actions

Illustrative project record

The work is performed by human experts, supported by testing tools.

Keep the improvements as the website changes. Ongoing monitoring, periodic testing, and support can follow the five-step engagement.

Explore ongoing support

FIX THE WEBSITE ITSELF

Accessibility problems usually require actual changes to the site.

EqualAccess. can move beyond recommendations and remediate accessibility barriers in the underlying website where access and scope allow.

That may involve HTML, CSS, JavaScript, themes, templates, forms, navigation, responsive behavior, content, and interactive components.

  • Keyboard navigation
  • Focus management
  • Accessible names
  • Form labels
  • Error handling
  • Semantic structure
  • Menus
  • Dialogs
  • Product controls
  • Contrast
  • Dynamic content
  • ARIA where appropriate

We focus on correcting the underlying experience.

Explore Code-Level Remediation
BEFORE · SOURCE COMPONENT<div onclick="addToCart()">
  Add to cart
</div>

A click handler alone does not provide native button semantics or keyboard behavior.

AFTER · CORRECTED CONTROL<button type="button"
  onclick="addToCart()">
  Add to cart
</button>
Native semantics + keyboard activation
Illustrative markup change. Cart updates, announcements, and the full journey still need implementation and retesting.

YOUR WEBSITE INCLUDES CODE YOU DIDN’T WRITE

A good theme can still inherit an inaccessible booking tool, app, or widget.

Reviews, chat, booking, payment tools, subscription apps, loyalty programs, maps, and embedded forms can introduce barriers into otherwise improved websites.

Determine
Is the issue genuinely in the third-party component?
Configure
Can settings or implementation changes improve it?
Document
What barrier remains?
Escalate
What does the provider need to fix?
Evaluate
Is a workaround or alternative necessary?
ReviewsIncluded in review
Booking toolBarrier remains open
Your website
The complete customer experience

Your code + third-party components

PaymentsCritical journey
Chat & supportKeyboard + screen reader
Configure · Escalate to vendor · Evaluate a workaround · Consider an alternative

We won’t mark a third-party barrier “fixed” when it still prevents access.

CLEAR TECHNICAL DELIVERABLES

Know what’s wrong, what was fixed,
and what still needs attention.

EqualAccess.ILLUSTRATIVE PROJECT RECORDAccessibility work.
Clearly documented.
Agreed scope · WCAG-based evaluation
Navigation componentRemediated & retested
Form labels and errorsRemediated & retested
Third-party booking widgetOpen · vendor action
Findings & fix notes Verification evidence Remaining limitations
Example record only. Deliverables are agreed for each engagement. Where procurement requires it, a scoped VPAT & ACR can be discussed.

Accessibility Assessment

A WCAG-based review of the agreed pages, components, templates, and user journeys.

Manual Testing

Human evaluation of keyboard behavior, content, interactions, forms, and requirements automation cannot reliably determine.

Assistive Technology Testing

Screen-reader and interaction testing relevant to the agreed scope.

Prioritized Findings

Validated issues with context, affected functionality, technical requirement, and recommended next step.

Code-Level Remediation

Technical accessibility fixes where included and technically possible.

Verification & Retesting

Corrected functionality tested again after remediation.

Accessibility Documentation

A record of scope, findings, remediation, verification, and known limitations.

Ongoing Support

Continued monitoring and accessibility support as the website changes.

COMMUNICATE THE WORK

Give visitors a clear way to understand your efforts and report a problem.

An accessibility statement can explain your organization’s accessibility efforts, identify a way for visitors to report difficulties, and provide relevant contact information.

It should reflect real accessibility work. It does not replace testing and remediation.

Official reference: DOJ guidance on accessibility feedback.

Accessibility statement · illustrative outline
YOUR ORGANIZATIONOur accessibility commitment
  1. 01Accessibility commitment
  2. 02Technical standard or goal
  3. 03Relevant testing information
  4. 04Known limitations, where appropriate
  5. 05A contact method for accessibility feedback
Publish an accurate statement and a working feedback route your team can monitor.

ALREADY FACING A CLAIM?

Proactive accessibility and active lawsuit support are different situations.

If a lawsuit or demand letter has already arrived, start with the specific technical allegations and coordinate the accessibility work with your legal team.

EqualAccess. can evaluate the reported barriers, test the broader website, remediate technical issues, verify the work, and provide documentation your team can use alongside counsel.

Your attorney handles the legal matter. EqualAccess. handles the website.
Get Priority Support

Focused technical support for an active claim.

KEEP THE IMPROVEMENTS

The website will keep changing after
the accessibility project ends.

New products, campaigns, apps, plugins, content, code releases, and third-party changes can introduce new accessibility barriers.

Ongoing reviews help your team notice changes, investigate their impact, and return new findings to the accessibility process.

Explore Ongoing Monitoring & Support

Official reference: W3C guidance on conformance and changing content.

Keep accessibility
in view.
As the website changes
  1. ReleaseNew content & code
  2. ReviewMonitor & investigate
  3. RespondRemediate & retest
  4. RecordDocument & follow up
Ongoing support applies the same five-stage process to new or recurring barriers.

KNOW WHICH PATH APPLIES

Private businesses and state or local governments do not follow exactly the same web rules.

PRIMARILY THE AUDIENCE FOR THIS PAGE

ADA Title III

Businesses and nonprofits that are public accommodations.

Generally relevant to
Examples include restaurants, hotels, retail stores, doctors’ offices, private hospitals, and private schools.
Website technical standard
DOJ’s general Title III website guidance does not prescribe a specific WCAG version in a detailed website regulation. Applicable obligations need legal review.

Official reference: DOJ: businesses open to the public.

STATE & LOCAL GOVERNMENT

ADA Title II

State and local government entities.

Relevant to
Government websites, programs, services, and mobile applications.
Website/mobile technical standard
DOJ’s rule specifies WCAG 2.1 Level AA, subject to the rule’s scope, exceptions, and compliance dates.
Explore ADA Title II Compliance

Official reference: DOJ Title II compliance guide.

ACCURATE EXPECTATIONS

Accessibility is technical work,
not a permanent badge.

A scanner score

Does not establish that the complete experience is accessible.

An overlay

Does not replace evaluating and correcting underlying barriers.

An “ADA certification” badge

Does not confer government-issued certification of a private website.

WCAG conformance

Does not guarantee that a business will never receive a legal claim.

A completed project

Does not mean a changing website will stay accessible forever.

WCAG conformance requires satisfying the applicable technical requirements, not reaching a percentage score. W3C does not verify organizations’ conformance claims; the content provider is responsible for them.

What was tested. What was found. What was fixed.
What was verified. What remains.

Official reference: W3C conformance claims.

PRACTICAL ADA WEBSITE ACCESSIBILITY

Built for businesses that need someone
to handle the actual work.

Ecommerce & Retail

Online stores, product interfaces, apps, and cart and checkout journeys.

Restaurants & Hospitality

Menus, reservations, ordering, location information, booking integrations, and downloadable content.

Healthcare & Dental

Service information, appointment forms, patient-facing content, documents, and scheduling tools.

Service Businesses

Marketing sites, quote forms, lead generation, client portals, booking, and customer-service experiences.

Growing Companies

Internal teams and agencies that need accessibility expertise, testing, or verification.

Businesses Already Remediating

Organizations with an audit or prior project that need help fixing or verifying remaining issues.

Implementing changes internally? Our Consulting & Training can support your developers, designers, and content team.

ADA WEBSITE COMPLIANCE FAQ

Common questions about
ADA website accessibility.

DOJ has consistently taken the position that ADA requirements apply to goods, services, privileges, programs, and activities offered through websites. Title III applies to businesses open to the public, while Title II applies to state and local governments.

DOJ's current Title III web guidance does not set a specific WCAG version as a detailed regulatory standard for private-business websites. WCAG is nevertheless the principal technical accessibility standard used to evaluate and improve web accessibility. Legal obligations can depend on the organization, jurisdiction, agreement, court order, or other applicable requirement.

If no specific requirement dictates another version, WCAG 2.2 Level AA is a strong current technical target. W3C encourages use of its latest WCAG version, and WCAG 2.2 was designed to remain backward compatible with earlier WCAG 2 versions.

No scanner can evaluate the entire accessibility experience. DOJ warns that a clean automated report does not necessarily mean everything is accessible, and W3C describes conformance evaluation as involving both automated testing and human evaluation.

Automated tools and overlays may detect or address certain issues, but they should not be treated as substitutes for evaluating and correcting underlying accessibility barriers. EqualAccess. focuses on testing and remediation in the website itself.

Yes, when remediation is included in scope and we have the necessary technical access. We can address accessibility issues in themes, templates, HTML, CSS, JavaScript, forms, navigation, components, and content where technically possible.

Usually not. Many accessibility barriers can be corrected within an existing website. Where a particular component or third-party integration cannot reasonably be remediated, we can help identify alternatives.

Yes. We can review an existing audit or issue list and determine whether the findings remain current and actionable. Additional testing may be necessary if the site has changed or the report does not provide sufficient technical detail.

Our accessibility testing can support websites and web applications across a wide range of technologies. Common platforms include Shopify, WordPress, WooCommerce, BigCommerce, Webflow, Squarespace, Wix, and custom websites and web applications.

When remediation is required, the exact approach depends on how the website is built and what technical access is available.

No accessibility provider can guarantee that technical remediation will prevent a legal claim. EqualAccess. provides technical accessibility services, not legal advice. Our work focuses on identifying barriers, correcting them, verifying the resulting experience, and helping maintain accessibility over time.

Important fixes should be retested. Websites that change regularly may also benefit from ongoing monitoring, periodic manual review, developer support, and accessibility checks around major releases.

That requires a more focused workflow. EqualAccess. can review the allegations, test the relevant website functionality, remediate accessibility barriers, verify the work, and work alongside your legal team on the technical side.

ADA Website Lawsuit Support

Official guidance: DOJ web accessibility and the ADA, W3C WCAG overview, and W3C conformance evaluation.

START WITH THE WEBSITE

Find the barriers. Fix what matters.
Build a clearer path forward.

Tell us about your website and what prompted the accessibility review. We’ll help you understand what should be tested, what needs to be fixed, and how to move from accessibility issues to verified improvements.

Already have an audit, accessibility report, demand letter, or issue list? We can start by reviewing the work you already have.

Opens in a new tab.