Creating accessible PDFs
Over time, updates to the capabilities of PDF creation have made PDF accessibility possible. Strides including the LaTeX Tagging Project have enabled LaTeX-based PDFs to be accessible as well, and improvements continue to occur.
The release of TeX Live 2025, in particular, is what makes this process possible in Overleaf. Note that LuaLaTeX is the recommended compiler when using MathML.
You can ensure your project's settings are set up accordingly by learning how to change compilers and TeX Live versions.
Our approach is largely informed by the LaTeX Project's accessible PDF instructions, which you can refer to for more details on the following topics.
Note that implementing these practices doesn't guarantee that every element of your project is accessible—see this page's FAQs section for more information.
Tagging
In essence, PDF tagging is a process that automatically creates a "structure" that is easily identified by screen readers, and is more searchable both now and in the future. It leverages the existing structure defined by your LaTeX code so the screen reader can differentiate between elements like headers, body text, figures, and equations.
TeX Live 2025 fully supports automated PDF tags with the \DocumentMetaData declaration. Add this declaration before \documentclass. There are two important keys to this declaration that affect tagging capabilities: tagging and tagging-setup .
tagging
taggingEnsure that tagging is enabled by setting the tagging key to on.
tagging-setup
tagging-setupConfigure how your document is tagged by changing the value of the tagging-setup key.
In this example, we used math/setup=mathml-SE for MathML Structure Element tagging, but it can be set to any value that \tagpdfsetup supports.
Descriptions
In addition to automatic tagging, you may also need to also add descriptions of the content of the elements, particularly if your document contains images and/or tables.
Images
It's simple to add vital descriptions for images in Overleaf, which can also help with understanding the context of certain images when referencing the LaTeX code. All you have to do is add the associated image description option in each instance of \includegraphics. There are three main types of images to distinguish for accessibility: images that require alternative (alt) text, artifacts, and images that translate to actual text.
Alt text
Adding alternative text to images ensures that the photo has a description that can be used as a text-based substitute to the visual. Use the alt key and input a text value.
Artifacts
If an image doesn't need to be picked up by a screen reader (i.e., if it's purely decoration), mark the image as an artifact. Use the artifact key without assigning a value.
Actual text
If an image is a solely a picture of a Unicode character, then include the text-based character. Use the actualtext key and assign it a single character (without brackets).
Tables
While tables usually have text associated with them, it's still important that the text is associated with the correct aspects of the table. Add \tagpdfsetup before your tabular or in the preamble to begin the set up for your Overleaf project's tables. There are two main types of tables to distinguish for accessibility: data tables and presentation tables.
Data tables
If a table has at least one header row, then designate which rows are the header rows. Use the table/header-rows key and input a series of numbers that correspond with the locations of the header rows.
Presentation tables
If a table is not meant to be interpreted as a table by a screen reader, then mark it as a presentation table. Use the table/tagging=presentation key.
FAQs
Are the packages in my Overleaf project compatible with these features?
You can refer to the LaTeX Tagging Project's packages status list.
Can I still use beamer? Are there other packages available for presentations?
There are limitations to using beamer; check out the experimental ltx-talk class.
Is the Overleaf editor accessible?
Yes. As a web application, Overleaf leverages the accessibility features and functionality of modern web browsers which are regularly assessed by accessibility experts. Our latest completed Voluntary Product Accessibility Template (VPAT) shows conformance with Web Content Accessibility Guidelines (WCAG) 2.2 Level AA.
Can PDFs produced by Overleaf satisfy the requirements of Title II of the Americans with Disability Act (ADA) and the harmonized European Standard for accessibility (EN 301 549)?
Yes. Legislation in the United States and Europe requires that PDFs meet WCAG 2.1 AA. To meet WCAG 2.1 AA, a PDF must be a tagged PDF. Support for tagging a PDF is provided in TeX Live 2025.
Can PDFs produced by Overleaf meet the PDF/UA-1 standard?
Yes. The LaTeX Project’s Tagging Project is specifically designed to produce the structural tags required by PDF/UA-1 (and the upcoming PDF/UA-2). If a user follows the LaTeX Project's current tagging recommendations, they are effectively building a document that is "PDF/UA-ready," which is the strongest way to meet the WCAG 2.1 AA legal mandate required by US and European legislation.
How do I switch my compiler to LuaLaTeX?
It's easy to switch to using LuaLaTeX, the LaTeX compilation engine that is recommended by the LaTeX tagging project team. While the default compiler in Overleaf is PDFLaTeX, you can switch to LuaLaTeX in your project settings.
Where can I select the most recent version of TeX Live?
You can get the latest in Overleaf Labs, which provides access to the "rolling TeX Live" image in Overleaf, including the latest in PDF tagging support. This experimental TeX Live version is primarily for testing changes to TeX Live, packages, and previewing new accessibility features before they’re compiled into our annual TeX Live release.
Most PDF tagging features are available in the standard TeX Live 2025 image.
Last updated
Was this helpful?