Resources

ADA Title II Document Compliance Guide

Everything state and local governments need to know about the new digital document accessibility requirements under ADA Title II, including WCAG 2.1 AA standards, deadlines, and how to remediate your documents.

Last updated: March 2026

1. What is ADA Title II?

The Americans with Disabilities Act (ADA) was signed into law in 1990 to prohibit discrimination against individuals with disabilities. Title II of the ADA specifically applies to state and local government entities, requiring that all programs, services, and activities be accessible to people with disabilities.

For decades, Title II primarily focused on physical accessibility — ramps, elevators, accessible restrooms, and similar accommodations. But as government services moved online, a critical gap emerged: digital content, including the documents governments publish on their websites, was largely inaccessible to people using assistive technologies like screen readers.

In April 2024, the Department of Justice (DOJ) published a final rule under Title II that explicitly establishes technical standards for web and digital content accessibility. For the first time, there are clear, enforceable requirements for making digital documents — including PDFs, Word files, spreadsheets, and presentations — accessible to all users.


2. New Digital Accessibility Requirements

The 2024 final rule adopts WCAG 2.1 Level AA (Web Content Accessibility Guidelines) as the technical standard that state and local governments must meet. WCAG 2.1 is published by the World Wide Web Consortium (W3C) and is the most widely recognized international standard for digital accessibility.

WCAG 2.1 AA covers four core principles. All digital content must be:

  • Perceivable — Information must be presentable in ways all users can perceive, including providing text alternatives for images and captions for multimedia.
  • Operable — Navigation and interaction must be possible using a keyboard alone, without requiring a mouse.
  • Understandable — Content and interface behavior must be predictable and readable.
  • Robust — Content must work reliably with current and future assistive technologies, including screen readers and braille displays.

For documents specifically, this means PDFs, Word files, and other digital publications must have proper structure, tagged content, alternative text for images, and a logical reading order that assistive technologies can interpret.


3. Who Is Affected?

ADA Title II applies to all state and local government entities, regardless of size. This includes:

  • State agencies and departments
  • County and municipal governments
  • Public school districts (K-12)
  • Public colleges and universities
  • Public libraries
  • Public transit authorities
  • Courts and judicial systems
  • Public utilities and special districts
  • Law enforcement agencies
  • Public health departments and hospitals

If your organization receives public funding or operates as a function of state or local government, you are covered by Title II. There is no minimum size threshold — a small town with 500 residents has the same legal obligations as a city of 5 million, though the compliance deadlines differ based on population.


4. Compliance Deadlines

The DOJ established two compliance deadlines based on the population served by the government entity:

Deadline 1

April 24, 2026

State and local government entities serving a population of 50,000 or more.

Less than 2 months away

Deadline 2

April 26, 2027

State and local government entities serving a population of fewer than 50,000.

About 13 months away

These deadlines apply to all web content and digital documents published by the entity. There is no grace period and no extension mechanism in the final rule. Governments that miss the deadline are immediately subject to enforcement actions and complaints.

Population size is determined using the most recent Census data. For entities that serve multiple jurisdictions (such as regional transit authorities), the total combined population is used.


5. What Documents Are Covered?

The rule covers all digital content made available through a government entity's website or digital channels. For documents, this includes:

  • PDF files — Meeting agendas, minutes, budgets, reports, forms, applications, permits, ordinances, plans, and any other publicly posted PDF documents.
  • Microsoft Word documents — Letters, memos, policies, and any .doc/.docx files available for download.
  • Excel spreadsheets — Budget data, datasets, statistical reports, and any .xls/.xlsx files.
  • PowerPoint presentations — Meeting presentations, training materials, and any .ppt/.pptx files.
  • Other digital content — Interactive maps, data visualizations, embedded media, and any other digital content published through web channels.

A common misconception is that only "new" documents need to be accessible. The rule applies to all content currently published on your website, not just documents created after the rule took effect. If a PDF from 2015 is still available on your site, it must be made accessible by the deadline.

For most government websites, PDFs represent the largest volume of non-compliant documents. It is common for a mid-size city website to have thousands of PDFs, the vast majority of which were created without accessibility in mind.


6. What Makes a Document Accessible?

An accessible document is one that can be read and navigated by assistive technologies, particularly screen readers. To meet WCAG 2.1 AA and PDF/UA (ISO 14289) standards, documents must include:

Tagged Structure

Every element in the document — headings, paragraphs, lists, tables, images — must be tagged with its semantic role. Tags tell screen readers what type of content each element is, just as HTML tags do on a web page. An untagged PDF appears as a wall of undifferentiated text to a screen reader.

Alternative Text for Images

Every meaningful image, chart, graph, or diagram must have alternative text (alt text) that conveys the same information the image provides visually. Decorative images should be marked as artifacts so screen readers skip them.

Logical Reading Order

The order in which a screen reader encounters content must match the logical order a sighted reader would follow. Multi-column layouts, sidebars, headers, and footers must be ordered correctly in the tag tree so content flows naturally.

