Opened 13 years ago

Closed 13 years ago

#2939 closed task (fixed)

Implement a11y for Autocompleter

Reported by: bill Owned by: haysmark
Priority: high Milestone: 0.9beta
Component: Accessibility Version: 0.9
Keywords: Cc:
Blocked By: Blocking:

Description

For the screen reader, I wonder if we can just treat this as a plain input box, and ignore the drop down.

Change History (5)

comment:1 Changed 13 years ago by Becky Gibson

Status: newassigned

There is currently no easy way to detect that a screen reader is being used in order to know to ignore the drop down. This needs further investigation to see how to support the screen reader.

comment:2 Changed 13 years ago by Becky Gibson

I believe we can make this accessible. Design is posted in the dijit forum: http://dojotoolkit.org/accessibility-autocompletor-and-select

comment:3 Changed 13 years ago by Becky Gibson

Owner: changed from Becky Gibson to haysmark
Status: assignednew

Autocompleter behavior - the goal is to make this work the same as the FF and IE address bars:

  1. As user types drop down is displayed and matching entries are listed, As the user continues typing, the list of choices is updated to match what the user has typed. (this happens today)
  1. When user presses down arrow, first option in open drop down is highlighted and edit field is updated with the currently highlighted option. Focus remains in the edit field. Call setValueNow each time the edit field is updated so screen reader will speak the updated value. Initial value typed by user is stored within widget.
  1. If after highlighting an option (and seeing it displayed in the edit box), the user presses escape: The drop down list is closed, the edit box is updated with what the user actually typed (which was stored in the step above) rather than the option which was displayed when the escape key was pressed.
  1. When the user presses enter on a highlighted option the drop down closes and that value is entered in the edit field (the widget does this today). The stored value of what the user originally typed gets reset within the widget.
  1. With an option highlighted (and displayed in the edit box) if the user types a character, that character gets appended to the end of the value in the edit box. (This is not ideal from a usability standpoint but it is the way the browser address bars work).
  1. Not absolutely necessary but would like to see arrow key cycle through list of choices AND edit box. For example: when arrow down and reach the end of the choices, the highlight is taken out of the list of choices and the edit field is updated to reflect what the user actually typed (like pressing escape as in #3). Pressing down again puts the highlight on the first item in the list of choices and update the edit field with that choice. Up arrow does the same thing in the opposite direction - move from first choice into edit field and then to last choice.

comment:4 Changed 13 years ago by haysmark

Status: newassigned

comment:5 Changed 13 years ago by Douglas Hays

Resolution: fixed
Status: assignedclosed

(In [8913]) Fixes #2939. Proxy commit for haysmark. Added a11y code. Popup menu only appears in AutoCompleter? while you are typing if autoComplete is true (some people were confused by what autoComplete meant). You can still press down or click the down arrow to display the list. Pressing down arrow on the keyboard now brings up the full list. It used to only display the one matching option and you had to manually clear the textbox to get the full option list.

Note: See TracTickets for help on using tickets.