The Web Is Getting Less Accessible. AI-Assisted Coding Is a Big Reason Why

The 2026 WebAIM Million report shows accessibility failures rising for the second year running. With Title II and Section 504 deadlines now less than a year out, the data has uncomfortable implications for municipalities, community colleges, and HHS-funded organizations.

Every year, WebAIM runs an automated accessibility audit against the top one million home pages on the web. It is the closest thing the industry has to a State of the Union, and the 2026 edition arrived with a finding that surprised almost no one in the audit community and should alarm everyone else: 95.9% of home pages have detectable WCAG failures, up from 94.8% last year. The average page now contains 56.1 distinct errors, a 10.1% jump in twelve months.

Awareness has never been higher. Tooling has never been more abundant. Federal enforcement deadlines for Title II of the ADA and Section 504 of the Rehabilitation Act are bearing down. And the web is still getting worse, not better.

There is a reason. It is not the one most leaders want to hear.

Why the Numbers Are Going the Wrong Direction

The 2026 WebAIM Million report points to two structural shifts behind the regression. Page complexity is up 22.5% year over year, and ARIA usage is up 27%, much of it implemented incorrectly. In other words, sites are doing more, with more scripts, more components, more interactive layers, and the accessibility scaffolding is not keeping pace.

Sitting underneath both shifts is a workflow change that the industry has not fully reckoned with: AI-assisted development. Builders, agencies, and in-house teams are spinning up sites and components faster than ever using tools like GitHub Copilot, Cursor, Lovable, and a long tail of AI page builders. Speed has gone up. Quality control has not.

“If 96% of sites are not passing WCAG compliance, our AI developers are not doing it right either. Your AI platforms are not going to build it right.”

That is the practitioner read from our audit team, and it tracks with what we see in the field. The pattern is clearest at the small business and public accommodation end of the market, where a developer can stand up a restaurant or hotel site over a weekend for a couple of thousand dollars and walk away. Accessibility never enters the conversation. The site looks fine. It scans clean enough to satisfy a casual review. And it discriminates against every screen reader user who tries to use it.

Municipal and higher-ed sites tend to escape this specific failure mode because their builds drag out and involve more stakeholders. Their problem is different but related. Marketing teams and IT departments are increasingly using AI to ship components, plugins, and one-off pages on top of older codebases. “Oh, you know what, I can go make these things. I just go throw it in and I can use AI, and now I’m a developer.” That is happening across institutions right now, and the resulting accessibility debt does not show up until someone with a screen reader, or a plaintiff’s attorney, finds it.

The deeper issue is that AI tools optimize for code that compiles and looks correct, not for code that works with assistive technology. An automated scan, including the kind built into many AI coding assistants, will happily confirm that an image has alt text. It will not catch that the alt text reads image123.jpg. A human running a screen reader catches that in five seconds. AI does not.

The Big Six: Failures That Should Not Still Be Happening in 2026

WebAIM’s data continues to show six failure types as the dominant offenders across the million home pages it scans. None of them are exotic. All of them are fixable today.

• Low-contrast text: found on 83.9% of home pages
• Missing alternative text on images: 53.1%
• Missing form input labels: 51%
• Empty links: 46.3%
• Empty buttons: 30.6%
• Missing document language: 13.5%

Ask any auditor which of these clients dismiss as minor, and the answer is the ones the client cannot see. Empty buttons, empty links, missing language attributes. These are invisible at the surface and devastating for anyone navigating with a screen reader. Form labels get the same treatment for the same reason. A sighted user looks at a fork icon next to a search box and reads it instantly. A screen reader user gets silence, or worse, gets “button” and no context.

This is the core failure mode the report exposes. Accessibility is not getting ignored because it is hard. It is getting ignored because the people approving the website cannot perceive what is broken.

Why a Delayed Deadline Is Not a Reprieve

In the weeks since the DOJ pushed the Title II compliance deadline to April 2027, and HHS extended Section 504 web compliance to May 2027, a worrying number of public-sector leaders have visibly relaxed. Our team has had the same conversation repeatedly: a client who was panicking in early spring is now telling us they have a year to figure it out.

They do not.

The DOJ’s deadline is the deadline by which the federal government will enforce the law. It is not the date on which the law becomes applicable. The underlying requirement has been in place for years. Private individuals, advocacy organizations, and plaintiff law firms are not required to wait for the DOJ to act. According to data tracked by Seyfarth Shaw’s ADA Title III blog, roughly 5,100 digital accessibility lawsuits were filed in 2025, a 20% increase over the prior year. Almost half were against organizations that had been sued before and failed to remediate properly.

