A similar topic came up when we had been discussing hgroup and what that could map to (just a group right now), but in working on other updates to the HTML AAM spec today, I thought I'd check the temperature of the working group for roles like these. Especially since the header and footer elements are only exposed as landmarks under certain conditions, and the rest of the time these "semantic" HTML elements are no different than div elements.
Could it not be potentially beneficial to allow AT to expose something beyond a generic or group role for these elements, even if we put a stipulation that the role only be overtly exposed to the user if provided an accessible name?
Note that there are potentially similar existing roles with dpub doc-pageheader and doc-pagefooter
Edit: I should have mentioned that I am aware this is retreading an older issue - #963 - but as that was closed in 2019 before the generic concept was implemented, and now we're also working on defining minimum role to combat generics not being useful, again, maybe we should think about if we should start thinking about rethinking this maybe?
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.3