Back to Blog

A Librarian Asked Which of Our Templates Make Accessible PDFs. None Did.

Shihab Shahriar Antor•November 14, 2026

In November a librarian at a public university in the United States wrote to us with a question we could not answer well. She had added LetX to her library’s LaTeX guide. Instructors on her campus have to publish accessible documents, and they were asking her which of our templates produce accessible PDFs.

The honest answer was none. We had more than a thousand templates, and not one of them built a tagged PDF. This post is what we did about it in the days after, and what we still have not done.

Why the answer was none

A PDF made the usual way is a picture of a page. A screen reader gets letters at positions and has to guess the rest: what is a heading, where the columns of a table are, what a figure shows. A tagged PDF carries that structure inside the file. For most of its life LaTeX could not write one. The LaTeX Tagging Project changed that: with a current LaTeX release, one declaration at the top of a document turns tagging on.

Our build servers already ran that release. Nothing in our gallery used it. And the editor would have chosen the wrong engine for such a document: under XeLaTeX the equations carry no MathML, which is most of what a screen reader needs from a maths handout.

What we changed

  • The engine. A new project that asks for a tagged PDF is now built with LuaLaTeX, the engine the LaTeX Project recommends for it. Nobody has to know that to get it right.
  • Three templates. An article, a letter and a course handout, the documents she named first. Each has comments saying which few lines to keep when you replace the sample text.
  • A rule for the label. A template is called accessible in our gallery only after it is built on LetX and its PDF passes a PDF/UA-2 check in veraPDF with no failed rule. The template page says which version of the validator and when.

What the validator said

All three passed on 14 November 2026: 1,728 rules checked by veraPDF 1.30.4, none failed. Two things are easy to leave out and the standard asks for both. A table has to say which row holds its headers, and a drawing made in TikZ needs alt text just as a photograph does.

This is the smallest document we know that passes. The first seven lines are what makes the difference.

main.tex
\DocumentMetadata{
  lang=en-US,
  pdfstandard=ua-2,
  pdfversion=2.0,
  tagging=on,
  tagging-setup={math/setup=mathml-SE}
}
\documentclass{article}
\usepackage{unicode-math}
\usepackage{hyperref}
\hypersetup{pdftitle={A first accessible document}, pdfdisplaydoctitle=true}

\title{A first accessible document}
\author{Your Name}
\date{}

\begin{document}
\maketitle

\section{Why this PDF is tagged}
The first lines of this file turn tagging on. Headings, lists and equations
are written into the PDF with their structure, so a screen reader can use them.

\begin{itemize}
  \item It can list the headings and jump to one.
  \item It can read an equation aloud, such as \( E = mc^2 \).
\end{itemize}

\section{What to add as you write}
Give every figure alt text and say which rows of a table are headers.
\end{document}

What we have not done

Nobody has listened to these PDFs with a screen reader yet. A validator checks what a machine can check. It cannot tell whether an alt text is a good description, or whether a page makes sense read aloud. The next step is to ask people who use a screen reader to listen and tell us what they hear, starting with the librarian’s own campus, and to change the templates and this post to match.

So the label on those templates says what is true and nothing more: a tagged PDF that passes the PDF/UA-2 check. It does not say compliant with any law. That depends on what you write in the document, and it is for your institution to judge.

If you teach or write in LaTeX

Start from one of the accessible templates, or read how to make your own document accessible. If you are moving a course, there is a page on accessible course materials written in LaTeX, with the dates of the US rule. And if you use a screen reader and one of these PDFs reads badly, write to support@letx.app. That is the report we most want.

Frequently asked questions

Do LaTeX templates produce accessible PDFs?

Most do not. An ordinary LaTeX PDF has no tags, so a screen reader cannot tell a heading from a paragraph or read a table by its columns. A template has to turn tagging on with a \DocumentMetadata declaration and be built with a current LaTeX release. LetX has three templates that do this, and each one’s PDF passes a PDF/UA-2 check.

How does LetX decide that a template is accessible?

The template is built on LetX and its PDF is run through veraPDF, an open-source validator, against the PDF/UA-2 profile. It gets the Accessible PDF label only if no rule fails. The template page says which version of the validator was used and when.

Is passing a validator the same as being accessible?

No. A validator checks what a machine can check: that tags, a language, a title and text alternatives exist. It cannot judge whether an alt text describes the picture well or whether the reading order makes sense. Those need a person, ideally one who uses a screen reader.

Keep reading

Ready to try LetX?

Join researchers and students focusing on their work, not the tools.

Get Started Free
Shihab Shahriar Antor

Written by Shihab Shahriar Antor , AI Engineer & Founder of Shahriar Labs. Builder of LetX (collaborative LaTeX) and offSchool (SSC science and maths, learned through simulations).