jQuery UI autocomplete plugin - jQuery Accessibility

The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Message from discussion jQuery UI autocomplete plugin
Received-SPF: pass (google.com: domain of rich_calogg...@wgbh.org designates 198.147.175.8 as permitted sender) client-ip=198.147.175.8;
Date: Tue, 09 Nov 2010 14:19:37 -0500
From: Rich Caloggero <rich_calogg...@wgbh.org>
Subject: Re: jQuery UI autocomplete plugin
To: jquery-a11y@googlegroups.com
Message-id: <ECAFE5FA8E404EDF804FFA5DEEBF47F8@wgbh.org>
MIME-version: 1.0
Content-type: multipart/alternative;
 boundary="Boundary_(ID_PvILNX86BX5qmeCm1RCdlg)"
References: <6C645886-E70E-4C56-A975-663D5CCD740E@zufelt.ca>
 <AANLkTimaX+AqQEhmTpi5xArV2bYtkeQtykC7iJWD2gd6@mail.gmail.com>

This is a multi-part message in MIME format.

--Boundary_(ID_PvILNX86BX5qmeCm1RCdlg)
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: quoted-printable

I remember looking at and commenting about this about a year ago.  I =
tested the autocomplete with Jaws (version 10.xx at the time).  I found =
that the use of role=3D"menu" causes problems for Jaws. I suggested they =
use a role of "list" on the menu and it seemed to work better.  I need =
to look back at the code, but from the brief test of the online demos, I =
find that the default case works and the others seem not to work.  Maybe =
only the default case got the updated role?

-- Rich

  ----- Original Message -----=20
  From: Scott Gonz=E1lez=20
  To: jquery-a11y@googlegroups.com=20
  Sent: Monday, November 08, 2010 8:35 AM
  Subject: Re: jQuery UI autocomplete plugin


  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 <li...@zufelt.ca> 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







    --=20
    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=3Den.




  --=20
  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=3Den.

--Boundary_(ID_PvILNX86BX5qmeCm1RCdlg)
Content-type: text/html; charset=iso-8859-1
Content-transfer-encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.6000.16735" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>I remember looking at and commenting =
about this=20
about a year ago.&nbsp; I tested the autocomplete with Jaws (version =
10.xx at=20
the time).&nbsp; I found that the use of role=3D"menu" causes problems =
for Jaws. I=20
suggested they use a role of "list" on the menu and it seemed to work=20
better.&nbsp; I need to look back at the code, but from the brief test =
of the=20
online demos, I find that the default case works and the others seem not =
to=20
work.&nbsp; Maybe only the default case got the updated =
role?</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>-- Rich</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<BLOCKQUOTE=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
  <DIV style=3D"FONT: 10pt arial">----- Original Message ----- </DIV>
  <DIV=20
  style=3D"BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: =
black"><B>From:</B>=20
  <A title=3Dscott.gonza...@gmail.com =
href=3D"mailto:scott.gonza...@gmail.com">Scott=20
  Gonz=E1lez</A> </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>To:</B> <A =
title=3Djquery-a11y@googlegroups.com=20
  =
href=3D"mailto:jquery-a11y@googlegroups.com">jquery-a11y@googlegroups.com=
</A>=20
  </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Monday, November 08, 2010 =
8:35=20
  AM</DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Subject:</B> Re: jQuery UI =
autocomplete=20
  plugin</DIV>
  <DIV><BR></DIV>Hey Everett,<BR><BR>The demo you were looking at is =
running the=20
  most recent stable release, so that's a good place to be looking. We =
also have=20
  <A=20
  =
href=3D"http://view.jqueryui.com/master/demos/autocomplete/multiple.html"=
>http://view.jqueryui.com/master/demos/autocomplete/multiple.html</A>=20
  which is running the same demo straight from the master branch of our =
git repo=20
  (currently down, GitHub just changed their API which broke our site; =
we're=20
  working on bringing it back up).<BR><BR>One thing to note is that the =
multiple=20
  word support is just a demo built on top of our single word =
autocomplete=20
  widget. What that means is there's no official support for it: no =
tests, no=20
  documentation, may not have a full API, etc. However, we do try to =
provide as=20
  much support for them as we reasonably can, so if you'd like to help =
improve=20
  the multiple word demos, we'd certainly appreciate any =
help.<BR><BR>For a=20
  quick overview of our process: we design our plugins on our planning =
