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

Possible confusing language in WAI-ARIA 1.1 Authoring Guide #426

Closed
macgyver opened this issue Aug 25, 2016 · 2 comments
Closed

Possible confusing language in WAI-ARIA 1.1 Authoring Guide #426

macgyver opened this issue Aug 25, 2016 · 2 comments
Assignees

Comments

@macgyver
Copy link

I am implementing a radio button group and I was wondering about the instructions here
https://www.w3.org/TR/wai-aria-practices-1.1/#radiobutton

Specfiically this bit:

Space selects the radio button with focus and de-selects other radio buttons in the group.

Slightly before that, it says that left/right/up/down keys should cycle through the options of a radio group by focusing and selecting them. Can you explain how it is possible to focus a radio option without selecting it, such that the space key would then be necessary to select it?

I hope this is the right place to raise a question like this, please let me know if you know of a better place, thank you!

@mcking65
Copy link
Contributor

@macgyver, you are right; it is confusing. I will fix it.

The only time focus lands on a radio that is not selected is when you move focus inside of a group where none of the buttons are selected. In this case, space would focus the radio that has focus. It would not effect any other buttons. In all other circumstances, when you tab to a radio group, focus should land on the selected radio button.

@mcking65
Copy link
Contributor

Copied this issue to the new aria-practices repo as w3c/aria-practices/#96. Closing it here.

pkra pushed a commit that referenced this issue May 20, 2024
per the changes to HTML AAM - w3c/html-aam#420
closes #426

Firefox and Chromium browsers have been confirmed to expose address with a group role.  Webkit does not appear to have made this change yet, but someone using macOS with VoiceOver would be none the wiser, since it'll still communicate `<address aria-label=foo>` as a 'group' even though it has not been officially mapped as such.

This is marked as an editorial update as the implicit mapping column is a reflection of reality, and the implicit roles are not defined by this specification.
pkra pushed a commit that referenced this issue May 20, 2024
related to #373
i, u, b, small map to generic.  Comments referring to the elements being exposed by their platform specific text styles remain in comments.

bdi/bdo map to generic. Reference writing-mode properties in comments for ia2/atk

`data` and `a no href` map to generic as decided.

also: simplifies br element mapping table
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants