W3C home > Mailing lists > Public > w3c-wai-ua@w3.org > October to December 2006

RE: User Agent Teleconference for 26 October 2006

From: Jim Allan <jimallan@tsbvi.edu>
Date: Thu, 26 Oct 2006 12:43:20 -0500
To: Jan Richards <jan.richards@utoronto.ca>, WAU-ua <w3c-wai-ua@w3.org>
Message-id: <HDEAKIPKOHBCMDILOOPNKEMJGOAB.jimallan@tsbvi.edu>


> 9.5 No events on focus change (P2)
>
> - this would seem to have AJAX problems - ex. if focus change triggers
> formatting code that give the control its "has focus" look.

interesting. In the Note: it says "In this configuration, user agents should
still apply any stylistic changes (e.g. highlighting) that may occur when
there is a change in content focus."
Such as, tabbing to a link changes the focus, and the link text changes to
bold.

Are you saying stylistic changes should not be allowed? or is there an
example where applying a style change is a problem?

How would this be different in an AJAX control that changes the way it
appears when it gets focus, but is not activated?


>At the same  time this is tricky because format changes can also change
>the state of  the control. (e.g. check a check box)

current functioning in UAs allows users to navigate to (give focus to) a
form control without causing a change of state. the first radio button in a
group of radio buttons does not get selected when tabbing between groups,
although once in a group moving between the radio buttons does cause a
change of state. Tabbing between (giving focus to) checkboxes does not
change state. I suppose changing the state of a form control could be an
event written by an author...

what am I missing?


> - "5.1 No automatic content focus change (P2)" already handles loss of
> focus that might occur onfocus so maybe point to this in techs.
>
> - ATAG handling of this: A success criteria ("The author must have the
> option to ensure that selection is separate from activation (e.g.,
> navigating through the items in a dropdown menu without activating any
> of the items). ") within A.2.1 For the authoring tool user interface,
> ensure that all functionality is operable via a keyboard or a keyboard
> interface. [Priority 1]
> http://www.w3.org/WAI/AU/2006/WD-ATAG20-20060629/WD-ATAG20-2006062
> 9.html#gl-tool-accessible-operable
>
>
> Cheers,
> Jan
>
>
> Jim Allan wrote:
> > W3C User Agent Teleconference for 26 October 2006
> > -------------------------------------------------------------
> > Chair: Jim Allan
> > Date: Thursday, 26 October 2006
> > Time: 2:00-3:00 pm Boston Local Time, USA (19:00-20:00 UTC/GMT)
> > Call-in: Zakim bridge at: +1-617-761-6200, code 8294#
> > IRC: sever: irc.w3.org, port: 6665, channel: #ua.
> > -------------------------------------------------------------
> > Please send RSVP or additional agenda items to the list.
> >
> > Agenda Action Items
> >
> >
> > 	1. Review of UAAG techniques for checkpoints
> > 		9.3 Move content focus (P1)
> > 		9.4 Restore viewport state history (P1)
> > 		9.5 No events on focus change (P2)
> >
> >
> >  for currency and relevance. submit suggested deletions, improvements,
> > additions to the list.
> >
> > Jim Allan, Webmaster & Statewide Technical Support Specialist
> > Texas School for the Blind and Visually Impaired
> > 1100 W. 45th St., Austin, Texas 78756
> > voice 512.206.9315    fax: 512.206.9264  http://www.tsbvi.edu/
> > ---> Share to Win!! <---
> >
>
> --
> Jan Richards, M.Sc.
> User Interface Design Specialist
> Adaptive Technology Resource Centre (ATRC)
> Faculty of Information Studies
> University of Toronto
>
>    Email: jan.richards@utoronto.ca
>    Web:   http://jan.atrc.utoronto.ca
>    Phone: 416-946-7060
>    Fax:   416-971-2896
>
>
>
Received on Thursday, 26 October 2006 17:43:03 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 27 October 2009 06:51:37 GMT