wiki (<A=20
  href=3D"http://wiki.jqueryui.com">http://wiki.jqueryui.com</A>). This =
wiki=20
  contains markup, visual, and API design. Once we've got an idea of =
what we=20
  want to build, we'll prototype the plugin in a branch, figure out =
which parts=20
  of our design are working well, which aren't and where any holes might =
exist.=20
  Then we iterate on the design and flesh out the rest of the code. Once =
the API=20
  and code are mostly stable, we'll pull the plugin into the master =
branch, and=20
  it will be released in the next major version.<BR><BR>We do have plans =
to=20
  release a multi word autocomplete (<A=20
  =
href=3D"http://wiki.jqueryui.com/ListBuilder">http://wiki.jqueryui.com/Li=
stBuilder</A>)=20
  which will be built on top of autocomplete (<A=20
  =
href=3D"http://wiki.jqueryui.com/Autocomplete">http://wiki.jqueryui.com/A=
utocomplete</A>)=20
  which utilizes menu (<A=20
  =
href=3D"http://wiki.jqueryui.com/Menu">http://wiki.jqueryui.com/Menu</A>)=
. Right=20
  now the menu plugin hasn't been officially released, but if you look =
at the=20
  bottom of jquery.ui.autocomplete.js, you'll see that there's an =
initial=20
  implementation of menu in there. That menu plugin has since had a lot =
of=20
  improvements in our menu branch (<A=20
  =
href=3D"https://github.com/jquery/jquery-ui/tree/menu">https://github.com=
/jquery/jquery-ui/tree/menu</A>)=20
  and menu is slated for our next major version (1.9), though it has not =
yet=20
  been pulled into the master branch.<BR><BR>We do have some ARIA =
attributes in=20
  both the autocomplete and menu plugins. So it's probably best to start =
with=20
  just single word autocomplete and verify that it's fully accessible =
and then=20
  move on to multi word autocomplete.<BR><BR>Almost all of our =
discussion for=20
  everything jQuery-related happens on the jQuery Forums (<A=20
  href=3D"http://forum.jquery.com">http://forum.jquery.com</A>). There =
are two=20
  forums specifically for jQuery UI: Using jQuery UI (<A=20
  =
href=3D"http://forum.jquery.com/using-jquery-ui">http://forum.jquery.com/=
using-jquery-ui</A>)=20
  for people using existing plugins and Developing jQuery UI (<A=20
  =
href=3D"http://forum.jquery.com/developing-jquery-ui">http://forum.jquery=
.com/developing-jquery-ui</A>)=20
  for people building official jQuery UI plugins. However, we still use =
this=20
  Google Group for accessibility discussions because Zoho, our forum =
software,=20
  has some accessibility issues which obviously prevents many of the =
people=20
  interested in helping out with accessibility from being able to do=20
  so.<BR><BR>Right now I see two places where you could easily help =
out:<BR>1)=20
  Fill out any missing accessibility information on the planning wiki =
for menu=20
  and autocomplete, possibly list builder as well.<BR>2) Fork jQuery UI =
on=20
  GitHub and send pull requests.<BR><BR>Any other types of contributions =
would=20
  be appreciated as well and if you have any questions feel free to post =
them=20
  here or on the main forums (if they're just general questions, the =
forums are=20
  probably better since they receive much higher traffic).<BR><BR><BR>
  <DIV class=3Dgmail_quote>On Mon, Nov 8, 2010 at 12:11 AM, E.J. Zufelt =
<SPAN=20
  dir=3Dltr>&lt;<A =
href=3D"mailto:li...@zufelt.ca">li...@zufelt.ca</A>&gt;</SPAN>=20
  wrote:<BR>
  <BLOCKQUOTE class=3Dgmail_quote=20
  style=3D"PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: =
rgb(204,204,204) 1px solid">
    <DIV style=3D"WORD-WRAP: break-word">Good evening,
    <DIV><BR></DIV>
    <DIV>I tested the jQuery UI autocomplete plugin today at&nbsp;<A=20
    href=3D"http://jqueryui.com/demos/autocomplete/multiple.html"=20
    =
target=3D_blank>http://jqueryui.com/demos/autocomplete/multiple.html</A> =
.=20
    &nbsp;We are considering adopting this plugin in Drupal Core, and I =
tested=20
    quickly to see if it was accessible to screen-reader users (not that =
this is=20
    our only group to be concerned about, it was just quick). &nbsp;I =
noticed=20
    thatit does not appear to work for screen-reader users, testing with =
JAWS=20
    11.0.1467 / FF 3.6.</DIV>
    <DIV><BR></DIV>
    <DIV>I skimmed briefly over the plugin source and it doesn't appear =
to be=20
    using ARIA correctly. &nbsp;I would like to help to improve the =
plugin, but=20
    am not familiar with the jQuery UI community / development cycles =
etc.</DIV>
    <DIV><BR></DIV>
    <DIV>It would be really helpful if someone could tell me if there is =
a more=20
    recent version that I should be testing, and if there is a demo =
somewhere=20
    (note we need the multiple values autocomplete). &nbsp;Also, if =
someone=20
    could provide me with a primer to the community, sites used, etc, =
that would=20
    be greatly appreciated.</DIV>
    <DIV><BR></DIV>
    <DIV>Thanks in advance,</DIV>
    <DIV>
    <DIV><SPAN=20
    style=3D"WORD-SPACING: 0px; FONT: medium Helvetica; TEXT-TRANSFORM: =
none; COLOR: rgb(0,0,0); TEXT-INDENT: 0px; WHITE-SPACE: normal; =
LETTER-SPACING: normal; BORDER-COLLAPSE: separate"><SPAN=20
    style=3D"WORD-SPACING: 0px; FONT: 12px Helvetica; TEXT-TRANSFORM: =
none; COLOR: rgb(0,0,0); TEXT-INDENT: 0px; WHITE-SPACE: normal; =
LETTER-SPACING: normal; BORDER-COLLAPSE: separate">
    <DIV style=3D"WORD-WRAP: break-word"><SPAN=20
    style=3D"WORD-SPACING: 0px; FONT: 12px Helvetica; TEXT-TRANSFORM: =
none; COLOR: rgb(0,0,0); TEXT-INDENT: 0px; WHITE-SPACE: normal; =
LETTER-SPACING: normal; BORDER-COLLAPSE: separate">
    <DIV style=3D"WORD-WRAP: break-word">
    <DIV><SPAN style=3D"FONT-SIZE: medium"><SPAN style=3D"FONT-SIZE: =
12px">
    <DIV>Everett Zufelt<BR></DIV>
    <DIV><A href=3D"http://zufelt.ca" =
target=3D_blank>http://zufelt.ca</A></DIV>
    <DIV><BR></DIV>
    <DIV>Follow me on Twitter<BR><A href=3D"http://twitter.com/ezufelt"=20
    target=3D_blank>http://twitter.com/ezufelt</A><BR><BR>View my =
LinkedIn=20
    Profile<BR><A href=3D"http://www.linkedin.com/in/ezufelt"=20
    target=3D_blank>http://www.linkedin.com/in/ezufelt</A></DIV>
    =
<DIV><BR></DIV></SPAN></SPAN></DIV></DIV></SPAN></DIV></SPAN></SPAN><BR><=
/DIV><BR></DIV></DIV>
    <P></P>-- <BR>You received this message because you are subscribed =
to the=20
    Google Groups "jQuery Accessibility" group.<BR>To post to this =
group, send=20
    email to <A href=3D"mailto:jquery-a11y@googlegroups.com"=20
    target=3D_blank>jquery-a11y@googlegroups.com</A>.<BR>To unsubscribe =
from this=20
    group, send email to <A=20
    href=3D"mailto:jquery-a11y%2Bunsubscribe@googlegroups.com"=20
    target=3D_blank>jquery-a11y+unsubscribe@googlegroups.com</A>.<BR>For =
more=20
    options, visit this group at <A=20
    href=3D"http://groups.google.com/group/jquery-a11y?hl=3Den"=20
    =
target=3D_blank>http://groups.google.com/group/jquery-a11y?hl=3Den</A>.<B=
R></BLOCKQUOTE></DIV><BR>
  <P></P>-- <BR>You received this message because you are subscribed to =
the=20
  Google Groups "jQuery Accessibility" group.<BR>To post to this group, =
send=20
  email to jquery-a11y@googlegroups.com.<BR>To unsubscribe from this =
group, send=20
  email to jquery-a11y+unsubscribe@googlegroups.com.<BR>For more =
options, visit=20
  this group at=20
http://groups.google.com/group/jquery-a11y?hl=3Den.<BR></BLOCKQUOTE></BOD=
Y></HTML>

--Boundary_(ID_PvILNX86BX5qmeCm1RCdlg)--
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
Account Options
