scottaohara
commented
3 months ago as mentioned during triage - this is a symptom of a larger problem, that there is an assumption that if roles are not identified as "allowed" or "required" by the ARIA spec - that therefore anything else must be invalid. And this is an example of that over simplification.
So, what we really need to think about is do we need to define content models for the different roles (similar to HTML element's content models). Or do we need to identify specifical "not allowed" roles/elements for specific roles - where if a role is not listed, then it should be considered "allowed".
or: [ insert other idea(s) here ]
MarioBatusic
spectranaut
pkra
Description of bug or feature request
I've run into a use case where headings are used to break up sections of multiple articles within a feed. These are not article-specific headings (which should be within the article node); in my case, the headings have date/time text that group multiple articles below them.
My specific use case is a chat feed with timestamps that group several messages. Another more traditional use case could be a blog feed with headings per month or year.
I haven't run into any practical issues with this semantic structure -- keyboard focus doesn't land on the headings, and no one has complained about them in user testing yet.