The ADA Title II website rule, in plain language.

State and local governments must make their websites, mobile apps and online documents meet WCAG 2.1 Level AA. Governments serving 50,000 people or more must comply by April 26, 2027. Smaller governments and all special districts must comply by April 26, 2028.

Last checked

The short answer

In April 2024 the U.S. Justice Department added web and mobile app rules to its ADA Title II regulation. They say a public entity’s web content and mobile apps must conform to WCAG 2.1 Level AA, an international accessibility standard.

The original deadlines were April 24, 2026 and April 26, 2027. An interim final rule published on April 20, 2026 moved each deadline back one year, to April 26, 2027 and April 26, 2028. Nothing else in the rule changed. The extension is being challenged, so check the current dates before relying on them. We update this page when they change.

  • Population of 50,000 or more: April 26, 2027
  • Population under 50,000: April 26, 2028
  • Special district governments: April 26, 2028

Who is covered

Every state and local government entity, and the departments and agencies that are part of it. That includes cities, towns, townships and counties, state agencies, public schools, colleges and universities, public libraries, transit agencies and special districts such as water, sewer, park, fire and hospital districts.

Your deadline depends on total population, not on how many people you employ or serve. Cities, towns and counties use their 2020 Census population. Independent school districts use the Census Bureau’s school district estimates. A department or agency without its own count uses the population of the government it belongs to. Special districts don’t have a population count under the rule, so they all get the later date.

  • Cities, towns, townships and counties
  • State agencies
  • Public schools, colleges and universities
  • Public libraries and transit agencies
  • Special districts

What has to be accessible

Everything you make available on the web or in a mobile app, including content a vendor provides or runs for you under a contract. If a company hosts your payment portal, agenda software or permit forms, that content is covered too.

Documents count. Agendas, minutes, forms, reports and newsletters posted as PDFs, Word files or spreadsheets are part of your web content.

  • Web pages and web apps
  • Mobile apps
  • PDFs, Word files and spreadsheets
  • Online forms and payments
  • Video and audio
  • Vendor-hosted tools and portals

The exceptions

The rule lists five kinds of content that don’t have to meet WCAG 2.1 AA. Each has conditions, and you may still need to provide an accessible version when someone with a disability asks for one.

Archived content. Content created before your deadline, kept only for reference or recordkeeping, stored in an area labeled as an archive, and not changed since.

Older documents. PDFs and other documents posted before your deadline, unless people still use them to apply for or use your services.

Third-party posts. Content posted by people who aren’t acting for you, such as public comments.

Individual secured documents. Password-protected documents about one person, property or account, such as a utility bill.

Older social media posts. Posts made before your deadline.

Documents are usually the biggest job

For most small governments, documents take more time than the website. Many town and district sites have hundreds of PDFs, and some are scanned images that a screen reader can’t read at all.

You have four choices for each document: fix it, turn it into a web page, move it to a properly labeled archive, or take it down. Current forms and applications have to be accessible no matter when they were posted. Meeting agendas and minutes posted after your deadline do too.

  • Fix the document
  • Turn it into a web page
  • Archive it with the conditions met
  • Remove it if no one needs it

Overlays and widgets

Some companies sell a widget that adds a menu of display options and promises instant compliance. The rule requires that your content itself conforms to WCAG 2.1 AA. A widget doesn’t fix missing form labels, untagged PDFs or a site that can’t be used with a keyboard, and many people who rely on screen readers find these widgets get in the way. We don’t sell or recommend them.

What happens if you miss the deadline

The Justice Department can investigate complaints and take action, and people with disabilities can sue public entities under Title II for a court order and attorneys’ fees. The rule does allow that a minor failure that doesn’t affect anyone’s use of the site may not be a violation, but you have to be able to show that.

This page explains the rule in general terms. It isn’t legal advice, so ask your attorney about your situation.

What it costs

An accessibility audit from us starts at $2,000 for a typical site, with a fixed price based on the number of page templates and documents to test. Fixes are quoted from the audit. Document work is priced once we see a sample of your files, because a scanned 40-page report and a one-page form are very different jobs.

Many sites need template fixes more than page-by-page work. Fixing a header, menu or form template once fixes it everywhere it appears.

What to do now

  1. Inventory

    List your sites, apps, vendor tools and documents, and note which documents people use to apply for or use services.

  2. Check

    Run an automated check to find the obvious problems, then have a person review key pages, because automated tools catch only part of the issues.

  3. Fix templates

    Fix the shared templates first: menus, headers, forms and page layouts. Each fix covers every page that uses it.

  4. Handle documents

    Fix, convert, archive or remove documents, starting with forms and anything people need to use your services.

  5. Publish a statement

    Post an accessibility statement with a way to report problems and ask for an accessible version.

  6. Keep it up

    Train the people who post content and check the site regularly, so new pages and documents don’t undo the work.

Common questions

Does the extension mean we can wait?

It gives you more time, not less work. A typical audit, fixes and document cleanup take months, and the extension is being challenged in court. Starting now leaves room for budget cycles and procurement.

Which deadline applies to us?

If your total population is 50,000 or more, April 26, 2027. If it’s under 50,000, or you’re a special district, April 26, 2028. Cities, towns and counties use their 2020 Census population.

Do we have to fix old meeting minutes?

Not if they were posted before your deadline and nobody uses them to apply for or take part in your services, or if they’re in a properly labeled archive. You may still need to provide an accessible version when someone asks. Minutes posted after your deadline must be accessible.

Our website vendor says they’re compliant. Are we covered?

You’re responsible for content provided for you under a contract, including vendor-hosted tools. Ask the vendor for a recent accessibility report against WCAG 2.1 AA, and test the parts of the site people use most.

Is WCAG 2.2 required?

No. The rule requires WCAG 2.1 Level AA. Meeting WCAG 2.2 as well is good practice and covers 2.1.

Can an automated checker tell us if we comply?

No. Automated tools are a good first step, but the Justice Department says you can’t rely on them alone. A person has to check things like keyboard use, reading order and whether image descriptions make sense.

Does this apply to private businesses?

This rule covers state and local governments under Title II. Businesses open to the public fall under Title III of the ADA, which doesn’t have a specific web rule but is often the basis for website lawsuits.

Find out where your site stands.

Tell us your website and roughly how many documents you publish. We’ll reply within one business day with next steps.