ADA Title II web accessibility: deadlines, documents and a practical plan

ADA Title II is the part of the Americans with Disabilities Act that covers state and local governments. A Department of Justice (DOJ) rule under Title II requires their web content and mobile apps to meet WCAG 2.1 Level AA, and that includes the documents they post: PDFs, Word files, presentations and spreadsheets. Public entities serving 50,000 or more people must comply by April 26, 2027. Smaller entities and special district governments have until April 26, 2028. This guide explains who's covered, what the standard means in plain terms, the five exceptions, and a step-by-step plan for your documents.

The short version

• Who: state and local governments and their departments and agencies, including public school districts, public colleges and universities, and special districts.
• What: web content and mobile apps must meet WCAG 2.1 Level AA. Web content includes PDF, Word, PowerPoint and Excel files.
• When: April 26, 2027 if your total population is 50,000 or more. April 26, 2028 if it's under 50,000, or if you're a special district government.
• Exceptions: five narrow ones, including some archived content and some documents posted before your compliance date.
• After that date: every new document you post has to meet the standard. Clearing the backlog is a project. Keeping up is a routine.

Who's covered

Title II applies to every "public entity": any state or local government and its departments, agencies and other instrumentalities. In practice, that includes:

• States and state agencies
• Counties, cities, towns, villages and townships
• Public school districts
• Public colleges and universities, as part of the state or local government they belong to
• Special districts, such as water, transit, parks, library, fire, port and hospital districts
• Courts, police departments, public libraries and transit agencies

The rule covers content you provide "directly or through contractual, licensing, or other arrangements." If a vendor runs your agenda portal, online payments, permit system or learning platform, the content it provides for you is still your responsibility.

The rule doesn't cover private businesses, which fall under ADA Title III, or federal agencies, which follow Section 508. Private colleges aren't covered by this rule, though Section 504 and Title III apply to many of them. Healthcare providers funded by the Department of Health and Human Services (HHS) have a parallel rule with its own dates. See our Section 504 guide.

Who owns the work. If your organization has 50 or more employees, it must already have a designated ADA coordinator (28 CFR 35.107). That person is a natural owner for this project, working with communications, IT, records staff and every department that posts documents.

Deadlines

Your date depends on your "total population," which the rule ties to Census Bureau figures:

• Most governments use their population from the most recent decennial Census.
• Independent school districts use the Census Bureau's Small Area Income and Poverty Estimates, not enrollment.
• A department or agency without its own figure uses the population of the government it belongs to. A city police department uses the city's population.
• Special district governments have the later date, whatever their size.

Not sure which date applies? The deadline finder asks a couple of questions and shows your date, the standard and the exceptions.

The April 2026 extension

DOJ published the rule on April 24, 2024. It originally set April 24, 2026 for larger entities and April 26, 2027 for smaller entities and special districts. On April 20, 2026, DOJ published an interim final rule that moved both dates back a year, to the dates above. Only the dates changed. The standard, the exceptions and the definitions are the same. You may still see the old dates in older articles and vendor emails.

DOJ said it had overestimated how quickly entities, and the technology available to them, could be ready. It noted that generative AI "does not yet reliably automate the remediation of inaccessible content at scale." DOJ also said it may propose changes to the rule's requirements during the extension. If it doesn't, it says it fully expects to implement the rule on the new dates. The sensible plan is to work toward the dates on the books now and watch for updates.

State laws

Some states have their own digital accessibility laws with different requirements or dates, such as Colorado's HB21-1110. Check your state's rules as well.

What WCAG 2.1 Level AA means in plain terms

The Web Content Accessibility Guidelines (WCAG) are a standard from the World Wide Web Consortium (W3C). Version 2.1 has testable "success criteria" at three levels: A, AA and AAA. The rule requires every Level A and Level AA criterion, 50 in all, using the version W3C published on June 5, 2018. The criteria sit under four principles: content must be perceivable, operable, understandable and robust.

Most criteria were written with web pages in mind, but they apply to documents too. For a PDF or Office file, Level AA mostly comes down to this:

Software can check some of these, such as whether a file is tagged or whether an image has alt text. Others need a person: whether the alt text is accurate, whether the reading order makes sense, whether color carries meaning. An honest report shows both.

You'll also hear about PDF/UA (ISO 14289), the international standard for accessible PDF files. The Title II rule names WCAG, not PDF/UA, but PDF/UA's checks catch many of the structural problems behind WCAG failures. Our guides to PDF/UA and WCAG vs PDF/UA explain how they relate.

"ADA 508 compliant" and "508 compliant PDF"

