W3C home > Mailing lists > Public > public-comments-wcag20@w3.org > April 2009

RE: Technique G167

From: Andrew Kirkpatrick <akirkpat@adobe.com>
Date: Tue, 28 Apr 2009 13:15:03 -0700
To: Phill Jenkins <pjenkins@us.ibm.com>, "public-comments-wcag20@w3.org" <public-comments-wcag20@w3.org>
Message-ID: <5076E68FCD2E91428C2479984A81E1147B37B069EB@NAMBX01.corp.adobe.com>
Believe it means verify that they are visually adjacent and programmatically adjacent.  Form control labels need to be programmatically associated but may be visually separated, but in this case it is important for there to be both visual and programmatic tests to ensure success for visually impaired and sighted users.

Thanks,
AWK

Andrew Kirkpatrick

Senior Product Manager, Accessibility

Adobe Systems

akirkpat@adobe.com<mailto:akirkpatrick@adobe.com>

From: w3c-wai-ig-request@w3.org [mailto:w3c-wai-ig-request@w3.org] On Behalf Of Phill Jenkins
Sent: Tuesday, April 28, 2009 4:06 PM
To: public-comments-wcag20@w3.org
Cc: w3c-wai-ig@w3.org
Subject: Technique G167


Referring to the Testing procedures for General Technique G167
        G167: Using an adjacent button to label the purpose of a field
        http://www.w3.org/TR/2008/NOTE-WCAG20-TECHS-20081211/G167

Tests
Procedure

For a field and a button using this technique:
1.        Check that the field and button are adjacent to one another in the programmatically determined reading sequence.
2.        Check that the field and button are rendered adjacent to one another.

Expected Results

 *   All checks are true.

My questions are:
What is the difference between bullet 1 and 2?  Both seem to be trying to determine that the input field and button are adjacent to each other.  To me, programmatically determining the reading sequence is the same as determining how they are rendered. In other words - "programmatically determined reading sequence" is a definition for "rendering".  Checking that they are rendered adjacent to each other can be done by walking through the code as a human or using a user agent to execute the code - but that is ONE test procedure with a manual or machine method.  We should NOT have test procedures saying to run an automated test tool and a second test procedure saying to inspect the code manually.  I ask my self, how can they be programmatically determined to be next to each other and not be rendered adjacent to each other, except there are bugs in the  user agent?

Is there some other intended difference between these two bullets by the author or working group?  otherwise I think they should be combined into one test procedure.

For a field and a button using this technique:
1.        Check that the field and button are adjacent to one another when rendered (i.e., programmatically determined reading sequence).

Expected Results

 *   All checks are true.

Regards,
Phill Jenkins,
Received on Tuesday, 28 April 2009 20:16:24 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Sunday, 17 July 2011 06:13:27 GMT