Compliance Guide

What the Law Requires — and How to Comply Before the Deadline

A complete guide for local government officials navigating ADA Title II digital accessibility requirements. Understand the law, the standards, and the steps to compliance.

--- days until the April 24, 2026 deadline

On This Page

The Law: ADA Title II Final Rule

On April 24, 2024, the Department of Justice published its final rule under Title II of the Americans with Disabilities Act, codified at 28 CFR Part 35, Subpart H. For the first time, the rule establishes specific, enforceable technical standards for state and local government digital content.

What the Rule Says

Title II of the ADA prohibits discrimination on the basis of disability by state and local government entities. The final rule clarifies that this prohibition extends to all web content and mobile applications made available by state and local governments.

The rule adopts WCAG 2.1 Level AA as the technical standard. All web content — including PDF documents, forms, multimedia, and interactive applications — must conform to these criteria.

Key Provisions

  • 28 CFR § 35.200 — State and local governments must ensure their web content conforms to WCAG 2.1 Level AA success criteria.
  • 28 CFR § 35.201 — The requirement applies to all web content made available by or on behalf of the public entity, including content on third-party platforms.
  • 28 CFR § 35.202 — Documents posted on government websites (PDFs, Word docs, spreadsheets) must be accessible or an equivalent accessible version must be provided.
  • 28 CFR § 35.204 — Archived web content (not updated since the compliance date and maintained exclusively for reference) may be exempt.
  • 28 CFR § 35.205 — Content posted by third parties on government platforms is not covered, but government-posted content on third-party platforms is.
  • 28 CFR § 35.207 — An undue burden defense is available but requires documented evidence and still mandates providing an alternative accessible format.

Compliance Deadlines

The DOJ established a tiered deadline structure based on population size:

April 24, 2026

Large Municipalities

50 Days Away

Local governments with populations of 50,000 or more must achieve full WCAG 2.1 Level AA conformance for all web content, including every PDF document available on their websites.

April 26, 2027

Small Municipalities

Local governments with populations under 50,000 must achieve the same level of conformance. While the deadline is later, the requirements are identical.

Important Note

Compliance Is Not Optional

Unlike voluntary frameworks or best practices, the ADA Title II rule is a federal regulation with enforcement teeth. The DOJ has actively pursued enforcement actions against state and local governments for digital accessibility violations since 2013, resulting in consent decrees, fines, and mandatory remediation programs.

What Must Be Accessible

The rule covers all digital content that a local government makes available to the public. This includes far more than just web pages:

Web Content

  • All website pages
  • Online forms and applications
  • Interactive maps and tools
  • Embedded videos and audio
  • Social media content posted by the government

Documents

  • PDF files (the largest category)
  • Word documents
  • Excel spreadsheets
  • PowerPoint presentations
  • Any file linked from the website

Common Government PDFs

  • Council/board meeting minutes
  • Annual budgets and financial reports
  • Zoning ordinances and land use plans
  • Building permits and applications
  • Public notices and agendas
  • Parks and recreation guides
  • Emergency management plans

Mobile Applications

  • Utility payment apps
  • 311 reporting apps
  • Transit and parking apps
  • Recreation booking apps
  • Emergency alert apps

WCAG 2.1 Level AA Requirements

The Web Content Accessibility Guidelines (WCAG) 2.1 Level AA includes 50 success criteria organized under four principles, known by the acronym POUR.

P Perceivable

Information and user interface components must be presentable to users in ways they can perceive.

Criterion Requirement PDF Impact
1.1.1 Non-text Content All images, charts, and graphics must have text alternatives (alt text) Critical — most PDFs fail this
1.2.1–1.2.5 Time-based Media Audio/video must have captions, transcripts, or audio descriptions Embedded media in PDFs
1.3.1 Info and Relationships Structural information (headings, tables, lists) must be programmatically determinable Critical — requires PDF tagging
1.3.2 Meaningful Sequence Reading order must be correct when linearized Critical — untagged PDFs have no reading order
1.3.3 Sensory Characteristics Instructions must not rely solely on shape, color, size, or location Moderate
1.4.1 Use of Color Color must not be the only visual means of conveying information Moderate — charts and graphs
1.4.3 Contrast (Minimum) Text must have a contrast ratio of at least 4.5:1 against background Moderate
1.4.4 Resize Text Text must be resizable up to 200% without loss of content Moderate
1.4.5 Images of Text Real text must be used instead of images of text where possible Critical — scanned PDFs are images of text

