LaTeX November 2026 update: tagged PDF and when to upgrade
LaTeX released its November 1, 2026 kernel update with further support for tagged PDF. If your paper compiles reliably and a deadline is close, keep the working environment and test the update in a copy. If your institution or publisher requires an accessible PDF, this release is worth evaluating early.
The update improves structural support for headings, lists and theorem-like environments, and extends package compatibility. Producing a PDF, producing a tagged PDF, and meeting PDF/UA requirements are separate checks.
What changed in the November 2026 LaTeX release?
The official announcement says the 2026-11-01 kernel was sent to CTAN and was already available through TeX Live updates. That does not establish which version your computer or online editor is running. LaTeX News 44 gives the details:
| Change | What paper authors should know |
|---|---|
| More work on headings, lists, theorems and proofs | Custom layouts need checks for both appearance and logical structure |
Extended tagging support for float | Support now includes \newfloat, \restylefloat and \floatstyle |
listings is mostly tagging-compatible | Frames, escapes to math and brace-delimited \lstinline still have limitations |
titlesec emulation remains incomplete | Do not assume existing \titleformat settings are fully supported |
New kernel command \strongemph | Semantic strong emphasis, with default styling involving bold and bold italic |
| Reference, page handling and long-table fixes | Specific fixes cover subcaption with amsmath, afterpage and unnumbered longtable |
A package that works in an ordinary build may behave differently when tagging is enabled. Check the official package and class compatibility index and read the notes for each dependency in your template.
What is a tagged PDF? Is it the same as bookmarks?
A PDF's visual layer places text, lines and images on pages. Its structure layer describes relationships between headings, paragraphs, lists and figures. Assistive technology can use that structure to navigate and read a document, depending on the reader software.
AI-generated conceptual illustration: visual layout and logical structure need separate checks. The tree is conceptual, not the output of a PDF inspection tool.
Bookmarks provide navigation destinations. They do not replace document-wide structure tags. Selectable text is also insufficient evidence that heading levels, reading order or table-header relationships are correct. PDF/UA is a PDF accessibility standard; declaring it as a target does not establish conformance.
Papers with figures and equations need particular attention. Meaningful figures need alternative text, data tables need identified headers, and accessible mathematics also depends on mathematical representations and reader support.
The LaTeX kernel, TeX Live and your editor are different layers
AI-generated conceptual illustration: an upstream release reaches a project only through the compilation environment that actually runs it.
- The LaTeX kernel has a release date, such as
2026-11-01. - Distributions such as TeX Live and MiKTeX provide engines, format files and packages. Installations from the same TeX Live year can have different update states.
- Online editors deploy and select particular environments. A “TeX Live 2026” label alone does not prove that a project uses the November kernel.
Look for the LaTeX2e <...> date in the complete build log. Check the engine and package versions too. Adding \listfiles to the main file's preamble makes LaTeX list loaded file versions near the end of the log.
The upstream announcement is not evidence that EasyLaTeX or another hosted platform has deployed this kernel. Test the actual engine, template and package combination used by your project.
How to start testing tagged PDF
The official usage instructions recommend LuaLaTeX for new documents; supported configurations can also use pdfLaTeX. An existing XeLaTeX project needs a check of its fonts, language packages and template before an engine change.
This small English document illustrates the setup. Place \DocumentMetadata before \documentclass. Its lang=en describes the sample's English text; set the appropriate document language for your own paper.
\DocumentMetadata{ lang=en, tagging=on, pdfstandard=ua-2}\documentclass{article}\listfiles\title{A small tagged document}\author{Example Author}\date{}\begin{document}\maketitle\section{Results}The experiment has two observations.\begin{itemize} \item The first observation. \item The second observation.\end{itemize}\end{document}This minimal example compiled successfully on TeXLive.net on November 5, 2026, using LuaLaTeX and LaTeX2e <2026-11-01>, producing a one-page PDF. This was a compilation check, not a PDF/UA conformance test.
Compile with LuaLaTeX in an environment supporting these interfaces. Expect a PDF containing a title, section and list, then inspect its tags and reading order. pdfstandard=ua-2 sets a target; it does not replace PDF/UA validation. This example does not test figures, equations, non-English typesetting or a journal template.
Real papers also need author-supplied information. The documented interfaces include \includegraphics[alt={...}]{...} for meaningful image descriptions and \tagpdfsetup{table/header-rows={1}} to identify a table's first row as headers. Match the configuration to your installed versions and table structure instead of applying one setting indiscriminately.
Should you upgrade a paper in progress?
AI-generated conceptual illustration: evaluate the new environment in a copy before adopting it for the submission version.
| Situation | Suggested approach |
|---|---|
| Deadline close, stable paper, no new recipient requirement | Keep the reproducible environment and test separately |
| New project with an accessible-PDF requirement | Confirm the target standard, template support and validation process early |
| Extensive custom headings, lists or code displays | Check titlesec, listings and the relevant class files first |
| Errors or layout changes after updating | Compare against the baseline log and PDF; isolate changed dependencies |
Save the source, last correct PDF and full log. Record the main file, engine and versions. In a copy, add the template, packages, figures and mathematics incrementally and check each result. For ordinary failures, use the LaTeX compilation troubleshooting guide. For a multi-file manuscript, start with large-project organization.
For an EasyLaTeX project, the project-to-PDF guide explains choosing a main file and compiler. Base an upgrade decision on the actual log, template tests and recipient requirements.
What should you check before submission?
Review heading levels, reading order, figure descriptions, table-header relationships, and the reading experience for equations and references. Use a validator accepted by the recipient that supports the intended PDF/UA version, alongside manual reading tests. A successful build or the presence of tags does not establish that the whole paper conforms to PDF/UA.
Common questions
Does updating LaTeX automatically create an accessible PDF?
You need suitable tagging settings, compatible packages and a compatible template, plus semantic information for images and tables. Validate the output.
Will tagged PDF make AI read my paper more accurately?
Tools that support structure information can use it. This release does not provide a controlled comparison of AI reading accuracy, so it cannot support promises about a model understanding papers better.
Should every project switch to LuaLaTeX?
Check the template, fonts, language and submission requirements first. LuaLaTeX is the project's recommended engine for new tagging documents, not a reason to switch every existing manuscript immediately.
Official references
- November 1, 2026 announcement
- LaTeX News 44: full release notes
- Accessible-PDF usage instructions
- Package and class tagging compatibility
Sources checked November 5, 2026. Illustrations generated with NanoBanana Pro for EasyLaTeX.