People often search for "ADA 508 compliant," but the ADA and Section 508 are different laws. Section 508 of the Rehabilitation Act covers federal agencies and the technology they buy, build and publish. Its standards use WCAG 2.0 Level AA. The Title II rule uses WCAG 2.1 Level AA, which includes every WCAG 2.0 success criterion. So a document that meets WCAG 2.1 AA also meets WCAG 2.0 AA. If a federal partner or grant asks for a "508 compliant PDF," a document that meets WCAG 2.1 AA also meets the WCAG 2.0 AA requirements Section 508 applies to documents.

What counts as web content

The rule defines web content broadly: text, images, sounds, videos, controls, animations and "conventional electronic documents." Conventional electronic documents are files in four formats:

• PDF
• Word processing (such as .docx)
• Presentation (such as .pptx)
• Spreadsheet (such as .xlsx)

That covers most of what public entities post:

• Agendas, minutes and board packets
• Applications, permits, registration forms and other fillable forms
• Budgets, financial reports and audits
• Newsletters, flyers, brochures and press releases
• Ordinances, policies, plans and studies
• Maps, schedules and menus posted as files
• Syllabi, slides and course readings
• Documents inside a mobile app you provide

It doesn't matter much where a file lives. Documents on your main website, in a document center or agenda portal, in a learning management system or in a vendor's app are covered when you provide them, directly or through a vendor. Content behind a login is covered too. DOJ proposed exceptions for password-protected course content in 2023 but left them out of the final rule.

The five exceptions

1. 1. Archived web content

   Content created before your compliance date, kept only for reference, research or recordkeeping, stored in an area clearly marked as an archive, and not changed since it was archived.

   Example:

   Board minutes from 2015 kept in an 'Archive' section and never edited.

   Watch out:

   Anything you update or move back into regular use loses the exception.

2. 2. Preexisting documents

   PDFs, word-processing files, presentations and spreadsheets posted before your compliance date, unless they are currently used to apply for, access or take part in your services, programs or activities.

   Example:

   A 2019 parks master plan PDF that no one needs to use to get a service.

   Watch out:

   Forms, applications and documents people currently need do not qualify, no matter when they were posted.

3. 3. Content posted by third parties

   Content posted by members of the public or other third parties who aren't acting for you, such as comments on a public forum.

   Example:

   A resident's comment on a city discussion page.

   Watch out:

   Content a vendor or contractor posts for you is still your responsibility.

4. 4. Individualized, secured documents

   Password-protected or otherwise secured documents about a specific person, property or account, such as a utility bill or a medical record.

   Example:

   One resident's water bill in an online account.

   Watch out:

   You still have to provide an accessible version promptly when someone with a disability needs it.

5. 5. Preexisting social media posts

   Social media posts you published before your compliance date.

   Example:

   A 2023 post announcing a road closure.

   Watch out:

   Posts made after the compliance date must be accessible.

Each exception is narrower than it sounds. Content qualifies only if it meets every condition. A few points trip people up:

• Archived content must meet four conditions: it was created before your compliance date (or copies older paper records), it's kept only for reference, research or recordkeeping, it's stored in an area clearly marked as an archive, and it hasn't changed since it was archived. Edit it, or bring it back into regular use, and it no longer qualifies.
• Preexisting documents are files posted before your compliance date. They lose the exception if people currently use them to apply for, access or take part in your services, programs or activities. A 2015 permit application that's still in use doesn't qualify. This exception covers documents only, not web pages.
• Third-party content means posts by members of the public, like comments on a discussion page. It doesn't include content a vendor, contractor or partner posts under an arrangement with you, and the comment platform you provide still has to be accessible.
• Individualized, secured documents must be both about a specific person, property or account and password-protected or otherwise secured, like a resident's water bill in an online account.
• Preexisting social media posts are posts published before your compliance date. New posts need alt text on images and captions on videos.

Two more things to know:

The duty to respond still applies. Even when an exception applies, the ADA's general duties don't go away. If someone with a disability asks for an accessible version of an excepted document, you need to provide it, or the information in it, promptly.

Keep a record. For each exception you rely on, note the document, which exception applies, the evidence for each condition, and who decided and when. Our guide to Title II exceptions walks through each one with examples and a sample log.

Other parts of the rule

