The State of Accessibility and AI in 2026

The State of Accessibility and AI in 2026: What Every Business Needs to Know

I have spent eight years in accessibility, since 2017. I am a blind developer, so I do not study this from the outside, I live in it every day with a screen reader. In that time I have tested products, trained teams, consulted, and built the tools, and I am still in the weeds doing screen reader testing every single week. So when I tell you the ground is shifting under this industry, it is not a hot take. It is what I am watching happen in real time, from the inside. I run accessibility at a small company now, but I have also done this work inside some of the biggest names in the field, so I have seen how it gets done at every scale. That is exactly how I know it is not working for most people.

Here is where the accessibility industry actually stands in 2026, and what every business shipping software right now needs to understand, because most of them have no idea how much the rules just changed. I am not writing this to scold anybody. I am writing it because the people who most need this are the ones least likely to hear it, and I would rather you hear it from me now than from a lawyer later.

Accessibility is not glamorous, and that is part of the problem

Let me just say the quiet part out loud. Accessibility is not exciting. It is not the feature that gets you on the front page. It is not the thing that makes your demo pop. For most people building something, it is the thing they will deal with later, if at all.

I get it. But “later, if at all” is exactly how we ended up where we are. And where we are is a place where the people who most need to do accessibility are the least equipped to.

The industry priced out the people who need it most

Here is the part that actually bothers me. Accessibility, as an industry, is not built for everybody. It is built for big companies with budgets.

A full accessibility audit usually runs a few thousand dollars, commonly somewhere between 2,500 and 10,000, and the services that put a real disabled person in front of your product start around 4,500 dollars and are aimed at enterprises. If you are a small business or a solo developer, that is just out of reach. So you do nothing. Not because you do not care, but because the front door costs more than you have.

And doing nothing is getting more dangerous, not less. Website accessibility lawsuits jumped about 37 percent last year, with more than 2,000 filed in just the first half of 2025, and most of them hit e-commerce and small businesses. There is no small business exemption. The demand letters alone ask for ten to twenty-five thousand dollars to settle. So the people who cannot afford a 5,000 dollar audit are the exact people getting hit with a 15,000 dollar demand letter. That is backwards.

I do not want to say accessibility is broken. But it needs to change, because right now it leaves out almost everybody who is not a large company.

Then AI showed up and changed the math

Now add AI to all of this.

Everybody is coding with AI now. There is even a name for it, vibe coding, a term Andrej Karpathy coined in early 2025 for building software by describing what you want in plain language and letting the AI write the code, guiding it by prompting and testing instead of reading every line. And honestly, it is amazing. People who could never ship software before are shipping real things now. I love that.

But here is what I need people to hear. Accessibility is more important now than it has ever been, even though a lot of people are quietly acting like it matters less. And the reason is simple: accessibility is not a strength of AI.

The research is pretty blunt about this. Large language models produce inaccessible code by default, and the newest models did not fix it. In one recent benchmark, models passed accessibility checks only a few percent of the time, with several WCAG failures in a single sample, and the hardest pages failed completely. AI is good at some pieces, like contrast and basic semantic HTML, but it misuses ARIA, it misses anything dynamic, and it has no idea what it is actually like to use the thing with a screen reader. AI is not your accessibility expert.

So put it together. We have more people shipping more code faster than ever, using a tool that does not prioritize accessibility in what it produces. Which means, day by day, the things we all rely on are getting less accessible, not more, even as there are more of them. And this is not just websites. It is mobile apps, it is the AI experiences everyone is bolting on right now, it is all of it. If a real person uses it, it is in scope, and most of it was never checked by anyone who actually navigates the world the way I do. That is the trend I keep seeing, and it is the one nobody wants to talk about.

And the field already agrees, even if the hype does not

I want to be clear that I am not out on a limb here. If you read what the serious people in accessibility are saying about 2026, the consensus is remarkably consistent. AI helps when you pair it with knowledgeable human reviewers, and it hurts when you let it replace them. One industry roundup put it perfectly: teams that expect AI to do accessibility for them will keep missing the real barriers, just faster than before. Another expert was blunter, that in the right hands AI is a genuinely useful tool, and in the wrong hands it is how snake oil salesmen swindle people who do not know any better.

That is exactly the line I walk, and it is why I built things in two halves. You need the tool inside the workflow, and you need a real human who lives this to catch what the tool never will. Not one or the other. Both. The whole industry is converging on that answer. The only thing missing is making it reach the people who are not big enough to afford a seat at that table.

What the industry actually needs to do

I think we need to go back to the basics of accessibility, and we need to help a whole new group of people who never had to think about this before.

The vibe coder shipping their first app is not a bad person. They just do not know what a screen reader is, and nobody ever taught them. Most of the indie developers I talk to every single day have never used one. So if we want them to care, we cannot hand them a 200-page WCAG document and a five-figure invoice. We have to meet them where they are.

That means two things have to change. The tools have to bring accessibility into the way people actually build now, which is with AI. And the services have to become something a normal person can both afford and understand. Self-serve options exist, but they mostly assume you already know the vocabulary. The big firms are all chasing big businesses. Almost nobody is thinking about how you make accessibility affordable and approachable for everybody else.

This is why I built what I built

So I stopped waiting for the industry to fix it and started building.

The first piece is on the AI side. Since AI will not prioritize accessibility on its own, a group of us built something that makes it. Together with Jeff Bishop and the Community Access folks, I helped build a team of accessibility agents that plug into the AI coding tools people already use, Claude Code, GitHub Copilot, and Claude Desktop, and review the interface as it is being written. The accessibility work happens while you build, by agents that actually know what good looks like, instead of being something you bolt on at the end or after you get sued. They are open source, because gatekeeping the fix would defeat the entire point. You can find them here: the accessibility agents on GitHub.

The second piece is the human side, and it is the one I am most excited about. Back in 2021, I really sat with something I had known for years from doing this work: accessibility was long, arduous, expensive, and intimidating, and that is exactly why people avoided it. It had quietly become a thing you only do when a lawyer makes you. That is not how it should feel.

I think accessibility should be personal. It should be effective. And it should be easy enough for someone who genuinely wants to do right by their users but has no idea where to start. That is what my teardowns are. I actually use your product the way a blind customer would, with a screen reader, and I tell you in plain terms where it works and where it falls apart, for a price a small business can actually say yes to. No 200-page report, no five-figure invoice, no lawsuit required.

This is bigger than me, and it takes all of us

I want to be clear about something. I am not trying to corner a market here. I am trying to open one up.

Accessibility has to be democratized. Right now it sits behind big budgets and big firms, and the knowledge sits with a small group of specialists, and that has to change. The people building the future, the indie developers, the small teams, the founders vibe coding their first product, need to be let in, not priced out and not talked down to. That means spreading awareness, sharing what we know instead of guarding it, and making the on-ramps cheap and human instead of expensive and intimidating.

And no one person does this alone. The accessibility community is small. But we are mighty, and we always have been, because we are the people who actually live this every day. So this is a genuine call to everyone in this field, and to everyone building with AI right now. Let’s work together. Let’s stop locking accessibility behind five-figure invoices and start treating it like the basic right it is. Let’s meet this new wave of builders where they are and bring them in instead of shutting them out.

Because here is what I actually want. In an AI economy where anyone can build anything, I want everyone to succeed, the builders and the disabled people who deserve to use what they build. Those are not competing goals. They are the same goal. We just have to decide, together, as an industry, to build it that way.

How to actually start

If you build things, here is the one thing I would ask. Stop treating accessibility as the thing you will get to someday. The someday version is the lawsuit version, and it is the most expensive and least kind version there is.

You do not have to become an expert overnight, and you do not have to do it alone. You just have to start small. That is what my teardowns are for. I use your product the way a blind customer would, on real screen readers, and I give you a clear, honest, prioritized read on where it actually stands and what to fix, for a price a small business can say yes to without flinching. I publish them in public too, so you can see exactly what you are getting before you spend a dollar. When you want one of your own, it is right here: book a teardown.

And if you are not sure where you stand, or you just want to talk it through, my door is always open. I am always available, for a teardown, for a bigger review down the road, or honestly just to point you in the right direction. Tell me what you are building, and I will give you the truth about where it stands, no pressure either way.

The industry priced accessibility like a luxury. I have spent eight years proving it is a basic, and I am building it that way. If that is the kind of accessibility you believe in, come build it with me.