7020 2009-06-12 18:46:47 +0000 Work through aria-activedescendent scenario 2011-06-02 14:09:50 +0000 1 1 1 Unclassified ARIA Core AAM 1.0 PC All RESOLVED FIXED P1 normal --- 1 andi.snowweaver andi.snowweaver dbolter aria-ua-impl oldest_to_newest 25562 0 andi.snowweaver 2009-06-12 18:46:47 +0000 In particular, the issue of HTML elements as children of an object with aria-activedescendent and whether or not they can be focusable. 25563 1 andi.snowweaver 2009-06-12 18:48:19 +0000 Scrolling into view of the of focused activedescendant needs to be included in the scenario 26032 2 andi.snowweaver 2009-07-21 23:10:17 +0000 Best Practices Guide may be helpful. The browser needs to handle it when the authors have done it incorrectly. Concern about aria-activedescendant focus and how it might not be the same as desktop focus (comment for WAI-ARIA). From DB: The web developer wants to have all keyboard handling on the container so that all keypresses go to the container 26038 3 andi.snowweaver 2009-07-22 14:06:52 +0000 July 22, F2F in Boston: Browser has to be able to put visible focus on the active descendant. Actual focus would be on the container. For example, container has focus, but set active descendant. Visible focus should be moved to the descendant. Rule: any element that has focus and has ariaactivedescendant, visible focus should be directed to the childid. Current implementations don't put desktop focus on the childid. DB says because the container handles the keyboard events. If made it the desktop focus, events could bubble up to the container if child doesn't handle and the focus would inherit the user's display settings. In July 31st editor's draft, make it the desktop focus with a note asking for feedback from implementers. 27081 4 andi.snowweaver 2009-09-11 16:38:54 +0000 Changed the overview paragraph but not the rules yet. Want to discuss with UAI TF before proceeding. 27082 5 dbolter 2009-09-11 16:39:37 +0000 (In reply to comment #3) > July 22, F2F in Boston: > > Browser has to be able to put visible focus on the active descendant. I disagree. Visual styling is up to the web developer. > Actual > focus would be on the container. Agreed. > > For example, container has focus, but set active descendant. Visible focus > should be moved to the descendant. I can see the attraction of this. But it breaks the mental model of ARIA being purely a passive semantic description of what the scripter is already doing visually (styling). I'll try to be open minded though :) > > Rule: any element that has focus and has ariaactivedescendant, visible focus > should be directed to the childid. > Via script :) 27190 6 andi.snowweaver 2009-09-15 16:11:10 +0000 From September 15 UAI TF meeting: DB: what does it mean to keyboard handlers on container element? DB: if put real focus on child and don't know where it came from or if dealing with mashup scenario, it's possible that the child could swallow the event DB: breaks simple model of ARIA that want developers to have CS: would be good for sighted keyboard users who customize the desktop focus and for ATs that customize the focus DB: AT doesn't see the difference because UA fires the events for the AT to fake it CS: MS research shows that a growing number of users are customizing their desktop focus CS: at F2F, we were talking about describing this as desktop focus, describe some of these concerns, and ask for feedback DB: not clear why aria-activedescendant is needed DB: from ARIA TF, hear that people implementing grids need it because it simplifies the JavaScript keep draft of aria-activedescendant scenario the same but add editorial note of what we are thinking and what some of the issues are, ask for feedback think DOM focus is the same as desktop focus - need to say that somewhere or have a glossary term 27196 7 andi.snowweaver 2009-09-15 17:49:44 +0000 Restored edited paragraph and added editorial note. 30984 8 andi.snowweaver 2010-01-12 16:41:39 +0000 Waiting for public review comments. 47235 9 andi.snowweaver 2011-04-07 14:22:43 +0000 Rich to draft the changes and circulate for review. 49060 10 andi.snowweaver 2011-06-02 14:09:50 +0000 Completed at May 2011 Face to Face