Re: CAREFUL CRITICAL review of the Annotated Checklist

At 07:37 2/06/2006, Gregg Vanderheiden wrote:
<blockquote>
The annotated checklist gives us (and everyone else when we release it) a 
very easy way to evaluate our success criteria and proposed techniques.

I would like people from each Task force to take the success criteria that 
they are assigned and
- look over the annotated checklist very carefully.
- pretend you are a harsh critic. – Rip up what we have.  Find the holes.

Releasing this can make our guidelines understandable and usable – but that 
can be overshadowed if we have obvious holes in it as well.
Even if you know it is solid – if you think it could look like it has holes 
– or could be misunderstood – point that out.

Do your worst. Please do it immediately.
</blockquote>

This is a very useful resource.

I have the following comments.

I opened the page in Amaya 9.0, which found a well-formedness issue at line 
52, char 128: the closing tag of the label for "Level 3?" misses the final ">".

The heading for sufficient techniques for each success criterion contains 
the text "For technology types: ..., Programming (Java, Flash, etc), ...". 
Would "applets" be more appropriate than "Programming"? (See definition of 
applets in Wikipedia: http://en.wikipedia.org/wiki/Applet)

For SC 2.2.1, the code for the checkbox got mixed up: it is currently
<input name="sc221" id="sc221" value="SC 2.2.1">
instead of
<input name="sc221" id="sc221" value="SC 2.2.1" type="checkbox">
(i.e. the type attribute is missing)

When comparing the titles of the techniques, I found a mixture of singular 
and plural. Compare for example "Providing a text alternative for the area 
element" (singular forms) with "Using alt attributes on images used as 
submit buttons" (plurals).
I would prefer singular when that is appropriate, but changing this would 
affect many techniques and failures. Below are the proposed singular forms.

F2: Failure of SC 1.3.1 and 1.3.4 due to using CSS to create a variation in 
presentation of text that conveys information without also using the 
appropriate markup or text
F3: Failure of SC 1.1.1 due to using CSS to include an image that conveys 
important information
F15: Failure of SC 4.1.2 due to implementing a custom control that does not 
use an accessibility API for the technology, or does so incompletely
F20: Failure of SC 1.1.1 and 4.1.2 due to not updating a text alternative 
when a change to non-text content occurs
F22: Failure of SC 3.2.5 due to opening a windows that is not requested by 
the user
F24: Failure of SC 1.4.1 due to specifying a foreground color without 
specifying a background color or vice versa
F30: Failure of SC 1.1.1 due to using a text alternative that is not an 
alternative (e.g. filename or placeholder text)
F42: Failure of SC 1.3.1 due to using a scripting event to emulate a link
F54: Failure of SC 2.1.1 due to using only a pointing-device-specific event 
handler (including gesture) for a function
F28: Failure of SC 2.2.1 due to using a server-side technique to 
automatically redirect a page after a time-out

G88: Providing a descriptive title for a Web unit
G96: Providing textual identification of an item that otherwise relies only 
on shape and/or position to be understood
G103: Providing a visual illustration of a complex idea, an event, or a process
G107: Using "activate" rather than "focus" as a trigger for a change of context
G117: Using text to convey information that is conveyed by a variation in 
presentation of text
G122: Including a text cue whenever a color cue is used
G128: Indicating current location within a navigation bar

H28: Providing the definition for an abbreviations by using the abbr or the 
acronym element
H30: Providing link text that describes the purpose of a link for an anchor 
element (or: ... for each anchor element ?)
H32: Providing a submit button
H35: Using the alt attribute on the applet element
H36: Using the alt attribute on an image used as submit button
H37: Using the alt attribute on the img element
H39: Using the caption element to associate a caption with a data table
H40: Using a definition list
H43: Using id and headers attributes to associate data cells with header 
cells in a data table
H44: Using the label element to associate a text label with a form control
H28: Using the lang attribute to identify a change in the natural language
H63: Using the scope attribute to associate header cells and data cells in 
a data table
H65: Using the title attribute to identify a form control when the label 
element cannot be used
H69: Providing a Heading element at the beginning of each section of content
H70: Using the frame element to group blocks of repeated material
H71: Providing a label for a group of radio buttons or checkboxes using the 
fieldset and legend elements
H73: Using the summary attribute of the table element to give an overview 
of a data table

SCR22: Using a script to control blinking and stop it in three seconds or 
less (or: Using script ...)

SVR1: Implementing an automatic redirect on the server side instead of on 
the client side


Future links:
SC 1.4.2: Playing sound only on user request (future link)
SC 1.4.2: Providing a control near the top of the Web unit that turns off 
sound that plays automatically (future link) [but we could leave it in 
plural to stress that the control should turn off all sounds in the content]
SC 2.2.2: Setting each animated gif image to stop blinking after n cycles 
(within 3 seconds) (future link)
SC 2.5.4: Providing a help bubble (future link)
SC 3.1.5: Providing a sign language version of information, an idea, or a 
process that must be understood in order to use the content (future link)
SC 4.1.2: Using XHTML role, state, and value attributes if repurposing a 
static element as interactive user interface component (future link)
SC 4.2.1: Providing a link to an alternative along with an explanation of 
the purpose of that link (future link)

In one cases, punctuation needs to be fixed:
F39: Failure of SC 1.1.1 due to providing a text alternative that is not 
null (e.g. alt="spacer" or alt="image") for an images that should be 
ignored by AT


Regards,

Christophe


-- 
Christophe Strobbe
K.U.Leuven - Departement of Electrical Engineering - Research Group on 
Document Architectures
Kasteelpark Arenberg 10 - 3001 Leuven-Heverlee - BELGIUM
tel: +32 16 32 85 51
http://www.docarch.be/ 


Disclaimer: http://www.kuleuven.be/cwis/email_disclaimer.htm

Received on Wednesday, 7 June 2006 11:01:45 UTC