Skip to main content

In Accessibility, Later Means Never

Throughout my digital accessibility work, one question keeps coming up: does this need to be accessible now, or can it wait until after the deadline?

Imagine launching something a portion of your audience can't use, but publishing it anyway because a date on a calendar said you had to. That happens constantly. Every time it does, people with disabilities get excluded.

Later most likely means never

Let's be honest. If you are consistently putting digital accessibility on the back burner, it means digital accessibility is not a priority for you or your organization. What's worse is when you are having these discussions, which is great, and you are aware of the limitations, but you are actively choosing not to be accessible.

You don't have to take my word for it. On April 20, 2026, four days before state and local governments were required to meet WCAG 2.1 Level AA under the ADA Title II web rule, the Department of Justice pushed the deadline back a year. Compliance is now April 2027 for larger entities and April 2028 for smaller ones. The reasons for the delay included resource constraints, staffing limitations, and remediation technology, generative AI among it, that hasn't delivered what people hoped. The rule had been on the books since 2024. Two years of notice and the work wasn't done.

That is "later means never" playing out on a national scale. The DOJ says it fully anticipates enforcing at the new deadline, and the underlying obligation never went away. Private ADA lawsuits didn't pause for a year either.

Elsewhere, nobody is waiting. The European Accessibility Act has been enforceable since June 28, 2025, and it applies to any organization selling into the EU, including American ones.

Many equate digital accessibility work with something time-consuming and costly. I'd argue the opposite. If you bake digital accessibility into your everyday workflow instead of putting a quick fix on your site at the end, it is very doable.

This is where I come in. If you had all of the tools at your fingertips to make your website digitally accessible for all, many of you would do it. That signals a workflow problem, and workflow problems can be fixed.

Accessible first

For the longest time in the web world, it was drilled into us: we MUST be mobile-first. The new one is shorter. Accessible-first. If people can't get in, nothing else you built matters.

The process is similar to what mobile-first asked of us. It requires planning, and the earlier you integrate accessibility into your projects, the better. It requires understanding how people with disabilities actually use websites and other digital platforms, then using that information when you build. I recommend consulting with organizations whose mission is to help people with disabilities. Work with them, watch how they use technology, find the pain points.

Then you start building, and you start seeing deviations from your plan. Something you planned for doesn't look right, or it isn't going to work as well as you thought.

This is where we drift. You start making decisions on the fly, and if you aren't careful, this is exactly where accessibility slides back onto the back burner.

It's also where your workplace culture around accessibility shows itself. If your team is trained and constantly looking for ways to improve accessibility, drift feels like a pivot. If it isn't, drift feels like a mountain.

Trying is not enough. Build the systems that make sure accessibility survives contact with the design and build stages. It is not optional, so stop treating it that way.

How I build accessible-first

1. Plan first, and plan with real users in mind. Decide what accessible means for this project before you write a line of code. Bring in people who use assistive technology, or the organizations that support them, while the plan is still cheap to change.

2. Use what you're building. Not a demo of it. Actually use it, the way someone landing on it cold would. This is how you find the things you overlooked.

3. Look for the gaps and ask questions. Where did the build drift from the plan? What decision did you make on the fly last Tuesday that nobody has checked since?

4. Try to break it. Unplug the mouse. Turn on the screen reader. Tab through the whole thing. Shrink it, zoom it to 400%, throw bad data at it. You will find problems, and you will understand what you built far better than you did before.

5. Verify, then review again. Because something is always missed.

When I was building my personal journal, I wanted it to feel alive and deeply personal. One of the features shows the weather conditions on the feed page as they are right now. On individual posts, it shows what the weather was like when I wrote the entry.

I wanted to take it one step further and add the time of day.

That complicated things. Now I wasn't just handling different weather conditions, I was handling weather conditions crossed with time of day; and that combination can become inaccessible fast. Every one of those combinations, 1,104 of them in total, had to be checked for color contrast. Not the ones I thought were risky. All of them.

I used Claude Code to help work through that matrix, then checked its output and flagged what needed adjusting, and for some it did need adjusting. If you use AI in your work, this step matters more, not less. Never take what AI produces at face value. Check it, then check it again.

A weekend of planning and building, plus a few days of review, got the rebrand done. Accessible-first didn't slow that down. Skipping it and retrofitting later is what would have cost me weeks.

I'm still going over the updated design and styles, because something always is missed.

A more accessible web starts with you

I believe in practicing what you preach and leading the change you want to see online and in the world. Each one of us has a responsibility to make sure what we produce can be accessed by everyone.

That includes captioning videos, making sure background and foreground have enough separation so text can actually be read, breaking complex topics into information people can understand, and making sure your website works without a mouse — to name a few.

Let's work together to make the web a better, more inclusive place for everyone.