This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
http://www.w3.org/mid/B6CB855C5769484F862F4FB2CCFA50F402D545A7@VHAISHMSGJ2.vha.med.va.gov 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]
Is this just asking for examples of how to use <canvas> in an accessible way?
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: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Did Not Understand Request Change Description: no spec change Rationale: please see comment 1
Moved to HTML A11y TF component.
This is a meta bug. Particular bugs against canvas can be filed (many have).