/accessible-pdfAccessible PDFs from LaTeX, checked
Type /accessible-pdf in Lexi, the assistant in the LetX editor. It reads your project against the LaTeX Project’s list of what works with tagged PDF and tells you, free, whether it can pass today. With Pro it then makes a copy on TeX Live 2026 and works on the copy until its PDF passes the PDF/UA-2 checks veraPDF runs, or tells you what still fails. You approve the description of every figure, and a person must still judge the alternative text and the reading order.
Three possible answers, before anything changes
- Can convert
Nothing in the way. Lexi switches tagging on in the copy and builds.
- Can convert, with changes
Some packages have to change. Each one is listed, with what takes its place, before you decide.
- Cannot pass today
The class or a package cannot be tagged yet. Lexi says which, and copies nothing.
/accessible-pdf
This project can be made into a tagged, accessible PDF
Lexi works on a copy, Lab report (accessible). Your project is not touched.
What would change in the copy
- mdframed becomes tcolorbox
- minted becomes listings
- subcaption stays as it is, and may be what still fails at the end
- Builds with LuaLaTeX on TeX Live 2026, so that the maths can be read aloud
- 2 figures need a description. Lexi drafts them where it can see the picture, and you approve each one.
This verdict is free for everyone. Making the accessible copy is part of Pro. See Pro
Status list: the LaTeX Project's, read on 20 November 2026.
What it does, step by step
It reads your project and gives a verdictFree
Lexi reads every.texfile in the project, and your own class and package files, against the LaTeX Project’s status list of classes and packages that work with tagged PDF. It answers with one of the three verdicts above and lists what it would change, package by package. It builds nothing and changes nothing.It makes a copyPart of Pro
Your project is never edited. Lexi makes a copy named after it, with “(accessible)” after the name, on TeX Live 2026, the release the status list describes. When the document has maths, or was built with XeLaTeX, the copy builds with LuaLaTeX, so that the maths can be read aloud.It works on the copy in roundsPart of Pro
In the copy, Lexi switches tagging on and makes the changes the verdict listed. Each round is a build of the copy and a check of its PDF by veraPDF. It stops when the checks pass, when further rounds stop getting closer, or when the run has done what one run may, and says what still fails. You can let it continue.It drafts a description of each figure, and you decidePart of Pro
Where a figure is a PNG or JPEG picture, Lexi looks at it and drafts a description. A PDF, EPS or SVG figure, or a drawing made in the source, gets an empty box, and the words are yours. You approve each description, change it, or mark the figure as decoration, one figure at a time. There is no “approve all”.Only then is the claim addedPart of Pro
When every check but the claim itself passes and every figure is decided, LetX adds the PDF/UA-2 claim to the copy, builds it again and checks the PDF that carries the claim. If that check fails, the claim is taken out again.
What it never says
It does not hand out a badge. When the checks pass, it says exactly what happened, in these words:
This copy passes the PDF/UA-2 checks veraPDF runs
The PDF now says it follows PDF/UA-2. A person must still judge the alt text and the reading order.
Followed by the veraPDF version and the date of the check.
- A PDF from LetX never claims PDF/UA-2 while a check fails.
- No assistant writes the claim. Lexi, and the connector for Claude and ChatGPT, refuse to write a PDF/UA claim into a document; only the last step above adds it, after the checks.
- A claim you typed yourself is yours. LetX leaves it as it is.
What cannot pass today, and why
Tagged PDF is new in LaTeX, and not every class and package works with it yet. The LaTeX Project keeps a status list of which do, and /accessible-pdf follows it rather than hoping. When the list says a project’s class cannot be tagged, Lexi says so before anything is copied, and does not try. We would rather tell you no before you spend an evening on it than after.
As the list stood when we read it on 20 November 2026, these classes could not pass:
- Beamer (slides)
- memoir
- KOMA-Script (scrartcl, scrbook)
- IEEEtran
- llncs (Springer LNCS)
- REVTeX (revtex4-2)
- moderncv
And whatever the class, a document cannot pass today when:
- it makes a PDF form, because form fields cannot be tagged yet;
- it loads pdfpages, because pages taken from another PDF carry no tags;
- it needs a package that runs only on XeLaTeX, such as xeCJK, because tagging needs pdfLaTeX or LuaLaTeX.
This is what Lexi’s panel says for Beamer and for memoir, word for word:
The LaTeX Project lists the class beamer as not supported for tagged PDF. No change to the file would make it pass, so Lexi does not try and nothing is copied.
The class memoir does not work with tagged PDF yet. Nothing is copied.
The list changes as the LaTeX Project’s work goes on, and LetX reads it again every day, so a class that cannot pass today may pass later. Your own class and package files are not on the list; they are checked by building. For slides, the ltx-talk class takes the place of Beamer.
Who checks: veraPDF
veraPDF, an open-source PDF validator, checks the copy’s PDF against its PDF/UA-2 profile. PDF/UA-2 (ISO 14289-2) is the part of the PDF/UA standard written for PDF 2.0: how a PDF is built so that a screen reader, a braille display or a reading tool can use it. veraPDF runs on a server of its own that reads that one PDF, and no AI model is involved in the check.
The same checker is free on every plan in the editor: a button beside your PDF runs veraPDF’s checks and shows what to fix.
What stays your job
A validator reads how a file is built, not what it says. Before you submit or post the PDF, the panel asks you to do what no program can:
- Read each description once more against its figure.
- Listen to a page or two with a screen reader. NVDA on Windows and VoiceOver on a Mac are free.
- Read the headings as an outline, and check that the reading order makes sense.
- Look for colour that carries meaning on its own, and for text with too little contrast.
- Some university checkers (PAC, Ally, Acrobat) do not read PDF/UA-2 yet and may report errors on a correct file. We last checked in November 2026. If your university asks for one of them, ask which version of PDF/UA it expects.
What is free, and what is part of Pro
Free, on every plan
- The verdict from
/accessible-pdf, for any project you can open. - The PDF accessibility check in the editor: veraPDF’s checks from a button beside your PDF.
- Templates whose PDFs passed veraPDF’s PDF/UA-2 check when we built them.
Part of Pro, Academic Pro, Team and Institution
- The copy on TeX Live 2026, and Lexi’s rounds on it.
- Drafted descriptions of PNG and JPEG figures, for you to approve.
- The PDF/UA-2 claim, added only after the checks pass.
This is a long task and uses more of your Lexi allowance than a chat.
Starting something new?
Start from a template whose PDF already passes: each accessible template was built on LetX and passed veraPDF’s PDF/UA-2 check, from an article, a letter and a course handout to slides on ltx-talk and thesis templates. To do it by hand, the guide to an accessible PDF from LaTeX goes through it line by line, and this post tells how the templates came about.
Why universities in the United States are asking
The Department of Justice’s rule under Title II of the ADA asks state and local governments, public universities among them, to make their web content meet WCAG 2.1 Level AA. Its Interim Final Rule of 20 April 2026 moved the dates to 26 April 2027 for public entities with a total population of 50,000 or more, and 26 April 2028 for smaller ones and special district governments. The Department has said it plans further rulemaking on the rule’s substance, so check its own page for the current state.
PDF/UA is a standard for PDF files and the rule names WCAG, so passing veraPDF’s checks is not a statement that a document meets the rule. This page is not legal advice: your accessibility office decides what applies to you. For instructors, there is more on accessible course materials written in LaTeX.
Questions
Is the verdict free?
Yes. Typing /accessible-pdf in a project gives the verdict on every plan, the free one included: Lexi reads the project and says whether it can pass today and what would change. Making the copy and converting it is part of Pro, Academic Pro, Team and Institution.
Does it change my project?
No. Lexi works on a copy it makes for this, named after your project with "(accessible)" after the name. Your original is never edited, and a project that cannot pass today is not copied at all.
Who decides that the PDF passes?
veraPDF, an open-source validator, with its PDF/UA-2 profile, on a server of its own. Lexi does not decide: its rounds stop when veraPDF finds nothing left to fail but the claim itself, and the PDF that carries the claim is checked again. Every pass names the veraPDF version, the profile and the date.
Does Lexi write the alternative text?
It drafts a description for each figure that is a PNG or JPEG picture, from the picture and its caption. A draft is only a draft: you approve each one, change it, or mark the figure as decoration, and the PDF/UA-2 claim is added only after every figure is decided. Figures of other kinds get an empty box for you to fill.
Are my figures sent to an AI model?
Only when you ask Lexi to draft descriptions, and then only the figures that are PNG or JPEG files, each with its caption, as the privacy policy says. Your documents are never used to train AI models.
Why can my class not pass?
The LaTeX Project's status list says it does not work with tagged PDF yet, or, for Beamer, that it has no tagging support. No change to your file can get past the class, so Lexi says so and copies nothing. For slides the ltx-talk class works with tagging, and for other documents the article, report and book classes do.
Does a pass mean my PDF meets the ADA rule?
No. A pass means the PDF passes the PDF/UA-2 checks veraPDF runs, which is what a program can verify. The rule names WCAG, and whether a document meets it also depends on what it says, its alternative text and its reading order, which a person must judge. Your accessibility office decides what applies to you.
Why does Acrobat or Ally report errors on a PDF that passes?
When we last checked, in November 2026, PAC, Blackboard Ally and Acrobat's checker did not read PDF/UA-2, so they may report problems in a tagged PDF 2.0 file that passes veraPDF's PDF/UA-2 profile. If your university asks for one of them, ask which version of PDF/UA it expects.
Find out whether your project can pass
Open it in LetX and type /accessible-pdf in Lexi. The verdict is free.
Open the free editor