O Operable

User interface components and navigation must be operable by all users.

Criterion Requirement PDF Impact
2.1.1 Keyboard All functionality must be operable through a keyboard interface Critical — PDF forms and links
2.1.2 No Keyboard Trap Keyboard focus must not become trapped in any component Moderate — form fields
2.4.1 Bypass Blocks Mechanism to skip repeated content blocks Low — primarily web pages
2.4.2 Page Titled Documents must have titles that describe their topic or purpose Critical — most PDFs lack titles
2.4.3 Focus Order Focus order must preserve meaning and operability Moderate — form tab order
2.4.4 Link Purpose The purpose of each link must be determinable from link text Moderate
2.4.6 Headings and Labels Headings and labels must describe topic or purpose Critical — requires proper tagging

U Understandable

Information and the operation of user interface must be understandable.

Criterion Requirement PDF Impact
3.1.1 Language of Page The default language of the document must be programmatically identified Critical — most PDFs lack /Lang
3.1.2 Language of Parts Language changes within content must be identified Moderate
3.2.1 On Focus Receiving focus must not cause unexpected changes of context Low — form fields
3.2.2 On Input Changing a form setting must not automatically cause unexpected changes Low — interactive PDFs
3.3.1 Error Identification Input errors must be identified and described in text Moderate — PDF forms
3.3.2 Labels or Instructions Labels or instructions must be provided for user input Moderate — PDF forms

R Robust

Content must be robust enough to be interpreted by a wide variety of assistive technologies.

Criterion Requirement PDF Impact
4.1.1 Parsing Content must be well-formed and properly nested Critical — PDF structure tree
4.1.2 Name, Role, Value All UI components must have accessible names and roles Critical — tagged PDF elements

PDF-Specific Requirements (PDF/UA-1)

PDFs are the single largest source of accessibility failures on government websites. An untagged PDF is essentially invisible to screen readers. The PDF/UA-1 standard (ISO 14289-1) defines what a fully accessible PDF looks like.

What Makes a PDF Accessible?

Structure Tags (StructTreeRoot)

Every PDF must contain a complete structure tree that maps content to semantic roles — headings, paragraphs, tables, lists, figures. This is what screen readers use to navigate the document.

Marked Content (BDC/EMC)

Content streams must contain marked content operators that link visual content on the page to nodes in the structure tree. Without these, assistive technology cannot associate text with its semantic meaning.

Alternative Text

Every non-decorative image must have an /Alt entry in its structure element. Decorative images must be marked as artifacts. Charts and graphs require descriptive captions.

Document Language

The /Lang entry must be set at the document level (e.g., "en-US") and at the element level for any content in a different language. This is required for screen reader pronunciation.

Reading Order

The logical reading order must be encoded in the structure tree, independent of the visual layout. Multi-column documents, sidebars, and callout boxes must read in the correct sequence.

Table Structure

Data tables must be tagged with Table, THead, TBody, TR, TH, and TD elements. Header cells must have scope attributes so screen readers can associate data cells with their headers.

PDF/UA-1 vs. WCAG 2.1 AA

These are complementary, not competing standards. WCAG 2.1 AA defines what accessibility outcomes are required (e.g., "non-text content has a text alternative"). PDF/UA-1 defines how to achieve those outcomes in PDF format specifically (e.g., "Figure elements must have an /Alt entry"). A fully compliant PDF meets both standards simultaneously.

Consequences of Non-Compliance

The ADA Title II rule is not aspirational guidance — it is an enforceable federal regulation. Non-compliance carries real consequences.

DOJ Enforcement Actions

The Department of Justice can investigate and bring enforcement actions against non-compliant local governments. Since 2013, the DOJ has reached settlements with numerous municipalities, requiring them to remediate their digital content, pay compensatory damages, and submit to multi-year monitoring.

Civil Penalties

First-time violations can result in civil penalties up to $75,000. Subsequent violations can reach $150,000. These amounts are subject to inflation adjustment and have been increasing. Penalties are assessed per violation, and a single non-compliant website can contain hundreds of violations.

Private Lawsuits

Individuals can file private lawsuits under the ADA for injunctive relief and attorney's fees. Digital accessibility lawsuits have increased dramatically — over 4,600 were filed in 2023 alone. Local governments are not immune from these suits.

Consent Decrees

Settlements typically include multi-year consent decrees requiring ongoing remediation, regular audits, staff training, and public reporting. These are costly, time-consuming, and carry reputational damage for the municipality.

Notable Enforcement Examples

  • The DOJ has reached settlements with cities, counties, and state agencies across the country for inaccessible web content
  • Settlement agreements typically require full WCAG conformance within 12-24 months
  • Municipalities have been required to hire dedicated accessibility coordinators as part of settlement terms
  • Post-settlement monitoring often extends 3-5 years with regular compliance audits

Exceptions and Limitations

The final rule includes several narrowly defined exceptions. These are not broad exemptions — they are limited carve-outs with specific conditions.

Archived Content (28 CFR § 35.204)

Web content that was created before the compliance date, is not updated or edited after the compliance date, and is maintained exclusively for reference, research, or recordkeeping may be exempt. However, if the content is still actively used or referenced by the public, it likely does not qualify as "archived."

Government entities must still provide the content in an accessible format upon request, even if the online version is not remediated.

Undue Burden (28 CFR § 35.207)

A public entity may claim that compliance would result in a "fundamental alteration" or "undue burden." However, this defense requires:

  • A written statement from the head of the public entity (not a subordinate) documenting why compliance constitutes an undue burden
  • Evidence of the financial and administrative resources available
  • Even when undue burden is claimed, the entity must still provide the information through an alternative accessible means
Third-Party Content (28 CFR § 35.205)

Content posted by members of the public on government platforms (e.g., public comments on a forum) is generally not covered. However, content that the government posts on third-party platforms (e.g., government social media accounts) is covered.

Preexisting Conventional Documents

Documents that exist only in paper form and have not been digitized are not covered by the web accessibility rule. However, once any document is posted to a government website — even as a scanned image — it must meet WCAG 2.1 AA standards.

Special District Entities

The rule applies to all "public entities" under Title II, which includes cities, counties, towns, townships, special districts, school districts, and any instrumentality of state or local government. There is no exemption based on entity type — only the deadline varies by population.

How Quillinox Addresses Each Requirement

Quillinox was purpose-built to address the specific accessibility requirements that local government PDFs must meet. Here's how our pipeline maps to the standards.

Requirement Standard How Quillinox Solves It
Structure tags PDF/UA-1, WCAG 1.3.1 Builds complete StructTreeRoot with H1-H6, P, Table, L/LI, Figure elements via in-place tagging
Reading order PDF/UA-1, WCAG 1.3.2 AI analysis determines correct reading order; structure tree encodes logical sequence
Image alt text PDF/UA-1, WCAG 1.1.1 AI generates meaningful alt text for all non-decorative images; decorative images marked as artifacts
Document language PDF/UA-1, WCAG 3.1.1 Sets /Lang at document level and on individual elements where language changes
Document title PDF/UA-1, WCAG 2.4.2 Sets document title in metadata from AI-detected content
Table headers PDF/UA-1, WCAG 1.3.1 Tags tables with THead/TBody/TR/TH/TD and scope attributes
List structure PDF/UA-1, WCAG 1.3.1 Properly nests L > LI > LBody elements for ordered and unordered lists
Marked content PDF/UA-1 Injects BDC/EMC operators into content streams, linking page content to structure tree nodes
Color contrast WCAG 1.4.3 Analysis flags contrast issues for manual review (content not altered)
Legal authenticity 28 CFR § 35.200 In-place tagging preserves original document content — no reconstruction or replacement
Audit evidence DOJ enforcement defense Cryptographic hash chain audit trail provides tamper-evident proof of remediation efforts

Your Compliance Roadmap

Whether your deadline is April 2026 or April 2027, the steps to compliance are the same. Here is a practical path forward.

Audit Your Current State

Inventory every PDF on your website. Identify which documents are tagged, which are untagged, and which are scanned images. Quillinox can crawl your site and produce this inventory automatically.

Prioritize Your Backlog

Focus first on high-traffic, public-facing documents: budgets, meeting minutes, permits, and applications. These are the most likely to be the subject of complaints or enforcement actions.

