- From: Charles McCathieNevile <charles@w3.org>
- Date: Mon, 23 Apr 2001 15:49:53 -0400 (EDT)
- To: David Woolley <david@djwhome.demon.co.uk>
- cc: <w3c-wai-ig@w3.org>
In my opinion there is a problem with the way access keys are specified - basically they require the browser to do some work that almost no browser does (iCab is one exception, and there are ways of using CSS to get other browsers to be a bit more forthcoming) because it doesn't actually say that anywhere in the spec. This is (I think) treated in the User Agent Guidelines. Which are in Last call, so if anyone is reviewing and looking for things to think about... http://www.w3.org/TR/UAAG10 cheers Chaals On Mon, 23 Apr 2001, David Woolley wrote: > PSS Perhaps XHTML needs a tags or attributes for textual information? With Access Keys you have a problem that they won't be fully supported until fully used and one of the factors in their not being fully used is they aren't fully supported. However, it seems to me that there is a fairly obvious way of labelling their function in HTML: put a title attribute on the element that is accessed by the key. It's then up to the browser to provide a table of access keys from this information. In this case, there seems little conflict with the perception that title always means a "tool tip" pop up display. -- Charles McCathieNevile http://www.w3.org/People/Charles phone: +61 409 134 136 W3C Web Accessibility Initiative http://www.w3.org/WAI fax: +1 617 258 5999 Location: 21 Mitchell street FOOTSCRAY Vic 3011, Australia (or W3C INRIA, Route des Lucioles, BP 93, 06902 Sophia Antipolis Cedex, France)
Received on Monday, 23 April 2001 15:49:59 UTC