See, this is already opening up a whole set of discussions. We have to: - finish ARIA 1.1 - finish SVG a11y - finish ARIA EPUB semantics - finish the new graphics module - test all the mapping specs. … and help with the html5 work. This is A LOT, This is just not that critical to gum things up now. If we do this I would ask that it be left for ARIA 2.0. Rich Rich Schwerdtfeger > On Feb 4, 2016, at 10:18 AM, Joseph Scheuhammer <clown@alum.mit.edu> wrote: > > On 2016-02-03 9:26 PM, Matt King wrote: >> 3. list because all comboboxes have a list, and that list is identified by a relationship and known to be visible when expanded is true. > > A value of list also indicates that the options in the list are the only ones that match what the user has typed thus far. That is, the more the user types, the fewer the options. If aria-autocomplete is not set to "list", then the list will show all possible options and not only matches. > > However, I don't have an opinion about deprecating the current aria-autocomplete values, mainly because I don't have a feel for if users find them useful or not. A sighted user can see whether the completion is inline or not, whether the list is filtered or not, or both, or neither. Is that important to relay to AT users? I would need some form of user studies to be convinced either way, but I don't see that happening in the ARIA 1.1 time frame. > > -- > ;;;;joseph. > > 'Die Wahrheit ist Irgendwo da Draußen. Wieder.' > - C. Carter - > >
Received on Thursday, 4 February 2016 17:21:02 UTC