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: Richard Schwerdtfeger <schwer@us.ibm.com>
Date: Fri, 22 Jan 2010 16:36:17 -0600
To: Steven Faulkner <faulkner.steve@gmail.com>
Cc: Ian Hickson <ian@hixie.ch>, public-canvas-api@w3.org, HTML WG <public-html@w3.org>, public-html-request@w3.org
Message-ID: <OF7AFE229C.E3223E7F-ON862576B3.006069B9-862576B3.007C2BEE@us.ibm.com>
Agreed. Fallback would assume it is rendered without the need of things 
like CSS. That is not the case. 

Rich Schwerdtfeger
Distinguished Engineer, SWG Accessibility Architect/Strategist



Steven Faulkner <faulkner.steve@gmail.com> 
Sent by: public-html-request@w3.org
01/21/2010 07:22 AM

To
Ian Hickson <ian@hixie.ch>
cc
public-canvas-api@w3.org, HTML WG <public-html@w3.org>
Subject
Re: Proposal: Canvas accessibility and a media querries approach for 
alternative content (Action Item 6 in the HTML Accessibility Task Force)






Hi Ian,
in light of the discussion on the canvas subdom, i don't think the
spec, especially use of the term "fallback" accurately reflects the
use the subdom can be put to.

can you change it so it no longer usese this term or defines when the
content of the subdom can be considered 'fallback' and when it isn't
'fallback'

if not I will file a bug.

regards
steve
Received on Friday, 22 January 2010 22:36:59 GMT

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