WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: making Select 2 more accessible

for

From: Jennifer Sutton
Date: Oct 21, 2013 10:51AM

Paul and list:

Paul, thanks for taking a look and offering your advice. I appreciate
your time.
I'm passing along your message.

Generally speaking, I'll try not to clutter the list with lots of
one-off inquiries like this; however, I'd like to note, in passing,
that more and more of these widgets are being built without
accessibility knowledge (of ARIA, specifically). Or at least *I'm*
seeing more and more. And I'm increasingly concerned about the
ramifications. I know people are working on jQuery, Dojo, and the
like, but somehow, I am not getting the feeling that we're reaching
devs where they are.

And of course, it's not just ARIA; it's keyboard navigation, focus,
and so forth.

I'll continue to do what I can, as I am sure so many of us are, to
reach out to devs, even if it's just one widget at a time.

Best,
Jennifer

At 09:05 AM 10/21/2013, you wrote:
>Ouch! It's a custom "fake" select input with no ARIA at all. They'll
>have TON of work to do to make this accessible like a native
><select> input. I don't think it's worth the effort just because
>they want a certain look and feel. Native select's on mobile devices
>are designed to be more usable in that medium, they're also required
>for accessibility unless you use a good custom select implementation
>like jQuery Mobile's.
>
>Maybe tell them to copy jQuery Mobile's implementation. That's my advice :)
>
>Paul J. Adam
>Accessibility Evangelist
>www.deque.com