Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Identify elements which support aria-roledescription without an explicit or implicit role #77

Open
joanmarie opened this issue Jul 5, 2017 · 2 comments
Assignees
Labels
Allowed aria-* attributes ARIA 1.2 related Issues directly related to updates in ARIA 1.2

Comments

@joanmarie
Copy link

joanmarie commented Jul 5, 2017

As described in w3c/aria#500, there is a need to prohibit the exposure of the value of aria-roledescription for certain elements (e.g. div and span) when there is no explicit or implicit ARIA role. Alternatively, or in addition, the HTML AAM could explicitly allow the exposure of the value of aria-roledescription on certain elements (e.g. meter used without an explicit role).

(Edited to add note):
The purpose/motivation behind this request is that we want to strongly discourage authors from using aria-roledescription on elements which lack useful semantic meaning, and we want to strongly encourage (and perhaps insist) that user agents do not expose the value of aria-roledescription when it is used on an element which lacks useful semantic meaning and also lacks an implicit or explicit ARIA role. But there's no way we can come up with a host-language-agnostic, universally-agreed-upon definition of "useful semantic meaning" or "generic element." If such elements are explicitly identified in the host-language-specific AAMs and/or related documents, we (ARIA spec and/or Core AAM) should be able to point authors and user agents to those specs to get the implementation and user experience desired and intended for aria-roledescription.

@joanmarie
Copy link
Author

Tweaking the summary. I'm working on draft text for the ARIA spec. The current content is:

User agents MUST expose the aria-roledescription attribute if a valid value is applied to a host language interactive control.

If aria-roledescription is applied to a host language container element, user agents must not expose aria-roledescription unless the author also defines an explicit WAI-ARIA role value, or the host language has explicitly identified the element as supporting aria-roledescription.

(emphasis added)

@joanmarie joanmarie changed the title Identify elements which do not support aria-roledescription Identify elements which support aria-roledescription without an explicit or implicit role Jul 5, 2017
@scottaohara
Copy link
Member

To handle things like this, prohibited use of aria-label/labelledby on necessary elements, and that some of the remaining global aria-* attributes still make no sense on some HTML elements - e.g., <p aria-controls=foo> (what is a paragraph controlling?) - I want to address these with #266

@scottaohara scottaohara added this to the ARIA 1.2 Related milestone May 13, 2021
@scottaohara scottaohara modified the milestones: ARIA 1.2 Related, ARIA in HTML: Next Sep 20, 2021
@scottaohara scottaohara added Allowed aria-* attributes ARIA 1.2 related Issues directly related to updates in ARIA 1.2 labels Sep 20, 2021
@scottaohara scottaohara removed this from the ARIA in HTML: Next milestone Mar 3, 2022
@scottaohara scottaohara added this to the ARIA in HTML 1.1 milestone Mar 13, 2022
@scottaohara scottaohara self-assigned this Mar 13, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Allowed aria-* attributes ARIA 1.2 related Issues directly related to updates in ARIA 1.2
Projects
None yet
Development

No branches or pull requests

2 participants