You received this message because you are subscribed to the Google Groups "jQuery Accessibility" group.
To post to this group, send email to jquer...@googlegroups.com.
To unsubscribe from this group, send email to jquery-a11y...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/jquery-a11y?hl=en.
Another thought, I am writing quickly so I haven't looked back at the code.If I recall correctly the autocomplete isn't actually changing the active descendant. It is, in the fact that it is changing the listitem that has the active descendant id, but it isn't actually changing the value of the active descendant property itself. This might mean that UAs aren't firing the correct events to have the change tracked.
Also, if I recall, there is no way to specify a prefix to the ids for the widget, meaning possibly that the widget can only be used once per page. This would probably make it difficult to use in a system like Drupal where it may need to appear multiple times on the same page. Perhaps there is a way to do this currently that I am missing.
You can see the new menu in action here:
Its also included in the milestone 3 release, downloadable here:
----- Original Message -----From: E.J. ZufeltSent: Saturday, November 20, 2010 3:36 AMSubject: Re: jQuery UI autocomplete plugin
I tested the demo of the menu. JAWS 11 / FF 3.6 reports this as a listbox, not as a menu. It doesn't appear to have a title at all (JAWS just reads "listbox"). It also doesn't appear to have any content.I imagine that with some more work and experimentation we can get this working properly, I don't think that using aria-live is the proper way to do this.
Everett ZufeltFollow me on Twitter
View my LinkedIn Profile
On 2010-11-19, at 1:50 PM, Jörn Zaefferer wrote: