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

Localization - How to inform screen reader users that localization is limited to on-screen text #893

Closed
terracoda opened this issue Dec 12, 2022 · 13 comments
Assignees

Comments

@terracoda
Copy link
Contributor

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.

@terracoda
Copy link
Contributor Author

@Nancy-Salpepi brought this issue to our attention while testing Ratio and Proportion.

@Nancy-Salpepi
Copy link

linking to phetsims/qa#863

@terracoda
Copy link
Contributor Author

terracoda commented Dec 12, 2022

Suggested solution is to draft a paragraph for the PDOM that succinctly captures that

  • localization is for on-screen text only
  • for sims with interactive description, the designed description are only available English.

@terracoda
Copy link
Contributor Author

Draft 1:

  • Interactive description feature is only available in English at this time. Localization available for on-screen text only.

@zepumph
Copy link
Member

zepumph commented Dec 14, 2022

@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:

image

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.

@zepumph
Copy link
Member

zepumph commented Dec 14, 2022

Sorry, I labelled thinking this issue was in RAP, not in common code, carry on for the next sim!

@terracoda
Copy link
Contributor Author

@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.

@terracoda
Copy link
Contributor Author

terracoda commented Dec 14, 2022

Draft 2:

  • Localized language translation only available for visually displayed text. The fully described interactive experience is only available in English.

Draft 3:

  • Localized language translations are only available for visually displayed text. For simulations with Interactive Description or Voicing, the described experience is available only in English.

Draft 4:

  • Localization is only available for visually displayed text. The Interactive Description or Voicing features are in English only.

Draft 5:

  • Localization is for visually displayed text. Interactive Description and Voicing features, when available, are in English.

@terracoda
Copy link
Contributor Author

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.

@terracoda terracoda assigned kathy-phet and unassigned terracoda Dec 14, 2022
@kathy-phet
Copy link

I like Draft 5.

@kathy-phet kathy-phet removed their assignment Dec 14, 2022
@Nancy-Salpepi
Copy link

I also like the wording in Draft 5.

@terracoda
Copy link
Contributor Author

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.

@terracoda terracoda changed the title Localization - How to inform screen reader users thatlocalization is limited to on-screen text Localization - How to inform screen reader users that localization is limited to on-screen text Jun 15, 2023
@terracoda
Copy link
Contributor Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants