W3C home > Mailing lists > Public > public-html@w3.org > February 2011

Re: Canvas accessibility: A new mode for all focusable elements?

From: Maciej Stachowiak <mjs@apple.com>
Date: Mon, 07 Feb 2011 15:28:03 -0800
Cc: "HTML WG (public-html@w3.org)" <public-html@w3.org>
Message-id: <C62F7BC5-A1FA-4CDC-8F2A-ABC763D03E10@apple.com>
To: Frank Olivier <Frank.Olivier@microsoft.com>

On Feb 7, 2011, at 3:00 PM, Frank Olivier wrote:

> Wrt the following spec text:
> 
> http://dev.w3.org/html5/spec/Overview.html#the-canvas-element
> "In non-visual media, and in visual media if scripting is disabled for the canvas element or if support for canvas elements has been disabled, the canvas element represents its fallback content instead. 
> When a canvas element represents embedded content, the user can still focus descendants of the canvas element (in the fallback content). This allows authors to make an interactive canvas keyboard-focusable: authors should have a one-to-one mapping of interactive regions to focusable elements in the fallback content."
> 
> This means that any focusable element in the DOM now has a new 'non-visual' mode. 
> 
> Does the html wg have any concern about allowing *any* focusable element to have a non-visual mode? 
> 
> Should the list of allowable elements under a canvas element be enumerated and specced?
> 
>> From an implementation perspective, we have a big new area with little in the way of specced behavior.


>From a technical perspective, for WebKit, it shouldn't be a huge problem to allow canvas descendants to receive focus, and making it a subset would not materially simplify the implementation.

 - Maciej
Received on Monday, 7 February 2011 23:29:06 GMT

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