On Thu, Jul 23, 2026 at 11:07:25AM -0600, Charles Staats wrote: > Hello, > > Currently, `texi2any --latex` appears to discard any alt text tag, see > https://github.com/latex3/tagging-project/issues/1491#issuecomment-5061006949. > Would it be possible to change this? > > Ideally, there would be some sort of flag like `--accessible` or > `--latex-tagging` that could be passed to the texi2any script that would > cause certain changes to the TeX and pdf output, such as the following:
I do not think that a command-line should be used for that. Maybe a customization variable. > * Forward any alt text to the `\includegraphics` commands. This seems to be relevant independently of the remaining. However, it looks like it was added in 2021, according to https://ctan.tetaneutral.net/macros/latex/required/graphics/grfguide.pdf What happends if graphicx is older with an unknown alt= passed? > * Insert a `\DocumentMetadata` command (with appropriate settings) at the > beginning of the document. Which LaTeX version support \DocumentMetadata? What happens if the version used does not? In case it is possible to use \DocumentMetadata, which should be the format of the lang? Some examples on the internet look like BCP 47, but it is not so clear. > * (For pdf output) compile with lualatex instead of pdflatex. texi2any does not compile the LaTeX file, just produces it. > * Ideally, we would also have "actual" and "artifact" tags as well. If I > understand correctly, the "actual=<stuff>" tag indicates to screenreaders > that the image should be treated as if it were the text "<stuff>"; It seems to be actualtext=, not actual=. We could use a file like image.txt that we use in Info output, for example for that. It is not clear, however, how to specify it. Is it an issue if there are end of line in it? Blank lines? The manual does not show any example. Also it seems to be quite recent, end of 2024, similarly, what happens with older graphicx with an unknown actualtext= passed? > the > "artifact" tag tells the screenreader to ignore the image altogether (used, > e.g., for logos). Not sure that there is a use in Texinfo to LaTeX conversion. > There may be other changes needed, as discussed in the issue linked above. > (Note: Some of these may be better dealt with on the TeX side rather than > the texinfo side.) I think that \hypersetup{pdftitle={}} could be added. It looks like a relevant addition in the default case. It is not clear to me why style=nextline is incompatible with tagging. Is it really important, or should it be fixed someday? The noparboxtagging stuff seems obscure to me, but I can add it if there is some explanation, and also it is not clear to me if \AssignTaggingSocketPlug and \tagpdfparaOff are backward compatible enough. Regarding \usepackage{unicode-math}, I do not have a clear idea whether it is a good idea to use that instead of amsmath. It seems that the \mathbf and similar commands should be changed, but it is not so clear either. Also it seems to require some specific fonts. Maybe there could be some customization option to generate LaTeX for an engine or the other. -- Pat
