Closed terracoda closed 1 year ago
@Nancy-Salpepi brought this issue to our attention while testing Ratio and Proportion.
linking to https://github.com/phetsims/qa/issues/863
Suggested solution is to draft a paragraph for the PDOM that succinctly captures that
Draft 1:
@emily-phet and I discussed this issue today, and we feel that it isn't worth time delaying publication for Ratio and Proportion. Here is what the a11y view currently looks like:
The localization tab and heading are described, just not the buttons. Though it is incomplete, its blankness does convey a lack of support from a non-visual perspective.
We recommend deferring this issue and continuing with publication. We also do not recommend taking the locale panel out of the sim, as it is a nice improvement that has been tested and implemented since the summer.
Sorry, I labelled thinking this issue was in RAP, not in common code, carry on for the next sim!
@zepumph and @emily-phet, I completely respect your decision to not include a paragraph in the Localization Tab Panel for RaP. The lack of language names on the buttons does make it pretty impossible to make a meaningful change to the language while using screen reader software. Hopefully, screen readers won't try to change the language than get themselves in a pickle.
Maybe the paragraph should warn that changing the local language will not affect the described experience, and inform that it only changes the text that is visually on the screen.
Draft 2:
Draft 3:
Draft 4:
Draft 5:
How do folks feel about Draft 5? Short, succinct and not using negative wording like "only". There is no need to down play what these features actually provide.
Tagging @kathy-phet, @emily-phet , @Nancy-Salpepi, @zepumph, @jessegreenberg, @Matthew-Moore240.
I like Draft 5.
I also like the wording in Draft 5.
Ok, great! 2 votes seems good to me. I am assigning to @jessegreenberg for implementation. @jessegreenberg, please re-assign to appropriate dev if you are not that person.
Implementation of this is happening over in #930 (a duplicate, but more recent issue), so I will copy draft 5 over to that issue and close this one.
For the Voicing feature we have a response that communicated that Voicing is turned off if the language gets switched to anything other than English.
For screen reader users, we are considering the case where they will be able to find the Localization Tab, but then we need to let them know that Localization is limited to on-screen text and that the Interactive Description feature, if available, is only available in English.