- From: Jim Allan <allanj@tsbvi.edu>
- Date: Thu, 04 Aug 2005 10:11:42 -0500
- To: Cathy Laws <claws@us.ibm.com>, WAU-ua <w3c-wai-ua@w3.org>
http://cita.disability.uiuc.edu/wai-eval/show-test/index.php?test_id=264 how to separate browser response from webserve message. current url exists and creates a server response of page not found. suggest changing to non-existent url www.foo.xxx, this will generate a response from the user agent. http://cita.disability.uiuc.edu/wai-eval/show-test/index.php?test_id=265 Not sure what this is supposed to do. for an existing url, the server should generate a page not found error. what does the browser do if the server does not generate a 404 (page not found) error? is there a webserver that does not generate a 404 error? http://cita.disability.uiuc.edu/wai-eval/show-test/index.php?test_id=134 link to frame page works. the actual page with frames does not include a longdesc attrib in the frame element. edit page <http://cita.disability.uiuc.edu/wai-eval/frames/frame-test.html> to add longdesc <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Frameset//EN"> <HTML> <HEAD> <TITLE>UAAG Test Suite: HTML 4.01 Frame Test Page</TITLE> </HEAD> <FRAMESET ROWS="70%, 15%, 15%"> <FRAME NAME="head" SRC="frame-target1.html" longdesc="top frame containing test link 1" TITLE="Frame Test Suite Information" SCROLLING="yes"> <FRAME NAME="target1" SRC="frame-target2.html" longdesc="middle frame containing test link 2" TITLE="Frame Test Suite Target 1" SCROLLING="yes"> <FRAME NAME="target2" SRC="frame-target3.html" longdesc="bottom frame containing test link 3" TITLE="Frame Test Suite Target 2" SCROLLING="yes"> <NOFRAMES> This test suite requires frames to be supported and enabled by your browser. Please enable frames to use this suite. </NOFRAMES> </FRAMESET></HTML> Source code div should be source code of frameset page with longdesc attributes. http://cita.disability.uiuc.edu/wai-eval/show-test/index.php?test_id=136 frames page link is incorrect, page does not exist. create new page, based on <http://cita.disability.uiuc.edu/wai-eval/frames/frame-test.html> with no title attributes. Source code div should be source code of frameset page with no title attributes. http://cita.disability.uiuc.edu/wai-eval/show-test/index.php?test_id=148 This is not a good test case because there is not a real URL for the areas. add foo1.htm and foo2.htm as href for AREA elements. Currently, the user agent may satisfy this checkpoint by rendering repair text based on any of the following available sources of information: URI reference, content type, or element type. To me URI is the value of the href on the area. Not sure what text information the content type or element type should generate. Examples might be helpful - URI reference = foo1.htm, content type =??, element type="area" Note: we may need to review all of the Results sections for ambiguity and/or adding examples. http://cita.disability.uiuc.edu/wai-eval/show-test/index.php?test_id=151 frames page link is incorrect, page does not exist. create new page. use <http://cita.disability.uiuc.edu/wai-eval/frames/frame-test.html> as basis for new page. delete title attribute for each frame. Use the same frameset page referenced in Test 136 Currently, the user agent may satisfy this checkpoint by rendering repair text based on any of the following available sources of information: URI reference, content type, or element type. To me URI is the value of the href on the area. Not sure what text information the content type or element type should generate. Examples might be: Title of target page, uri of target page, name attrib on frame element Should title of src page (e.g.. title element in head of frame-target1.html) be used as repair text? Not sure what text information the content type or element type should generate. Examples might be helpful. http://cita.disability.uiuc.edu/wai-eval/show-test/index.php?test_id=166 linked frame page is missing. link to <http://cita.disability.uiuc.edu/wai-eval/frames/frame-test.html>, it does not have a noframes element and should work fine. Currently, the user agent may satisfy this checkpoint by rendering repair text based on any of the following available sources of information: URI reference, content type, or element type. To me URI is the value of the href on the area. Not sure what text information the content type or element type should generate. Examples might be helpful. Source code div should be source code of frameset page with attributes. http://cita.disability.uiuc.edu/wai-eval/show-test/index.php?test_id=195 need a more complex table, and better explanation of the expected results. Perhaps something like - http://www.accessibleinter.net/portfolio/writing/building_accessible_tables_ example.php question: in the example above, is the colgroup element or the colgroup attribute providing the structure. should the test only focus on the element, or do we need 2 tests one for the colgroup element and one for the attribute? JAWS is not revealing the second row of TH http://www.minzweb.de/en/pages/working/tables3.html http://www.webreference.com/html/tutorial11/3.html http://cita.disability.uiuc.edu/wai-eval/show-test/index.php?test_id=225 You said "The one test is not very representative of this checkpoint." do you have a suggestion? a more complex animation? The test requires that the user be able to remap the 'esc' to some other keystroke, to stop the animation. ESC actually stops the loading of the entire page not just the animation. We need a more relevant test example. need to discuss in the group. Jim Allan, Webmaster & Statewide Technical Support Specialist Texas School for the Blind and Visually Impaired 1100 W. 45th St., Austin, Texas 78756 voice 512.206.9315 fax: 512.206.9264 http://www.tsbvi.edu/ ---> Share to Win!! <---
Received on Thursday, 4 August 2005 15:11:08 UTC