Re: Understanding WCAG 2- SC 2.4.3

On Fri, Oct 8, 2010 at 10:00 AM, Sailesh Panchang <spanchang02@yahoo.com>wrote:

> Refer: http://www.w3.org/WAI/GL/2010/WD-UNDERSTANDING-WCAG20-20100923/
> Understanding SC 2.4.3
> Comment: The first two list items(out of six) following Examples repeat the
> text under Intent verbatim. I do not understand why.
> The fifth list item says the left nav links are made to appear before main
> content via CSS but the left nav links actually main content in the code.
> And this helps navigating to main content directly and this passes SC 2.4.3.
> Comment:
> I think it fails SC 2.4.3.
> A sighted keyboard user will be confused if  he cannot tab to a set of
> links that appear before main content. In a left to right and top-down
>  system one might expect tab focus to go to left nav links first. For a
> screen reader user too, this may pose problems:  there may be an h1 before
> main content and no heading before left nav links. So it may be difficult to
> identify end of main content. If the page layout has been explained to a
> blind user, he too will be confused if he cannot navigate to left nav before
> main content.
> (If left nav appear after main content visually and in tab order, it is
> another matter).
> Sailesh Panchang
> Web Accessibility Specialist
> www.deque.com
>
>  ==============================
==
Response from the Working Group
================================
We have removed the first example.

We are rewording the second example so it reads more like an examples:

2. On a web page that contains a tree of interactive controls, the user can
use the up and down arrow keys to move from tree node to tree node. Pressing
the left arrow key expands a node, then using the down arrow key moves into
the newly expanded nodes.

We do not believe that Example 5 fails 2.4.3, since the tab order still
follows the reading order, and the reading order follows a logical order.

Loretta Guarino Reid, WCAG WG Co-Chair
Gregg Vanderheiden, WCAG WG Co-Chair
Michael Cooper, WCAG WG Staff Contact


On behalf of the WCAG Working Group