E-mail List Archives
Thread: making Select 2 more accessible
Number of posts in this thread: 4 (In chronological order)
From: Jennifer Sutton
Date: Mon, Oct 21 2013 9:45AM
Subject: making Select 2 more accessible
No previous message | Next message →
Greetings, WebAIM:
Anyone used this:
Select2:
<http://ivaynberg.github.io/select2/>;http://ivaynberg.github.io/select2/
and improved its accessibility?
I encountered it on a Web site, when trying to place an order for
merchandise, and I'm working with a developer to try to improve it.
Best,
Jennifer
From: Paul J. Adam
Date: Mon, Oct 21 2013 10:05AM
Subject: Re: making Select 2 more accessible
← Previous message | Next message →
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
On Oct 21, 2013, at 10:45 AM, Jennifer Sutton < = EMAIL ADDRESS REMOVED = > wrote:
> Greetings, WebAIM:
>
> Anyone used this:
> Select2:
> <http://ivaynberg.github.io/select2/>;http://ivaynberg.github.io/select2/
>
> and improved its accessibility?
>
> I encountered it on a Web site, when trying to place an order for
> merchandise, and I'm working with a developer to try to improve it.
>
> Best,
> Jennifer
>
> > >
From: Jennifer Sutton
Date: Mon, Oct 21 2013 10:51AM
Subject: Re: making Select 2 more accessible
← Previous message | Next message →
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
From: Bryan Garaventa
Date: Tue, Oct 22 2013 4:32PM
Subject: Re: making Select 2 more accessible
← Previous message | No next message
The following article may be of assistance: "Why There are Only Two Ways to
Make ARIA Widgets Programmatically Focusable for Screen Reader Users"
https://www.ssbbartgroup.com/blog/2013/10/22/why-there-are-only-two-ways-to-make-aria-widgets-programmatically-focusable-for-screen-reader-users/
----- Original Message -----
From: "Jennifer Sutton" < = EMAIL ADDRESS REMOVED = >
To: "WebAIM Discussion List" < = EMAIL ADDRESS REMOVED = >
Sent: Monday, October 21, 2013 9:51 AM
Subject: Re: [WebAIM] making Select 2 more accessible
> 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
>
> > >