• Conforming alternate versions. Posting a separate accessible version instead of fixing the original is allowed only when technical or legal limits make it impossible to make the original accessible. Turning a PDF into an accessible web page and removing the PDF is different: the web page becomes the content, and it has to meet the standard.
• Fundamental alteration or undue burden. You don't have to take steps that would fundamentally alter a program or impose undue financial and administrative burdens. The head of your entity, or their designee, must make that decision in writing after considering all available resources, and you must still provide access to the maximum extent possible.
• Minimal impact. A small shortfall may not count as a violation if people with disabilities can still get the same information and services with substantially equivalent timeliness, privacy, independence and ease of use. ADA.gov's example is text contrast of 4.45:1 instead of the required 4.5:1. It's a defense, not a plan.
• Equivalent facilitation. You can use a different approach if it gives substantially equivalent or greater accessibility and usability.

A documents playbook: inventory, prioritize, fix, monitor

Most public entities have hundreds or thousands of documents online. You won't fix them all at once, and you shouldn't fix them in random order. Work through four steps.

Step 1: Inventory everything you've published

Step 2: Prioritize

Fix documents in an order that matches how people use them:

1. Forms and applications people use to get services: permits, licenses, registrations and benefit applications.
2. Documents people need to take part in meetings and programs: agendas, packets, notices, schedules and course materials.
3. Documents that get the most visits or links.
4. Recent documents, then long, rarely used ones.

Then review possible exceptions. Documents posted before your compliance date that no one needs for a service, and older content you can move into a clearly marked archive, may qualify. Record each decision with its reason. To size the work, try the remediation cost calculator.

Step 3: Fix documents and the process that makes them

• Fix at the source. Most PDFs start as Word or PowerPoint files. Use built-in heading styles, add alt text, mark table header rows and export a tagged PDF. Fix the template once and every future document benefits. See how to make a PDF accessible.
• Remediate what's already posted. Add or repair tags, set the reading order, write alt text, mark table headers, label form fields, and set the title and language. Our guide to tagged PDFs explains the structure.
• Run OCR on scans first. A scanned page is a picture until it has a text layer. See scanned PDFs and OCR.
• Give forms extra care. Every field needs a label, and the tab order must follow the form. See accessible PDF forms.
• Have a person check what software can't judge. Is the alt text accurate? Does the reading order make sense? Does color carry meaning? For high-stakes documents, add a full manual review with a screen reader.
• Consider a web page instead. Notices, announcements and short updates are often easier to read, and easier to keep accessible, as web pages.
• Keep evidence. Save a report for each file that shows what was checked, when, and what a person reviewed.

Step 4: Monitor and keep new documents accessible

• Check before you post. Make an accessibility check part of publishing, like proofreading.
• Train the people who publish, starting with whoever posts agendas and minutes every week. Our agendas and minutes playbook has a weekly routine.
• Re-scan on a schedule to catch new and changed files.
• Put accessibility in contracts. Require vendors to deliver accessible documents and platforms. Their content counts as yours.
• Make requests easy. Publish how people can ask for an accessible version, and answer quickly.
• Report progress. Show leadership how many documents you've found, fixed and excepted, and what remains.

Templates

The deadline finder confirms your date and can email you a document accessibility plan template that follows the four steps above, ready to adapt for your council, board or leadership team.

Whatever template you use, a good plan names:

• An owner, often the ADA coordinator, and a team from communications, IT, records and the departments that publish
• Your compliance date and the population figure it's based on
• How you'll find documents, and how often you'll re-scan
• Your priority order, with target dates for each group
• Your exception log and who approves entries
• Your publishing checklist and training plan
• How people request accessible versions, and how fast you'll respond
• How and when you'll report progress

How Includoc helps

Includoc checks PDF, Word and PowerPoint files against WCAG 2.1 AA and PDF/UA and explains the results in plain English. It fixes documents with AI and shows you what still needs a person's review. Organizations can inventory every document on their website, record exceptions with a justification, monitor new uploads and produce board-ready progress reports. For high-stakes documents, a human-verified option adds a review by a certified accessibility specialist.

We don't add an overlay to your website, and we don't give legal advice. Our reports give you evidence of WCAG 2.1 AA conformance checks. Your counsel decides legal compliance. During our beta, checking is free. Fixing and organization plans open in early 2027. Check a document free.

Sources

• Federal Register, April 20, 2026: Extension of compliance dates for the ADA Title II web and mobile rule (opens another website) (interim final rule)
• Federal Register, April 24, 2024: Final rule on the accessibility of web information and services of state and local government entities (opens another website)
• ADA.gov: Fact sheet on the ADA Title II web and mobile accessibility rule (opens another website)
• eCFR: 28 CFR part 35, subpart H, Web and Mobile Accessibility (opens another website)
• W3C: Web Content Accessibility Guidelines (WCAG) 2.1, Recommendation of June 5, 2018 (opens another website)