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

Re: SVG 1.2 Comment: Accessibility: event handling

From: Chris Lilley <chris@w3.org>
Date: Sat, 20 Nov 2004 15:01:34 +0100
Message-ID: <22106171.20041120150134@w3.org>
To: Jonathan Chetwynd <j.chetwynd@btinternet.com>
Cc: "Will Pearson" <will-pearson@tiscali.co.uk>, "SVG (www) list" <www-svg@w3.org>, "dean Jackson" <dean@w3.org>

On Saturday, November 20, 2004, 9:35:08 AM, Jonathan wrote:


JC> Chris,

JC> unfortunately I've not expressed myself sufficiently well, which is an
JC> habitual problem.

And you seem not to have understood how some of the points I was making
answered your questions, while also not really answering mine.


JC> Whilst the specification fails to take account of the needs of keyboard
JC> users, Authors create user agents

Authors create content - are you talking about content authors o UA
creators here?

JC> that fail to be usable via the 
JC> keyboard, and yet claim they are for instance SVG1.1 compliant.

Since I pointed out that SVG 1.2 *does not have* keyboard events,
content authors are unable to use them. is that direct enough?

Creators of user agents, on the other hand, can hook up whatever devices
they wish to the pointer events, including keyboards. They just have to
use system facilities to do it, and can't expose the keyboard via the
DOM.

SVG 1.2 (to try and keep this on topic) fixes that, and adds the
missing keyboard events.

JC> We are then in the unfortunate position that not only are these UA not
JC> accessible, but furthermore there is no usability or accessibility 
JC> information generated for the next specification.

I'm unable to get the two halves of that sentence to relate to one
another.

JC> Please bear in mind that it was 'feedback' that led to the the change
JC> in event handling you refer to.
JC> The international community, would be expected to have a stronger voice
JC> than the disabled community.

Yes, as I said, it was feedback that led to DOM2 keyboard eventsbeing
withdrawn.

JC> You failed to address my query as to whether there is a  UA that is 
JC> keyboard accessible, though I would expect there are some.

And you failed to address my query about AT that use the DOM - so I
can't answer your question.

JC> regarding the UAAG, surely if keyboards events  are hopelessly broken,

They are not 'hopelessly broken'. In 1.1 they are simply not there
at all, and in 1.2, they are there and not broken.


-- 
 Chris Lilley                    mailto:chris@w3.org
 Chair, W3C SVG Working Group
 Member, W3C Technical Architecture Group
Received on Saturday, 20 November 2004 14:01:35 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 5 February 2014 07:14:52 UTC