-
Notifications
You must be signed in to change notification settings - Fork 127
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
Radio Group should not have accessible name required: true #427
Comments
If ARIA 1.2 is still limited to HTML Role Parity, this issue is not in scope. |
This is another change that is nearly editorial except for the fact that it has authoring impacts. Changing this would not slow 1.2. |
I'm having a hard time thinking of a good example where a radio group is better without a name. If someone comes up with one please add it and we will progress this bug - but until that time I'm going to park this with needsinfo. |
per the current spec, it would be required to add a name. but the names of the radio groups make it pretty clear what the intent of the group is asking one to decide. |
Discussed on today's editors meeting https://www.w3.org/2024/04/15-aria-editors-minutes.html#t01 |
Closing in favor of #2180 |
While most radio groups do need an accessible name, there are some instances where the radio buttons themselves sufficiently describe their operation without requiring an accessible name on the radio group itself.
HTML native radio groups do not require an associated fieldset/legend surrounding them so why should aria ones have this additional restriction.
The text was updated successfully, but these errors were encountered: