Am Thu, 20 Jun 2024 17:33:56 +0200 schrieb Pablo Rodriguez via ntg-context:
\setuptagging[state=start] is the culprit. "link" is the word displayed when links are hovered over.
well it would imho be better not to use that at all. Sorry but what context is doing here is cheating. It claims to add a structure (and probably manage to pass automated tests) but all StructElem with the exception of links are role mapped to NonStruct and so are non functional. Links miss the OBJR reference. Annotations only all have as /Content a generic text (link) (which creates your hover effect). When I let Adobe+NVDA read a PDF tagged with LaTeX it recognize and announces structures: heading level 2 A section text table with 2 rows and 2 columns row 1 column 1 header A column 2 header B row 2 header A column 1 data A header B column 2 data B out of table link https://www.example.com I can navigate from one heading to the next and inside tables (and when I hover a link the pop up is correct as we are setting the right Contents value.) If you do the same with a document tagged with context you only get a large blob of text A section textHeader AHeader B data Adata B https://contextgarden.net and no navigation at all. All the tagging in the file is useless, it even actually harms because it makes user believe they get an accessible PDF. Tagged, accessible PDF has a lot of shortcomings, especially when it comes to complex documents and math, but for standard documents it can do much better then what context is making out of it. -- Ulrike Fischer http://www.troubleshooting-tex.de/