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

Re: Please vote on the canvas accessibility proposal

From: Ian Hickson <ian@hixie.ch>
Date: Thu, 25 Feb 2010 11:30:49 +0000 (UTC)
To: Steven Faulkner <faulkner.steve@gmail.com>
Cc: public-canvas-api@w3.org, "public-html-a11y@w3.org" <public-html-a11y@w3.org>
Message-ID: <Pine.LNX.4.64.1002251129400.1729@ps20323.dreamhostps.com>
On Thu, 25 Feb 2010, Steven Faulkner wrote:
> >All the other cases I can think of -- braille users with no vision at 
> >all, speech synth users with no vision at all, text-mode users, etc -- 
> >the statement that there is no canvas support is actually pretty 
> >accurate, though not especially kind. It'd probably be better in these 
> >cases to actually let the user know that they are missing critical 
> >functionality than to silently say nothing.
> 1. how do they know that it is critical content?
> 2. how do they know what canvas support means? how many people who use a
> browser (many peopel don't even know what a browser it) now or will in the
> future know what it means?
> 3. If they are using firefox for example, they ARE using a browser that
> supports canvas.
> 4. there is no indication that the element is missing apart from the text
> that will be encountered inline along with any other text on the page, it
> will make no sense.

Sure. That's why it's non-conforming.

But it's better to say _something_ in this case than nothing.

(It's similar to the "your browser doesn't support framesets". Who knew 
what a frameset was? Users quickly learnt that that was code for "this 
site sucks" and they went elsewhere.)

Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
Received on Thursday, 25 February 2010 11:31:18 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:05:09 UTC