Re: Keyboard trap clarification for ATAG2

Seems cleaner to use the WCAG wording as Alex suggested.   I would not add
the additional text Jutta is suggesting as I believe it is  redundant to
the point of the topic.   But, I do think Jan's  suggestion is also a bit
more clear.   The problem is, it does address the documentation
requirement, but that should be covered through the requirement to document
all accessibility features and keyboard definitions.

Sueann Nichols

Phone: (720) 396-6739 (t/l) 938-6739
ssnichol@us.ibm.com
IBM Human Ability & Accessibility Center
http://www.ibm.com/able



|------------>
| From:      |
|------------>
  >--------------------------------------------------------------------------------------------------------------------------------------------------|
  |"Treviranus, Jutta (Academic)" <jtreviranus@faculty.ocad.ca>                                                                                      |
  >--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| To:        |
|------------>
  >--------------------------------------------------------------------------------------------------------------------------------------------------|
  |Alex Li <alli@microsoft.com>                                                                                                                      |
  >--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| Cc:        |
|------------>
  >--------------------------------------------------------------------------------------------------------------------------------------------------|
  |"Richards, Jan" <jrichards@ocad.ca>, "w3c-wai-au@w3.org" <w3c-wai-au@w3.org>                                                                      |
  >--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| Date:      |
|------------>
  >--------------------------------------------------------------------------------------------------------------------------------------------------|
  |10/04/2011 12:43 PM                                                                                                                               |
  >--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| Subject:   |
|------------>
  >--------------------------------------------------------------------------------------------------------------------------------------------------|
  |Re: Keyboard trap clarification for ATAG2                                                                                                         |
  >--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| Sent by:   |
|------------>
  >--------------------------------------------------------------------------------------------------------------------------------------------------|
  |w3c-wai-au-request@w3.org                                                                                                                         |
  >--------------------------------------------------------------------------------------------------------------------------------------------------|





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