Re: [techs] test case review assignments

Here is the results of my action item for test case reviews.

My recommendations with more details below:
ACCEPT - All INPUT elements with a TYPE attribute value of "image" have an 
ALT attribute. 
REJECT - Alt text for all INPUT elements with a TYPE attribute value of 
"image" does not use the words "submit" or "button" (English).
ACCEPT -Alt text for all INPUT elements with a TYPE attribute value of 
"image" contains all non decorative text in the image. 
ACCEPT - Alt text for all INPUT elements with a TYPE attribute value of 
"image" identifies the purpose or function of the image. 
REJECT - INPUT control, TYPE of "text", must have valid default text. 
REJECT - Alt text for all INPUT elements with a TYPE attribute value of 
"image" is less than 100 characters (English) or the user has confirmed 
that the Alt text is as short as possible. 

Details: 

>All INPUT elements with a TYPE attribute value of "image" have an ALT 
attribute. 
>http://www.w3.org/WAI/GL/WCAG20/tests/test58.html
This test has previously been accepted by the Techniques task force (see 
the HTML test status at [1]). I don't have any changes or enhancements to 
recommend.


>Alt text for all INPUT elements with a TYPE attribute value of "image" 
does not use the words "submit" or "button" (English). 
>http://www.w3.org/WAI/GL/WCAG20/tests/test192.html
This test was put on hold by the Techniques Task Force - see discussion on 
the list:  
http://lists.w3.org/Archives/Public/w3c-wai-gl/2005JanMar/0275.html.
There were issues as to what guideline this would map to.   What appeared 
to result from this discussion (from [2]) is:
<blockquote>
OK. Test 192 "don't label your submit buttons as 'submit'" is out.

Just to be clear - the Alt text for images used as form submit buttons
is
*not* covered under the guidelines. Guideline 1.1, L1, SC1 [Note: this is 
now GL 1.1 L1 SC 2: For functional non-text content, text alternatives 
serve the same purpose as the non-text content. If text alternatives can 
not serve the same purpose as the functional non-text content, text 
alternatives identify the purpose of the functional non-text content [I] ] 
does not
apply to form submit button images. Correct?

</blockquote>

But, there was some further discussion that use of the word "submit" does 
serve the same purpose even if it is redundant.  My proposal would be to 
reject this test since it is fairly well covered under test #59 (Alt text 
for all INPUT elements with a TYPE attribute value of "image" identifies 
the purpose or function of the image.) although one could argue that the 
purpose is to "submit."  The test example at least shows functionality by 
using "search" as the alt text. There is also no technique for this so we 
would need to create one and find an appropriate mapping. 

>Alt text for all INPUT elements with a TYPE attribute value of "image" 
contains all non decorative text in the image. 
>http://www.w3.org/WAI/GL/WCAG20/tests/test193.html
This test has previously been accepted by the Techniques task force. I 
think it would be easier to understand if this test included the actual 
image file that is used in the test.  Is an image something we can include 
in a test file?  In this case, I think just a finddogs.gif that had text 
that said "Find Dogs" would be appropriate.  I think an actual image would 
be helpful for all of the tests related to input elements with a type of 
image but it is most helpful in this particular test. I'll take an action 
item to create the necessary images if the group agrees that these should 
be added.

>Alt text for all INPUT elements with a TYPE attribute value of "image" 
identifies the purpose or function of the image. 
>http://www.w3.org/WAI/GL/WCAG20/tests/test59.html
This technique has previously been accepted by the Techniques Task Force. 
I don't have any changes or enhancements to recommend.

>INPUT control, TYPE of "text", must have valid default text. 
>http://www.w3.org/WAI/GL/WCAG20/tests/test126.html
I recommend rejecting this test or at least marking it as deprecated. This 
test is for the deprecated technique of including default text in input 
type=text and textarea field. This was an "until user agents" technique 
that has been deprecated since user agents and assistive technologies now 
properly handle empty input fields.  Do we need tests for deprecated 
techniques?

In addition, this test has a prerequisite test that has been rejected by 
the Techniques task force.  If we keep this test, we should update the 
link to remove the rejected prerequisite test.  The Guideline and SC 
mapping would need to be reviewed as well since this test currently maps 
to GL 3.1 but no specific SC.  I don't think that it can be mapped to GL 
3.1 any longer. The only possibility I see is GL 3.2 L2 SC4 (Components 
that have the same functionality in multiple delivery units within a set 
of delivery units are labeled consistently. [I] ) which is still not a 
good fit. 

>Alt text for all INPUT elements with a TYPE attribute value of "image" is 
less than 100 characters (English) or the user has confirmed that the Alt 
text is as short as possible. 
>http://www.w3.org/WAI/GL/WCAG20/tests/test60.html
This technique was rejected by the Techniques Task Force since it was 
considered covered by test #3: All Alt text is short. (
http://www.w3.org/WAI/GL/WCAG20/tests/test3.html). 

[1] http://www.w3.org/WAI/GL/WCAG20/tests/checkstatus.html
[2] http://lists.w3.org/Archives/Public/w3c-wai-gl/2005JanMar/0336.html

Becky Gibson
Web Accessibility Architect
                                                       
IBM Emerging Internet Technologies
5 Technology Park Drive
Westford, MA 01886
Voice: 978 399-6101; t/l 333-6101
Email: gibsonb@us.ibm.com

Received on Wednesday, 27 July 2005 18:53:16 UTC