Remediate at Scale

Manual remediation at $50-200 per document doesn't scale for backlogs of hundreds or thousands of PDFs. Automated pipelines like Quillinox can process documents in minutes, not days.

Validate Compliance

Run every remediated document through PDF/UA-1 and WCAG 2.1 AA validation. Automated validation catches structural issues; manual spot-checking confirms content quality.

Build Your Audit Trail

Document your remediation efforts with timestamped, verifiable records. If the DOJ investigates, you need to demonstrate good-faith compliance efforts. Quillinox's cryptographic hash chain provides this automatically.

Establish Ongoing Processes

Compliance is not a one-time project. Establish processes to ensure every new document published to your website is accessible from day one. Train staff on accessibility basics for document creation.

What the Law Requires — and How Axivelo Covers It

ADA Title II (28 CFR Part 35) and the 2024 DOJ rule set specific requirements for digital accessibility. Here is exactly how Axivelo addresses each one.

Legal Requirement Citation How Axivelo Covers It
Web content must conform to WCAG 2.1 Level AA 28 CFR § 35.200 Automated web page scanning with axe-core engine. Every page tested against all WCAG 2.1 AA success criteria. Results mapped to specific WCAG criterion with severity and page location.
PDF documents must be accessible or an accessible alternative provided 28 CFR § 35.200 9-stage PDF remediation pipeline: PDF/UA-1 tagging of the original document (preserving visual fidelity) plus a fully accessible HTML alternative. Both formats stored and served.
Images must have meaningful alternative text WCAG 1.1.1 AI-powered image description using Gemini vision. Existing alt text evaluated for adequacy — placeholders, filenames, and generic text automatically replaced with contextually accurate descriptions. Full audit trail of original vs. replacement text with reasons.
Documents must have proper structure (headings, tables, reading order) WCAG 1.3.1, 1.3.2 PDF/UA-1 structure tree injected into every document: heading hierarchy, table headers with scope, reading order, form labels, artifact marking. Verified by 10-point internal validation and VeraPDF PDF/UA-1 compliance check.
Self-evaluation of policies and practices 28 CFR § 35.105 Automated compliance scoring across all web pages, PDFs, and media. Dashboard shows real-time compliance percentage. Generates Accessibility Conformance Reports (ACR/VPAT) documenting evaluation results.
Records maintained for at least 3 years 28 CFR § 35.105 Immutable, hash-chained audit trail. Every action — scan, analysis, remediation, validation — recorded with cryptographic hash, timestamp, and previous entry hash for tamper detection. Original documents preserved in cloud storage with integrity verification.
Transition plan with timeline and methods 28 CFR § 35.150(d) Auto-generated Remediation Roadmap with current state assessment, completed items, pending items, media gaps, and timeline. Exportable as a compliance defense document.
Grievance procedure for accessibility complaints 28 CFR § 35.107 Built-in grievance intake and tracking system. Complainant name, barrier type, URL, status, resolution notes, and full status history. Exportable for DOJ inquiries.
Accessibility policy published 28 CFR § 35.107(b) Auto-generated Accessibility Policy document with agency name, ADA coordinator details, grievance procedure, and commitment statement. Downloadable as PDF and DOCX.
Conformance declaration per document 28 CFR § 35.105 Every remediated PDF receives a formal conformance declaration stating: WCAG 2.1 AA level, PDF/UA-1 verification result, axe-core HTML validation result, accessible formats provided, and 3-year retention commitment. Stored in the hash-chained audit trail.
Compliance by April 24, 2026 (population > 50,000) 89 FR 31236 Deadline tracking dashboard with countdown. Automated change detection scans monitor your website continuously. Priority scoring ensures highest-risk documents are remediated first.
Meeting agendas translated into applicable languages CA SB 707 (Brown Act) California cities and counties with 30,000+ population must translate meeting agendas into languages spoken by 20% or more of the local population with limited English proficiency, effective July 1, 2026. Quillinox can generate translated agenda documents as part of your compliance workflow.

The Deadline Is Real. The Solution Is Here.

Don't wait for a complaint or an enforcement action. Let Quillinox help you remediate your PDF backlog and build a defensible compliance record.

Request a Demo Talk to Our Team