Web Analytics

ADA Website Compliance in 2027: Deadlines, WCAG 2.1 AA and How We Help

ADA website compliance: accessible government website on a laptop beside a braille display and screen reader headphones

ADA website compliance is no longer a “someday” project. The U.S. Department of Justice has set a firm technical standard for state and local government websites, the deadlines are on the calendar, and lawsuits against inaccessible sites keep coming. Whether you run a city, village, township, county office, school district, church, campaign or small business, this guide explains what the rules require, when they take effect, and the practical steps to get your website compliant. It also explains how SnapSite.us has helped organizations build accessible websites since 2007.

What ADA Website Compliance Means

The Americans with Disabilities Act (ADA) was signed in 1990, long before most organizations had websites. Today the web is where residents pay utility bills, read meeting agendas, apply for permits, register for programs and find out when the street will be plowed. If a person who is blind, deaf, has limited mobility or has a cognitive disability cannot use your website, they are shut out of those services.

ADA website compliance means building and maintaining a website that people with disabilities can perceive, operate and understand, including people who use assistive technology such as screen readers, screen magnifiers, voice control software, braille displays or keyboard-only navigation.

In practice, the yardstick everyone measures against is the Web Content Accessibility Guidelines (WCAG) 2.1, published by the World Wide Web Consortium (W3C). WCAG is organized around four principles, often remembered as POUR:

  • Perceivable: information can be seen or heard in more than one way, such as alt text for images and captions for video.
  • Operable: every feature works with a keyboard, nothing flashes dangerously, and users have enough time to complete tasks.
  • Understandable: pages are predictable, forms explain errors clearly, and language is plain.
  • Robust: code is clean enough that assistive technologies can interpret it reliably.

The ADA Title II Rule: WCAG 2.1 AA Is Now the Standard

In April 2024, the Department of Justice published a final rule under Title II of the ADA that, for the first time, set a specific technical standard for the web content and mobile apps of state and local governments. That standard is WCAG 2.1 Level AA. You can read the DOJ’s own summary on ADA.gov.

Title II covers public entities, which includes:

  • Cities, villages, towns and townships
  • Counties and county offices such as clerks, treasurers, assessors and sheriffs
  • Public school districts, community colleges and public universities
  • Special districts such as park, library, fire protection, water and sanitary districts
  • Public health departments, transit agencies and other government instrumentalities

The rule reaches more than the homepage. It applies to the web content and apps a public entity provides or makes available, including content created for it by vendors and contractors. Agendas, minutes, budgets, forms, PDFs, calendars, online payment portals and embedded videos are all part of the picture.

Limited Exceptions

The rule includes a handful of narrow exceptions, such as clearly marked archived content that is no longer used, certain documents posted before the compliance date, some content posted by third parties, individualized password-protected documents, and older social media posts. These exceptions are narrower than many people assume. A preexisting PDF that residents still use to apply for a permit, for example, generally still needs to be accessible. When in doubt, plan to make it accessible.

ADA Website Compliance Deadlines for 2027 and 2028

The original rule required large public entities to comply by April 24, 2026. On April 20, 2026, the DOJ issued an Interim Final Rule that pushed every deadline back by one year. The technical standard did not change; only the dates moved.

WhoOriginal deadlineCurrent deadline
State and local governments with a total population of 50,000 or moreApril 24, 2026April 26, 2027
State and local governments with a total population under 50,000April 26, 2027April 26, 2028
Special district governmentsApril 26, 2027April 26, 2028
ADA Title II web accessibility compliance dates after the DOJ’s April 2026 Interim Final Rule.

Most villages, small cities, townships and counties in rural and suburban areas, including much of Southern Illinois and the Metro East, fall into the under-50,000 group with an April 2028 deadline. That may sound far away, but a full redesign, document cleanup and staff training can easily take a year for a busy municipal office.

