- From: Joseph Scheuhammer <clown@alum.mit.edu>
- Date: Thu, 5 May 2016 10:57:42 -0400
- To: public-aria@w3.org, Richard Schwerdtfeger <schwer@us.ibm.com>
On 2016-05-02 2:40 PM, Rich Schwerdtfeger wrote:
> Agenda: May 5, 2016 WAI-ARIA Working Group
>
> ...
> 3. Action 1743: aria-activedescendant on application (20 minutes *max* discussion) Matt
>
> - https://www.w3.org/WAI/ARIA/track/actions/1743- Proposal:
> https://rawgit.com/w3c/aria/action-1743/aria/aria.html#aria-activedescendant-
> Proposal:
> https://rawgit.com/w3c/aria/action-1743/aria/aria.html#application
I was asked to update the definition of aria-activedescendant for
combobox designs where it does not actually point to a descendant (part
of action-1490). The changes were made in this branch:
http://rawgit.com/w3c/aria/mck-action1490-activedescendant/aria/aria.html#aria-activedescendant,
see the last paragraph before the characteristics table.
The added paragraph repeated below:
"
A special use case is a combobox where its text input field has DOM
focus, and that input element uses aria-activedescendant to reference
the currently active item within the combobox's popup. In one use case,
the text entry field has role="combobox" whereas, in a second case, it
is a textbox. Regardless, the element referenced by
aria-activedescendant is not in fact a descendant of the text entry.
Nonetheless, aria-activedescendant is treated by user agents as the
active descendant of the combobox.
"
--
;;;;joseph.
'Die Wahrheit ist Irgendwo da Draußen. Wieder.'
- C. Carter -
Received on Thursday, 5 May 2016 14:58:05 UTC