What is the relationship between accessibility features and package management?

[Paul744]

Firstly, I note that I am not a package developer, so I don’t pretend to know how complex integrating accessibility into packages is. With that in mind, I can’t find any information in the accessibility documentation on how the core features interact with packages, with the main feature I am thinking of being alt text. Thus, I am unclear on if there is any risk with using unmaintained packages and having them fail to meet PDF UA/1 compliance. I know some Typst packages come with minimum Typst version information, but so far, only a small number of the ones I’ve sampled have 0.14 as the minimum version.

If someone could clarify how accessibility features interact with packages, I would appreciate it.

[Y.D.X]

Could you give a specific example of the concerned packages?

The answer depends on the category of the package.

• Scripting packages like digestify – Typst Universe are irrelevant to accessibility.
• Numbering packages like headcount – Typst Universe are basically show/set rules. If the package is not too hacky, it should not affect accessibility.
• Plot packages like lilaq – Typst Universe themselves are usually not quite accessible, but it would fine if you put plots in #figure(…, alt: "…", caption: […]).
• …

[Paul744]

I didn’t have any particular package in mind, though the notable example I consistently use is Fletcher, which hasn’t been updated in a while and still has a minimum Typst version of 0.13.

This was more me asking ahead in case I need to touch an unmaintained package. I wanted to get an understanding of which ones are likely to fall behind in terms of accessibility if left alone.