“It is like saying the speed limit here is only 45, but because we are not going to enforce it, you go ahead and blow through. That does not mean you are not breaking the law.”

The plaintiffs landscape has also shifted in a way that should worry every counsel reviewing this. AI tools now let individuals draft and file accessibility complaints without engaging an attorney. The cost to sue has dropped. The trigger is straightforward: someone could not access content on your site. The lawsuit follows.

Federal data underscores how widespread the gap is. The U.S. Access Board’s most recent Section 508 government-wide assessment found that only 37% of tested federal websites met conformance benchmarks. If the federal government is failing its own standard, the assumption that a county portal or a community college LMS is somehow in better shape is not a defensible one.

What Real Remediation Actually Looks Like

If the Big Six are technically fixable, the obvious question is why they keep showing up on more than half of all home pages. Two reasons.

First, automated scanners catch roughly 57% of accessibility issues. The other 43% require a human with assistive technology actually using the site. The scan will tell you the alt text exists. It will not tell you the alt text is useless. It will confirm the form has a label. It will not catch that the label is wrong, or attached to the wrong field, or unread by a screen reader because of how the component was structured.

Second, the overlay industry has spent the last decade convincing organizations that a single line of JavaScript can solve this problem. It cannot. Plaintiffs know it. The Federal Trade Commission’s recent action against accessiBe made that conclusion official. Lawsuits against sites running accessiBe, UserWay, and AudioEye have climbed every year.
An overlay that hides errors does not fix them, and a web accessibility compliance statement that promises adherence without delivering it is closer to a smoking gun than a defense.

A defensible remediation process looks like this:

• Automated scan to surface the obvious failures and quantify scope.
• Human audit using actual screen readers and keyboard-only navigation to catch the 43% that automated tools miss.
• Code-level remediation with specific guidance on what is wrong and how to fix it, not just a list of violations.
• Ongoing monitoring because every new component, plugin, and page can reintroduce failures, especially when AI tools are doing the building.

For organizations carrying large content libraries, the math is more forgiving than it looks. A community college with thousands of pages and tens of thousands of PDFs does not have to remediate each one individually. Most sprawling sites run on twenty or thirty underlying templates and layouts. Fix those, and a majority of the page-level issues resolve. For PDF libraries, start with analytics. Remediate the documents people actually use, post a transparent accessibility statement that invites requests for the rest, and work down the priority list across the compliance window.

What to Do Before April 2027

For municipalities and small public agencies

Commission a human-led audit now. The results give you a defensible baseline, a roadmap you can stretch across two fiscal years, and a website accessibility statement that reflects reality rather than aspiration. Prioritize fixes by traffic and by the severity of impact on assistive technology users. An eleven-month wait-and-see strategy is a wait-and-get-sued strategy.

For community colleges and public universities

Audit the templates, not the pages. For third-party portals and LMS platforms, escalate to the vendor with a written request for WCAG 2.1 AA conformance documentation. They are obligated to provide it, and most of them are quietly behind. Build the PDF remediation program around your highest-traffic documents first.

For HHS-funded healthcare organizations

The Section 504 extension to May 2027 changes nothing about your private litigation exposure. Community health centers and public health departments serve populations with disproportionately high rates of disability. Patient portal accessibility, intake forms, and health information PDFs should lead the remediation queue. Audit immediately and remediate on a schedule that gets you to full conformance well before the enforcement date.

The Real Takeaway

The 95.9% failure rate is the number that will get quoted. The line that should matter more sits in the methodology section: automated tools cannot bridge the gap. The web is being built faster than it is being built accessibly, and AI has accelerated both halves of that equation while only accelerating one of them honestly.

Leaders who hear “April 2027” and think they have a year are misreading the situation. The law is already in force. Lawsuits are already filed daily. The deadline is when the federal government joins the queue.

Get a Real Accessibility Audit

If your last accessibility check was an automated scan, or if you have never had a real audit, the gap between “we look okay” and “we are compliant” is exactly what the WebAIM data is measuring. Blue Atlas Marketing offers free initial accessibility audits for municipalities, school districts, community colleges, and HHS-funded organizations. We use human auditors and assistive technology, and we tell you exactly what needs to be fixed and how.