If you want to produce accessible documents from LaTeX, you should convert to HTML. ATs such as screen readers just work miles better than with PDFs, and given the resources put in developing browsers compared to PDF readers, I don't think this will change any time soon. Luckily conversion from LaTeX to HTML is very feasible today, as proved by arXiv. (Shameless plug: I maintain BookML specifically to help lecturers with the LaTeX to HTML work)
Very true! Although they are now comparable, if you rely on the browser native MathML instead of MathJax/LaTeX.
(You can test this on long arXiv HTML papers, e.g. https://ar5iv.labs.arxiv.org/html/1710.07304 is more than 60 pages as PDF. Mind you, the ar5iv default CSS is not great. I would use Latin Modern for formulas, at the very least.)
> I've never seen any modern tools that turn TeX into multifile HTML (one per section).
I believe all of them can do it out of the box now. I know for sure that LaTeXML, tex4ht and lwarp can split by chapter or section.
As you might be aware, the author of the message is David Carlisle, a very active member at TeX (766k rep) and is also a maintainer of many popular packages.
Needless to say, the guide you followed is 8 years old; Perhaps some things have changed.
I have. I don't want to link my HN identity to my SE identity (which is tied to my real world identity through mathoverflow) so I won't link here.
> Needless to say, the guide you followed is 8 years old; Perhaps some things have changed.
As I said, it was updated in February 2024. I was written by Ulrike Fischer who's also very involved in latex3. It's basically the current state of the art in accessible PDFs. And it's still not good enough.
I wish it were otherwise, but latex is the pinnacle of design-by-committee and tech debt. Given how latex3 turned out, I'm very pessimistic. The only thing latex has going for it is inertia.