W3C home > Mailing lists > Public > www-svg@w3.org > October 2004

RE: mouse alternatives

From: Doug Schepers <doug@schepers.cc>
Date: Tue, 12 Oct 2004 17:30:50 -0400
To: <www-svg@w3.org>
Message-Id: <20041012213052.045C58629E@plunder.dreamhost.com>

Hi, Jonathan-

I don't believe that it's appropriate for "mouse keys" to be explicitly
defined in SVG.

However, I *do* think that it's appropriate to include a mechanism for
directional navigation, and to define a method to map keys to activities.
Given these two abilities, I think that you would have the building blocks
for such accessibility, and authors could then take matters into their own
hands. Best practices and standardized accessibility specifications can
allow the authors to produce variously accessible content.

Regards-
Doug Schepers

doug . schepers  @ vectoreal.com
www.vectoreal.com

"Move into the future..." 

Jonathan Chetwynd wrote:
| 
| 
| There has been a brief discussion on IRC#SVG, which has led to not a 
| little confusion on my part at least.
| 
| What plans are there to enable 'mouse keys' in SVG?
| By 'mouse keys' I understand the accessibility alternatives to mouse 
| navigation, that use the keyboard.
| (not just tabbing but) Moving the mouse around the screen, dragging 
| objects, shift+apple+click+drag(mac)and other mouse interactivity.
| 
| Is the WG actively engaged in ensuring that this accessibility is 
| being integrated?
| 
| Some people have expressed the view that this is an OS issue, nothing 
| to do with SVG, and that in the meantime it is up to individuals to 
| create scripts to cover these eventualities.
| 
| regards
| 
| Jonathan Chetwynd
| http://www.peepo.co.uk     "It's easy to use"
| irc://freenode/accessibility
| 
| 
Received on Tuesday, 12 October 2004 21:30:56 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 5 February 2014 23:39:55 UTC