- From: Jonathan Chetwynd <j.chetwynd@btinternet.com>
- Date: Wed, 7 Feb 2007 18:40:28 +0000
- To: Chris Lilley <chris@w3.org>
- Cc: Cameron McCormack <cam@mcc.id.au>, SVG List <www-svg@w3.org>
Chris & Cameron, cheers for your responses, I don't spend enough time with the specs, and was a little concerned... cheers Jonathan Chetwynd On 7 Feb 2007, at 14:05, Chris Lilley wrote: On Wednesday, February 7, 2007, 10:51:50 AM, Jonathan wrote: JC> The SVG 1.2 description of keyboard events appears very terse, it's JC> copied below. JC> Is there a further enlarged description? for instance describing JC> tabbing through focusable elements? JC> 13.6 Key events JC> http://www.w3.org/TR/SVGMobile12/interact.html#KeyrEvents JC> Note: The W3C's Web Content Accessibility Guidelines (WCAG) advise JC> content creators to create device-independent content; in particular, JC> content should not require that the user has access to a (full-size) JC> keyboard. JC> User interface events that occur because of user actions that JC> generate key presses (as opposed to text - for example, function JC> keys, key presses for a game, etc) are called key events. You are right, its very terse - its intended as a reference, not a definition. And you are also correct that there is nowhere listed to find a fuller description. We should change "key events" to "key events, described in the [DOM Level 3 Events] specification." where the square brackets denote a link anchor as with other references. -- Chris Lilley mailto:chris@w3.org Interaction Domain Leader Co-Chair, W3C SVG Working Group W3C Graphics Activity Lead Co-Chair, W3C Hypertext CG
Received on Wednesday, 7 February 2007 18:40:45 UTC