Experience Design

The ADA Website Rule: What Tennessee Cities, Counties, and Districts Need to Know

The gold-lettered City Hall sign on the white pediment of a historic city hall with a clock tower

Every city, county, school system, and special district in Tennessee must make its website and mobile apps accessible to people with disabilities. The U.S. Department of Justice’s rule under Title II of the Americans with Disabilities Act sets the standard at WCAG 2.1 Level AA. Governments with 50,000 or more residents must comply by 04/26/2027. Smaller governments and every special district must comply by 04/26/2028.

Those dates moved once already. In April 2026, the Department of Justice pushed each deadline back a year. It did not change what the rule requires, and it was clear that the underlying duty to be accessible did not pause. For most public bodies in Middle Tennessee, the work is bigger than it looks, and the time to start is now.

Who Does the ADA Website Rule Cover?

The rule covers every state and local government entity, no matter its size. In Tennessee, that includes:

  • Cities and towns, from Franklin and Murfreesboro to towns of a few thousand people
  • Counties, including their departments, courts, and offices
  • School systems, including special school districts
  • Special districts: utility districts, emergency communications (911) districts, housing authorities, airport authorities, library boards, and development districts

Special districts land in the later tier no matter how many people they serve. Tennessee alone has 171 utility districts, according to the state Comptroller. Many of their websites were built years ago by a local vendor and haven’t been reviewed for accessibility since.

Organizations that receive funding from the U.S. Department of Health and Human Services face a separate rule under Section 504, with the same standard. Recipients with 15 or more employees must comply by 05/11/2027, and smaller recipients by 05/10/2028. That reaches community health centers, Medicaid providers, Head Start programs, and many nonprofits.

What Are the Deadlines?

Who Deadline Standard
Governments with 50,000+ residents 04/26/2027 WCAG 2.1 AA
Governments under 50,000 and all special districts 04/26/2028 WCAG 2.1 AA
HHS-funded organizations, 15+ employees 05/11/2027 WCAG 2.1 AA
HHS-funded organizations, fewer than 15 employees 05/10/2028 WCAG 2.1 AA

Population is based on Census Bureau figures. If your city sits near the 50,000 line, confirm which tier you fall in before you plan around a date.

What Does the Rule Actually Cover?

The rule covers everything a public entity provides online, not just the homepage. That includes:

  • Every page of the website, including ones a vendor manages for you
  • Documents posted on the site: PDFs of meeting minutes, agendas, budgets, water quality reports, applications, and forms
  • Online services: bill pay, permit applications, service requests, and job applications
  • Video and audio: recorded board meetings and public service announcements need captions
  • Mobile apps the entity offers to the public

Documents are where most organizations underestimate the work. A utility district may have a modern-looking website and hundreds of scanned PDFs that a screen reader can’t read at all. Content a government provides through a contractor is also covered, so a payment portal or agenda system run by a third party still has to meet the standard.

Are There Exceptions?

Yes, and they are narrow. The rule exempts:

  • Archived content kept only for reference, stored in a clearly marked archive, and not changed since it was archived
  • Documents posted before the compliance date, unless people still use them to apply for, access, or take part in a service
  • Content posted by members of the public, such as comments on a city’s page
  • Individual documents behind a password, such as a single resident’s bill
  • Social media posts made before the compliance date

Each exception has conditions. A permit application posted in 2019 that residents still download today is not exempt. When in doubt, plan to fix it.

What Is WCAG 2.1 AA in Plain English?

WCAG, the Web Content Accessibility Guidelines, is the international standard for accessible websites. Level AA is the middle tier and the one the law points to. In practice, it means:

  • People can see it. Text has enough contrast against its background, and images have text descriptions a screen reader can announce.
  • People can use it without a mouse. Every link, menu, and form works with a keyboard alone.
  • People can understand it. Pages have clear headings, form fields have labels, and error messages explain how to fix the problem.
  • It works with assistive technology. The code is structured so screen readers and voice control software can interpret it.

We cover the most common failures, and how to fix them, in What an Accessible Website Actually Requires.

How Far Off Are Most Public Websites?

Further than most administrators expect. When we ran automated tests on a sample of utility district and city homepages in Middle and East Tennessee, every site failed at least one WCAG check. The common issues were low-contrast text, headings out of order, links with no readable name, and pages that block zooming on a phone.

Automated tools catch only part of the problem. Keyboard access, screen reader behavior, captions, and documents need a person to test them. A site that scores well on an automated check can still fail a resident who relies on a screen reader to pay a water bill.

Where Should a Public Entity Start?

  1. Confirm your deadline. Check your population tier, or whether you are a special district or HHS recipient.
  2. Inventory what you publish. List your pages, PDFs, forms, videos, and any third-party systems residents use.
  3. Test the pages people use most. Start with bill pay, service requests, meeting information, and contact pages.
  4. Fix or replace. Some sites can be fixed in place. Others are cheaper to rebuild on an accessible foundation than to patch.
  5. Fix documents going forward. Set a standard so every new PDF is accessible before it’s posted.
  6. Publish an accessibility statement. Tell residents how to report a problem and how you’ll respond. See our own statement for an example.
  7. Keep checking. Content changes every week. Accessibility is maintained, not finished.

Avoid shortcuts that promise compliance with a single line of code. Accessibility widgets and overlays don’t change the underlying website, and they don’t meet the rule.

How Gridwell Helps

Gridwell builds and maintains ADA compliant websites for public and publicly funded organizations across Middle Tennessee. We start with a free Accessibility Snapshot: an automated test of your homepage and key pages, your deadline, and the top issues to fix, written for a board or council rather than a web developer. From there, we can audit, fix, or rebuild the site and keep it accessible as your content changes.

Frequently Asked Questions

Does the ADA website rule apply to small towns and utility districts?

Yes. The rule covers every state and local government entity regardless of size. Governments under 50,000 residents and every special district, including utility districts, must comply by 04/26/2028.

What standard does the ADA website rule require?

WCAG 2.1 Level AA, the Web Content Accessibility Guidelines published by the World Wide Web Consortium.

Do PDFs on our website have to be accessible?

Yes, in most cases. Documents posted on or after the compliance date must be accessible, and older documents are covered if people still use them to apply for or access a service.

Are we covered if a vendor runs our website or payment portal?

Yes. The rule covers content a public entity provides through contractors and vendors, so third-party systems residents use must also meet WCAG 2.1 AA.

Will an accessibility widget make our site compliant?

No. Widgets and overlays change how a page looks in the browser but don’t fix the underlying code, documents, or forms. The rule requires the website itself to meet WCAG 2.1 AA.

Find out where your website stands

Request a free Accessibility Snapshot. We'll test your homepage and key pages, then send a one-page report with your deadline and the top issues to fix.