W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > January to March 2014

implementing Canvas to assure accessibility

From: Jennifer Sutton <jsuttondc@gmail.com>
Date: Sun, 09 Mar 2014 20:34:22 -0700
Message-Id: <>
Message-Id: <>
To: "w3c-wai-ig-w3.org":;
Greetings, WAI-IG:

I posted a message similar to this one to the WebAIM list on February 
27, but I didn't receive any answers to the thread:

So, I'm slightly modifying my message and posting here, in hopes of 
gathering input.

I'm wondering if involved parties could offer the list an update on 
Canvas accessibility. One of Steve's recent tweets, pasted below my 
name, suggests that there's progress .

What I'd welcome is an update on the application of/implications for 
the use of Canvas, with respect to accessibility, in the real world, 
right now. I'm working with a client who's implementing it, and I 
need to provide guidance to assure both that the Canvas 
implementation can be made as accessible as possible (not just to 
screen reader users, of course). And I want to provide guidance about 
fallback techniques.

Questions that are crossing my mind include:

-- If Canvas is implemented to create an image, but the raw data is 
still available, will that raw data suffice, in terms of 
accessibility? I would think some kind of textual description would 
be valuable to all, including anyone using an older browser that 
might not support Canvas.

-- Are there any Canvas-generating libraries that are particularly 
focusing on assuring accessibility?

-- What is the best source of accessible examples?


@stevefaulkner tweeted:

HTML5 <canvas> hit Region and focus ring details and example 

Wednesday, February 26, 2014 at 9:14:40 AM
Received on Monday, 10 March 2014 03:35:11 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 13 October 2015 16:21:50 UTC