E-mail List Archives

Re: <select multiple> and WCAG compliance


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

On 24/10/2017 12:47, Roel Van Gils wrote:
> Hi,
> I consider using `<select multiple>` (see example below) a very poor practice in terms of accessibility (and usability in general). I usually suggest using a series of checkboxes instead.
> <select multiple>
> <option value="volvo">Volvo</option>
> <option value="saab">Saab</option>
> <option value="opel">Opel</option>
> <option value="audi">Audi</option>
> </select>
> Most users don't know they have to hold down a modifier key (dependent on the OS they're using) to select more than items, and even if even they know (or tell them), it's hard for certain users to operate the keyboard and the mouse at the same time. Without a mouse, I believe that's not even possible in most browsers.
> Screenreader support is also spotty, but it's possible (if you try hard enough).
> My question is: is it acceptable to let a website fail for WCAG 2.1.1 ('Make all functionality available from a keyboard') when the author uses perfectly valid and semantic HTML? That seems wrong.

Who is suggesting that <select multiple> would fail WCAG 2.0 2.1.1 ?

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.

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