On Fri, Jul 24, 2026 at 01:03:45PM +0100, Gavin Smith wrote: > You haven't explained why any of that is important. > > I feel that this discussion is missing important context, such as what an > "accessible" document is, why it is important, and how you would check if > a document is "accessible" or not.
I think that it is the same as accessibility in other context, to generate PDF that people can use even without being able to see, for example. I think that it is a worthy objective in itself, as long as it integrates well with texi2any/Texinfo. Both for alt for images and for the pdftitle (which I interpret as something like settitle), this fits well and seems relevant. > I don't understand why a > problem with texi2any output is being discussed on a LaTeX bug tracker > in the first place, as that would seem not to be the responsibility of > the LaTeX project in the first place. That's because the LaTeX project people generate LaTeX from Texinfo for the asymptote manual, which is in Texinfo and try to have the PDF obtained from this LaTeX be accessible according to some checker. I think that it is interesting feedback, because the people in the tracker can read and understand the LaTeX code generated by texi2any, figure out why the PDF generated from it is not accessible according to the tool they use and give feedback on what should be fixed, texi2any LaTeX output, or LaTex, for instance. Charles forwarded the discussion here with the purprose of having texi2any changed, which looks good to me. -- Pat
