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

Screen Reader says "10 Billion" as "one zero billion" #301

Closed
Tracked by #729
stemilymill opened this issue Sep 1, 2021 · 10 comments
Closed
Tracked by #729

Screen Reader says "10 Billion" as "one zero billion" #301

stemilymill opened this issue Sep 1, 2021 · 10 comments

Comments

@stemilymill
Copy link

For phetsims/qa#702

Test device : Dell laptop
Browser/screen reader combos: Firefox & NVDA, Chrome and JAWS

When using the Change Mass spinner, if the mass is set to 10 billion kg, the screen reader says "one zero billion kilograms" instead of "ten billion kilograms."

This did not happen in the published version.

(I'm still learning terminology, please correct me so I can improve)

@jessegreenberg
Copy link
Contributor

Thanks @stemilymill. Normally I would say this kind of screen reader output is out of our control but since it isn't happening in the published version maybe something has changed. Ill try to get it to happen myself and then look for anything that might have changed in the formatting of the value.

@jessegreenberg
Copy link
Contributor

Confirmed with NVDA + Firefox.

@jessegreenberg
Copy link
Contributor

@terracoda said that maybe in the published version we were spelling out numbers like "ten". Ill check into that. If we cannot find why this is happening or if something changed in the formatting @terracoda and @emily-phet suggested we could spell out the numbers.

@zepumph
Copy link
Member

zepumph commented Sep 8, 2021

I confirmed in https://phet-dev.colorado.edu/html/gravity-force-lab-basics/1.0.3/phet/gravity-force-lab-basics_a11y_view.html that the published version is using real numbers, not words:

image

There are the two items copied from each sim:

<!--On master:-->
<input data-trail-id="388-389-563-570-565-734-735-709-706-705-691" id="388-389-563-570-565-734-735-709-706-705-691"
       data-focusable="true" class="a11y-pdom-element" type="range" aria-orientation="vertical"
       aria-valuetext="2 billion kilograms" min="1" max="10" step="1" aria-valuenow="2"
       aria-roledescription="number spinner">


<!--Published version:-->
<input data-trail-id="378-465-469-640-641-619-618-617-603" id="378-465-469-640-641-619-618-617-603"
       data-focusable="true" class="a11y-sibling" type="range" aria-orientation="vertical"
       aria-valuetext="3 billion kilograms" min="1000000000" max="10000000000" step="90000000"
       aria-valuenow="3000000000" aria-roledescription="number spinner">

@jessegreenberg
Copy link
Contributor

Thanks @zepumph, thats helpful! I just confirmed that published version does not have this bug. The biggest difference I see is the min, max, and step attributes though I am not sure why that would cause this. Ill try to isolate in an example HTML case.

@jessegreenberg
Copy link
Contributor

I verified that this is happening in the RC. I verified that this is NOT happening in the last published version. I have not been able to find a way to reproduce this in a basic HTML example. I tried adding attributes up to the slider that is in master. Then I tried copying the exact HTML in the PDOM into a different HTML page and didnt' see this happen.

More surprising is that I just notice this is NOT happening in the unbuilt version off of master.

@jessegreenberg
Copy link
Contributor

jessegreenberg commented Sep 15, 2021

One difference I see between unbuilt and built is that in the built version there are directional embedding marks:
image

The embedding marks are on the aria-valuetext and the aria-roledescription. These are set with setAttributeToElement of PDOMPeer, I wonder if stripEmbeddingMarks should be used there.

@jessegreenberg
Copy link
Contributor

I just confirmed that removing the directional marks fixes this issue.

@jessegreenberg
Copy link
Contributor

Resolved in the above commit. This has been cherry picked into the scenery gravity-force-lab-basics-1.1 release branch for GFL:B.

@KatieWoe
Copy link
Contributor

KatieWoe commented Nov 2, 2021

Looks ok on Win 11

@KatieWoe KatieWoe closed this as completed Nov 2, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants