[pepa65]

Just use typst, way easier to install (single binary) and use (much easier to write directives): https://typst.app

I use the commandline binary, you could use the website as well.

[CJefferson]

typst people on latex posts are like Rust people on C++ posts :) (and I say this as a Rust programmer).

With regards typst, I will consider it when there is any kind of accessible output -- at the moment it only seems to make PDFs, and those PDFs are entirely inaccessible by blind people.

[yjftsjthsd-h]

Because the PDFs only carry an image? (I'm assuming if there was real text the tools could extract it, but could be wrong)

[CJefferson]

PDF to text tools can extract some text, but get confused by tables, maths, etc.

You can annotate a PDF with the raw actual text, which is then used by screen readers, but typst (and LaTeX currently) don't do this. It certainly isn't trivial to do, but it would be useful.

The other option would of course be to produce HTML, which (unless you do horrible things) is generally very accessible, but neither typst or LaTeX do this well (LaTeX does it OK, but I find I usually need to clean up the result).

[uxp8u61q]

PDFs produced by LaTeX aren't accessible either.

[CJefferson]

You are right, but LaTeX has the advantage of having a much bigger user base and documentation, so I'll still with it until Typst has some clear advantages (like accessibility).