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 16:09:57 +0000
To: public-html-a11y@w3.org
Message-Id: <E1RDetx-0006mp-7e@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=14419

--- Comment #8 from Tab Atkins Jr. <jackalmage@gmail.com> 2011-10-11 16:09:56 UTC ---
(In reply to comment #7)
> > 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.

The spec.
<http://www.whatwg.org/specs/web-apps/current-work/multipage/the-canvas-element.html#the-canvas-element>

"When authors use the canvas element, they must also provide content that, when
presented to the user, conveys essentially the same function or purpose as the
bitmap canvas. This content may be placed as content of the canvas element. The
contents of the canvas element, if any, are the element's fallback content."

-- 
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 16:10:04 GMT

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