“Every organization we work with that has delayed an accessibility audit tells us the same thing: they assumed it was a larger project than it turned out to be. In most cases, focused development work can fix the violations driving 90% of the legal exposure in two to three weeks. The audit takes a day. The documentation takes an afternoon. The delay is what costs money.”
Most Operations Directors and Legal Counsel dealing with web accessibility are somewhere in the same position: they know the lawsuits are rising, they have heard something about a DOJ deadline, and someone has probably suggested buying an overlay widget to sort it out quickly. None of that adds up to a defensible program.
In 2025, over 5,100 federal ADA website lawsuits were filed, up 37% from the prior year. The five violations cited in the majority of those complaints are not obscure WCAG technicalities. They are missing alt text, unlabelled form fields, poor color contrast, broken keyboard navigation, and missing skip links. A development team that knows what they are looking at can fix all five in weeks. The expensive version of this story is finding out from a plaintiff rather than from your own audit.
AI tools have changed the economics of accessibility auditing in ways that matter commercially. But they have not changed what a legally defensible compliance position actually requires: code-level remediation, documented audit history, and ongoing monitoring. This guide covers all of it.
KrishaWeb has implemented WCAG compliance programs for clients in eCommerce, healthcare, and financial services. The pattern we see consistently: organizations that audit first and remediate systematically spend roughly 67% less on compliance over their first three years than those who respond to a demand letter.
How the Legal Landscape Has Shifted
The ambiguity that gave organizations room to argue about digital accessibility liability has been narrowing for years. Two developments in 2024 and 2025 effectively closed it for most business categories.
In April 2024, the Department of Justice published a final rule establishing WCAG 2.1 Level AA as the required technical standard for state and local government websites. The compliance deadline for entities serving populations over 50,000 is April 24, 2026. For smaller entities, it is April 2027. That is the first time the DOJ has tied a specific WCAG version to a specific enforcement date. Whatever ambiguity existed for public sector organizations is now resolved.
Private businesses under Title III are in a technically different position: there is still no DOJ rule specifying a technical standard for commercial websites. In practice, that does not reduce the risk. It may increase it. Private litigation has filled the regulatory gap entirely. Courts consistently apply WCAG 2.1 AA as the benchmark in Title III cases. Every web accessibility lawsuit filed in 2025 cited WCAG failures. The absence of a formal rule has not slowed plaintiffs. It has given them more room to operate.
The filing numbers and what they mean
5,100+ federal ADA website lawsuits filed in 2025, up 37% year over year
30% compound annual growth in federal ADA web filings since 2018
746% year-over-year increase in ADA web filings in Illinois in the first half of 2025 alone
40% of federal Title III lawsuits now filed by pro se plaintiffs, many using AI drafting tools (Source:AdaScanPro 2025)
The federal count excludes state court filings, demand letters that settle privately before anyone files, and DOJ enforcement actions. The real exposure for most organizations is higher than the federal docket suggests.
The 40% pro se figure deserves attention on its own. Someone who encounters an inaccessible checkout can now generate a federal complaint in an afternoon using AI drafting tools. The barrier that previously kept small individual claims from being filed has effectively collapsed. The volume of demand letters and small-scale filings that never make it into the federal statistics has grown accordingly.
For organizations with EU market exposure, the European Accessibility Act became mandatory across all member states in June 2025. Banking, eCommerce, and most digital services are in scope. EAA standards largely track WCAG 2.1 AA, so US-focused compliance work covers the majority of European requirements. Confirm specific product scope with counsel.
eCommerce carries the largest litigation exposure in this space. 70% of all ADA digital accessibility lawsuits in 2025 targeted online retailers, concentrated around checkout flows, product image navigation, and form fields. If your business is in eCommerce, food service, healthcare, or financial services and has not done a formal audit, assume violations exist that a scanner could identify before a plaintiff does.
The One Solution That Does Not Work
Accessibility overlay widgets are still being sold aggressively as a compliance solution. They need to be addressed directly before anything else in this conversation, because organizations with an overlay installed and Legal operating under the assumption that it provides cover are carrying risk they do not know they have.
Overlays are JavaScript plugins that promise WCAG compliance with a single line of code. In 2025, sites using these tools were sued at rates comparable to sites without them. Courts have not treated overlay installation as evidence of good-faith compliance. Disability advocacy organizations and accessibility specialists have documented the technical reasons that overlays cannot do what they claim. The litigation data from 2025 confirms that the legal position matches the technical reality.
If your organization has an overlay installed, the assumption that it provides legal protection needs to be revisited with Legal before anything else. Code-level remediation is the only approach that holds up in court. This is no longer a contested point in the accessibility field.
What Your Site Is Almost Certainly Failing On
The violations driving the majority of ADA web lawsuits fall into five categories. This is actually useful information, because it means the highest litigation risk is also the most tractable: these are not obscure WCAG requirements that require architectural redesign. They are content attributes, HTML labels, CSS values, and structural additions that a development team with clear guidance can work through systematically.
Violation
Cited in % of 2025 Complaints
What It Actually Is
How Hard to Fix
Missing alt text on images
89%
No text alternative for images that convey meaning
Content change. Tedious at volume, straightforward technically. AI tools help at scale.
Missing form labels
72%
Form inputs without programmatic labels for screen readers
HTML attribute. One line per field. Fast with a developer who knows what to look for.
Insufficient colour contrast
68%
Text/background combinations below WCAG 4.5:1 ratio
CSS change. Scanner-detectable. Design approval is required for brand colors.
Keyboard navigation failures
61%
Elements that cannot be reached or operated without a mouse
Structural. Interactive elements need focus states and keyboard event handlers.
Missing skip navigation
55%
No mechanism to skip repeated navigation to the main content
Single link addition. Low effort, well documented.
“The sites we audit that have the worst compliance profiles are not usually neglected sites. They are well-maintained sites where accessibility was never part of the development brief. The violations accumulate over years of content updates and feature additions, each one small, but the combined profile is substantial enough to attract attention.”
The cost calculation is straightforward. The fix for these violations does not change depending on when you do it. The only change is whether it arrives attached to a demand letter and attorney fees or as a line item in your development sprint.
The Market You Are Accidentally Locking Out
Most internal conversations about web accessibility start in Legal and stay there. That framing treats accessibility as a cost center with no upside. However, the market data presents a different perspective.
1.3 billion people globally live with a disability affecting web use (WHO)
61 million adults in the US have a disability affecting web use, 26% of the adult population (CDC)
69% of users with disabilities leave inaccessible sites without reporting the problem (BeAccessible)
83% of users with disabilities limit online shopping to sites they already know are accessible (BeAccessible)
The 69% figure is where the commercial argument is sharpest. Nearly seven in ten users who encounter an inaccessible site leave without saying anything. They do not submit a help request. They do not fill out the exit survey. They close the tab and spend their money somewhere else. That loss never appears in your analytics. It is invisible, which is precisely why it compounds over the years without being addressed.
The improvements that make a site accessible to users with visual or motor impairments also make it better for users without them. Properly labeled form fields improve autocomplete accuracy on mobile. A clear heading structure helps both screen reader users and people who skim. High-contrast text is easier to read on a phone screen outdoors. Every WCAG improvement is additive. No version of this work makes a site worse for the users who were already converting.
KrishaWeb has measured post-remediation conversion changes on several eCommerce clients. Across sites where accessibility work was paired with a broader audit, checkout completion rates improved between 4% and 11%. A portion of that improvement comes directly from accessibility fixes. A larger portion comes from the structural and labeling improvements that accessibility requirements surface in forms and checkout flows that were already creating friction for all users.
What AI Actually Does in Accessibility Compliance
The claims from accessibility tool vendors can be vague about what AI-powered scanning actually delivers. Here is a precise account of where AI changes the work and where it does not.
Where AI genuinely helps
AI-powered scanning tools have compressed what used to take days of specialist manual review into hours of automated analysis. Tools like Deque’s axe DevTools, Siteimprove, and Accessibe crawl an entire site, map every page against WCAG criteria, flag violations by severity, and return a prioritized remediation list quickly. For the high-confidence violations, missing alt text, contrast failures, unlabelled form fields, and broken keyboard paths, AI-powered scanning is fast, reliable, and significantly cheaper than starting with manual reviews.
Alt text generation at scale is the second area where AI adds meaningful value. For a product catalog with 20,000 images, manual alt text writing is months of work. AI tools automatically generate descriptive alternatives, flagging images with ambiguous context for human review. It still needs editorial oversight, but it removes most of the manual labor from what would otherwise be the most time-consuming remediation task on a content-heavy site.
Ongoing monitoring is the third. Accessibility is not a one-time project. Sites drift out of compliance as content is updated, features are added, and design changes are deployed. An automated monitoring tool integrated into the development pipeline catches new violations before they reach production. Without this, organizations that achieve compliance frequently lose it within six months.
Where AI has clear limits
Automated scans, including well-configured AI-powered ones, reliably detect roughly 30% to 40% of WCAG criteria. They can partially flag another 45%, but those partial detections need a person to evaluate whether there is actually a violation. Cognitive accessibility barriers, complex user flow failures, semantic meaning problems, and ARIA implementation errors require human specialist judgment. A screen reader user navigating a complex checkout flow will encounter issues that no automated scanner identifies, because the scanner does not experience the flow; it parses the code.
A compliance program built entirely on automated scanning is not legally defensible. Courts look at evidence of a good-faith, ongoing compliance effort: audit documentation, remediation records, retest results, and a published accessibility statement. Automated AI scanning contributes to that evidence. It does not constitute it.
Task
AI-Powered Tools
Human Specialist Required
Initial violation detection at scale
Fast and reliable for 30-40% of WCAG criteria
Required for contextual and semantic issues
Alt text generation for large image libraries
Automated generation with human review flag
Review for accuracy and context
Colour contrast analysis
Reliable automated detection
Brand colour decisions require design input
Keyboard navigation testing
Can detect missing focus indicators
Full flow testing requires a human navigating the interface
ARIA implementation review
Limited — code parsing only
Required: screen reader behaviour testing
User flow accessibility
Cannot be automated reliably
Required: tested by a specialist with assistive technology
Ongoing monitoring for new violations
Automated — integrates into CI/CD pipeline
Periodic specialist review of flagged items
Documentation for legal defence
Can generate structured reports
Review and sign-off required before filing
How to Build a Programme That Holds Up
The sequence that produces a legally defensible result without creating unnecessary cost or delay is straightforward. The organizations that handle this well do not treat it as a one-time remediation project. They build accessibility into their development workflow the same way they build security testing in.
Step 1: Automated baseline audit
Start with an automated scan of the full site. This takes hours, not days, and immediately tells you which pages carry the highest violation density, which failure categories appear most frequently, and how far from WCAG 2.1 AA you currently sit. Most tools have free tiers sufficient for a first scan. The output gives you a prioritized list before you spend any money on specialist time.
Step 2: Manual specialist review for contextual violations
Use the automated results to commission a manual audit by a certified accessibility specialist for the violations the scanner flagged as requiring contextual review. Look for CPACC or ADS credentials. This is where user flow problems, ARIA failures, and semantic structure issues are properly assessed. The output needs to be formally documented and retained. Not summarized in a Slack thread. Actually stored with dates, findings, and sign-off.
Step 3: Remediate in order of litigation risk
Fix the five high-litigation-risk violation categories first: alt text, form labels, color contrast, keyboard navigation, and skip navigation. Everything else follows once those are resolved. Most development teams with clear guidance complete these five categories within two to three weeks on a typical mid-size site. The temptation to address low-effort violations first and defer the complex ones is precisely the pattern that leaves the high-litigation-risk issues unresolved when a demand letter arrives.
Step 4: Implement ongoing monitoring
Once initial remediation is complete, integrate an automated monitoring tool into your development pipeline that flags new violations before they reach production. This is the step most organizations skip, and it is why sites that achieve compliance frequently drift back out of it within six months as the site is updated. Compliance is not a point-in-time event. It is a maintained state.
Step 5: Publish an accessibility statement
An accessibility statement is a WCAG requirement and a practical legal signal. Name the standard you are targeting, describe your current conformance status honestly, provide a mechanism for users to report problems, and include a timeline for ongoing work. Courts treat a published and maintained accessibility statement as evidence of good-faith effort toward compliance. Its absence, when violations are found, is treated as evidence of the opposite.
KrishaWeb builds WCAG compliance into the site’s architecture from the initial development brief rather than retrofitting it post-launch. For organizations assessing their current gap, our team combines automated AI scanning, certified specialist review, and a documented remediation program that produces the evidence trail Legal needs if a demand letter arrives.
Most organizations arrive at accessibility compliance after receiving a demand letter. At that point, the remediation costs more, the timeline is compressed by legal pressure, and attorney fees are attached to work that could have been done at a fraction of the cost twelve months earlier. The organizations that manage this well treat it like any other operational risk category: audit, remediate, monitor, document, and maintain.
The specific calculus for 2026 is clearer than it has been in previous years. The DOJ has set a standard and a date for the public sector. Private litigation has set an effective standard for the commercial sector through the courts. The five violations driving the majority of complaints are known and fixable. AI tools have changed the economics of the audit phase meaningfully. The business case for the disability market adds a revenue argument to the risk management argument. KrishaWeb’s web design and development services build WCAG compliance into site architecture from the start. For organizations that need to assess their current gap, establish a remediation program, and build the documentation their legal team needs, our AI development solutions team handles the technical and process sides of that work together. The Free AI Website Audit provides a baseline accessibility report, the violation categories with the highest litigation exposure on your specific site, and a prioritized remediation roadmap within five business days.
Frequently Asked Questions
Does my business website legally have to be ADA-compliant?
In practice, yes, even without a formal Title III rule from the DOJ covering commercial websites. Courts across the country have consistently ruled that the ADA covers business websites, using WCAG 2.1 AA as the benchmark. Over 5,100 federal lawsuits were filed in 2025. The absence of a formal rule has not protected businesses from litigation. It has created a litigation environment in which private plaintiffs have moved faster than regulators.
What is WCAG and which version applies now?
WCAG stands for Web Content Accessibility Guidelines, published by the W3C. Courts most often cite WCAG 2.1 AA in Title III cases. WCAG 2.2 is the current published version and is increasingly cited in newer guidance. By targeting 2.2 now, you position yourself ahead of the enforcement trajectory. WCAG 3.0 is still in working draft with no confirmed release timeline. For practical compliance purposes, build to WCAG 2.2 AA, and you cover both current enforcement benchmarks and the near-term direction of travel.
Are overlay widgets a legitimate compliance solution?
No. The 2025 litigation data is unambiguous: sites using overlay widgets were sued at rates comparable to sites without them. Courts have not treated overlay installation as evidence of good-faith compliance. Disability advocacy organizations and accessibility professionals have documented in detail why overlays cannot achieve what they claim. Code-level remediation, documented audit history, and ongoing monitoring are the only combination that holds up.
How long does a compliance program actually take?
Fixing the five highest-litigation-risk violations takes most development teams two to three weeks with clear guidance on a typical mid-size site. Full remediation to WCAG 2.1 AA on a mid-size site runs four to eight weeks. Large sites with legacy codebases or large document libraries take longer. The timeline shortens significantly when the project starts with an automated scan that produces a prioritized list rather than requiring the development team to locate violations manually.
What can AI tools realistically contribute to accessibility compliance?
Automated scanning at scale, alt text generation for large image libraries, color contrast analysis, ongoing monitoring for new violations, and structured documentation. Reliable automated detection covers approximately 30% to 40% of WCAG criteria. Contextual failures, ARIA implementation errors, and user flow issues still require a human specialist using assistive technology. Use AI tooling for breadth, speed, and monitoring. Use certified human specialists for depth, flow testing, and the documentation that legal needs.
What documentation does Legal actually need?
Dated audit reports with specific findings; remediation logs showing what was fixed and when; re-test results confirming that fixes resolved the flagged violations, and a published and maintained accessibility statement on the site. Courts look at whether an organization made a documented good-faith effort toward compliance, not necessarily whether it achieved perfect conformance. The paper trail is what demonstrates the effort. An organization with a documented audit history and a clear remediation program is in a materially better position than one with no documentation, even if both have some remaining violations.
This article provides general information about website accessibility compliance and should not be construed as legal advice. Organizations with specific legal matters relating to ADA or WCAG compliance should consult qualified legal counsel. Statistics are drawn from third-party research published in 2025 and 2026.
Nisarg Pandya
Project Manager
Experienced Project Manager and Scrum Master at KrishaWeb, delivers expertise in Scrum methodologies, Laravel, React.js, UX design, and project management, ensuring efficient project delivery and agile implementation.
KrishaLabs
KrishaStudio
KrishaStore
