- From: Frank Olivier <franko@microsoft.com>
- Date: Fri, 22 Jan 2010 19:40:56 +0000
- To: James Craig <jcraig@apple.com>, Richard Schwerdtfeger <schwer@us.ibm.com>
- CC: Ian Hickson <ian@hixie.ch>, "public-canvas-api@w3.org" <public-canvas-api@w3.org>, HTML WG <public-html@w3.org>
The 'DOM/content attribute (media="screen, audio, etc")' seems like the best approach to me...The easiest authoring pattern here IMO is: 1. Write HTML that contains canvas, with 'canvas not supported' fallback content. 2. At runtime, in script, clear the 'canvas not supported' fallback content, and replace it with one or more a11y-fallback nodes, each tagged with the modality/modalities they support. (No duplication of a11y content) Thanks Frank From: public-html-request@w3.org [mailto:public-html-request@w3.org] On Behalf Of James Craig Sent: Thursday, January 21, 2010 11:37 AM To: Richard Schwerdtfeger Cc: Ian Hickson; public-canvas-api@w3.org; HTML WG Subject: Re: Canvas Accessibility Next steps On Jan 20, 2010, at 8:48 PM, Richard Schwerdtfeger wrote: I revised my original proposal to accommodate your request to use media queries as the selection mechanism so that it would be aligned with David Singer's proposal for video and audo tags. This may fit better into the media queries approach if it's defined in CSS (@media) or as a DOM/content attribute (media="screen, audio, etc") instead of the media-specific elements (<visual>, <audio>) suggested in the most recent version of the proposal.
Received on Friday, 22 January 2010 19:43:39 UTC