WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Need for Increment Buttons?

for

From: Patrick H. Lauke
Date: Dec 14, 2018 6:30PM

On 14/12/2018 22:28, glen walker wrote:
> With VoiceOver, even though it tells you you can swipe up or down to adjust
> the value, you have to change your rotor first. There's and "adjust value"
> rotor setting and once that's set, then swiping up/down will change the
> value.

By default (at least in my experience/my testing), VO/iOS automatically
switches to "adjust value" when you focus on an <input type="range">, so
there's no need to manually change the anything in the rotor first.

> However, that doesn't work on the whatsock example

Because, as said, it's not an actual <input type="range">, but really
just a series of <div> elements with added mouse/touch events/keyboard
events and appropriate aria roles/attributes. The role is what makes VO
believe it's an actual range type input - hence its announcement that
you can swipe up or down to change the value - but as it then doesn't
trigger any of the mouse/touch/keyboard handlers, it doesn't do anything.

> but it does work on a
> native <input type="range">

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