How to meet 3.1.6 leftovers

Hi guys,

Was cleaning up the drafts based on decisions from the 12 January call 
today and ran across the following. In the 23 November draft, SC 3.1.6 
and 2.4.7 were nearly identical and on last week's call, we decided to 
remove 3.1.6 per Team B's recommendation.

The corresponding how to meet documents [1][2] were nearly identical. 
However, there were a few extra items in the 3.1.6 document that may 
require team B's consideration.

Differences:

1.) The technique titled, "Using absolute positioning based on 
structural markup" was listed as optional for 3.1.6 and sufficient for 
2.4.7.

2.) 3.1.6 included the following example:
  Example 1. A blind user uses his screen reader to read a page 
containing interactive fields.

After orienting himself to the contents of the page, he tabs through the 
interactive fields. Since some fields are disabled, not all fields occur 
in the tab sequence. However, the order in which he visits the fields is 
consistent with the order of the fields when he read the page. That is, 
if one field occurs before another in the tab order, the first preceded 
the second when reading the page.

Will leave it to you guys to figure out whether any of this needs to be 
moved to how to meet 2.4.7.

Thanks,

-Ben

[1] How to meet 2.4.7
<http://www.w3.org/WAI/GL/WCAG20/WD-UNDERSTANDING-WCAG20-20051216/Overview.html#navigation-mechanisms-focus>
[2] How to meet 3.1.6
<http://www.w3.org/WAI/GL/WCAG20/WD-UNDERSTANDING-WCAG20-20051216/Overview.html#meaning-focus>

Received on Monday, 16 January 2006 23:14:22 UTC