The sad state of PDF-Accessibility of LaTex Documents (2016)

The thing is: LaTeX might try hard to look like a declarative language for structured documents, but it is not. It is a set of TeX macros. And TeX is a type setting system.<p>There is no good reason to put the accessibility into the type setting. Instead, use a declarative (e.g., any markup) language, translate that a) to (LaTeX) and b) to accessibility annotations and then combine the two results. Problem solved.<p>Unfortunately you will either lose a lot of expressiveness along the way or you have to find a <i>very</i> sophisticated markup language.

An answer, particularly in the sciences, is to also distribute the source *.tex files, which being plain text with markup, can be handled just fine by things like emacspeak, or accessibility tooling for other sensible editors.<p>This comes up a bit around the blind accessibility issue for mathematics, which is why I suspect it&#x27;s bubbling up this week on HN.

Even though LaTeX is still not very close to producing perfectly accessible PDF documents, there is some recent work towards this goal.<p>- <a href="https:&#x2F;&#x2F;ctan.org&#x2F;pkg&#x2F;tagpdf" rel="nofollow">https:&#x2F;&#x2F;ctan.org&#x2F;pkg&#x2F;tagpdf</a><p>- <a href="https:&#x2F;&#x2F;ctan.org&#x2F;pkg&#x2F;accessibility" rel="nofollow">https:&#x2F;&#x2F;ctan.org&#x2F;pkg&#x2F;accessibility</a><p>I am using the former for some personal documents and found that it improves text selection and copying on Apple devices. (This could be related to how PDFKit handles text.)<p>Edit: formatting.

Converting LaTeX to HTML may be a route to making it accessible. I&#x27;m working on this project: <a href="https:&#x2F;&#x2F;github.com&#x2F;arxiv-vanity&#x2F;engrafo" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;arxiv-vanity&#x2F;engrafo</a><p>It&#x27;s 80% of the way there, but with 80% more work it could be a pretty complete implementation.<p>It powers this: <a href="https:&#x2F;&#x2F;www.arxiv-vanity.com&#x2F;" rel="nofollow">https:&#x2F;&#x2F;www.arxiv-vanity.com&#x2F;</a>

If you want accessibility, it would be better to convert your content to XML and run the LaTeX through MathJax first, using accessibility extensions (<a href="https:&#x2F;&#x2F;mathjax.github.io&#x2F;MathJax-a11y&#x2F;docs&#x2F;" rel="nofollow">https:&#x2F;&#x2F;mathjax.github.io&#x2F;MathJax-a11y&#x2F;docs&#x2F;</a>). Then use a third-party converter such as PrinceXML to generate the PDF from the XML.

One pattern I like to use is to write my documents using markdown which can be compiled into pdf via latex with a template of my choosing. It is also capable of compiling to other formats which may be more accessible such as plain text, html and docx.<p><a href="https:&#x2F;&#x2F;pandoc.org&#x2F;" rel="nofollow">https:&#x2F;&#x2F;pandoc.org&#x2F;</a><p>[edit to add link to pandoc]

The &quot;accessibility&quot; LaTeX package maintainer is looking for help in this area: <a href="https:&#x2F;&#x2F;github.com&#x2F;AndyClifton&#x2F;accessibility&#x2F;issues&#x2F;42" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;AndyClifton&#x2F;accessibility&#x2F;issues&#x2F;42</a>

Ross Moore did a presentation about accessibility and PDF at the 2020 TUG online conference.<p><a href="https:&#x2F;&#x2F;youtu.be&#x2F;VF9Ubax_HIY" rel="nofollow">https:&#x2F;&#x2F;youtu.be&#x2F;VF9Ubax_HIY</a>

The author writes:<p>&quot;Did I mention that both Word and LibreOffice generate tagged PDFs?&quot;<p>But then the simple solution is this: Convert your LaTeX to Word or LibreOffice. Then generate the PDF.<p>Absurdly the easiest way to convert LaTeX to Word&#x2F;LibreOffice is by creating a PDF first (<a href="https:&#x2F;&#x2F;tex.stackexchange.com&#x2F;questions&#x2F;111886&#x2F;how-to-convert-a-scientific-manuscript-from-latex-to-word-using-pandoc" rel="nofollow">https:&#x2F;&#x2F;tex.stackexchange.com&#x2F;questions&#x2F;111886&#x2F;how-to-conver...</a>), import that into Word&#x2F;LibreOffice and then create your PDF&#x2F;A from that.

Why must the PDF encapsulate all requirements? My understanding of accessibility requirements it that you must have <i>a</i> version that is amenable to automatic speech, not that all versions must be.

1. Needs (2016) in the title.<p>2. Even by 2016, pdfTeX had been largely superseded by LuaTeX.<p>3. The author bizzarely links to &quot;the mess&quot; of the literate source of TeX the program as a WEB file rather than as a typeset document.<p>4. AIUI, the source code of the TeX engine has nothing&#x2F;very little to do with adding tags to PDFs, which it is the job for LaTeX packages. Admittedly, understanding and writing their source code is a rarer skill than reading the literate source of TeX.

<a href="https:&#x2F;&#x2F;tex.stackexchange.com&#x2F;questions&#x2F;498987&#x2F;generate-pdf-a-1b-with-lualatex" rel="nofollow">https:&#x2F;&#x2F;tex.stackexchange.com&#x2F;questions&#x2F;498987&#x2F;generate-pdf-...</a>

I can&#x27;t believe MathML just died and it&#x27;s like not even part of the conversation about the history of math markup.

&gt;Take your average computer science graduate from the last ten years. Do you think anyone would be remotely able to understand what is going on there?<p>Yes, you literally read the literate program of TeX and understand what&#x27;s going on: <a href="http:&#x2F;&#x2F;brokestream.com&#x2F;tex.pdf" rel="nofollow">http:&#x2F;&#x2F;brokestream.com&#x2F;tex.pdf</a><p>I had never learned Pascal but I&#x27;ve managed to edit and compile TeX successfully, and it was easier than trying to understand any of my own non-literate programs.<p>&gt;My point being that if we wouldn’t rely on TeX itself and use ANT (or whatever alternative) which is written in the quite elegant OCaml, than hacking it would be at least possible for mere mortals. Although I have to admit, despite being in love with OCaml since my PhD days, it’s also a quite niche language. But imagine if the whole thing was written in Python, or at least C.<p>Imagine if software engineers were actual engineers instead of glorified script kiddies.<p>&gt;I wish someone would design a new space shuttle because while it&#x27;s a neat project I only understand MKS units and it&#x27;s too much effort to use a calculator for converting between them and Imperial units.

Imagine how much further ahead HTML&#x2F;CSS would have been if the academic crowd abandoned latex 20 years ago.<p>Revisit this comment in 5 years.

I had a realization a while back, that in my opinion LaTeX isnt really needed anymore. Pretty much anything you can do with LaTeX, you can do with HTML. Want a PDF? Most browsers will print to PDF now, or you can use a library like this:<p><a href="https:&#x2F;&#x2F;github.com&#x2F;dompdf&#x2F;dompdf" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;dompdf&#x2F;dompdf</a><p>Need a page break? Here you go:<p><a href="https:&#x2F;&#x2F;developer.mozilla.org&#x2F;Web&#x2F;CSS&#x2F;break-after" rel="nofollow">https:&#x2F;&#x2F;developer.mozilla.org&#x2F;Web&#x2F;CSS&#x2F;break-after</a><p>Im not sure what you would do about TikZ and stuff like this, but I have seen some pretty wild stuff in CSS, so surely its possible:<p><a href="https:&#x2F;&#x2F;pattle.github.io&#x2F;simpsons-in-css" rel="nofollow">https:&#x2F;&#x2F;pattle.github.io&#x2F;simpsons-in-css</a>