Received: by 10.14.53.67 with SMTP id f43mr176567eec.0.1289223317950; Mon, 08 Nov 2010 05:35:17 -0800 (PST) X-BeenThere: jquery-a11y@googlegroups.com Received: by 10.14.35.221 with SMTP id u69ls510411eea.7.p; Mon, 08 Nov 2010 05:35:16 -0800 (PST) Received: by 10.14.119.1 with SMTP id m1mr162564eeh.12.1289223316629; Mon, 08 Nov 2010 05:35:16 -0800 (PST) Received: by 10.14.119.1 with SMTP id m1mr162563eeh.12.1289223316592; Mon, 08 Nov 2010 05:35:16 -0800 (PST) Return-Path: Received: from mail-ew0-f44.google.com (mail-ew0-f44.google.com [209.85.215.44]) by gmr-mx.google.com with ESMTP id t3si1462711eeh.7.2010.11.08.05.35.15; Mon, 08 Nov 2010 05:35:15 -0800 (PST) Received-SPF: pass (google.com: domain of scott.gonza...@gmail.com designates 209.85.215.44 as permitted sender) client-ip=209.85.215.44; Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of scott.gonza...@gmail.com designates 209.85.215.44 as permitted sender) smtp.mail=scott.gonza...@gmail.com; dkim=pass (test mode) header...@gmail.com Received: by mail-ew0-f44.google.com with SMTP id 27so2913025ewy.31 for ; Mon, 08 Nov 2010 05:35:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type; bh=CQ7k++mPsHY3hTJUzOQn3+um6zTODFgOFn4Q6Jki46E=; b=Vo/k3VRZsG2Pvs/8/ZKgFrRBC6rZB6/4RExmq7HWAepH7/dc8Ks6AamK1tmB9Bg6Wn fDzl/LHsjs+YrPy701kbgi5GoBY/k8+CEXzAd8nqmEGpe5A0LVDs7UrNSZYZ3qACYWYz ozTdTmjNVdICisNNCom6N+bxFucx9f6VQ06SA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=RA4ddt/rvRG3suk7h9Ha11uFfW5sKRozKyWwhTm7t5pEcGpprl4eg3MmkIVvYBuEsJ RMsln9BMT4rVx9cjO8Me1KZ7Xege9cwfS16lAmH3ruxXC2pIwWUTh1bp1YqZOiBTrgij eE4cuvRYPiJY/YoVMiYfN42WCl2VCJF3gMR+0= MIME-Version: 1.0 Received: by 10.213.25.143 with SMTP id z15mr899608ebb.62.1289223315225; Mon, 08 Nov 2010 05:35:15 -0800 (PST) Received: by 10.14.45.11 with HTTP; Mon, 8 Nov 2010 05:35:15 -0800 (PST) In-Reply-To: <6C645886-E70E-4C56-A975-663D5CCD7...@zufelt.ca> References: <6C645886-E70E-4C56-A975-663D5CCD7...@zufelt.ca> Date: Mon, 8 Nov 2010 08:35:15 -0500 Message-ID: Subject: Re: jQuery UI autocomplete plugin From: =?ISO-8859-1?Q?Scott_Gonz=E1lez?= To: jquery-a11y@googlegroups.com Content-Type: multipart/alternative; boundary=0015174beacebd7c7904948ab125 --0015174beacebd7c7904948ab125 Content-Type: text/plain; charset=ISO-8859-1 Hey Everett, The demo you were looking at is running the most recent stable release, so that's a good place to be looking. We also have http://view.jqueryui.com/master/demos/autocomplete/multiple.html which is running the same demo straight from the master branch of our git repo (currently down, GitHub just changed their API which broke our site; we're working on bringing it back up). One thing to note is that the multiple word support is just a demo built on top of our single word autocomplete widget. What that means is there's no official support for it: no tests, no documentation, may not have a full API, etc. However, we do try to provide as much support for them as we reasonably can, so if you'd like to help improve the multiple word demos, we'd certainly appreciate any help. For a quick overview of our process: we design our plugins on our planning wiki (http://wiki.jqueryui.com). This wiki contains markup, visual, and API design. Once we've got an idea of what we want to build, we'll prototype the plugin in a branch, figure out which parts of our design are working well, which aren't and where any holes might exist. Then we iterate on the design and flesh out the rest of the code. Once the API and code are mostly stable, we'll pull the plugin into the master branch, and it will be released in the next major version. We do have plans to release a multi word autocomplete ( http://wiki.jqueryui.com/ListBuilder) which will be built on top of autocomplete (http://wiki.jqueryui.com/Autocomplete) which utilizes menu ( http://wiki.jqueryui.com/Menu). Right now the menu plugin hasn't been officially released, but if you look at the bottom of jquery.ui.autocomplete.js, you'll see that there's an initial implementation of menu in there. That menu plugin has since had a lot of improvements in our menu branch (https://github.com/jquery/jquery-ui/tree/menu) and menu is slated for our next major version (1.9), though it has not yet been pulled into the master branch. We do have some ARIA attributes in both the autocomplete and menu plugins. So it's probably best to start with just single word autocomplete and verify that it's fully accessible and then move on to multi word autocomplete. Almost all of our discussion for everything jQuery-related happens on the jQuery Forums (http://forum.jquery.com). There are two forums specifically for jQuery UI: Using jQuery UI (http://forum.jquery.com/using-jquery-ui) for people using existing plugins and Developing jQuery UI ( http://forum.jquery.com/developing-jquery-ui) for people building official jQuery UI plugins. However, we still use this Google Group for accessibility discussions because Zoho, our forum software, has some accessibility issues which obviously prevents many of the people interested in helping out with accessibility from being able to do so. Right now I see two places where you could easily help out: 1) Fill out any missing accessibility information on the planning wiki for menu and autocomplete, possibly list builder as well. 2) Fork jQuery UI on GitHub and send pull requests. Any other types of contributions would be appreciated as well and if you have any questions feel free to post them here or on the main forums (if they're just general questions, the forums are probably better since they receive much higher traffic). On Mon, Nov 8, 2010 at 12:11 AM, E.J. Zufelt wrote: > Good evening, > > I tested the jQuery UI autocomplete plugin today at > http://jqueryui.com/demos/autocomplete/multiple.html . We are considering > adopting this plugin in Drupal Core, and I tested quickly to see if it was > accessible to screen-reader users (not that this is our only group to be > concerned about, it was just quick). I noticed thatit does not appear to > work for screen-reader users, testing with JAWS 11.0.1467 / FF 3.6. > > I skimmed briefly over the plugin source and it doesn't appear to be using > ARIA correctly. I would like to help to improve the plugin, but am not > familiar with the jQuery UI community / development cycles etc. > > It would be really helpful if someone could tell me if there is a more > recent version that I should be testing, and if there is a demo somewhere > (note we need the multiple values autocomplete). Also, if someone could > provide me with a primer to the community, sites used, etc, that would be > greatly appreciated. > > Thanks in advance, > Everett Zufelt > http://zufelt.ca > > Follow me on Twitter > http://twitter.com/ezufelt > > View my LinkedIn Profile > http://www.linkedin.com/in/ezufelt > > > > -- > You received this message because you are subscribed to the Google Groups > "jQuery Accessibility" group. > To post to this group, send email to jquery-a11y@googlegroups.com. > To unsubscribe from this group, send email to > jquery-a11y+unsubscribe@googlegroups.com > . > For more options, visit this group at > http://groups.google.com/group/jquery-a11y?hl=en. > --0015174beacebd7c7904948ab125 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hey Everett,

The demo you were looking at is running the most recent= stable release, so that's a good place to be looking. We also have h= ttp://view.jqueryui.com/master/demos/autocomplete/multiple.html which i= s running the same demo straight from the master branch of our git repo (cu= rrently down, GitHub just changed their API which broke our site; we're= working on bringing it back up).

