AX/4E titleiichecklist.com
The free ADA Title II web accessibility checklist

FREE TITLE II READINESS QUIZ · CITIES & COUNTIES

Could this happen at your city or county?

A resident can't pay a water bill, request a record, or report a pothole because the page, form, or payment flow isn't accessible. The ADA Title II web rule covers every online service your government offers. Five scenarios show where you stand. Large entities have until April 26, 2027; smaller ones until April 26, 2028.

April 26, 2027Large public entities (population 50,000 or more)
April 26, 2028Small entities and special district governments
WCAG 2.1 AAThe required standard for web content and mobile apps

Your deadline follows the population of the jurisdiction you serve. Cities and counties of 50,000 or more residents face April 26, 2027.

Could this happen to us? Take the quiz Get the full checklist

QCould this happen to us? The 5-scenario quiz

Two minutes, no email required. Each scenario is real and each has an easy next step. "Not sure" counts as no, because if you're not sure, nobody owns it yet.

1. Can residents pay bills, request records, apply for permits, and report problems on your site?

What if: A resident with a disability cannot pay a utility bill online and faces a late fee, or cannot file a records request the law entitles them to.

Why it matters: Core civic transactions are the highest-stakes content you have, because exclusion has a direct cost to the resident.

2. Could someone complete your top transaction start to finish with a keyboard?

What if: A resident using a keyboard or screen reader gets stuck at a payment field and can't finish, so the service is closed to them.

Why it matters: Keyboard access is a baseline of WCAG 2.1 AA and the fastest way to find where a flow breaks.

3. Are your council agendas, budgets, and public notices readable by assistive technology?

What if: A resident who wants to comment at a council meeting can't read the agenda PDF, so they can't participate in their own government.

Why it matters: Public-meeting documents are current-use content tied to civic participation; the document exception does not cover them.

4. Do your software and website vendors' contracts require accessibility?

What if: Your payment portal fails for a resident with a disability. The vendor points at the contract; the contract says nothing about accessibility.

Why it matters: Vendor platforms you provide under contract are your responsibility under the rule, not the vendor's alone.

5. Does your government have an accessibility statement, an owner, and a plan?

What if: A resident hits a barrier and has no one to contact and no alternative way to get the service done.

Why it matters: A named owner and a public statement turn good intentions into accountable, documented good faith.

What counts as city and county web content?

Department pages, online bill pay and permitting, records-request and report-a-problem forms, council agendas and minutes, budgets and public notices, job applications, maps, e-newsletters, social posts, and every PDF linked from them.

The city and county traps

Third-party payment and permitting portals with weak keyboard support; scanned agendas and notices posted as image-only PDFs; inaccessible online forms for records and complaints; and department microsites nobody remembers to maintain.

What's the easy next step?

You don't need to fix everything this month. You need a list, an owner, and a start. The free checklist gives you all three: 5 plain-language items for whoever runs the office, 10 technical items for whoever runs the website.

Get your Title II checklist Start with a simple readiness review

Powered by AX4E — practical accessibility help for websites, documents, forms, and public communication.

Questions people ask

Which deadline applies to our city or county?

It depends on population. Entities serving 50,000 or more must comply by April 26, 2027. Smaller entities have until April 26, 2028. Use the population of the jurisdiction you serve.

Does the rule cover every department, including police and fire?

Yes. Every department is covered: police, fire, public works, clerk, courts, elections, and parks. Any web content or app residents use to access services must meet WCAG 2.1 AA.

Our payment and permitting tools are third-party platforms. Are we responsible?

Yes. Content provided under contract is not excepted. Put WCAG 2.1 AA in the contract at renewal and request the vendor's conformance report.

More readiness quizzes: Schools · Libraries · Parks · Transit · PDFs · Forms.