Table Headers

Data tables must have properly marked header cells (TH tags) so screen readers can associate data cells with their column and row headers. Complex tables with merged cells or multiple header levels require additional scope attributes.

Form Labels and Fields

Interactive PDF forms must have every field properly labeled so users know what information is expected. Tab order must follow a logical sequence, and required fields must be identified.

Bookmarks and Navigation

Documents longer than a few pages should include bookmarks that mirror the heading structure, allowing users to quickly navigate to specific sections without scrolling through the entire document.

Document Language

The document must declare its primary language (e.g., English, Spanish) so screen readers use the correct pronunciation engine. Passages in other languages should be marked with language attributes as well.

Color Contrast and Visual Design

Text must have sufficient contrast against its background (a minimum ratio of 4.5:1 for normal text, 3:1 for large text). Information must not be conveyed by color alone — for example, a chart that uses only color to distinguish data series is not accessible.


7. Consequences of Non-Compliance

Failing to meet ADA Title II requirements carries serious legal and financial consequences:

DOJ Enforcement Actions

The Department of Justice actively investigates and enforces ADA compliance. The DOJ has pursued enforcement actions against government entities of all sizes, from small counties to major state agencies. Investigations can be triggered by individual complaints, advocacy organizations, or DOJ-initiated reviews.

Lawsuits and Legal Costs

Private individuals can file lawsuits against government entities that fail to provide accessible digital content. Disability rights organizations also bring systematic litigation. The legal costs of defending an accessibility lawsuit — even if you settle — typically far exceed the cost of proactive remediation.

Financial Penalties

Civil penalties for ADA violations can reach $75,000 for a first offense and $150,000 for subsequent violations. These penalties are per violation — and with hundreds or thousands of inaccessible documents on a website, the exposure adds up rapidly.

Reputational Damage

Government entities exist to serve all members of their community. When a city or county is sued for accessibility failures, it generates negative press coverage and erodes public trust. Proactive compliance demonstrates a commitment to equitable access for all constituents.

Loss of Federal Funding

In some cases, ADA non-compliance can jeopardize federal funding. Federal agencies may condition grants and contracts on demonstrated compliance with civil rights laws, including the ADA.


8. How to Get Compliant

Achieving compliance is a process, not a one-time event. Here is a practical roadmap:

1

Audit Your Current Documents

Start by understanding the scope of the problem. Crawl your website to identify every document that is publicly available. Run automated accessibility checks against each one. You need to know how many documents you have, how many are non-compliant, and the severity of the issues.

2

Prioritize by Risk and Impact

Not all documents carry equal risk. Prioritize high-traffic documents (budget reports, meeting agendas), legally required publications, and documents related to critical services (permits, applications, public health information). Documents that are rarely accessed or outdated may be candidates for removal rather than remediation.

3

Remediate Documents

Each document needs to be brought into compliance with WCAG 2.1 AA and PDF/UA standards. This involves adding tags, writing alt text, fixing reading order, marking up tables, and setting document metadata. Manual remediation of a single PDF can take 30 minutes to several hours depending on complexity. Automated tools can dramatically reduce this time.

4

Verify Compliance

After remediation, every document should be validated against PDF/UA standards using tools like veraPDF or PAC (PDF Accessibility Checker). Automated validation catches structural issues, but manual review is also important — especially for alt text quality and reading order logic.

5

Establish Ongoing Processes

Compliance is not a one-time project. Every new document published to your website must be accessible from the start. This requires training staff on accessible document creation, integrating accessibility checks into your publishing workflow, and periodically auditing your site for new non-compliant content.


9. How CASO Comply Can Help

CASO Comply is an AI-powered document accessibility remediation platform built specifically for organizations facing the scale of the ADA Title II challenge. Instead of manually remediating each PDF one at a time, CASO Comply automates the process at a fraction of the cost.

Automated PDF Remediation

Our PDF remediation service uses AI to automatically tag document structure, generate accurate alt text for images, fix reading order, mark up tables, and set all required metadata. What would take a human hours per document, CASO Comply handles in minutes.

Free Compliance Scan

Not sure where you stand? Our free compliance scan crawls your website, identifies every document, and produces a detailed report showing how many are non-compliant and what issues exist. No commitment required — just a clear picture of your current status.

Built for Government Scale

Whether you have 50 PDFs or 50,000, CASO Comply scales to meet the challenge. Our on-premise Docker agent processes documents on your infrastructure, so sensitive government files never leave your network. We are SOC 2 Type II certified and built with government procurement requirements in mind.

Ongoing Compliance

CASO Comply is not just a one-time fix. The agent monitors your document directories and automatically remediates new files as they are added, ensuring you stay compliant long after the deadline has passed.

The deadline is approaching.

Governments serving 50,000+ residents must be compliant by April 24, 2026. Start with a free scan to understand the scope of your compliance gap.