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: Fri, 19 Nov 2004 22:17:33 +0100
Message-ID: <946671251.20041119221733@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 Friday, November 19, 2004, 9:15:05 PM, Jonathan wrote:

JC> Chris,

JC> I'm more than a little concerned regarding the accessibility of current
JC> SVG user agents, and question why this lack of progress is not 
JC> informing the development of the current 1.2 specification.

I'm primarily concerned with the specification, of course; and ensuring
this gives adequate direction to implementors of user agents and AT
add-ons.

JC> You state: "any pointing device which can give a position will work."
JC> this assertion is easy to make, but perhaps harder to obtain.

Well, its important to make the assertion rather that 'the events are
for mice only' for example.

JC> In a recent exchange on irc:mozilla/svg it was suggested that "svg1.1
JC> does not specify key events", which in it's way is true.

Its certainly true. Its not just 'suggested'.

JC> (the implication being that therefore it is not a requirement.)
JC> UAAG states:  " Ensure that the user can operate, through keyboard 
JC> input alone, any user agent functionality available through the user
JC> interface" .

Again, you are mixing up specifications and user agents.

JC> This may partly be explained by the rather ineffective: "an SVG user
JC> agent should conform to UAAG." - should - may have been intended as 
JC> sufficient, but in this instance the flesh is weak, as we are now some
JC> years late.
JC> asv is no better, as the transition from browser to viewer is broken,
JC> and the number of keyboard navigable pages ~=0.
JC>   - It maybe that there are other UA that have keyboard access, please
JC> advise me. -

As you correctly observe, SVG 1.0/1.1 has *no* keyboard events, because
the DOM2 keyboard events were removed from he DOm specification due to
being hopelessly broken from an internationalization point of view and
thus inaccessible to most of the world population.

SVG 1.2 uses DOM3 events, which

a) do give keyboard  and text access
b) are well internationalised
c) abstract out the inpt device from the text it produces and this,
allow alternative accessible input devices to easily fit in with
unchanged content.

Perhaps you could tell *us* about some accessibility aids that function
via the DOM, or even get some manufacturers of such devices interested
in

JC> The significant change in event handling is not reflected in the 
JC> current UAAG or indeed the overdue SVG Accessibility AT and UA 
JC> guidelines. Does the 1.2 specification indicate the significance of 
JC> accessibility in an appropriate manner, given the response to the 1.1
JC> guidelines, bearing in mind the lack of progress on updating these 
JC> accessibility guidelines.

Not sure what you are trying to say there.

JC>  It isn't possible to refer to them, because
JC> they don't exist, and furthermore there haven't been usability studies
JC> to inform their development.

I'm fairly sure that devices such as head-mounted pointers, eye
trackers, etc exist having seen videos of them in use. If they can give
a screen position, thats all that is needed.


-- 
 Chris Lilley                    mailto:chris@w3.org
 Chair, W3C SVG Working Group
 Member, W3C Technical Architecture Group
Received on Friday, 19 November 2004 21:17:34 UTC

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