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

RE: Keyboard trap clarification for ATAG2

From: Richards, Jan <jrichards@ocad.ca>
Date: Tue, 4 Oct 2011 18:01:02 +0000
To: "w3c-wai-au@w3.org" <w3c-wai-au@w3.org>
Message-ID: <0B1EB1C972BCB740B522ACBCD5F48DEB037F5650@ocadmail-maildb.ocad.ca>
That would give us:

2.1.2 No Keyboard Trap: If keyboard focus can be moved to a component, including editing views that render content that may have keyboard traps, using a keyboard interface, then focus can be moved away from that component using only a keyboard interface, and, if it requires more than unmodified arrow or tab keys or other standard exit methods, the user is advised of the method for moving focus away. (Level A)

...which is a bit wordy. How about...

2.1.2 No Keyboard Trap: If keyboard focus can be moved to a component, including components in rendered editing views, using a keyboard interface, then focus can be moved away from that component using only a keyboard interface, and, if it requires more than unmodified arrow or tab keys or other standard exit methods, the user is advised of the method for moving focus away. (Level A)


Cheers,
Jan


> -----Original Message-----
> From: Treviranus, Jutta (Academic)
> Sent: October 4, 2011 12:43 PM
> To: Alex Li
> Cc: Richards, Jan; w3c-wai-au@w3.org
> Subject: Re: Keyboard trap clarification for ATAG2
> 
> Perhaps we can remove "of the page" and insert the words after
> components, "including editing views that render content that may have
> keyboard traps" and then use this text.
> 
> Jutta
> 
> On 2011-10-04, at 12:26 PM, Alex Li wrote:
> 
> > I don't get why we are trying to reinvent the wheel here.  What is it
> about WCAG 2.0 2.1.2 that does not cover what we need here?
> > 2.1.2 No Keyboard Trap: If keyboard focus can be moved to a component
> of the page using a keyboard interface, then focus can be moved away
> from that component using only a keyboard interface, and, if it
> requires more than unmodified arrow or tab keys or other standard exit
> methods, the user is advised of the method for moving focus away.
> (Level A)
> >
> > All we need to do is to remove the term "of the page".
> >
> > From: w3c-wai-au-request@w3.org [mailto:w3c-wai-au-request@w3.org] On
> Behalf Of Richards, Jan
> > Sent: Tuesday, October 04, 2011 9:00 AM
> > To: w3c-wai-au@w3.org
> > Subject: Keyboard trap clarification for ATAG2
> >
> > On yesterday's call I said that I would take a shot at simplifying
> the keyboard trap requirement. It still says "documented", but it is
> more clear that it only applies narrowly to editing views that render
> content to the point where keyboard traps become possible:
> >
> > A.3.1.2 No Keyboard Traps: *Keyboard traps* are prevented as follows:
> (Level A)
> >     (a) In the Authoring Tool User Interface: No keyboard traps are
> present; and
> >     (b) In Editing-Views that Render Content: If an editing-view
> renders the content being edited such that a keyboard trap might exist
> in the content, then the authoring tool provides a documented keyboard
> method for moving the focus away from such content.
> >
> > keyboard trap (UNCHANGED)
> > A user interface situation in which a keyboard interface may be used
> to move focus to, but not from, a user interface component or group of
> components.
> >
> > Cheers,
> > Jan
> >
> >
> > (MR) JAN RICHARDS
> > PROJECT MANAGER
> > INCLUSIVE DESIGN RESEARCH CENTRE (IDRC)
> >
> > T 416 977 6000 x3957
> > F 416 977 9844
> > E jrichards@ocad.ca
> >
> > Twitter @OCAD
> > Facebook www.facebook.com/OCADUniversity
> >
> > OCAD UNIVERSITY
> > 100 McCaul Street, Toronto, Canada  M5T 1W1
> > www.ocadu.ca
Received on Tuesday, 4 October 2011 18:01:25 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 4 October 2011 18:01:25 GMT