Screen readers
Someone who is blind
Can important content and controls be understood and operated with a screen reader?
ADA WEBSITE COMPLIANCE
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.
START WITH ACCESSIBILITY
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.
Someone who is blind
Can important content and controls be understood and operated with a screen reader?
Someone who cannot use a mouse
Can navigation, forms, menus, products, and checkout be completed with a keyboard?
Someone with low vision
Can content be enlarged, reflowed, and understood with sufficient contrast?
Someone who is deaf or hard of hearing
Is important prerecorded media appropriately captioned where required?
Someone with cognitive or learning disabilities
Are instructions, errors, interactions, and content understandable and predictable?
The goal is not simply a better scanner score.
The goal is a website people can use.
ADA ≠ WCAG
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.
The legal context
A framework for evaluation
Practical accessibility work
THE TECHNICAL TARGET
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.
The foundation of the WCAG 2 series.
Adds criteria addressing mobile, low vision, and other accessibility needs.
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
Find useful technical signals across the website.
Review meaningful alt text, focus order, errors, and interactions.
Evaluate names, roles, states, structure, and announcements.
Follow the paths that matter to customers and visitors.
A much clearer accessibility picture.
Technology + human expertiseDOJ 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
Main navigation, dropdowns, mobile menus, keyboard access, focus order, skip mechanisms, and keyboard traps.
Labels, required fields, instructions, validation, error identification, confirmation messages, and submission.
Collections, filters, product options, quantity controls, cart, accounts, and checkout-related journeys.
Headings, landmarks, lists, tables, links, page titles, semantic structure, and content relationships.
Captions, transcripts, audio-description considerations, media controls, and prerecorded content where applicable.

Modals, tabs, accordions, sliders, carousels, menus, popovers, filters, and custom controls.
Alternative text, decorative images, informative graphics, icons, and visual-only information.
Contrast, focus indicators, zoom, text spacing, reflow, responsive behavior, and information conveyed through color.
PDFs and other downloadable content where included in scope. PDF & Document Remediation
Accessible names, roles, states, values, dynamic updates, reading order, and screen-reader communication.
BEYOND INDIVIDUAL PAGES
We evaluate accessibility in the context of what your visitors are actually trying to accomplish.
WHAT THE WORK ACTUALLY LOOKS LIKE
Explore four illustrative examples, from the original barrier to the corrected component and verification.
Submenu only appears on hover.
Enter opens · Tab reaches links · Esc closes
<button aria-expanded="true"
aria-controls="shop-links">Shop</button>Partial markup for illustration. Complete behavior and testing depend on the component.
The error does not identify the field or explain the correction.
Enter an email address in the format name@example.com.
LABEL + ERROR + FIELD ASSOCIATION<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.
Mouse-only swatches.
No accessible name or selected state.
Keyboard selection and state communication retested.
<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.
The keyboard focus is behind this dialog.
Focus stays in the open dialog and returns to its trigger on close.
<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.
FLEXIBLE ACROSS PLATFORMS
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.
Review focus
Accessibility work can be scoped across many modern platforms.
COMMON PLATFORMS WE SUPPORT
Don’t see your platform? We may still be able to help.
FROM FIRST REVIEW TO DOCUMENTED IMPROVEMENTS
Identify the website, platform, important pages, templates, components, user journeys, and accessibility target. Automated analysis helps surface patterns to investigate.
Illustrative project record
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.
Illustrative project record
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.
Illustrative project record
Test corrected functionality again using the methods relevant to the original issue. Repeat important journeys and check for regressions in related components.
Illustrative project record
Document the scope, findings, remediation, verification evidence, known limitations, and follow-up work so your team can understand the status and next steps.
Illustrative project record
Keep the improvements as the website changes. Ongoing monitoring, periodic testing, and support can follow the five-step engagement.
Explore ongoing supportFIX THE WEBSITE ITSELF
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.
We focus on correcting the underlying experience.
Explore Code-Level Remediation<div onclick="addToCart()">
Add to cart
</div>A click handler alone does not provide native button semantics or keyboard behavior.
<button type="button"
onclick="addToCart()">
Add to cart
</button>Native semantics + keyboard activationYOUR WEBSITE INCLUDES CODE YOU DIDN’T WRITE
Reviews, chat, booking, payment tools, subscription apps, loyalty programs, maps, and embedded forms can introduce barriers into otherwise improved websites.
Your code + third-party components
We won’t mark a third-party barrier “fixed” when it still prevents access.
CLEAR TECHNICAL DELIVERABLES
A WCAG-based review of the agreed pages, components, templates, and user journeys.
Human evaluation of keyboard behavior, content, interactions, forms, and requirements automation cannot reliably determine.
Screen-reader and interaction testing relevant to the agreed scope.
Validated issues with context, affected functionality, technical requirement, and recommended next step.
Technical accessibility fixes where included and technically possible.
Corrected functionality tested again after remediation.
A record of scope, findings, remediation, verification, and known limitations.
Continued monitoring and accessibility support as the website changes.
COMMUNICATE THE WORK
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.
ALREADY FACING A CLAIM?
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.Focused technical support for an active claim.
KEEP THE IMPROVEMENTS
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 & SupportOfficial reference: W3C guidance on conformance and changing content.
KNOW WHICH PATH APPLIES
Businesses and nonprofits that are public accommodations.
Official reference: DOJ: businesses open to the public.
State and local government entities.
Official reference: DOJ Title II compliance guide.
ACCURATE EXPECTATIONS
Does not establish that the complete experience is accessible.
Does not replace evaluating and correcting underlying barriers.
Does not confer government-issued certification of a private website.
Does not guarantee that a business will never receive a legal claim.
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.Official reference: W3C conformance claims.
PRACTICAL ADA WEBSITE ACCESSIBILITY
Online stores, product interfaces, apps, and cart and checkout journeys.
Menus, reservations, ordering, location information, booking integrations, and downloadable content.
Service information, appointment forms, patient-facing content, documents, and scheduling tools.
Marketing sites, quote forms, lead generation, client portals, booking, and customer-service experiences.
Internal teams and agencies that need accessibility expertise, testing, or verification.
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
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.
Official guidance: DOJ web accessibility and the ADA, W3C WCAG overview, and W3C conformance evaluation.
START WITH THE WEBSITE
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.