W3C home > Mailing lists > Public > public-html-a11y@w3.org > October 2011

[Bug 14419] when canvas isn't supported, or for blind users, the canvas element's content should be displayed, so excluding input types like text and select is discriminatory

From: <bugzilla@jessica.w3.org>
Date: Tue, 11 Oct 2011 15:48:35 +0000
To: public-html-a11y@w3.org
Message-Id: <E1RDeZH-0005wN-1t@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=14419

--- Comment #7 from James Salsman <jsalsman@gmail.com> 2011-10-11 15:48:33 UTC ---
In a text mode browser or a browser with images disabled due to user option
selection or prohibitively low bandwidth, the canvas is technically usable but
unavailable.  It is available but unusable for the blind.

> When a canvas is unusable, the fallback content is meant
> to represent the same thing as the canvas.

Where are you reading that?  It's mistaken.

> How is a text input in the fallback supposed to represent anything
> on the canvas other than a canvas-implemented text input?

For example, suppose a custom bookcase vendor asks customers to sketch their
wall and neighboring furniture configuration and locations of wall studs on a
canvas element.  Can you think of any better fallback content than a form for
their phone number and/or email so that they might be contacted by a designer?

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Tuesday, 11 October 2011 15:48:37 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 04:42:47 GMT