bokand
commented
4 months ago The browser automatically adds nodes in the accessibility tree if there is a navigation style rule
This is what I was thinking - create a "fake" (in the sense that there's no matching DOM node) Ax node with an Aria command or link role, but as you say, there's no box there. I wonder how this works on Android for gestural navigations? Will need to run this by accessibility experts.
We need to ensure that navigations tied to gestures are also visible in the accessibility tree. If the action is specified completely in CSS, that won't be the case. There's a couple of options we can consider:
The browser automatically adds nodes in the accessibility tree if there is a navigation style rule. Not sure what the location for those nodes should be or if there is precedent for UA inserted accessibility nodes which don't have a corresponding box.
The navigation rule only applies if there is a link (a tag?) for that URL in the DOM. The author can choose to make that element visually hidden but accessible. This also helps for cases where CSS is not available. But it feels too limiting since maybe the author has a click handler which triggers the navigation in script.