-
Notifications
You must be signed in to change notification settings - Fork 48
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
separator role on button #488
Comments
naw, that seems quite reasonable esp. since it can represent an interactive control that a button could reasonably serve as a base for. |
scottaohara
added a commit
that referenced
this issue
Aug 30, 2023
closes #488 allows role=separator on elements exposed as a button. any other author requirements for appropriately setting that up / ensuring the correct information is communicated would still need to be evaluated, but separate from whether the role is allowed or not.
4 tasks
and boosh. easy PRs are easy. gotta inform the checkers now / get some implementation commitments to acknowledge this change, and then it can be merged if good to go |
1 task
Thanks @stevefaulkner and @scottaohara |
scottaohara
added a commit
that referenced
this issue
Oct 4, 2023
closes #488 allows role=separator on elements exposed as a button. any other author requirements for appropriately setting that up / ensuring the correct information is communicated would still need to be evaluated, but separate from whether the role is allowed or not. * Addition: allow role=separator on button elements * update changelog
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Gerard Cohen asked me why
role=separator
is not allowed on abutton
element. From reading the definition in the aria spec, i don't see a reason not to allow.you wizened souls may think otherwise?
The text was updated successfully, but these errors were encountered: