- From: John M Slatin <john_slatin@austin.utexas.edu>
- Date: Tue, 17 Jan 2006 07:43:00 -0600
- To: "Ben Caldwell" <caldwell@trace.wisc.edu>, <public-wcag-teamb@w3.org>
Let's include Ben's message in our review of SC 2.4.7. Sounds like we need to do the following: 1. Determine whether the technique he mentions really is sufficient to meet SC 2.4.7 (if not, make a recommendation to the WG and incljde in survey) 2. Decide if the example (included below) should be added to the examples (or used to replace something that's currently there) Thanks. John "Good design is accessible design." Dr. John M. Slatin, Director Accessibility Institute University of Texas at Austin FAC 248C 1 University Station G9600 Austin, TX 78712 ph 512-495-4288, fax 512-495-4524 email jslatin@mail.utexas.edu Web http://www.utexas.edu/research/accessibility -----Original Message----- From: public-wcag-teamb-request@w3.org [mailto:public-wcag-teamb-request@w3.org] On Behalf Of Ben Caldwell Sent: Monday, January 16, 2006 5:14 PM To: public-wcag-teamb@w3.org Subject: 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/Overvi ew.html#navigation-mechanisms-focus> [2] How to meet 3.1.6 <http://www.w3.org/WAI/GL/WCAG20/WD-UNDERSTANDING-WCAG20-20051216/Overvi ew.html#meaning-focus>
Received on Tuesday, 17 January 2006 13:43:09 UTC