-
Notifications
You must be signed in to change notification settings - Fork 4
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
(Voicing) How to voice disabled controls? #396
Labels
Comments
We will try to resolve the Voicing of disabled controls in phetsims/scenery#1220 Hopefully, we won't need the reading block work around. |
terracoda
changed the title
(Voicing) Disabled Controls - Would reading blocks make sense?
(Voicing) How to voice disabled controls?
Sep 29, 2021
terracoda
added
priority:5-deferred
status:on-hold
and removed
design:a11y
meeting:a11y-team
priority:5-deferred
labels
Sep 29, 2021
Marking as on hold as work is done in phetsims/scenery#1220 |
See phetsims/scenery#1220 (comment), this isn't going to be dealt with soon, and likely not for RAP's publication this year. Marking deferred. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In Ratio and Proportion and in many other simulations there is a need sometimes to disable access to an interactive control.
There are standard methods using HTML and ARIA to communicate a control is disabled. These methods are implemented through the use of the PDOM. In Voicing design and implementation not all inputs have access to the PDOM.
For example, mouse and touch input events do not go through the PDOM whereas keyboard and focus-based gestures do.
In the Voicing API, we have the ability to make on-screen text voice-able or readable through what we call "reading blocks".
I am wondering if reading blocks might be a viable option for making disabled controls and their disabled state voice-able?
I am adding meeting label for this question.
The text was updated successfully, but these errors were encountered: