This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 12214 - Canvas fallback content implementation is underspecified
Summary: Canvas fallback content implementation is underspecified
Alias: None
Product: HTML WG
Classification: Unclassified
Component: LC1 HTML5 spec (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
Keywords: a11y, a11ytf, a11y_canvas
Depends on:
Reported: 2011-03-01 20:37 UTC by Rich Schwerdtfeger
Modified: 2011-08-04 05:13 UTC (History)
9 users (show)

See Also:


Description Rich Schwerdtfeger 2011-03-01 20:37:29 UTC
I spoke with my accessibility contact at Google who spoke to their webkit developers. They felt this text  to be under specified:

"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."

They felt this left it unclear as to how fallback content should respond to keyboard input. The suggested adding the following text

"Elements in canvas fallback content should behave as if they were on the page but invisible and having no effect on layout. Mouse input would go directly to the canvas because the children do not layout so they have no position to hit test."
Comment 1 Michael Cooper 2011-03-08 16:20:36 UTC
Bug triage sub-team adding a11ytf keyword because this is related to active HTML A11Y TF activity on canvas.
Comment 2 Ian 'Hixie' Hickson 2011-05-06 00:53:06 UTC
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document:

Status: Partially Accepted
Change Description: see diff given below
Rationale: I've tried to clarify the reported problem.
Comment 3 contributor 2011-05-06 00:54:15 UTC
Checked in as WHATWG revision r6097.
Check-in comment: clarify what 'focus' means
Comment 4 Michael[tm] Smith 2011-08-04 05:13:44 UTC
mass-move component to LC1