WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Need for Increment Buttons?

for

From: Jonathan Cohn
Date: Dec 14, 2018 8:46AM

I guess this might also be why volume sliders in some native IOS applications don't really work. I remember encountering one specific app where VoiceOver indicated that I had adjusted the value of the slider, but then there was no effect on the resulting audio.
I guess a slider is not just a hidden numeric input field with aria used to set min, max, and adjust by values? Because then the SR could just change the value of the input field.

Best Wishes,

Jonathan Cohn

> On Dec 14, 2018, at 9:48 AM, Patrick H. Lauke < <EMAIL REMOVED> > wrote:
>
> On 14/12/2018 14:15, Brandon Keith Biggs wrote:
>
>> Wow, you're right, why doesn't either the slider or input number box adjust
>> the value with swipe up and down, it should.
>
> The role="slider" exposes it as if it were a real slider (i.e. an <input type="range">) - which triggers VoiceOver/Talkback to give their usual hints (use swipe/use volume keys). However, as it's not a real actual slider, performing those actions by themselves has no effect. From JavaScript, you can't detect volume key presses on Android. And while you can detect touchscreen events (and therefore swipes), when AT is running those gestures are consumed directly by the AT and not passed to the page/JavaScript (unless you use a passthrough gesture like double-tap-and-hold).
>
> This sort of thing was mentioned/documented a while ago in https://www.w3.org/TR/using-aria/#aria-touch
>
> This is one of the scenarios that is hoped will be improved once we have the Accessibility Object Model (AOM) https://wicg.github.io/aom/spec/ and in particular the related input event types https://wicg.github.io/aom/spec/input-events.html
>
> P
> --
> Patrick H. Lauke
>
> www.splintered.co.uk | https://github.com/patrickhlauke
> http://flickr.com/photos/redux/ | http://redux.deviantart.com
> twitter: @patrick_h_lauke | skype: patrick_h_lauke
> > > >