search

phetsims / a11y-research

a repository to track PhETs research into accessibility, or "a11y" for short
MIT License
3 stars 0 forks source link

Sliders ignored when navigating from "Form Controls" In VoiceOver Rotor #151

Open zepumph opened 4 years ago

zepumph commented 4 years ago

While working on https://github.com/phetsims/gravity-force-lab/issues/233, I found that, while navigating with "form controls" in the iOS rotor, on refresh the virtual cursor will skip over the first four sliders and go straight to the ruler. I was able to reproduce this with simple HTML like: 

<input type="range"/>
<input type="range"/>
<input type="range"/>
<input type="range"/>
<div role="application"/>
<input type="button"/>
<input type="button"/>
<input type="button"/>

After discussing with @jessegreenberg, we decided to submit a bug to apple and to not look into workarounds. Here is the bug report I submitted:

When navigating in safari on my iPad with VoiceOver turned on, I have found that it is possible for sliders in a page to be ignored by the "Form Controls" rotor selection.

Steps to reproduce:

  • Switch the rotor to "form controls"
  • Navigate to a page with sliders in it, I used the following as a scrap HTML file and it did the trick. In following bullets I will refer to this html scrap for focus order etc. 
    <input type="range"/>
<input type="range"/>
<input type="range"/>
<input type="range"/>
<input type="button"/>
<input type="button"/>
<input type="button"/>
  • Once navigated to it, reload the page (I'm not sure this is absolutely necessary)
  • While on a form control in the navigation bar, re-select the "form controls" rotor selection.
  • swipe down out of the navigation bar form controls. The first highlighted form controls will be a button.
  • Now while on a button in the HTML page, if you re-select "form controls" from the rotor, you will now be able to swipe up to the input ranges above.

I know from many other pages and usages that sliders are expected to be in the form controls selection, so I must assume that this is some sort of bug and not a feature. Thank you ahead of time.

Witnessed on iPad 7th gen 13.2.3