What Actually Changed?

The ADA has required equal access to government services since 1990. What was missing, until recently, was clear guidance on what “accessible” means in the digital world.

In April 2024, the U.S. Department of Justice filled that gap with a final rule specifying one clear technical standard for web accessibility: WCAG 2.1 Level AA (Web Content Accessibility Guidelines), representing an internationally recognized framework for making digital content usable by people with visual, auditory, motor, and cognitive disabilities.

Before this rule, many organizations were guessing at what was required. Now there is no guesswork.

Does This Apply to You?

The rule applies directly to state and local government entities and their programs, including:

• Cities, counties, and municipalities
• Public schools and independent school districts
• Public universities and community colleges
• Libraries, courts, public utilities, and transit agencies
• State agencies of all kinds

Even if your organization is not a government entity, you may still be affected. Vendors, contractors, and partners who deliver digital content or services on behalf of a public agency are expected to meet the same standards. In other words, if you manage a website, create digital documents, or run social media for a government-adjacent client, this is relevant to you.

The Deadlines at a Glance

April 24, 2026: Public entities serving populations of 50,000 or more

April 26, 2027: Public entities serving under 50,000 people, and special district governments

Every public entity, regardless of size, must ultimately comply. The later deadline for smaller entities gives less-resourced municipalities a bit more runway to prepare.

What Needs to Be Accessible?

More than you might expect. The rule covers digital content that public entities produce and manage, including:

• Websites and web pages
• Mobile apps
• PDFs and downloadable documents
• Online forms
• Videos (yes, captions matter)
• Social media posts created after your entity’s compliance deadline

There are some narrow exceptions, including older archived content that is clearly designated as such and not updated, pre-existing documents maintained for reference purposes, and genuinely third-party content (like public comments). But the large majority of what your team creates and posts going forward falls within scope.

What Does WCAG 2.1 Level AA Mean in Plain English?

The guidelines are built around four principles. Your digital content needs to be:

Perceivable: Accessible through more than one sense. Images need descriptive text alternatives. Videos need captions. Color contrast needs to be strong enough for people with low vision.

Operable: Navigable without a mouse. Someone using a keyboard, voice control, or other assistive technology should be able to get around your site fully.

Understandable: Clear, consistent, and predictable. Plain language helps here, as do labeled form fields and meaningful error messages.

Robust: Compatible across browsers, devices, and assistive technologies.

In practice, this means things like: every image has alt text, every video has captions, your site works by keyboard alone, your PDFs are tagged for screen readers, and you are not relying on color alone to communicate meaning.

The good news: much of this is already good web practice. If your site was built thoughtfully in recent years, you may be closer to compliance than you realize.

Why Accessibility Is Good for More Than Just Compliance

Here is a reframe worth sitting with: accessible design is just better design.

One in four adults in the United States lives with some form of disability. Adults over 50 (one of the fastest-growing online audiences) often depend on features like text magnification, high contrast, and simplified navigation. Captions benefit people watching video in a noisy room. Clear page structure helps everyone scan faster.

When you build for the most varied needs, you build something that works better for everyone.

There is also a meaningful SEO and AI search benefit. A well-structured, accessible website with descriptive headings, labeled images, and clear navigation is far easier for search engines and AI tools to understand and recommend. Accessibility and discoverability are increasingly the same thing.

How to Get Started (Without Getting Overwhelmed)

The idea of auditing your entire website and document library can feel like a lot. But there is a sensible order of operations.

Step 1: Take Stock of What You Have

List your digital assets: your main website, any microsites, mobile apps, PDFs you link to, forms, embedded videos, and any tools or platforms you use to deliver services. You do not need to fix everything at once. Prioritizing high-traffic, high-visibility content first is entirely reasonable.

Step 2: Run a Quick Scan

Free tools like WAVE (wave.webaim.org) or Google’s Lighthouse can give you an immediate read on the most obvious issues on your site. These automated scanners are fast and free, though they catch roughly 30 to 40 percent of accessibility issues. Think of them as a starting point, not a finish line.

Step 3: Get a Real Audit

A comprehensive accessibility audit combines automated scanning with manual review by an accessibility specialist and testing with actual assistive technology – we can help you with this. This is where you will get a full, defensible picture of where you stand and what needs to change.

Step 4: Build It Into Your Workflow Going Forward

The most sustainable approach is not a one-time remediation sprint. It is making accessibility part of how you create content and build digital properties from here on out. That means training your team on alt text, captions, and accessible document creation. It means accessibility reviews as part of your website update process. It means checking vendor contracts to confirm outside partners are meeting the same standard.

Step 5: Put a Feedback Mechanism in Place

The rule also expects organizations to have a way for users to report accessibility barriers. A simple accessibility statement on your website that includes a contact method for feedback is a good start and signals good faith.

Our Approach to Accessibility

Accessibility is not something we talk about from the sidelines. Our own website is built to meet WCAG 2.1 Level AA standards, and we use dedicated accessibility software to support and maintain that compliance.

When we build websites for clients, we implement that software as part of our standard process. It continuously scans the site, remediates issues that can be addressed automatically, and provides users with an accessibility interface that lets them customize their experience based on their needs, including screen reader adjustments, keyboard navigation, color contrast settings, and more.

That said, we want to be transparent about something the accessibility community rightly emphasizes: overlay tools are a powerful complement to accessibility, but they are not a substitute for building accessibly from the ground up. Our approach pairs the software platform with foundational accessibility practices in design and development so that both the underlying code and the user-facing experience meet the standard.

If you are working with a web partner who is not thinking about accessibility at the build level, that is a conversation worth having.

The Bottom Line

The ADA Title II deadline is not something to push to the back burner. But it is also not something to dread. Getting your digital presence to a compliant, accessible state is genuinely achievable — especially if you start with a clear inventory, prioritize the most important properties, and work with partners who know what they are doing.

And once you get there, you will have a website that works better for more of your community, ranks better in search, and holds up against legal scrutiny. That is a good investment no matter how you look at it.

Not sure where your site stands? We’re happy to talk through it with you.