- From: Charles McCathieNevile <charles@w3.org>
- Date: Sat, 6 Mar 1999 22:01:04 -0500 (EST)
- To: Al Gilman <asgilman@iamdigex.net>
- cc: WAI UA group <w3c-wai-ua@w3.org>
I think this is covered by "make alternative content available", allow the user to navigagte among active elements (links, form controls, elements with associated event triggers)" and "allow the user to navigate the DOM tree". But Your point is well taken - I will think about this a bit longer. Charles McCathieNevile On Sat, 6 Mar 1999, Al Gilman wrote on the question of whether searching for attribute values was a priority 1 capability, after I had said it probably wasn't: This capability may be more critical than it at first appears. The critical failure in Lynx was when people could not find SUBMIT buttons even though they clearly said SUBMIT in the rendered text. It turns out that the text 'SUBMIT' was not content but an element attribute. Anything that is going to show should be included in the text which can be found by a search. I don't know how to reword the checkpoint right away but this is the capability that may yet merit Priority 1. Al --Charles McCathieNevile mailto:charles@w3.org phone: +1 617 258 0992 http://purl.oclc.org/net/charles W3C Web Accessibility Initiative http://www.w3.org/WAI MIT/LCS - 545 Technology sq., Cambridge MA, 02139, USA
Received on Saturday, 6 March 1999 22:01:08 UTC