W3C home > Mailing lists > Public > public-html@w3.org > January 2010

Re: Proposal: Canvas accessibility and a media querries approach for alternative content (Action Item 6 in the HTML Accessibility Task Force)

From: Steven Faulkner <faulkner.steve@gmail.com>
Date: Wed, 20 Jan 2010 13:01:37 +0000
Message-ID: <55687cf81001200501i630a49b0m15bbeaa54c726522@mail.gmail.com>
To: Henri Sivonen <hsivonen@iki.fi>
Cc: Maciej Stachowiak <mjs@apple.com>, Ian Hickson <ian@hixie.ch>, public-canvas-api@w3.org, HTML WG <public-html@w3.org>
HI henri,

>> one method of triggering the interaction for mouse users and one for
keyboard users, seems like a waste of effort?

>It seems that this sort of thing happens inevitable when the APIs become
low-level enough.
 OK, but I am trying to understand why one would do this?
if you include a link in the canvas sub dom so it will be accessible to
users, why would you duplicate the functionality using script instead of
pointing the click event on the canvas to the link?

in the end if a single method is suitable for all users its a win for all
no?

regards
stevef?

2010/1/20 Henri Sivonen <hsivonen@iki.fi>

> On Jan 20, 2010, at 14:52, Steven Faulkner wrote:
>
> > one method of triggering the interaction for mouse users and one for
> keyboard users, seems like a waste of effort?
>
> It seems that this sort of thing happens inevitable when the APIs become
> low-level enough.
>
> --
> Henri Sivonen
> hsivonen@iki.fi
> http://hsivonen.iki.fi/
>
>
>


-- 
with regards

Steve Faulkner
Technical Director - TPG Europe
Director - Web Accessibility Tools Consortium

www.paciellogroup.com | www.wat-c.org
Web Accessibility Toolbar -
http://www.paciellogroup.com/resources/wat-ie-about.html
Received on Wednesday, 20 January 2010 13:02:30 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:17:00 GMT