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 13732 - canvas accessibility
Summary: canvas accessibility
Alias: None
Product: HTML WG
Classification: Unclassified
Component: HTML a11y Task Force (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: This bug has no owner yet - up for the taking
QA Contact: This bug has no owner yet - up for the taking
Whiteboard: canvas
Keywords: a11y, a11y_canvas
Depends on:
Blocks: 13590
  Show dependency treegraph
Reported: 2011-08-10 03:29 UTC by Michael[tm] Smith
Modified: 2016-04-07 14:56 UTC (History)
8 users (show)

See Also:


Description Michael[tm] Smith 2011-08-10 03:29:10 UTC

The Canvas Element

Other than a reference to providing keyboard accessibility in the
fallback content, there is no reference to providing accessibility for
users with various disabilities.  Visual focus for off-screen elements
is an issue for users of screen magnification and low vision users, with
no visual keyboard indication and no tracking of programmatic focus in
the magnified area.  This makes "fallback content" appear to be the
"text-only alternative" of this decade.  Until there are strong
recommendations for how to make Canvas content accessible, there is a
huge risk of unequal access to interesting and innovative content.

[split out from bug 13590]
Comment 1 Ian 'Hixie' Hickson 2011-12-09 21:56:47 UTC
Is this just asking for examples of how to use <canvas> in an accessible way?
Comment 2 Ian 'Hixie' Hickson 2011-12-09 23:13:36 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: Did Not Understand Request
Change Description: no spec change
Rationale: please see comment 1
Comment 3 LĂ©onie Watson 2014-06-26 11:29:59 UTC
Moved to HTML A11y TF component.
Comment 4 Charles McCathieNevile 2016-04-07 14:56:25 UTC
This is a meta bug. Particular bugs against canvas can be filed (many have).