Why You Should Not Wait for the Deadline

  • Your ADA obligations already apply. The extension delayed when the specific WCAG 2.1 AA standard becomes mandatory. It did not pause Title II’s existing duty to provide equal access and effective communication, and people can still file complaints and lawsuits today.
  • The extension itself is being challenged. Disability rights groups objected to the delay, and a lawsuit was filed in May 2026 seeking to reverse it. The timeline could change again.
  • Rules may keep evolving. The DOJ has said it may revisit parts of the 2024 rule. Building to WCAG 2.1 AA (or the newer WCAG 2.2 AA, which includes everything in 2.1 AA) is the safest bet regardless.
  • Accessibility is cheaper when built in. Fixing a site during a planned redesign costs far less than retrofitting it under the pressure of a complaint.

Does ADA Website Compliance Apply to Businesses, Churches and Campaigns?

Private businesses and nonprofits that serve the public fall under Title III of the ADA rather than Title II. There is no Title III regulation that sets a specific web standard yet, but the DOJ has long taken the position that the ADA applies to the websites of businesses open to the public, and thousands of website accessibility lawsuits are filed against businesses every year. When courts and settlements spell out what a business must do, WCAG 2.1 AA is the usual benchmark.

For small businesses, churches and political campaigns, an accessible website is both a legal safeguard and a smart move. About one in four U.S. adults reports having some type of disability, and many more are older adults with changing vision, hearing or dexterity. An accessible site reaches more customers, members and voters.

This article is general information, not legal advice. Talk with your attorney about how the ADA applies to your organization.

The Most Common ADA Website Compliance Problems

When we audit municipal and small business websites, the same issues show up again and again. The good news is that most of them are straightforward to fix.

  1. Missing or useless alt text. Images without descriptions, or with file names like “IMG_2041.jpg,” tell a screen reader user nothing.
  2. Low color contrast. Light gray text on white, or white text over busy photos, fails WCAG’s 4.5:1 contrast ratio for normal text.
  3. Inaccessible PDFs. Scanned agendas and minutes are just pictures of text. Screen readers cannot read them unless they are tagged and run through text recognition. See our guide to accessible meeting agendas and minutes.
  4. Keyboard traps and hidden focus. Menus, sliders and pop-ups that cannot be reached or closed with the Tab and Escape keys lock out keyboard users.
  5. Unlabeled form fields. Payment, contact and permit forms without proper labels and clear error messages are impossible to complete with assistive technology.
  6. Videos without captions. Recorded council meetings and promotional videos need accurate captions, not just auto-generated ones left unreviewed.
  7. Vague links. A page full of “Click here” and “Read more” links is meaningless when a screen reader lists links out of context.
  8. Broken heading structure. Headings chosen for their font size rather than their meaning make pages hard to navigate.
  9. Third-party tools. Payment processors, calendars and embedded maps from outside vendors can fail even when your own pages pass.

A Note About Accessibility Overlays

Some vendors sell a single line of code that adds an accessibility toolbar and promises instant compliance. A toolbar that lets visitors enlarge text or switch contrast can be a helpful extra, but an overlay alone does not fix missing labels, inaccessible PDFs or broken code underneath. Many businesses that relied only on an overlay have still been sued. Real ADA website compliance comes from fixing the site itself.

A 7-Step Plan for ADA Website Compliance

Here is the roadmap we recommend to the municipalities and organizations we work with. You can use it whether you work with us or not.

1. Run an Automated Scan

Start with our free ADA compliance scanner to get a quick picture of contrast errors, missing alt text, empty links and other machine-detectable issues. Automated tools typically catch only part of the problems, so treat the results as a starting point.

2. Do a Manual Review

Unplug the mouse and try to use your site with only the keyboard. Then try your most important pages with a free screen reader such as NVDA on Windows or VoiceOver on Mac and iPhone. Can you pay a bill, find the next meeting agenda and submit a form? Our ADA compliance checklist for municipal websites walks through what to test.

