> From: Andy Budd [...] > Guideline 2.1 Make all functionality operable via a keyboard or a > keyboard interface. > > Is this not a little subjective? For instance, if a web > browser doesn't > support tabbing between links or form elements, it's beyond the site > developers ability to do anything about it. Of course site developers can't fix broken browsers through extra markup and/or javascript kludges. I'd see these guidelines working in the context of a browser which adheres to (at least the majority of) UAAG1.0 http://www.w3.org/TR/UAAG10/guidelines.html#tech-device-independent-ui Patrick ________________________________ Patrick H. Lauke Webmaster / University of Salford http://www.salford.ac.ukReceived on Tuesday, 17 August 2004 15:26:25 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 19 July 2011 18:14:16 GMT