Voting starts in March for the Drupal Association Board election.
Several months ago, after using Drupal sites for some time, I was surprised to find that some fields provide autocomplete functionality. I am an assistive technology user, and primarily use the JAWS screen-reader.
I noticed today that not only does autocomplete not function (e.g. free tagging), but that it can sometimes return undesirable results, as the unintentional Issue Tag "variable_get" at http://drupal.org/node/515236 shows.
Yahoo and Google have both implemented search suggestions accessible to screen-reader users (my only testing is with JAWS 10). Google's approach does not use ARIA, as it works in IE6. Yahoo's approach does use ARIA.
1. Resolve the issue where screen reader users may unintentionally select an inappropriate item in an autocomplete field.
2. Improve the markup of autocomplete fields to make autocomplete functionality accessible to screen-reader users. This will likely be best accomplished by using ARIA.
PASSED: [[SimpleTest]]: [MySQL] 27,414 pass(es). View
|#42||515262-aria-autocomplete-4.patch||2.21 KB||Everett Zufelt|
PASSED: [[SimpleTest]]: [MySQL] 26,968 pass(es). View
|#38||515262-aria-autocomplete-3.patch||1.96 KB||Everett Zufelt|
PASSED: [[SimpleTest]]: [MySQL] 27,003 pass(es). View
|#34||515262-aria-autocomplete-2.patch||1.83 KB||Everett Zufelt|
PASSED: [[SimpleTest]]: [MySQL] 26,973 pass(es). View
|#32||Screenshot-Create Article | drupal7.dev_.openconcept.ca - Chromium.png||69.47 KB||mgifford|