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

Clarification: update definition of 'any role' #358

Open
scottaohara opened this issue Oct 3, 2021 · 1 comment
Open

Clarification: update definition of 'any role' #358

scottaohara opened this issue Oct 3, 2021 · 1 comment
Assignees
Labels
Clarification needed Revise or expand the information provided Spec chore Updates to the spec that will result in no normative or informative changes

Comments

@scottaohara
Copy link
Member

The current definition of 'any role' states:

...Any role it indicates that any role value apart from the implicit ARIA semantics role value, MAY be used.

this definition should be updated to indicate that this is not a carte blanche invitation to truly add 'any role' to an element.

For instance, we should make mention of the fact that any specified role must also follow the rules of use as outlined in the ARIA specification. e.g., <i role=gridcell> is valid per <i> allowing 'any role', BUT it would be invalid to add this role to an<i> if that element were not owned by a role=row, which that would then need to be owned by a role=grid.

@scottaohara scottaohara added Clarification needed Revise or expand the information provided Spec chore Updates to the spec that will result in no normative or informative changes labels Oct 3, 2021
@scottaohara scottaohara added this to the ARIA in HTML: Next milestone Oct 3, 2021
@patrickhlauke patrickhlauke self-assigned this Oct 5, 2021
@scottaohara
Copy link
Member Author

note that #391 has added some updates to the paragraph that initially describes 'any role'.

scottaohara added a commit that referenced this issue Nov 4, 2022
related to validator/validator#1425 and #436

cc @stevefaulkner @sideshowbarker 

as per my comment in #436, here is part of the update I had planned to do to help address this.  

it is also related to #358, but does NOT close that issue completely.

I'm leaving in place the updates that Mike made in the merged PR, but likely will need to revise that column later on as well, so those specific call outs may be moved or changed in the future.

Any further changes we would like to see to this text to help here?
pkra pushed a commit to w3c/aria that referenced this issue May 20, 2024
related to validator/validator#1425 and w3c/html-aria#436

cc @stevefaulkner @sideshowbarker 

as per my comment in #436, here is part of the update I had planned to do to help address this.  

it is also related to w3c/html-aria#358, but does NOT close that issue completely.

I'm leaving in place the updates that Mike made in the merged PR, but likely will need to revise that column later on as well, so those specific call outs may be moved or changed in the future.

Any further changes we would like to see to this text to help here?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Clarification needed Revise or expand the information provided Spec chore Updates to the spec that will result in no normative or informative changes
Projects
None yet
Development

No branches or pull requests

2 participants