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

Re: SVG 1.2 Comment: Accessibility: event handling

From: Will Pearson <will-pearson@tiscali.co.uk>
Date: Thu, 18 Nov 2004 08:37:06 -0000
Message-ID: <006e01c4cd49$ed1e2920$36a3f70a@WILLXCFBVU8CQ8>
To: "Jonathan Chetwynd" <j.chetwynd@btinternet.com>
Cc: "SVG \(www\) list" <www-svg@w3.org>

Jonathan,

That seems a well phrased proposal that covers it.  You get my support 
*smile*.

Will
----- Original Message ----- 
From: "Jonathan Chetwynd" <j.chetwynd@btinternet.com>
To: "Will Pearson" <will-pearson@tiscali.co.uk>
Cc: "dean Jackson" <dean@w3.org>; "SVG (www) list" <www-svg@w3.org>
Sent: Wednesday, November 17, 2004 10:26 AM
Subject: Re: SVG 1.2 Comment: Accessibility: event handling


> Will,
>
> perhaps we could tighten up this request? how about:
>
> "Please provide generic event examples, including some keyboard examples 
> as only referring to mouse examples sets a poor standard for 
> accessibility"
>
> regards
>
> Jonathan Chetwynd
> http://www.peepo.co.uk     "It's easy to use"
> irc://freenode/accessibility
> On 17 Nov 2004, at 03:21, Will Pearson wrote:
>
>
> Hi Jonathan;
>
> The problems with scripted menus results from access technology being
> unaware that the screen has been updated by some Java script.
>
> I think, that if all changes were to be placed in the document model, and
> the SVG ua handle exploration of the SVG document, then there wouldn't be
> any problems.  This depends on how the AT got it's information, but that's
> something for the AT vendors to sort out.
>
> I do agree, that some keyboard event examples would be good.  There's a 
> lot
> of people who don't use mice for whatever reason, and keyboard navigation,
> especially for documant exploration, is a pre-requisite for accessibility.
>
> Will
> ----- Original Message -----
> From: "Jonathan Chetwynd" <j.chetwynd@btinternet.com>
> To: "SVG (www) list" <www-svg@w3.org>
> Cc: "dean Jackson" <dean@w3.org>
> Sent: Tuesday, November 16, 2004 1:25 PM
> Subject: SVG 1.2 Comment: Accessibility: event handling
>
>
>>
>> Dean,
>>
>> The continued use of mouse events in examples as for instance:
>> http://www.w3.org/TR/SVG12/painting.html#overlay-example
>> is a concern. This example particularly relevant as there has been
>> lengthy and unresolved discussions around accessible drop down lists in
>> the html/css/script communities. The example appears to assume mouse
>> skills, together with drag skills, which many find difficult to
>> impossible*.
>>
>> Would it be helpful if there was a more detailed explanation of event
>> handling in the SVG1.2 document with an example, maybe using a keyboard
>> to navigate a drop-down list?
>>
>> if so, could we please up date this and other examples to demonstrate
>> the improved XML event handling being offered?
>> http://www.w3.org/TR/SVG12/events.html#handler-element
>>
>> regards
>>
>> Jonathan Chetwynd
>> http://www.peepo.co.uk     "It's easy to use"
>> irc://freenode/accessibility
>>
>> *It is also not coherent, as one cannot make a selection, the mouse
>> must be down to see the list.
>> perhaps onmouseover, with option to click for list, with an X to
>> dismiss, and click again to select.
>> plus keyboard access.
>> drop down lists aren't a simple concept, so one cannot expect to have a
>> simple demonstration, that is accessible.
>>
>>
>>
>
>
>
> 
Received on Thursday, 18 November 2004 08:38:59 UTC

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