Hello ConTeXt friends, I am newly exploring ConTeXt in search of a better way to produce PDF/UA-1 accessible and PDF/A compliant documents programmatically. From my early experiments, ConTeXt docs appear to fully satisfy the veraPDF validator, but Adobe Acrobat’s Accessibility Checker has three qualms with ConTeXt-produced documents: 1. The document is configured to display the file name rather than the title in the top of the window (DisplayDocTitle == True is what I think is required). See here https://www.w3.org/TR/WCAG20-TECHS/PDF18.html. 2. "Tagged Annotations" fails, suggesting that the document’s links are not properly tagged. I believe the issue is missing "Link - OBJR” (object reference) tags. See here https://amp.levelaccess.net/public/standards/view_best_practice.php?violatio..., here https://www.w3.org/TR/WCAG20-TECHS/PDF11.html, and here http://verapdf.org. 3. "Tab Order" fails, I believe because ConTeXt does not specify that the tab order should follow the Document Structure, so Acrobat reads it as unspecified. See here https://www.w3.org/TR/WCAG20-TECHS/PDF3.html. Is there something I could be doing to correct these issues in my ConTeXt documents? Or is this a change that would have to be made within ConTeXt itself? I know that Adobe is not the definitive arbiter of what an “accessible” PDF looks like, but for many organizations, passing the Acrobat accessibility checker is a prerequisite, so it seems worthwhile to me to make ConTeXt capable of it. Many thanks! Connor Jackson