On April 24, 2026, we are required as educators to comply with the new ADA Title II standards which adhere to Web Content Accessibility Guidelines (WCAG) 2.1 Level AA. I regularly prepare mathematical and physics-heavy teaching materials using GitHub, Overleaf, and LaTeX. Because these documents often contain substantial mathematical notation, accessibility requires some extra care.

From reviewing the current landscape, I think of the available options as falling into two broad branches:

  1. Make LaTeX-generated PDFs more accessible, primarily through PDF tagging and related metadata.
  2. Move away from PDF-first workflows and instead render LaTeX source into more output-agnostic formats such as HTML, EPUB, markdown webpages.

This page collects resources I have found useful while exploring both paths and then I complain at the end – which is only fitting.


1. Accessible PDF workflows in LaTeX

This approach keeps LaTeX as the authoring environment and aims to produce tagged PDFs that work better with screen readers and other assistive technologies.

My present impression is that this is a promising and rapidly improving area, but still one under active development.

Good starting points

Institution and support resources

Notes on slides and presentations

Traditional beamer for LaTeX generated slides is not and likely will never be supported for PDF Tagging and accessibility. A newer alternative is:

  • ltx-talk – a newer LaTeX class aimed at presentation with accessibility/tagging in mind

If I revisit slide creation for accessibility in the future, this is likely where I would start rather than with beamer.

Adobe Acrobat and post-processing

Another possible route is post-processing PDFs in Adobe Acrobat:

I am less familiar with this, particularly for documents containing substantial mathematics, so I list it here mainly as a possible remediation tool rather than a method I can yet recommend from experience.


2. Moving beyond PDF-first output

The second branch is to treat LaTeX as source material that can be transformed into formats that are often more accessible by default, especially for web delivery, reflow on variable screen sizes, and integration with modern reading tools.

For me, this may eventually become the preferred long-term direction: writing notes in LaTeX, then publishing them as a website or another web-friendly format.

Tools and platforms worth watching

  • Pandoc User’s Guide – a general-purpose document converter that can bridge LaTeX into many output formats
  • PreTeXt – a “write once, read anywhere” authoring system especially attractive for technical and mathematical content
  • LaTeXML – a LaTeX-to-XML/HTML/MathML converter

Why this direction is attractive

A web-first or output-agnostic approach can make it easier to support:

  • screen readers
  • variable screen sizes
  • high-contrast or custom display settings
  • web publication
  • alternate export formats such as HTML, EPUB, or notebooks

I personally have been converting course notes into a GitHub-hosted website rather than distributing PDF alone.

AI-assisted conversion

I have also had some success using AI tools, including ChatGPT and Gemini, to help convert LaTeX source into HTML or Markdown-compatible content for one-off use cases. I do not view this as a substitute for stable methods such as PreTeXt, Pandoc, or LaTeXML. But for limited conversions, draft web pages, or restructuring notes into more flexible formats, it can be quite helpful.


My current perspective

At the moment, I think both branches are worth tracking:

  • Tagged PDF in LaTeX is becoming increasingly practical and may fit best for documents that must remain close to traditional academic PDFs.
  • Web / output-agnostic publishing may ultimately be the more flexible and more accessible long-term strategy for teaching materials, especially for mathematics-heavy notes.

Because this area is changing quickly, I expect many of the tools and recommendations above to improve over time. At the moment, none of these are a silver bullet approach and requires significant heavy-lifting from faculty often with limited direct institutional support. I’m mostly seeing lots of workshops and faculty-led resources being generated.

Just a quick glance at the discourse surrounding this does not paint a rosy picture:

There’s a big risk these requirements degrade our current instructional materials for students and push us further into just using big publisher materials rather than bespoke content which uses our unique expertise. To quote a common response:

Instructors at my school are responding to this largely by just not posting notes anymore. One writes all of his notes and mark down and then posts them, which seems like a lot of work.

The only reasonable course of action for many of us is to remove materials. We do not have time or technical capability to do anything else on the timeframe required.

A lot of people in my department are just going to stop uploading things. 🤷🏻‍♂️

I can’t say I blame them.

My lingering hope is that the tools get up to speed so that going forward, it is a smooth process to make new materials compliant and better for students. If you have built your own accessible LaTeX tools, conversion pipelines, or public teaching materials, I would be glad to hear about them. Community-shared examples are often the most useful way to learn what is working in practice.

Special thanks to Dr. Hunter Lehmann, Director of Undergraduate Advising for the School of Math at Georgia Tech. Several of the most useful resources collected here were prepared by him, whose guides and workshop materials have been especially helpful for understanding the current state of accessible LaTeX.