Accessible math in PDF: Formula tags, MathML, and testing

Prepare accessible mathematics by choosing the delivery profile, preserving the expression's structure, and testing whether a reader can understand and navigate it. Equations are not ordinary strings with unusual characters. Their layout can encode division, grouping, powers, limits, and relationships that a flattened reading loses. A technically present formula is useful only when its intended meaning remains available.

Begin with the mathematical task

Consider the illustrative expressions '(a + b) / c' and 'a + (b / c)'. A careless spoken or extracted version such as 'a plus b over c' can leave the grouping ambiguous. Ask the author what readers must do: identify a result, follow a derivation, compare terms, or manipulate the expression. That task determines which relationships the review must preserve.

Create an inventory of inline expressions, displayed equations, numbered equations, matrices, and diagrams containing notation. Keep units and definitions with their expressions. A correctly represented variable is still confusing when its definition appears only in a figure that was omitted from the accessible output. Subject-matter review belongs alongside structural review.

Choose the PDF profile before selecting a recipe

The PDF Association's PDF/UA-2 overview identifies the accessibility standard based on PDF 2.0. Its Math in PDF best-practice guide explains the PDF/UA-2 requirement for MathML associated with a Formula element, either through MathML structure elements or an associated MathML XML file. A short alternative description does not replace that profile's mathematical representation requirements.

Do not assume a procedure designed for a PDF/UA-1 export produces a PDF/UA-2 result, or that changing metadata upgrades the content. Record the authoring application, exporter version, chosen PDF version, and validation target. If a publisher requires a particular profile, confirm that requirement before investing in a workflow whose output cannot meet it.

Preserve structure rather than only appearance

W3C MathML Core defines a mathematical markup vocabulary and rendering behavior for the web. Elements can distinguish a fraction, a superscript, or a grouped expression. Its existence does not establish support in every PDF reader; it helps explain why structured mathematics carries more information than an image or an unqualified character sequence.

Use native equation tools or an authoring system that can preserve the required mathematical representation. Keep source notation editable through revisions. If an expression exists only as a screenshot, obtain an authoritative transcription before rebuilding it. An automated transcription should be reviewed for signs, grouping, indices, and omitted terms before it becomes a published alternative.

Add explanations without changing the mathematics

Explain unfamiliar symbols and the purpose of an equation in surrounding prose. For the illustrative fraction, state which quantity is being averaged or normalized and what its units are. This is editorial context, not a substitute for the expression itself. Avoid replacing a detailed equation with a vague description such as 'a formula showing the result'.

A carefully written linear explanation can help readers in environments with limited math support, but it must preserve the intended grouping and remain synchronized with the source. Have a qualified reviewer compare it with the equation. If you also publish HTML with mathematics, validate and test that deliverable separately; an accessible companion requires its own content and interaction review.

Validate and rehearse the reading tasks

1. Compare every expression with the approved mathematical source, including signs, indices, units, and equation numbers.
2. Inspect the exported representation against the selected PDF profile and run an appropriate validator.
3. Test representative simple and complex expressions with the intended viewer and assistive technology.
4. Ask the reviewer to identify mathematical relationships and follow an equation reference, rather than only listening for words.
5. Record unsupported behavior and provide an evaluated alternative where the delivery environment cannot support the required task.

Retain the exact PDF, source revision, tool versions, and findings. Use the LaTeX guide when that is your authoring route and the Unicode guide when symbols extract incorrectly. Do not describe a validator pass as proof that every equation is correctly understood by every reader.

Frequently asked questions

Sources

The statements above rest on the primary sources below. Where a source is a law or standard, the version and date named in the text are the ones checked on the review date. This guide is general information, not legal advice.

1. PDF Association: Best Practice Guide, Math in PDF
2. PDF Association: ISO 14289-2, PDF/UA-2
3. W3C: MathML Core . Mathematical markup; not a claim about PDF viewer support.