Re: ACTION-1490 updates for March 17 ARIA caucus

Thanks Matt. 

So, you are saying that any widget, which excludes dialog box, will be possible companions to the textbox in a combobox. I think this needs to be further limited. You would not want to have a searchbox fill a textbook. Also, although I could see using a Switch it really does not make sense as you would more likely just use a Switch instead of a combobox. Please look at the list of widgets with a tighter lens. 

Rich Schwerdtfeger




> On Mar 16, 2016, at 7:59 PM, Matt King <a11ythinker@gmail.com> wrote:
> 
> I posted the following comment in action 1490 describing revisions to the previous proposal for combobox.
>  
> Changes made as a result of March 10, 2016 meeting
>  
> Note: The revised combobox proposal is now in branch action1490-combobox:
> http://rawgit.com/w3c/aria/action1490-combobox/aria/aria.html#combobox <http://rawgit.com/w3c/aria/action1490-combobox/aria/aria.html#combobox>
>  
> The branch includes the following changes as a result of the Mar 10 discussion.
>  
> 1. Revised definition so that it does not imply that listbox and grid are classified as popups as opposed to elements that popup.
>  
> 2. elivated the following normative aria-autocomplete statement from author SHOULD to author MUST: 
> If the combobox provides autocompletion behavior for the text input as described in aria-autocomplete, 
> authors MUST set aria-autocomplete on the textbox element to the value that corresponds to the provided behavior. 
>  
> 3. Added an author MUST statement that restricts the role of the popup element to listbox, tree, grid, or dialog.
> And, correspondingly added listbox, tree, grid, and dialog as required owned elements.
>  
> Matt King