ADA Digital Accessibility Requirements

The U.S. Department of Justice finalized rules under Title II of the Americans with Disabilities Act requiring state and local government entities — including public universities — to ensure their digital content meets WCAG 2.1 Level AA accessibility standards. The compliance date for most covered entities is April 24, 2026.

This is not a new law. The ADA has been on the books since 1990. These are new, specific rules that define what "accessible" means for digital content and set an enforcement timeline.

The rules cover all digital content that public entities publish or make available — including course materials uploaded to an LMS, handout PDFs, and lecture notes shared with students.

A student using a screen reader cannot access a photo of a whiteboard. It renders as a blank rectangle. There is no text to read, no structure to navigate, no math to hear announced. The content simply does not exist for that student.

When professors respond to the new requirements by taking their notes down, everyone loses. The sighted students who relied on those materials lose them. And the students with disabilities — the ones the law was designed to help — still have nothing.

The goal is straightforward: a student using assistive technology should receive the same materials as everyone else. That is the right thing. The law isn't the villain here. The lack of tools and support to live up to it is.

The Title II rule covers state and local government entities, which includes:

• Public colleges and universities
• Public K-12 schools
• Community colleges, technical schools, and other public institutions
• Any government entity that publishes digital content

Private institutions are covered under Title III of the ADA, which has less specific digital accessibility requirements but is still the basis for accessibility-related litigation. The regulatory pressure is lower for private schools, but the legal exposure is real.

WCAG 2.1 Level AA is the technical standard the rules require. For documents, that translates to:

• Tagged PDF structure — headings, paragraphs, lists, and reading order embedded in the file so screen readers can navigate it
• Alt text for images — text descriptions for every image, diagram, and figure so visually impaired users know what they contain
• Machine-readable text — actual text, not a photograph of text
• Logical reading order — content that flows correctly for linear reading by assistive technology
• Accessible math — for STEM content: LaTeX or MathML that assistive technology can parse and announce, not images of equations

A document that looks fine visually can be completely inaccessible. The visual appearance and the accessible structure are independent properties. A PDF that prints well and displays correctly on screen may have no tag structure at all — meaning a screen reader encounters a content-free file.

Acknowledging that accessibility is hard is not an excuse to avoid it. It is an honest accounting of why the tooling gap is real and why faculty need actual support, not just a policy mandate.

• Handwritten math has no machine-readable standard — Generic OCR fails on equations. Integrals, summations, Greek letters, stacked fractions — they do not map cleanly to Unicode text. The only machine-readable formats for math that assistive technology can actually parse are LaTeX and MathML.
• Diagrams carry meaning in spatial arrangement — A circuit diagram, a proof sketch, a force diagram — the spatial relationships between elements are the content. Describing that with alt text in a single sentence is often inadequate.
• Existing tools assume digital-first documents — Adobe Acrobat's remediation tools, Microsoft's accessibility checker, most LMS accessibility features — all of them work on documents that started as typed text. They have limited support for handwritten originals or scanned materials.
• LaTeX accessibility is not plug-and-play — LaTeX can produce accessible PDFs, but it requires specific packages, configuration, and technical expertise. Most faculty using LaTeX are not accessibility engineers.

None of this makes the accessibility goal wrong. It makes the tooling gap real and the need for purpose-built solutions clear.

The Title II rule includes specific exceptions. Understanding them matters so you don't over-apply them:

Archived Content

Content qualifies as "archived" only if it meets all of these conditions:

• Created before the compliance date (April 24, 2026)
• Kept solely for reference, research, or recordkeeping
• Stored in a designated archive area
• Not modified after it was archived

If students regularly access content as part of their coursework, it is not archived — even if it was created before the compliance date.

Pre-Existing Documents

PDFs and other document files that existed before the compliance date have a partial exception — but only for documents that were not developed by or for the covered entity. Materials created by faculty and distributed to students do not receive this exception.

The ADA is enforced primarily through civil litigation. Students can file complaints with the Department of Justice or bring lawsuits directly. The DOJ can also pursue enforcement actions independently.

The institutional risk is real. Universities have paid significant settlements in accessibility cases in recent years. Those cases are not hypothetical — they involve real students who could not access real course materials.

The more important framing is not "what happens if you don't comply" but "what happens to students when materials aren't accessible." The answer is the same in both framings: students lose access to educational content they are entitled to.

The practical options vary depending on what kind of content you have and your technical comfort level:

For handwritten notes and scanned documents

This is the hardest case, and the one with the fewest existing tools. AccessibleNotes is purpose-built for this: upload a photo of handwritten notes (including math and equations), and the tool transcribes them into structured markdown with properly typeset LaTeX, then exports to PDF, DOCX, or HTML. You review and correct the transcription before exporting — the tool handles the heavy lifting, but you are always responsible for verifying accuracy and accessibility before sharing with students.

For LaTeX users

PreTeXt is a markup language designed for accessible mathematical documents. If your workflow is already LaTeX-based, PreTeXt produces accessible HTML and PDF output natively. The learning curve is real, but the output quality is excellent. Pandoc with accessibility flags can also convert LaTeX to accessible HTML.

For typed documents and slides

Pandoc can convert Word documents and markdown to accessible HTML and PDF. Microsoft Word and PowerPoint have built-in accessibility checkers. Adobe Acrobat Pro has remediation tools for existing PDFs. These work well when the source document is already digital.

For institutional or department-scale needs

Individual faculty shouldn't bear this alone. Accessibility Services offices and department administrators need tools that scale — bulk processing, validation reporting, and workflows that don't require technical expertise from every faculty member.