WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Need for Increment Buttons?

for

From: Patrick H. Lauke
Date: Dec 17, 2018 12:48PM

On 17/12/2018 19:24, Bryan Garaventa wrote:
> Hi,
> Unfortunately this is a known issue on the iOS platform and does not just impact browser-viewable sliders like the one on WhatSock, but also on any drag and drop type slider that uses standard JavaScript within hybrid applications such as native apps that include web components that do the same thing.

Not just iOS. Same thing happens in Android, where anything with a
role="slider" will get Talkback to announce a hint to "use the volume
keys to change the value" (or something to that effect).

> The reason being that, when role=slider is applied to an element, it only changes the native mapping in the accessibility tree in that browser, but does not automatically tie into the native functionality when the same control is implemented using Xcode, which is necessary for the single finger swipe action to automatically scroll the slider as it does in native apps.
>
> The last I heard, Apple has no plan to address this going forward, so it is always necessary to include accessible decrement and increment buttons to address these shortcomings in touch devices for the foreseeable future.

As said, the hope is that AOM events will provide a more sustainable
solution of this problem in future.

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