Under ADA Title II, most documents that state and local governments post online, including PDFs, forms, and reports, must meet WCAG 2.1 AA by April 26, 2027 or April 26, 2028. A few narrow exceptions apply.
Updated: September 24, 2026
Today, state and local governments rely on digital documents for applications, forms, reports, notices, policies, and meeting materials.
Moreover, as more public services move online, understanding ADA Title II document accessibility requirements has become a practical priority.
- Who: state and local governments, including special districts and public colleges.
- What: websites, apps, and documents such as PDF, Word, Excel, and PowerPoint files.
- Standard: WCAG 2.1 AA.
- When: April 26, 2027 for entities of 50,000 or more; April 26, 2028 for smaller entities and special districts.
Specifically, the U.S. Department of Justice (DOJ) ADA Title II digital accessibility rule, codified at 28 CFR Part 35, Subpart H, sets technical requirements for state and local governments using WCAG 2.1 AA.
It does not create a separate “PDF law.” Instead, a document’s purpose, publication date, and use decide whether it is covered or falls under an exception.
What Is ADA Title II?
In brief, Title II of the Americans with Disabilities Act (ADA) prohibits discrimination against people with disabilities by state and local governments, including through the websites, apps, and documents they provide.
Who Does ADA Title II Apply To?
Title II applies to state and local governments and their agencies. In particular, that includes states, counties, cities and towns, special district governments, public school districts, and public colleges and universities.
ADA Title III covers private businesses and private universities instead, while federal agencies follow Section 508.
What the Web and Mobile Rule Covers
In practice, the DOJ’s Title II web and mobile accessibility rule applies to covered web content and mobile applications that public entities provide or make available to the public.
Web content includes documents such as PDFs, Word files, presentations, and spreadsheets, which the rule calls conventional electronic documents.
The ADA.gov fact sheet on the web and mobile rule summarizes how the rule works.
Effective Communication Still Applies
In addition, Title II carries broader effective communication obligations (28 CFR 35.160). If content qualifies for a WCAG exception, that does not necessarily remove other ADA responsibilities toward residents with disabilities.
Depending on the circumstances, the entity may still need to supply an accessible alternative, or another form of effective communication, when someone needs the information in a document.
ADA Title II vs. Title III, Section 504 and Section 508
In practice, these four laws are often confused. Essentially, the difference is who they cover and which technical standard applies. Section508.gov explains the federal requirements in turn.
| Law | Who It Covers | Digital Standard |
|---|---|---|
| ADA Title II | State and local governments | WCAG 2.1 AA under the DOJ rule |
| ADA Title III | Private businesses open to the public | No set standard in regulation; WCAG is the common benchmark |
| Section 504 | Organizations receiving federal financial assistance | Set by each funding agency; HHS adopted WCAG 2.1 AA in 2024 |
| Section 508 | Federal agencies | Revised 508 Standards, which include WCAG 2.0 AA |
ADA Title II Compliance Deadlines and the 2026 Extension
In April 2026, the DOJ published an interim final rule extending the original Title II web and mobile accessibility deadlines by one year.
The technical standard, WCAG 2.1 AA, did not change, so the extra time is best spent on remediation.
| Public Entity | Current Compliance Date |
|---|---|
| Population of 50,000 or more | April 26, 2027 |
| Population under 50,000 | April 26, 2028 |
| Special district governments | April 26, 2028 |
Meanwhile, older articles may still list the original deadlines, so compliance plans built on them will be out of date. Consequently, the timeline below shows how each date moved.
Organizations should rely on current DOJ guidance when planning compliance. The Federal Register notice extending the compliance dates is the primary source for the change.
ADA Title II Document Accessibility Requirements
In short, for government documents, meeting WCAG 2.1 AA comes down to these elements:
- Proper PDF tagging and document structure
- Logical reading order and accessible navigation
- Meaningful alternative text
- Accessible tables and descriptive link text
- Sufficient color contrast
- Keyboard accessibility
- Properly labeled form fields
- Correct document language and machine-readable text
Even so, you should weigh the exact WCAG criteria in the context of each document. WCAG contains testable success criteria, but some accessibility questions need human judgment rather than automated testing alone.
Legal vs. Technical Requirements
Legal duties and technical standards work together, but they are not the same thing, and it helps to keep them separate when planning.
Title II establishes nondiscrimination obligations for covered public entities.
The DOJ web and mobile rule specifies WCAG 2.1 Level A and Level AA success criteria and conformance requirements for covered content.
Inventories, testing, remediation workflows, and audit records are not named in the rule, but they are the most reliable way to manage compliance and show your work.
WCAG 2.1 Level AA for Documents
Notably, WCAG 2.1 provides the technical framework the DOJ rule incorporates. The W3C’s Web Content Accessibility Guidelines (WCAG) 2.1 remain the authoritative source for every success criterion. Relevant considerations include:
- Text alternatives
- Structure and relationships
- Keyboard access and navigation
- Color and contrast
- Forms, labels, and error identification
- Document language
- Compatibility with assistive technologies
W3C’s WCAG2ICT guidance helps organizations understand how WCAG concepts apply to non-web documents and software. However, WCAG2ICT is informative guidance, not a separate legal requirement.
Map your document library against WCAG 2.1 Level AA so remediation effort goes to the files residents actually depend on.
Talk to Our TeamWhich Documents Need to Be Accessible?
In reality, government organizations publish many types of electronic content, and the key question is not simply whether a file is a PDF. Common document types include:
- PDF forms, applications, and permit applications
- Public notices and public policies
- Government, financial, and planning reports
- Meeting agendas and minutes
- Word documents, Excel spreadsheets, and PowerPoint presentations
- Procurement documents
Questions to Ask About Each Document
- Is the document covered web content?
- When was it made available?
- Is it currently used to access or participate in a government service, program, or activity?
- Does a specific exception apply?
- Which WCAG requirements apply?
Coverage Guide
ADA Title II Document Coverage and Exception Matrix
| Document or Content | General Treatment | Key Consideration |
|---|---|---|
| Current Permit Application | Generally covered | Used to access a government service |
| New Government PDF Report | Generally covered | Evaluate applicable WCAG requirements |
| Old Meeting Minutes | May qualify for exception | Depends on preexisting-document conditions |
| Individualized Secured Utility Bill | May qualify for exception | Must meet applicable conditions |
| Third-party Public Comment | May qualify for exception | Depends on circumstances |
| Vendor-created Government Document | May qualify for exception | Vendor involvement does not determine exemption |
| Archived Web Content | May qualify for exception | Must meet regulatory conditions |
| Preexisting Social Media Post | May qualify for exception | Must meet applicable conditions |
Each document still needs its own review against the regulatory conditions before a coverage decision is recorded.
ADA Title II Exceptions
Notably, the rule lists five exceptions in 28 CFR 35.201.
Even so, an exception can mean the WCAG requirements do not apply to that content in the same way. It does not mean a public entity has no accessibility responsibility.
Certain PDFs, word-processing files, presentations, and spreadsheets available before the applicable compliance date may qualify. Documents still used to access a service, such as a current permit application, do not qualify.
Similarly, archived web content can qualify when it meets all the regulatory conditions. Moving a document into an archive folder does not make it exempt on its own.
Content posted by third parties, such as public comments, may qualify. It does not qualify when a vendor or partner posts it under an arrangement with the entity.
Documents about a specific person, property, or account, such as a utility bill in a password-protected account, may qualify when they are secured.
Likewise, certain social media posts published before the applicable compliance date may qualify for an exception.
What Happens When an Exception Applies?
In addition, other ADA obligations, including effective communication and equal access to services, programs, and activities, can continue to apply. Organizations should record:
- Why the exception applies and the relevant regulatory provision
- When the document was created or published
- Who reviewed the decision
- Whether the document is still needed for a government service
- Whether an accessible alternative or effective communication is needed
Separate covered, archived, individualized, and third-party content, and record the rationale behind every exception decision.
Review Your Document LibraryDocument Accessibility Decision Model
In short, apply these five steps to each document in order. This is an operational framework for consistent decisions, not a substitute for legal advice.
How It Works
How Each Document Moves Through the Decision Model
- Covered Web Content?When it is not, check which other accessibility obligation applies
- Title II Exception?Record any exception you rely on, then weigh the remaining ADA duties
- Used for a Government Service?Service-critical files move to the front of the queue
- Applicable WCAG CriteriaReview the relevant Level A and Level AA criteria
- Remediate and ValidateFix identified barriers and document the testing results
Possible Outcomes
- Remediated and PublishedCovered file passes validation
- Exception RecordedRationale, provision and reviewer logged
- Alternative ProvidedEffective communication on request
Every document ends with a recorded decision, so the audit trail explains why each file was fixed, excepted, or handled another way.
Common PDF Accessibility Issues
In fact, a PDF can look visually correct while still failing ADA Title II PDF requirements for people using screen readers, keyboard navigation, or other assistive technologies. The issues below are the most common causes.
PDF Tags and Reading Order
To start with, PDF tags provide structural information that assistive technologies use to interpret content. Headings, paragraphs, lists, tables, and figures each need appropriate structure.
Above all, reading order matters most in multi-column reports, forms, newsletters, and documents with floating elements, where visual order and tag order often drift apart.
Alternative Text
Likewise, informative images such as charts, graphs, diagrams, maps, and infographics need meaningful text alternatives. The goal is to communicate the relevant information or function rather than simply describe the image.
Accessible Forms and Tables
For example, government forms are often essential for reaching public services. Form fields need appropriate labels, logical tab order, keyboard accessibility, and understandable instructions so every resident can complete them.
Tables need appropriate structure and identifiable headers so users can understand the relationships between headings and data.
Where forms sit inside a larger digital workflow, focus order, labels, contrast, and screen-reader support matter just as much.
OCR and Scanned PDFs
Optical Character Recognition (OCR) can convert scanned text into machine-readable text, a process covered in more depth in W3C technique PDF7 on OCR for scanned PDFs and in Mastering PDF Text Extraction: Tips and Tools.
However, OCR alone does not make a document fully accessible. A scanned document usually still needs:
- Correct tags and heading structure
- Reading-order correction
- Alternative text for informative images
- Table remediation
- Form-field remediation
ADA Title II PDF Accessibility Checklist
Before publishing a PDF, confirm each of these points. This beginner’s guide to document accessibility walks through each check on video.
- The file carries tags, and the tag tree matches the visible structure
- Headings follow a logical order, starting with one main title
- Reading order follows the visual order, including multi-column pages
- Informative images, charts, and maps carry alt text, while decorative images carry the artifact flag
- Data tables use header cells, and complex tables carry scope
- Form fields have labels, a logical tab order, and clear instructions
- Link text describes the destination
- Text contrast is at least 4.5:1, or 3:1 for large text
- The file properties carry a document title and language
- The file passes an automated check and a screen reader test
How to Make Government Documents Accessible
A practical document accessibility lifecycle runs from inventory to ongoing monitoring. Treating it as a repeatable cycle keeps large government document libraries manageable.
Inventory and Classify the Document Library
For the file-by-file technique behind each fix, see How to Make Documents Accessible.
First, record the document name, owner, location, publication date, version, document type, and purpose so every file has a known owner and status.
Then separate current, historical, archived, individualized, third-party, and potentially exempt content before any remediation work begins.
Prioritize High-Impact Documents
For libraries in the thousands, work in batches by document type, since the same fixes then repeat predictably. This rundown of common issues in bulk PDF accessibility remediation shows which defects repeat across a library.
To begin with, prioritize the documents that:
- Support government services
- Are frequently accessed or currently used
- Are required for applications
- Affect participation in government programs
Remediate Structural Issues
Next, address the applicable issues involving tags, headings, reading order, alternative text, tables, forms, links, and document language in each prioritized file.
For large document libraries, remediation works best as a structured process of discovery, remediation, validation, monitoring, and evidence tracking, often supported by dedicated document remediation software.
Validate With Manual and Assistive-Technology Testing
Even then, automated tools can identify many technical issues, but they cannot establish every aspect of accessibility. This guide to automated vs manual accessibility testing sets out where each method stops.
A reliable check combines three steps:
- An automated scan with Adobe Acrobat’s accessibility checker or the free PAC checker
- A manual review of reading order, alt text, and table structure
- A screen reader pass with NVDA or JAWS
PAC tests against PDF/UA (ISO 14289), the technical standard for accessible PDFs. PDF/UA is a useful benchmark, but the Title II rule itself requires WCAG 2.1 AA.
For teams handling this at volume, Limina, SDLC Corp’s document accessibility remediation software, brings testing, remediation, monitoring, and reporting into one workflow.
Publish and Monitor
Finally, publish the validated version, then reassess accessibility whenever a document is substantially changed so the published file never falls behind the standard.
Maintaining an Accessibility Audit Trail
Ultimately, organizations managing large document libraries should keep evidence of accessibility decisions. A useful record for every file can include:
| Audit Field | Example Information |
|---|---|
| Document name | Permit Application 2026 |
| Owner | Permitting Department |
| Version | v3.2 |
| Publication date | June 2026 |
| Document type | |
| Coverage status | Covered / Exception / Review Required |
| Exception rationale | Applicable provision |
| Remediation status | Complete / In Progress |
| Testing date | September 2026 |
| Testing method | Automated + Manual |
| Validation result | Passed / Issues Found |
| Publication status | Published |
| Next review | Scheduled date |
As a result, this record shows what was reviewed, who reviewed it, what decision was made, and when validation took place.
Procurement and Vendor Considerations
In many cases, government organizations often rely on vendors to build websites, applications, document systems, and digital content. Accessibility expectations belong in the contract rather than in a post-launch fix list.
What to Include in Vendor Contracts
Set out the accessibility requirements in the contract itself, rather than after delivery, and ask suppliers for accessibility testing and compliance reporting as a named deliverable.
- Applicable accessibility standards
- Accessible document deliverables
- Testing and remediation responsibilities
- Accessibility documentation
- Version control and source-file ownership
- Issue-resolution procedures
- Post-launch responsibilities
Similarly, you should not treat vendor-created content as exempt by default. In practice, the contract terms and the regulatory circumstances decide how it counts.
Accessibility Beyond the Document
Besides the files themselves, documents sit inside websites and applications, so the surrounding experience matters too. Keyboard navigation, screen-reader labels, contrast, forms, and accessible components all affect whether residents can reach and use a document.
SDLC Corp supports the build side through accessible web development services and the design side through UI/UX design services.
Set standards, testing duties, remediation ownership, and source-file rules before a vendor publishes documents on your behalf.
Plan Your Accessibility ProgramSDLC Corp Capability
Making Government Documents Accessible at Scale
SDLC Corp helps public entities find, fix, and verify accessibility issues across large document libraries, using Limina and a structured remediation workflow.
Assess and Prioritize
Inventory your document library, classify coverage and exceptions, and rank files by how residents use them.
Remediate and Validate
Fix tags, reading order, alt text, tables, and forms, then verify with automated checks, manual review, and screen readers.
Monitor and Report
Track new and changed documents, keep audit records current, and report progress ahead of your compliance date.
Further Reading and Primary Sources
Together, these references cover the parts of document accessibility this page only summarizes.
Frequently Asked Questions
In practice, this means state and local governments and their agencies, including counties, cities, special district governments, public school districts, and public colleges and universities.
Yes. An April 2026 interim final rule moved the dates to April 26, 2027 for public entities of 50,000 or more, and April 26, 2028 for smaller entities and special district governments.
In most cases, yes. PDFs posted on a government website or app count as conventional electronic documents, unless a specific exception applies.
The DOJ’s Title II web and mobile accessibility rule uses WCAG 2.1 Level AA as its technical standard for covered web content and mobile applications.
In short, Title II covers state and local governments, while Title III covers private businesses and other places open to the public, such as stores, hotels, and private universities.
Yes. Public colleges and universities are state or local government entities, so their websites, apps, and documents are covered by the Title II rule.
In practice, people can file complaints with the DOJ or bring lawsuits. As a result, outcomes can include investigations, settlement agreements, court orders, and required remediation.
However, some preexisting conventional electronic documents may qualify for an exception if they meet the applicable conditions. Being old alone does not make a PDF exempt.
In that case, the WCAG requirements under the Title II web and mobile rule may not apply to that document. However, other ADA obligations, including effective communication and equal access, can still apply.
Not on its own. OCR makes scanned text machine-readable, yet the file still needs tags, reading order, headings, alternative text, tables, and forms.
Only in part. Automated tools flag many issues, although some WCAG criteria and accessibility questions still require human testing and judgment.
It is not. WCAG2ICT is W3C guidance on applying WCAG concepts to non-web documents and software, so it carries no separate legal force.
