Live data from Hacker News

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

umij.wordpress.com

71–75 of 75 posts

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

#71
post #70
post #67

Earlier quoted context omitted.

I don't know lisp so maybe there where more nuances in your code, but often your want to analyse an integral in symbolic terms (for whatever integration definition you are using) The expression of the integral operator as a function in code is contrary to that with how people usually think about functions and code. The only language I know that properly manages to represent integrals as code is Wolfram Mathematica by…

Many (if not all?) CAS have some internal tree representation of mathematical structures, Mathematica is not the only one. I worked on such a system myself. To define data types for your expressions and then evaluate them via different algorithms is quite natural. So yes, we also used something like Integral(f, from: a, to: b) and then had like a gazillion techniques to actually evaluate that. Proof assistants do som…

> b) that by not separating the definition of an integral from its evaluation, you're not able to manipulate it directly as an expression or to evaluate it via different methods (e.g. symbolic vs. numerical methods).

I was mostly referring to this. Mathematica is simply my only experience with this kind of approach.

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

#72
post #5

Earlier quoted context omitted.

Standard maths notation is sight first and sight only. If you want maths for the blind you need to convert to something like s-expressions, which emacspeak and read perfectly.

There's a bunch of counter-argument here from working practising blind mathematicians who read and write raw TeX every day, so there's at least a non-zero audience. https://www.nfb.org/latex-what-it-and-why-do-we-need-it-0

Speaking of accessibility for math equations, there is some really good work done in MathJax 3: http://docs.mathjax.org/en/latest/basic/a11y-extensions.html... slides from presentation: https://mathjax.github.io/papers/CSUN19/csun2019_talk.pdf

You can try on any of the demos on this page: https://mathjax.github.io/MathJax-demos-web/ (right click on an equation to enable the accessibility options)

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

#73
The author writes:

"Did I mention that both Word and LibreOffice generate tagged PDFs?"

But then the simple solution is this: Convert your LaTeX to Word or LibreOffice. Then generate the PDF.

Absurdly the easiest way to convert LaTeX to Word/LibreOffice is by creating a PDF first (https://tex.stackexchange.com/questions/111886/how-to-conver...), import that into Word/LibreOffice and then create your PDF/A from that.

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

#74
post #35

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

https://tex.stackexchange.com/questions/498987/generate-pdf-...
Post reply on HN