One thing to note is that the multiple word support is just a demo buil= t on top of our single word autocomplete widget. What that means is there&#= 39;s no official support for it: no tests, no documentation, may not have a= full API, etc. However, we do try to provide as much support for them as w= e reasonably can, so if you'd like to help improve the multiple word de= mos, we'd certainly appreciate any help.

For a quick overview of our process: we design our plugins on our plann= ing wiki (http://wiki.jqueryui.com= ). This wiki contains markup, visual, and API design. Once we've got an= idea of what we want to build, we'll prototype the plugin in a branch,= figure out which parts of our design are working well, which aren't an= d where any holes might exist. Then we iterate on the design and flesh out = the rest of the code. Once the API and code are mostly stable, we'll pu= ll the plugin into the master branch, and it will be released in the next m= ajor version.

We do have plans to release a multi word autocomplete (http://wiki.jqueryui.com/ListBuilder) = which will be built on top of autocomplete (http://wiki.jqueryui.com/Autocomplete) which utilize= s menu (http://wiki.jqueryui.com/= Menu). Right now the menu plugin hasn't been officially released, b= ut if you look at the bottom of jquery.ui.autocomplete.js, you'll see t= hat there's an initial implementation of menu in there. That menu plugi= n has since had a lot of improvements in our menu branch (https://github.com/jquery/jquery-u= i/tree/menu) and menu is slated for our next major version (1.9), thoug= h it has not yet been pulled into the master branch.

We do have some ARIA attributes in both the autocomplete and menu plugi= ns. So it's probably best to start with just single word autocomplete a= nd verify that it's fully accessible and then move on to multi word aut= ocomplete.

Almost all of our discussion for everything jQuery-related happens on t= he jQuery Forums (http://forum.jquery.c= om). There are two forums specifically for jQuery UI: Using jQuery UI (= http://forum.jquery.com= /using-jquery-ui) for people using existing plugins and Developing jQue= ry UI (http://foru= m.jquery.com/developing-jquery-ui) for people building official jQuery = UI plugins. However, we still use this Google Group for accessibility discu= ssions because Zoho, our forum software, has some accessibility issues whic= h obviously prevents many of the people interested in helping out with acce= ssibility from being able to do so.

Right now I see two places where you could easily help out:
1) Fill = out any missing accessibility information on the planning wiki for menu and= autocomplete, possibly list builder as well.
2) Fork jQuery UI on GitHu= b and send pull requests.

Any other types of contributions would be appreciated as well and if yo= u have any questions feel free to post them here or on the main forums (if = they're just general questions, the forums are probably better since th= ey receive much higher traffic).


On Mon, Nov 8, 2010 at 12:11 AM, E.J. Zu= felt <lists@zufelt.= ca> wrote:
Good evening,

I te= sted the jQuery UI autocomplete plugin today at=A0http://jqueryui.c= om/demos/autocomplete/multiple.html . =A0We are considering adopting th= is plugin in Drupal Core, and I tested quickly to see if it was accessible = to screen-reader users (not that this is our only group to be concerned abo= ut, it was just quick). =A0I noticed thatit does not appear to work for scr= een-reader users, testing with JAWS 11.0.1467 / FF 3.6.

I skimmed briefly over the plugin source and it doesn&#= 39;t appear to be using ARIA correctly. =A0I would like to help to improve = the plugin, but am not familiar with the jQuery UI community / development = cycles etc.

It would be really helpful if someone could tell me if = there is a more recent version that I should be testing, and if there is a = demo somewhere (note we need the multiple values autocomplete). =A0Also, if= someone could provide me with a primer to the community, sites used, etc, = that would be greatly appreciated.

Thanks in advance,
Everett Zufelt

Follow me on Twitter
<= a href=3D"http://twitter.com/ezufelt" target=3D"_blank">http://twitter.com/= ezufelt

View my LinkedIn Profile
http://www.linkedin.com/in/ezufelt

=


--
You received this message because you are subscribed to the Google Groups &= quot;jQuery Accessibility" group.
To post to this group, send email to jquery-a11y@googlegroups.com.
To unsubscribe from this group, send email to jquery-a11y+unsubscribe@= googlegroups.com.
For more options, visit this group at http://groups.google.com/group/= jquery-a11y?hl=3Den.

--0015174beacebd7c7904948ab125--