Make the site work for everyone. Then prove it.

Two groups, under two different parts of the Americans with Disabilities Act. Title III covers private businesses that serve the public — retailers, restaurants, clinics, hotels, banks, gyms, professional services — and Title II covers public entities: state and local governments, school districts, transit agencies and public universities. Under Title III the requirements reach the digital front door of the business, so an online store, a booking flow or a patient portal is treated as part of the services you provide. Employers also have obligations to individuals under Title I when internal web applications are part of the job. In practice, if members of the public can transact with your organization online, plan to be compliant with WCAG 2.2 AA and to be able to show it.

The ADA itself sets a duty of access; the WCAG standards translate it into testable requirements. The elements that come up most often on the websites we audit: every interactive control reachable and operable from the keyboard, with a visible focus indicator; text contrast that meets the 4.5:1 ratio; text alternatives for images and icons that carry meaning; form fields with programmatic labels, and errors identified in text rather than by colour; captions for video and transcripts for audio; page titles, headings and landmarks that describe structure; content that reflows at 400% zoom; no flashing or auto-playing motion that cannot be stopped; and status messages announced to assistive technology. Mobile apps carry the same obligations as websites, and documents you publish online — PDFs especially — are included.

The Americans with Disabilities Act does not print a list of technical rules for websites. In practice, courts, regulators and enterprise buyers treat the Web Content Accessibility Guidelines — currently WCAG 2.2, at conformance level AA — as the working definition of an accessible website. So ADA website compliance means meeting those success criteria: everything operable by keyboard, sufficient colour contrast, text alternatives for images, labelled forms with clear error messages, content that works at 400% zoom and with a screen reader, and no reliance on colour or motion alone to convey meaning. That is the standard we build to, and the standard we document against.

They do not, and we would rather you hear that from us before you buy one. A widget sits on top of the page and cannot correct the markup underneath it, which is why UsableNet reports a rising share of 2025 filings against companies already running one, sometimes alleging the tool itself interfered with a screen reader. Preference toolbars can be a genuine convenience for some visitors, so we are not against them as a feature. We simply never let one stand in for remediation. The fix that holds up in a legal review or a procurement audit is in the code, and that is what we deliver.

It depends on how much of the site is built from shared components. A site with a coherent design system is far cheaper to remediate than fifty hand-built pages, because a single contrast token or form component fixes hundreds of instances at once. Our audit gives you the ranked findings with effort estimates attached, so you can approve a fixed scope rather than an open-ended retainer. Most clients start with the highest-impact barriers on revenue journeys, then schedule the remainder across normal release cycles — which spreads the cost and keeps the work inside your existing development rhythm.

Yes. Seyfarth's tracking put federal website accessibility filings at 3,117 in 2025, a 27% rise on the 2,452 recorded in 2024, and that count excludes state court actions and the far larger volume of demand letters that never reach a docket. The pattern matters more than the total: filings cluster on ecommerce, restaurants, healthcare and any site where a person cannot complete a transaction. Fixing the transaction path first therefore reduces both the legal exposure and the lost revenue, which is why our remediation plans are ordered that way.

It helps, though we would not sell it as an SEO tactic. The overlap is real: descriptive alternative text, a sane heading hierarchy, semantic landmarks, meaningful link wording, captions and transcripts, and fast keyboard-operable pages all make content easier for search engines and answer engines to parse as well as for people to use. Several of the fixes in an accessibility audit are the same fixes an SEO audit would recommend. Treat the search gain as a welcome side effect of a site that more people can actually use.

Directly, nothing — Title II covers state and local government entities. Indirectly, quite a lot. The rule names WCAG 2.1 AA as the standard, with compliance dates extended in April 2026 to 26 April 2027 for entities serving 50,000 or more people, and 26 April 2028 for smaller and special district entities. Public bodies now push that requirement down to their vendors, so if you sell software, services or content to municipalities, school districts, universities or public health systems, expect a conformance report to appear in the paperwork. Having one ready turns a procurement obstacle into an advantage.

That is our preferred arrangement. We audit, write the remediation plan, and then either implement in your repository alongside your engineers or hand them tickets specific enough to act on — the criterion, the component, the expected behaviour and how we will verify it. Your team keeps ownership of the codebase and gains the patterns, which is the point: after one project most teams stop introducing the same five issues. Where you have no in-house front-end capacity, our web development team does the implementation.

Specialists, not a script. Automated tooling runs first to clear the detectable bulk, then a person reviews against WCAG 2.2 AA and walks your key journeys with NVDA, JAWS, VoiceOver and TalkBack, keyboard only, at high zoom and in high-contrast mode. Findings and re-tests are recorded per success criterion, so you can show what was tested, when, and on what platform. Where risk or budget allows we add paid sessions with disabled users, which reliably surfaces friction no audit format catches.

It constrains a few choices and improves most of them. Contrast requirements can rule out one pale tint of a brand colour; the answer is usually a second approved shade for text rather than a redesign. Focus states, larger touch targets, readable type and honest link wording tend to make interfaces feel more considered, and they measurably help everyone using a phone in bright sunlight. We work with your designers rather than over them, and we bring the fixes back into the design system so the brand stays coherent.

No. There is no government body that issues an ADA certificate for a website, and any vendor selling one is selling a badge rather than compliance. What does exist, and what buyers and courts respond to, is evidence: an audit against the guidelines, a dated remediation record, assistive technology test results, a published accessibility statement, and an ACR or VPAT describing how the product measures against WCAG 2.2 AA. We produce that package as part of the engagement. It is also worth knowing that ADA obligations are ongoing rather than a one-time certificate: the duty applies to the website as it is today, so the organizations that stay out of trouble are the ones that keep testing after each release rather than the ones that framed a certificate in 2023.

Rarely with a regulator. Most ADA digital access claims begin with a law firm running automated checks across hundreds of websites, or with a disabled customer who could not complete a purchase and told someone. The letter that follows names a handful of failures, cites the ADA and the WCAG standards, and offers to settle. Because the underlying barriers are usually shared across every page of the website, one complaint tends to describe a site-wide condition — and the same condition invites the next letter. Organizations that remediate the code, publish an accessibility statement and keep dated test records are in a materially stronger position, both in negotiation and in avoiding the second round. Public bodies and governments face the same claims under Title II with a fixed DOJ deadline attached.

Apps and documents, yes. Native mobile apps are audited against WCAG 2.2 AA using the platform accessibility APIs and tested with VoiceOver and TalkBack, and we remediate published PDFs so they are tagged, ordered and readable rather than a flat scan. Embedded third-party tools — chat widgets, booking engines, payment iframes, review apps — are the common blind spot: they sit inside your journey but not in your code. We test them, document what fails, and give you the vendor-facing evidence to demand a fix or the case for replacing the tool. Several clients have used that report to move to an accessible alternative at renewal, which is cheaper than engineering around a broken embed.

You keep the code, the documentation and the habits, and you can keep us on a light governance retainer if you want the site re-tested each quarter and the conformance report kept current. Many clients pair that with ongoing design and development work, which is the cheapest way to stay conformant: accessibility checks ride along in the release process instead of becoming an annual emergency. Either way there is no lock-in and nothing is held hostage.