
ADA website accessibility. Done in code, not with overlays.
Overlay widgets promise instant compliance and leave the code underneath unchanged. Accessibility lives in the HTML, CSS, and behavior of the site itself, tested against the WCAG criteria that apply to it. We do that work, and we're clear about what it does and doesn't do.
Why ADA website accessibility matters now.
Lawsuits and demand letters under Title III of the ADA over inaccessible websites are a real and recurring business risk, and they reach small and mid-sized businesses, not only large corporations. Separately from the legal question, an inaccessible site turns away customers who use screen readers, keyboards, or magnification. Both are reasons to do the work. Neither is a reason to buy a widget.
What typically shows up in a claim
- Screen reader can't navigate the site
- Forms are missing labels
- Images are missing meaningful alt text
- Color contrast fails WCAG thresholds
- Keyboard navigation is broken
- Focus states are invisible
- Heading hierarchy is jumbled
- An accessibility overlay standing in for fixes in the code — sites running overlays have been named in claims too
What the standard actually is
WCAG 2.1 and 2.2 at level AA are the standards most commonly referenced in website accessibility cases, settlements, procurement requirements, and regulations. WCAG covers four principles — perceivable, operable, understandable, and robust — across dozens of testable success criteria.
The goal of remediation is to bring the site's actual code into conformance with the criteria that apply to it, and to be able to show the testing. Not to install a widget that claims compliance. The distinction matters practically, and it matters if anyone ever asks you to show your work.
Why accessibility overlays don't fix accessibility.
Sites running accessibility overlays have been named in accessibility lawsuits alongside sites without them. The tools that were sold as a one-click compliance fix don't change the code, and they haven't stopped the claims.
What overlays actually do
Overlays inject a JavaScript widget into the page that attempts to modify the site's behavior after it loads. They add toolbars, adjust contrast, attempt to rewrite alt text on the fly, and offer accessibility "modes" that toggle visual changes.
None of this changes the underlying code. The issues are still there. An overlay does not by itself demonstrate that the underlying website conforms to WCAG. The site’s content, structure, interactions, and code still require evaluation.
Why they fall short
- Screen readers don't reliably work with overlay-modified content
- An overlay is easy to detect, and its presence doesn't establish that the site conforms to anything
- Sites with overlays have been named in claims; the overlay was not a defense
- Overlay vendors typically disclaim liability in their terms of service
- Users with disabilities have publicly identified overlays as obstacles
- The National Federation of the Blind has formally opposed them, and accessibility practitioners have published an open Overlay Fact Sheet explaining why
Code-level remediation. Real testing. Documentation.
The same four stages as every Design225 engagement. For accessibility, the scope stage decides what gets tested and against which criteria, and everything after is measured against that. The audit and the fixes are done by the same in-house team that builds our client sites, not handed to a vendor.
The call
What the site is, how big it is, what prompted the question — a demand letter, a procurement requirement, a customer who couldn't use the site — and what the applicable target is. Usually WCAG 2.2 AA.
The scope
Which pages, templates, and components get tested, against which WCAG criteria, and what the audit delivers. For an existing site, the audit is scoped first and remediation is priced from its findings. For a rebuild, accessibility is scoped into the design and the build.
The build
The audit: manual and automated review of every page, form, and interactive element in scope, following the W3C guidance on evaluating web accessibility. Then the remediation, in the actual code: semantic HTML, proper ARIA, working focus management, accurate alt text, form labeling, keyboard navigation, contrast.
The follow-through
Re-test against the criteria in scope. Manual and automated evaluation is defined in the project scope. Screen-reader and assistive-technology testing is included only when the scope identifies the technologies, browsers, representative pages, and qualified tester. Document what was tested and fixed, and publish an accessibility statement. When a procurement-ready conformance report is required, Design225 can scope an Accessibility Conformance Report using the applicable ITI VPAT template. Optional ongoing monitoring catches regressions when new content or features ship.
The deliverables.
From the audit
- Audit report against the WCAG 2.2 AA criteria in scope, page by page and component by component
- Issue-by-issue documentation with severity ratings
- Remediation plan with effort estimates
- Screenshots and code references for each finding
- Prioritized roadmap if full remediation isn't immediate
From the remediation
- Code-level fixes for the audit findings in scope
- Re-test verification across screen readers and keyboard
- Accessibility statement published on the site — our own accessibility statement is the pattern: the standard tested against, known limits, how to report a problem, and the date last reviewed
- Documentation of what was tested and what was fixed
- Accessibility conformance report (VPAT) when a buyer or agency requires one
- Ongoing monitoring (optional, $250/month)
The audit price depends on site size — number of unique pages and components to test. Most audits land between $2,500 and $7,500. Remediation pricing is set after the audit, when we know what actually needs to be fixed.
Ongoing monitoring runs from $250 per month and catches accessibility regressions as new content or features ship.
For sites being rebuilt anyway, accessibility is built into every custom web design project: WCAG 2.2 AA is the working target, tested against the criteria defined in the scope. Building it in from the start is the easiest path.
What buyers usually want to know.
Is my business actually at risk of an ADA lawsuit?
We're not lawyers, and this isn't legal advice. What's public record is that Title III lawsuits and demand letters over websites exist, that they reach small and mid-sized businesses, and that a demand letter is a common first contact. Whether your business is a likely target depends on factors an attorney should weigh. What we can tell you is what the site does and doesn't do for the people who use it, and fix that.
What if I already have an accessibility overlay installed?
We'd recommend removing it once the underlying fixes are in place. An overlay doesn't make the code conform, and it isn't a substitute for testing. What holds up — practically, and if anyone asks you to show your work — is the site itself meeting the criteria in scope, with documentation of what was tested.
Can my existing developer fix the site instead?
Maybe — accessibility is specialized work. Generalist developers often miss the structural issues that matter most: focus management, the name and role of custom controls, reading order, form error handling. We're happy to provide the audit and let your team handle remediation if that's the preference. We're also happy to do the full job.
How long does remediation take?
Typical remediation runs 2 to 6 weeks depending on site size and the number of issues found; the schedule is set after the audit, when we know what needs fixing. Sites with extensive interactive components (forms, dashboards, custom widgets) run longer than primarily content-driven sites.
Does this guarantee I won't get sued?
No, and nothing can. Accessibility work supports accessibility and compliance efforts; it is not legal advice or a universal guarantee against claims. What a documented, tested remediation gives you is a site that works for more people and a record of what was tested and fixed — which is what you'd want to be able to show if the question ever came up. For your legal exposure, talk to an attorney.
What about a redesign instead of remediation?
Sometimes a redesign is more cost-effective than remediating a deeply broken site — particularly older sites built before accessibility was a baseline practice, or sites on a page builder where the fixes would have to be redone with every update; those are candidates for a rebuild with an editing system the team can keep using. We'll tell you on the audit which option is more sensible. If a full rebuild is the answer, accessibility is built in from the design stage, with WCAG 2.2 AA as the working target and testing scoped alongside everything else. On the Sullivan Suites build, for example, that meant descriptive alt text across the suite gallery and an application form with inline validation.

Schedule an audit.
Send a brief or call. We'll scope the audit, schedule the work, and tell you what the remediation path looks like. The first conversation is free.
