- From: Jon Gunderson <jongund@uiuc.edu>
- Date: Thu, 20 Feb 2003 11:16:41 -0600 (CST)
- To: Catherine Laws <claws@us.ibm.com>
- cc: <w3c-wai-ua@w3.org>
Thanks for your great comments on the test suites! I will update the test suite issues list [1] with these comments. This list is public. Jon [1] http://www.w3.org/WAI/UA/2002/12/issues-ts-html On Thu, 20 Feb 2003, Catherine Laws wrote: > > > > > > Jon, > > I have reviewed the test suites for Checkpoints 1.1 and 1.2 and have the > following comments/issues: > > General test suite comments: > > - If we have written sample testcases to test compliance with specific > checkpoints, do you want us to send them to someone, or are your students > at the University of Illinois or Colin Koteles writing all the test cases? > > - Have your students at the University of Illinois created a list of > comments about the test suites? If so, is that list published somewhere for > review? If not, could it be? > > Checkpoint 1.1 Full Keyboard Access > > Additional ACCESSKEY test cases could be written for LABEL, LEGEND, and MAP > AREAS. I have the same comment for Checkpoint 11.2 - Current author input > configuration. The same testcases could be used for both checkpoints, > especially if you combine some of the accesskey tests together. > > The FRAMESET test is not self-contained on the test page, and there is no > source for the individual frames. So a tester would still have to create > more HTML to run the test. > > Additional TABINDEX testcases could be written for AREA, BUTTON, OBJECT, > SELECT, and TEXTAREA. > > Changing Text Size test - how does it show compliance with Checkpoint 1.1? > > > Checkpoint 1.2 Activate event handlers > > ONCHANGE attribute for SELECT elements test - When the star color is > selected in the select menu, the graphic changes to the right color, but > the corresponding alt text always says "red star". The Javascript function > should also change the alt text for the test to make sense and to be an > accessible test. > > ONFOCUS and ONBLUR tests could be written for SELECT elements. > > ONCLICK and ONDBLCLICK tests should be written for some normally > activatable elements (A, AREA, INPUT of all types, BUTTON, TEXTAREA, > SELECT, OBJECT, OPTION) plus a few other types of non-activatable elements > in addition to IMG, like H1, TD, TH, or LI. > > For ONMOUSEOVER, ONMOUSEOUT tests, the tester should be able to hear > something different as well as see something different for the mouseover > event. For example, the alt text could also change when the "Lamp is > turned on." A pop-up menu is a more common and useful example, and there > should be onmouseover event tests for some normally activatable elements > (A, AREA, INPUT of all types, BUTTON, TEXTAREA, SELECT, OBJECT, OPTION) > plus other types of non-activatable elements in addition to IMG, like H1, > TD, TH, or LI. There should also be a test for ONMOUSEMOVE. > > There should be tests for ONKEYPRESS, ONKEYDOWN, and ONKEYUP. > > > Cathy Laws > > IBM Accessibility Center, WW Strategic Platform Enablement > 11400 Burnet Road, Bldg 903 Office 5B004, Austin, Texas 78758 > Phone: (512) 838-4595, FAX: (512) 838-9367, E-mail: claws@us.ibm.com, Web: > http://www.ibm.com/able > > Let us run with perserverence the race that is set before us. >
Received on Thursday, 20 February 2003 12:16:44 UTC