W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > April to June 2009

Use of Canvas tag and loading alternate templates

From: Stephani L. Roberts <stephani@MIT.EDU>
Date: Tue, 2 Jun 2009 14:09:51 -0400
Message-Id: <p06230910c64492692dd1@[]>
To: w3c-wai-ig@w3.org

We have a project here at MIT that may potentially be used by a large 
number of people on our campus. The designer intends to use the 
Canvas tag quite heavily. It's not clear yet if this is mainly to 
depict charts and graphs or if simply for "cool looking buttons". 
Either way, we need a strategy to make the application as accessible 
as possible without going so far as to say that  that they must not 
use the Canvas tag.

I've read the recent posts about ideas for how to make use of the 
Canvas tag more accessible. All great ideas, but also a lot of work 
that's possibly not worth if for this type of content. With Web 2.0 
content re-purposing (re-publishing), we were thinking that this 
financial the data might be better served to screen readers in a 
clean simplified format via more accessible template (only the 
presentation layer template would be different, all data is the 
same). We considered doing this via a link to a "simplified 
accessible version" or  an "enhanced accessibility version" to help a 
screen reader or other assistive technology.

Has anyone taken this approach when they've had to work around the 
Canvas tag? If so, how successful was it? Any thoughts about your 
approach, stumbling blocks, etc would be helpful.



Stephani L. Roberts
Web Accessibility Consultant - MIT  IS&T  ATIC Lab
building: n42-240k
phone: 253.0866

cell: 617.852.3100
email: stephani@mit.edu

Important: MIT IS&T staff will *NEVER* ask you for
your password, nor will MIT send you email
requesting your password information.
Received on Tuesday, 2 June 2009 18:10:31 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:36:33 UTC