W3C home > Mailing lists > Public > www-svg@w3.org > November 2005

SVG1.2: Where is the Accessibility Appendix & keyboard navigation

From: Jonathan Chetwynd <j.chetwynd@btinternet.com>
Date: Tue, 29 Nov 2005 11:13:06 +0000
Message-Id: <D50F53CA-22DF-49DC-855A-A6A1F0187109@btinternet.com>
Cc: Charles McCathieNevile <chaals@opera.com>, chris@w3.org
To: www-svg@w3.org

Where is the Accessibility appendix? the update from Appendix H:  
http://www.w3.org/TR/SVG11/access.html

What action is being taken to ensure that SVG1.2 specification does  
not assume "mouse" skills?

For instance -- 16.4 Processing order for user interface event
http://www.w3.org/TR/2004/WD-SVG12-20041027/events.html
is littered with references to pointers and mice.

Is there a (planned?) requirement that SVG viewers should support  
keyboard navigation?
After more than 2 years wrangling firefox 1.5 now supports focus and  
blur as script events
https://bugzilla.mozilla.org/show_bug.cgi?id=259062 **

There should be a default means of navigating any SVG document  
without requirement of script support.
http://www.peepo.co.uk/index.svg is keyboard navigable but requires  
scripting.

regards

Jonathan Chetwynd
Accessible Solutions
http://www.eas-i.co.uk

**in particular:

Accessibility is a significant part of compliance, please read the 1.1
specification and User Agent guidelines:

http://www.w3.org/TR/SVG11/access.html
"To conform to the SVG specification, an SVG user agent should  
conform to UAAG. "

http://www.w3.org/TR/UAAG10/guidelines.html#gl-device-independence
" Ensure that the user can operate, through keyboard input alone, any  
user agent
functionality available through the user interface"
"While this document only requires keyboard operation for  
conformance, it
promotes input device independence by also allowing people to claim  
conformance
for full pointing device support or full voice support."
"The user may have to operate the user interface with a variety of  
input devices
(e.g., keyboard, pointing device, and voice input) and output  
modalities"

so it can be said the specs do require keyboard functionality.

as a minimum it is clear that some means of navigation, (frequently  
'tab' and
'enter') is a requirement
Received on Tuesday, 29 November 2005 11:13:17 GMT

This archive was generated by hypermail 2.3.1 : Friday, 8 March 2013 15:54:32 GMT