WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: <select multiple> and WCAG compliance

for

From: Patrick H. Lauke
Date: Oct 24, 2017 6:44AM

On 24/10/2017 13:37, Roel Van Gils wrote:
> Thanks, Patrick. You're probably right, but I find this a very bitter truth.
>
>> Because of course it's not a fail. It's accessible, though arguably not very user friendly/usable/discoverable. But WCAG 2.0 isn't about usability.
>
> I find it very hard to claim that something is 'accessible' when in fact, it's not. I cannot demonstrate it's possible to select any number of arbitrary items in a multiple select without using a mouse in any of the mainstream browsers.. In fact, I think nobody can.
>
> That's why I was wondering if someone would think it's 'acceptable' to flag the use of <select multiple>, despite it's a valid use of HTML.

Sorry, I forgot that selecting *non-contiguous* multiple options does
not seem supported in browsers (contiguous ones can be selected in
browsers using just SHIFT+cursor keys). In that case yes, if a site/web
app relies on the ability to select multiple potentially non-contiguous
files (and does not, for instance, allow a user to somehow make further
refinements/selections), then it does indeed smell like an actual
failure due to lack of any actual user agent support for sensible
keyboard navigation in that respect.

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