-
Notifications
You must be signed in to change notification settings - Fork 2
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
Add accessible names to the PDOM? #109
Comments
Maybe phetsims/scenery#1526 (comment) is a good way to proceed here? But I'm not sure how screen reader support works if we have keyboard navigation (which I believe is enabled via turning on interactive description) but no description. |
I'd love to experiment with that, and see if there is an easy solution for this sim. Better than nothing! |
We'll poke around with the automatic solution and see how it goes. |
I'm working on this. |
By the way, we could just pass the actual accessible names manually without automatically discovering them and it would be very easy. |
I think we should move towards a commit point on the tandem-name-only one. Here are some review comments, and let's discuss in person:
Let's keep discussing! |
@AgustinVallejo @samreid @zepumph really like to proceed with 2 things:
|
After talking with @samreid we decided that it's best to manually apply the fields that already have i18n, and automate the rest with tandem. Assigning myself to start on (2) |
Should we add a tag name for scales? Currently they show up in PDOM as NONE |
… tandem name, if it is supplied, see phetsims/buoyancy#109
… tandem name, if it is supplied, see phetsims/buoyancy#109
I added the first occurrence of defaulting the accessibleName based on the tandem, if it is supplied. To begin, I added this for RectangularRadioButton which is a component that doesn't have a pre-existing string in the translation file. Note this also benefited other sims like Faraday's Electromagnetic Lab. Before: After: Heads up to @zepumph and @pixelzoom. |
I checked through density, buoyancy and density-buoyancy and all the a11y views look complete. For this issue, I do not feel we should add more tandem-based automation that will not be exercised in this context. But we have established the convention and made it easy to supplement as we proceed. @AgustinVallejo can this issue be closed? Should we put the remainder of the tandem patch above into a sun issue? |
I think the scale height slider could benefit from this as well, and then this issue can be closed. |
This is done :) Please reopen if you consider there's more work to do here |
…sed on a tandem name, if it is supplied, see phetsims/buoyancy#109" This reverts commit 018120a.
From #76, should we do this? And if so, what should the names be.
The text was updated successfully, but these errors were encountered: