The IndexTagged PDF

Tagged PDF

A LaTeX project in. A tagged PDF out: headings, lists, tables and figures a screen reader can move through, and every formula real mathematics, spoken aloud and copied out as text.

Open now

A project in, a tagged PDF out A zipped LaTeX project goes in. A PDF comes back, and inside it a tree of tags: the document, a heading, a paragraph, a formula that reads one half m v squared, and a figure that still needs a description. YOU SEND lecture-04.zip BACK Document H1Lecture 4: Energy PThe kinetic energy is Formulaone half m v squared Figureneeds a description
The structure a screen reader walks. Where only a person can finish the work, such as describing a figure, the report names the place.

What it is for

  • Course materials that must meet WCAG 2.1 AA, made from the LaTeX they were written in rather than patched afterwards.
  • A publishing workflow that already builds PDFs from LaTeX and needs them tagged, without anyone fixing tags by hand.
  • An agent preparing documents for people who listen to them.

What we measured

In our last measured run of real course documents, 80 of the 86 that built passed veraPDF's PDF/UA-2 check as they were delivered, and 234,545 of 235,724 formulas became real mathematics with a spoken form. Each PDF carries, inside it, a short statement in plain words of what was checked and what was not.

Price

Six cents a page. With the web page, the report and an archival copy, in one request, all of it costs ten cents a page. A document that cannot be built costs nothing.

Documentation

POST https://api.intex.institute/v1/pdf

The same request as every project service: your key in the Authorization header, and the project as a form upload in project, with main when the archive holds more than one main file. The details are in the docs.

The response

The PDF itself, as application/pdf, with two headers:

HeaderWhat it holds
Intex-PagesThe pages billed.
Intex-Cost-CentsWhat this request cost, in cents.

A project that cannot be built comes back as status 422, with the reason in a sentence and its place in your source, so you can fix it and send it again.

An example

curl https://api.intex.institute/v1/pdf \
     -H "Authorization: Bearer $INTEX_KEY" \
     -F project=@lecture-04.zip \
     -o lecture-04.pdf

Related