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


Can you explain why Scalable Vector Graphics (SVG) Full 1.2 (draft) 
**  currently makes no mention of accessibility?
As a core feature, where is the appendix?

SVG has the potential to develop and enrich the meaning of  
accessibility. This is particularly relevant as WCAG 2 has recently  
recognised the value of alternatives to text. Navigation and game  
play offer vast uncharted reefs:

Navigation: Is it wise to force users (and authors) to think?

The various HTML standards such as underlining and highlight borders  
have been foregone, yet where is their replacement in the  
accessibility documentation?

If only a single element has focus at a given time, and focus moves  
from one element to another by various events including keyboard  
events and pointer events.
Will this break the expected behaviour of the browser for users? ,  
and should this be mentioned, so that other user agents adapt?

Game play: Please read, consider, link and contribute to, The  
International Game Developers Association Accessibility SIG: http://

Finally, does the statement "This appendix is informative, not  
normative." contradict the assertion that "Accessibility is not an  
optional extension" ?

I hope to respond in more detail some time soon!

thanks for your patience once again

Jonathan Chetwynd
Accessible Solutions

**This was my original question as per subject line, please note I  
did not refer to either SVGMobile12  or SVG Tiny 1.2


On 29 Nov 2005, at 20:00, Chris Lilley wrote:

Accessibility is a core feature - it is therefore described in the core
SVG Tiny 1.2 specification. Accessibility is not an optional extension.

Received on Tuesday, 29 November 2005 22:27:29 UTC