Why does role=none|presentation only prohibit aria-label and aria-labelledby

[pkra]

Currently, role=none only prohibits the use of aria-label and aria-labelledby. I was wondering if other states and properties should not also be prohibited.

My starting point for this was aria-roledescription which seemed particularly odd to me. But then really all of them seemed odd. Of course I can see them being important if presentational conflict resolution, but in that situation wouldn't aria-label and aria-labelledby be equally useful?

I'm probably just missing a distinction. I'd be grateful for a clarifying comment.

[scottaohara]

i remember mumbling about this at one point. If i recall correctly, it wasn't really considered something to worry about since if a none/presentation element gets a global ARIA attribute, the presentational role is dropped in favor of the implicit or fallback role.

If an element has global WAI-ARIA states or properties, user agents MUST ignore the presentation role and expose the element with its implicit role. However, if an element has only non-global, role-specific WAI-ARIA states or properties, the element MUST NOT be exposed unless the presentational role is inherited and an explicit non-presentational role is applied.

though i (still) agree. it is a bit silly/confusing to say that naming them is prohibited, but all other global attributes are allowed/inherited... but also, if those attributes are used it negates the presentational role anyway... so in a very round about way, they're prohibited without saying as much.

[pkra]

Thanks, Scott. Perhaps the group can decide if we should add some clarifying language (though it seems hard to clarify by adding more information 😞 ).

[spectranaut]

In the meeting today, we discussed being ok with prohibited all attributes, as Scott mentioned, attributes are already sort of "prohibited" in a round about way. But we would have to edit the script that generates the tables. Maybe a topic for the editors meeting, @pkra ?