A Few Comments on the Latest Draft

These criteria are brilliantly written; thanks to each and every one of you
who had a hand in crafting them.  Just a few minor comments.


Criterion 2.2.1 Timing, contains the sentence:
"Essential Exception: the time limit is part of an activity where timing is
essential (for example, time-based testing) and time limits can not be
extended further without invalidating the activity."

In many instances, the time requirement for normally time-sensitive
activities such as time-based testing is waived for individuals with
disabilities to compensate for the interface inefficiencies of assistive
technology.  Consider adding a qualifying sentence explaining that this
exception shall not apply to a normally time-sensitive activity when the
time requirement has been waived for individual(s) with disabilities.


For the criterion "2.4.1 Bypass Blocks: A mechanism is available to bypass
blocks of content that are repeated on multiple Web pages," consider adding
a qualifying phrase such as: "unless these blocks of content constitute the
bottom of the web page."  I have seen developers use skip navigation links
for skipping repeated navigation bars which serve as page footers.  This
results in confusing and superfluous page elements.


In Criterion "2.4.4 Link Purpose (Context): The purpose of each link can be
determined from the link text and its programmatically determined link
context," I believe the "and" should be changed to "or."  By keeping it as
"and," this would effectively prohibit the use of links such as "more," and
"click here," as they could never meet both qualifiers.  In other words, the
purpose for these links could never be determined from the "link text" thus
making the "and" an impossible bar.  The use of "or" would allow for either
test to suffice and include conformance with both as well.


For all of the following criteria, please consider making them Level A
instead of AA unless there are compelling reasons not to do so.

3.2.3 Consistent Navigation: Navigational mechanisms that are repeated on
multiple 
Web pages within a set of Web pages occur in the same relative order
 each time they are repeated, unless a change is initiated by the user.
(Level AA)

3.2.4 Consistent Identification: Components that have the same functionality
 within a set of Web pages are identified consistently. (Level AA) 

3.3.3 Error Prevention (Legal, Financial, Data): For forms that cause 
legal commitments or financial transactions to occur, that modify or delete 
user-controllable data in data storage systems, or that submit test
responses, at least one of the following is true: (Level AA) 

list of 3 items
1. Reversible: Transactions are reversible. 

2. Checked: Submitted data is checked for 
input errors before going on to the next step in the 
process. 

3. Confirmed: A mechanism is available for reviewing, confirming, and
correcting information before finalizing the transaction. 

list end

3.3.4 Labels or Instructions: 
Labels or instructions are provided when content requires user input. (Level
AA) 

3.3.6 Error Prevention (All): For forms that require the user to submit
information, at least one of the following is true: (Level AAA) 

list of 3 items
1. Reversible: Transactions are reversible.

2. Checked: Submitted data is checked for 
input errors before going on to the next step in the 
process.

3. Confirmed: A mechanism is available for reviewing, confirming, and
correcting information before finalizing the transaction.

list end

Received on Sunday, 27 May 2007 19:12:37 UTC