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

Feedback: Change priority of 'unchecked' state assertion from 'should' to 'optional' in plan for Radio Group Example Using aria-activedescendant, V24.03.13 #1141

Open
mcking65 opened this issue Oct 21, 2024 · 0 comments
Labels
AT: VoiceOver for macOS Related to expectations associated with VoiceOver for Mac screen reader testing feedback Issue raised by or for collecting input from people outside the core project team. jaws nvda

Comments

@mcking65
Copy link
Contributor

To be consistent with the toggle button state assertions specified in issue #828, make the assertions related to conveying the 'unchecked' state optional. As discussed extensively in various meetings and other issues, the community group believes it is benefitial for default behavior to be that state is always conveyed for checkbox, toggle, and radio. However, to promote consensus among vendors, it is agreed that is sufficient to always convey the selected, checked, or pressed state.

Test Setup

@mcking65 mcking65 added feedback Issue raised by or for collecting input from people outside the core project team. jaws AT: VoiceOver for macOS Related to expectations associated with VoiceOver for Mac screen reader testing nvda labels Oct 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
AT: VoiceOver for macOS Related to expectations associated with VoiceOver for Mac screen reader testing feedback Issue raised by or for collecting input from people outside the core project team. jaws nvda
Projects
None yet
Development

No branches or pull requests

1 participant