Which laws actually apply to a business website?

In the US, the Americans with Disabilities Act as applied to websites through case law, plus state equivalents. In Europe, accessibility directives with defined conformance targets. The practical standard everyone builds to is the Web Content Accessibility Guidelines at level AA.

What does the lawsuit pattern look like?

High volume, low individual value, targeting sites with obvious automated-detectable failures. It is a numbers game rather than a considered legal review, which means the sites that get letters are the ones failing the checks a scanner runs in seconds.

What are the biggest violation categories?

Missing alternative text on meaningful images, insufficient colour contrast, form inputs with no associated labels, and content that cannot be operated by keyboard. Those four account for most claims, and all four are detectable automatically and fixable cheaply.

Do accessibility overlay widgets solve this?

No, and they have themselves become a target. They sit on top of the problem, frequently interfere with the assistive technology they claim to help, and are not accepted as remediation. The money is better spent fixing the underlying markup.

What is a compliant build posture?

Semantic markup, real labels, keyboard operability, sufficient contrast checked at design time, and reduced-motion respected. Built in from the start it costs almost nothing. Retrofitted after a complaint it costs a project, which is the whole argument for the posture.

How do I check my own site?

Run an automated scanner for the mechanical failures, then do the manual checks it cannot do: navigate the site with only a keyboard, and check that every image conveying information has meaningful alternative text. Automated tools catch maybe a third of real issues.

Only if the findings get fixed and the process changes. An audit that produces a report and no change in how pages are built means the same violations return with the next redesign. The durable answer is the checks living in the build rather than in an annual document.

Does accessibility affect SEO?

Overlapping, not identical. Semantic markup, meaningful alternative text, and clear heading structure help both. But the reason to do this is that people who need it cannot use your site otherwise, and the search benefit is a side effect rather than the case.

What if my site is built on a platform I cannot change?

You still own the content decisions: alternative text, heading structure, link text, colour choices, and form labels are usually editable even on a locked platform. That covers a meaningful share of the common violations without touching the template.

How much does compliance cost?

Very little on a new build, because it is a way of working rather than a feature. On an existing site it depends on how far the markup drifted. The reliable number is that it is cheaper than a claim, and considerably cheaper than a claim plus a rushed remediation.

What should I do first?

Run a scanner, fix contrast and missing labels and alternative text, then try to use the site with only a keyboard. That sequence closes the categories that generate most claims and takes days rather than a project.

Who owns this internally?

Whoever owns the site, with design and content both carrying part of it. Contrast is a design decision, alternative text is a content decision, and keyboard operability is a development one. Assigning it to a single person guarantees the other two categories keep reappearing.

Accessibility 2026 Trends Web Design How-to

Accessibility Law in 2026: The Lawsuit Landscape and the Compliant Build Posture

Accessibility lawsuits are up. Compliance is mostly about practice, not policy. Here’s what we ship.

John Cravey with AIFounderApr 18, 20264 min readUpdated Jul 6, 2026

Accessibility lawsuits against SMB websites have grown every year since 2018. 2026 is no different — plaintiffs’ firms have automated tools that scan SMB sites for WCAG violations and serve demand letters in bulk. Most lawsuits settle for $5k-25k. The cost of getting compliant up front is dramatically less. Here’s what the regulatory landscape actually requires in 2026 and the build practices we ship on every FH client site.

Free estimate · 2 minutes

Fast site, real proof, visible call button. Priced.

The estimate sketches the conversion-built site we would ship for your business in the first thirty days. Sixty seconds, no opt-in.

#The legal frameworks

ADA (US): Title III applies to public accommodations. Court rulings have established that ‘public accommodations’ includes commercial websites, even though the ADA predates the web. WCAG 2.1 AA is the de facto compliance bar.
Section 508 (US): federal agency websites; usually doesn’t affect SMBs unless they sell to government.
European Accessibility Act (EU): in effect from June 2025, requires WCAG 2.1 AA for commercial websites serving EU customers.
AODA (Ontario), UK Equality Act, Australian DDA: similar frameworks in other markets.

#The lawsuit pattern

Most SMB lawsuits go like this: an automated scan flags violations, a plaintiff’s firm sends a demand letter, the SMB has 30 days to remediate or settle. Settlements average $5k-25k. Plaintiff’s firms operate at scale — one firm can send 100+ demand letters per quarter. The math favors them: tools are cheap, demand letters cost nothing to send, settlements pay legal fees with a margin.

#The four biggest violation categories

Missing or wrong alt text on images. Every meaningful image needs descriptive alt; decorative images need alt="".
Insufficient color contrast. Text on background must hit 4.5:1 (WCAG AA) or 3:1 for large text. Most brand color palettes fail somewhere on the site.
Forms without labels. Every input needs an associated label (visible or aria-label, but present).
Keyboard-inaccessible interactive elements. Custom dropdowns, modals, and tabs that work with mouse but not Tab/Enter/Esc.

#The FH compliant-build posture

Semantic HTML by default. Use real button elements, not divs with onClick. Real form elements with labels. Real heading hierarchy.
Color contrast tested. Every text/background combination passes WCAG AA. We use a contrast checker (or our own design system tokens) to verify at design time.
Alt text on every image. The CMS / content layer enforces it — empty alt is allowed only when explicitly marked decorative.
Keyboard testable on every interactive component. We run a Tab-through audit on every page before shipping.
Focus styles visible. Default browser focus rings are fine; custom focus styles are tested.
Skip-to-content link at the top of every page.
Reduced-motion respected. Every animation falls back to instant on `prefers-reduced-motion`.
ARIA only when needed. Real semantic HTML beats ARIA-decorated divs. ARIA is for things that don’t have a native equivalent.

#Tools for ongoing compliance

axe-core in dev: catches violations in development.
Lighthouse accessibility audit in CI: blocks PRs with new violations.
Manual keyboard-only and screen-reader testing pre-launch: catches what automated tools miss.
Quarterly accessibility review: re-audits the site as content evolves.

#Overlay widgets are not a solution

Accessibility overlay widgets (AccessiBe, UserWay, etc.) are sold as one-line accessibility fixes. They’re mostly theater. Plaintiff’s firms specifically target sites using overlays, and courts have increasingly ruled that overlays don’t constitute compliance. Some overlays actively break the underlying site’s accessibility. We don’t install them on any FH client site.

#What the lawsuits target most

Public service-business sites and ecommerce sites — anything where a member of the public might interact. B2B-only sites with no public-facing pages are at lower risk (no general public to be excluded). Personal portfolios are at lowest risk (not a public accommodation in most interpretations). Most FH clients are public service-businesses; we treat them as full-risk and build accordingly.

#The accessibility statement page

Every accessible site has an /accessibility page documenting the standard followed (WCAG 2.1 AA), known limitations, and a contact method for users who hit accessibility issues. The page is part of compliance but more importantly a real channel — users with disabilities reach out via that channel and you get to fix issues directly instead of through legal.

#When the lawsuit hits

Two options: (1) settle and remediate; (2) defend. Settling is usually cheaper but doesn’t solve the underlying problem (you’re vulnerable to the next plaintiff). Defending requires a real accessibility audit and a remediation plan with timelines. We help clients with the second when it’s feasible; we recommend settling fast and remediating fast when it isn’t.

#ARIA: the right amount

Too much ARIA is worse than too little. `role="button"` on a `<button>` is redundant and can break screen readers. `aria-label` on a button with visible text overrides the visible text in announcement. ARIA is a precision tool for cases where semantic HTML can’t express what you need — not a decorator for every element.

#Mobile accessibility specifically

Touch targets must be 44×44 px minimum (Apple HIG, WCAG AAA). Most SMB sites have tap targets too small on mobile, especially in navigation menus. We audit and fix. Mobile screen-reader testing (VoiceOver on iOS) catches issues desktop testing misses.

#How this lands across FH client work

Every FH client site ships with WCAG 2.1 AA compliance and a documented accessibility statement. Lighthouse scores 95+ across the board. Zero accessibility lawsuits against any FH client in the last three years. If your site’s accessibility hasn’t been audited recently, book a consultation — the audit is a one-day engagement and the remediation is usually a one-week sprint.

Answers

Frequently asked questions

Which laws actually apply to a business website?: In the US, the Americans with Disabilities Act as applied to websites through case law, plus state equivalents. In Europe, accessibility directives with defined conformance targets. The practical standard everyone builds to is the Web Content Accessibility Guidelines at level AA.
What does the lawsuit pattern look like?: High volume, low individual value, targeting sites with obvious automated-detectable failures. It is a numbers game rather than a considered legal review, which means the sites that get letters are the ones failing the checks a scanner runs in seconds.
What are the biggest violation categories?: Missing alternative text on meaningful images, insufficient colour contrast, form inputs with no associated labels, and content that cannot be operated by keyboard. Those four account for most claims, and all four are detectable automatically and fixable cheaply.
Do accessibility overlay widgets solve this?: No, and they have themselves become a target. They sit on top of the problem, frequently interfere with the assistive technology they claim to help, and are not accepted as remediation. The money is better spent fixing the underlying markup.
What is a compliant build posture?: Semantic markup, real labels, keyboard operability, sufficient contrast checked at design time, and reduced-motion respected. Built in from the start it costs almost nothing. Retrofitted after a complaint it costs a project, which is the whole argument for the posture.
How do I check my own site?: Run an automated scanner for the mechanical failures, then do the manual checks it cannot do: navigate the site with only a keyboard, and check that every image conveying information has meaningful alternative text. Automated tools catch maybe a third of real issues.
Is an audit enough?: Only if the findings get fixed and the process changes. An audit that produces a report and no change in how pages are built means the same violations return with the next redesign. The durable answer is the checks living in the build rather than in an annual document.
Does accessibility affect SEO?: Overlapping, not identical. Semantic markup, meaningful alternative text, and clear heading structure help both. But the reason to do this is that people who need it cannot use your site otherwise, and the search benefit is a side effect rather than the case.
What if my site is built on a platform I cannot change?: You still own the content decisions: alternative text, heading structure, link text, colour choices, and form labels are usually editable even on a locked platform. That covers a meaningful share of the common violations without touching the template.
How much does compliance cost?: Very little on a new build, because it is a way of working rather than a feature. On an existing site it depends on how far the markup drifted. The reliable number is that it is cheaper than a claim, and considerably cheaper than a claim plus a rushed remediation.
What should I do first?: Run a scanner, fix contrast and missing labels and alternative text, then try to use the site with only a keyboard. That sequence closes the categories that generate most claims and takes days rather than a project.
Who owns this internally?: Whoever owns the site, with design and content both carrying part of it. Contrast is a design decision, alternative text is a content decision, and keyboard operability is a development one. Assigning it to a single person guarantees the other two categories keep reappearing.

Question we did not answer? Ask us directly and we will answer it here.

Tagged#Accessibility #2026 Trends #Web Design #How-to

Written by

John Cravey

Founder

Founder of Frontend Horizon. Writes most of the long-form work on the FH blog.