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

Re: Canvas Accessibility Next steps

From: James Craig <jcraig@apple.com>
Date: Tue, 19 Jan 2010 14:31:56 -0800
Cc: Ian Hickson <ian@hixie.ch>, public-canvas-api@w3.org, HTML WG <public-html@w3.org>
Message-Id: <DCBCB65C-39AD-4ACD-9443-78BA39EA8420@apple.com>
To: Richard Schwerdtfeger <schwer@us.ibm.com>
On Jan 19, 2010, at 11:40 AM, Richard Schwerdtfeger wrote:
> So, we would like the spec to allow for shadow DOM binding to canvas where that is possible and for the ability to use CSS Media Queries to choose alternative content. This means the DOM elements between the <canvas> </canvas> tags must not be used for fallback content but rather it be used for content for the accessible binding of a shadow DOM to the canvas drawing region and for alternative content: 
> 
Was this proposal discussed on the list or just in the call? If it was on the public-canvas-api list, I apologize for missing it. If it was on the call, please clarify the pronoun "we", as there were no attendees listed in the log, and it sounds like you've declared consensus. Even though there is no official group for canvas accessibility, accepted W3C procedure is that proposals of this nature should still be discussed through the email list at least 48 hours prior to declaring consensus.
> such as:
> 
> <canvas>
> <default> /!-- we can chose a different tag name --/
> </devault>
> <visual css media query properties used to select a particular alternative modality rendering based on IMS Global Learning Consortium Access For All content>
> </visual>
> <visual>
> </visual>
> <audio> /!-- this is a possibility for some users --/ 
> <audio> 
> </canvas> 
> 
> Yes, this requires the addition of a <visual> modality tag. At this point is agreed upon we are at a stalemate on producing spec. ready content to address canvas accessibility.
> 
Declaring a modality-specific tag name–such as visual or audio–seems like a bad idea. If an author would like their fallback content to be available to both modalities, this proposal will force them to duplicate that content, putting excess burden on the developer. 

James
Received on Tuesday, 19 January 2010 22:40:24 GMT

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