Consider prohibiting accessible name for listitem, rowgroup, term, time #1117
Description
See w3c/aria-practices#1231 , the following roles are categorized as "Do Not Name" in APG:
| role | Necessity of Naming | Guidance |
|---|---|---|
| listitem | Do Not Name | Naming is not supported by assistive technologies; it is necessary to include relevant content within the list item. |
| rowgroup | Do Not Name | Naming is not supported by assistive technologies. |
| term | Do Not Name | Since a term is usually the name for the role="definition" element, it could be confusing if the term itself also has a name. |
| time | Do Not Name | Naming is not supported by assistive technologies. |
Although the rationale provided for several of these is that naming isn't supported by ATs, it's not clear if they should be supported.
For time in particular, I think it's in the same situation as paragraph, where naming is prohibited.
I'm not sure if naming a
timeis ever useful. Atime, from what I understand, isn't typically focusable, but is more like a normal word within a paragraph. To understand the context, you'd read the full paragraph.
w3c/aria-practices#1231 (comment)
I think listitem is like paragraph. It can have a marker like a bullet or a number, but that's not an accessible name. Are there reasons to name list items that are somehow different from paragraphs?
For rowgroup I could imagine it being theoretically helpful to have a name if you navigate between rowgroups in a table or grid, but I'm not sure how ATs can navigate these structures.
term seems like time, it's usually a word or a phrase within a paragraph.