3. Inventory Your Documents

List every PDF, Word file and spreadsheet on your site. Decide what can be archived, what can be turned into a regular web page, and what must be remediated. For new agendas and minutes, create them accessibly from the start so the backlog stops growing.

4. Fix the Foundation

Your theme, menus, templates and forms affect every page on the site. Fixing them first gives you the biggest improvement for the effort. If your site is old or built on a platform that makes this hard, a redesign may be the most cost-effective path.

5. Check Your Vendors

Ask payment, agenda management, calendar and video vendors for a current accessibility conformance report (often called a VPAT). Build WCAG 2.1 AA requirements into new contracts and renewals.

6. Train the People Who Post Content

Most accessibility problems are introduced after launch by well-meaning staff who upload a scanned document or a photo without alt text. A short training session for clerks, administrators and department heads prevents most of these mistakes.

7. Publish a Statement and Keep Monitoring

Post an accessibility statement that explains your commitment and gives people a phone number and email to report problems or request information in another format. Then rescan regularly. ADA website compliance is ongoing maintenance, not a one-time checkbox.

How SnapSite.us Helps With ADA Website Compliance

SnapSite.us has built websites for municipalities, government agencies, campaigns, churches and small businesses since 2007. We are a service-disabled veteran-owned small business, and our founder is a former county executive and city council member who knows firsthand how much a small municipal staff juggles. Accessibility is built into every site we deliver, not bolted on afterward.

  • Accessibility audits: automated scanning plus hands-on keyboard and screen reader testing, with a plain-English report that ranks issues by impact.
  • ADA-compliant website design: new municipal websites built to WCAG 2.1 AA, mobile-friendly, fast and easy for staff to update.
  • Remediation of existing sites: if you are not ready for a redesign, we fix contrast, headings, menus, forms, alt text and code on the site you have.
  • Accessible agendas and documents: tools and workflows for posting agendas, minutes and ordinances as accessible web content instead of scanned PDFs.
  • Built-in accessibility tools: our Snap Accessibility and ADA Auditor plugins help visitors adjust the display and help your staff spot problems before they go live.
  • Staff training: short, practical sessions so your team keeps the site compliant after launch.
  • Ongoing monitoring and hosting: managed WordPress hosting with security, backups, updates and regular accessibility checks.

Because we work with small towns every day, our pricing is built for small budgets. We would rather help a village of 800 get compliant than watch it pay for a lawsuit settlement instead of a street repair.

ADA Website Compliance FAQ

What standard does my website need to meet?

For state and local governments, the DOJ’s Title II rule requires WCAG 2.1 Level AA. For businesses and nonprofits, WCAG 2.1 AA is the standard most often used in settlements and court orders.

When is the ADA website compliance deadline for my town?

Governments with a total population of 50,000 or more must comply by April 26, 2027. Governments under 50,000 and special districts must comply by April 26, 2028, under the DOJ’s April 2026 extension. Your general ADA obligations apply now.

Do our PDFs and meeting minutes have to be accessible?

Generally, yes. Documents you post for the public to use are covered. There are limited exceptions for some archived and older documents, but anything residents still rely on should be accessible.

Will an accessibility widget make us compliant?

Not by itself. A toolbar can be a useful extra, but the underlying site still has to meet WCAG 2.1 AA.

How long does it take to make a website compliant?

A small site with few documents can often be remediated in a few weeks. A larger municipal site with years of PDFs may take several months, which is why starting now matters.

Get Started With a Free ADA Website Check

The deadlines are set, the standard is clear, and the work is manageable when you start early. Run our free ADA compliance scanner today, then contact SnapSite.us or call (618) 539-2281 for a no-pressure review of your results. We will tell you honestly what needs fixing, what it will cost, and how to get your website accessible to every resident and customer you serve.

You May Like

Your Promotional Content goes here

Categories
Secret Link