Closed KatieWoe closed 1 year ago
I have not yet been able to reproduce this. At first I thought it may be another case of a Property leaking into a PDOM attribute value, but I manually passed a Property and it didn't care at all.
@KatieWoe can you please try to reproduce in the debug version, or on master. I would like to see if there are any assertions when it happens. If there are not, and it continues to be hard to reproduce, then I believe it may just be an NVDA quirk, and a challenge to make more progress on. Thanks!
It happens both on master and in the debug version, and I did not see any errors. Let me know if you want to pair on this.
Here's a video of the bug:
Thanks. That is great. I can easily reproduce in firefox and I cannot get this in chrome.
I wondered if it was because of the hair spaces we put after repeating aria-valuetext in AccessibleValueHandler, but removing those did nothing.
I also found https://stackoverflow.com/questions/20386266/how-to-prevent-jaws-from-saying-invalid-entry-on-required-fields which made it seem like it was because of required form fields, but that doesn't apply to us and our code has no required
attributes.
Aha! looks like this is the culprit
Firefox+NVDA didn't like that the slider step didn't evenly go into the min and max. I could adjust this by decreasing the threshold constant by EPSILON so that the range matches the step.
Done and ready for confirmation in next version. ( I only cherry picked https://github.com/phetsims/ratio-and-proportion/commit/8641054fcb219d0ecddc36258c74ca7e5ce6ca25)
Looks fixed in rc.2
Test device Dell Operating System Win 11 Browser Firefox + NVDA Problem description For https://github.com/phetsims/qa/issues/852 When NVDA reads out the slider for the hand, it may say that the slider is invalid. I've only seen this so far when the ratio is locked on the second screen.
Troubleshooting information: