W3C home > Mailing lists > Public > www-svg@w3.org > May 2008

SVG, keyboard navigation & CSS: call for paradigm reduced testcases

From: Jonathan Chetwynd <j.chetwynd@btinternet.com>
Date: Tue, 13 May 2008 12:51:43 +0100
Message-Id: <7C78753E-C910-4F62-BF6A-E8B176B7AA4F@btinternet.com>
To: www-svg <www-svg@w3.org>
SVG, keyboard navigation & CSS:
call for paradigm reduced testcases.

parity implementing :hover and :focus

I'm concerned by the lack of keyboard navigation examples both in the  
SVG specifications and the wild.
it seems to me, that lack of attention to this detail is hampering  
development for us all.
many users prefer to navigate applications using a keyboard.
some only have this option.

in html, keyboard navigation is relatively straightforward, and where  
script is not an issue, CSS is fit for purpose.

However with SVG this is not the case.

I have struggled to create testcases with the greatest difficulty,
it seems that few browsers or AT developers are aware of the issue.

even where there is awareness the solutions are not as straightforward  
as one should expect them to be.
unless on limits oneself to the very simplest cases...

this is just one case, less than ideal, but a simple and common enough  
idea:
http://www.peepo.co.uk/temp/moulin/moulin.svg
compare the simple hover effect and code with the less successful focus.

quite possibly I missed a trick?
if not, do we need to consider how such examples can be fed back into  
the specs to ensure simple parity implementing :hover and :focus?
the least amount of surprises for the user & author while keeping  
things correct..

ie in this case something related to: hover can include the parent,  
whereas focus does not.

regards

~:"



Jonathan Chetwynd

j.chetwynd@btinternet.com
http://www.openicon.org/

+44 (0) 20 7978 1764
Received on Tuesday, 13 May 2008 11:52:51 GMT

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