This Wiki page is edited by participants of the HTML Accessibility Task Force. It does not necessarily represent consensus and it may have incorrect information or information that is not supported by other Task Force participants, WAI, or W3C. It may also have some very useful information.

Canvas

From HTML accessibility task force Wiki
Jump to: navigation, search


This wiki space is intended for the use of the Canvas API sub-group of the HTML Accessibility Task Force. Content in this wiki is developmental, and should be considered (and cited) as such.

Canvas Sub-Group Meetings & Minutes

Next meeting: [this group is not currently meeting]

The Canvas sub-team will meet every other Monday at 6:00 PM Boston Time until work is concluded. Meeting information is as follows:

  • IRC: server: irc.w3.org, channel: #html-a11y.
  • Zakim Code: 2119# (a11y#)

Next Agenda

(for September 8th, 2014)

Meeting: Canvas Task Force
Chair: Sam Ruby
agenda+ Testing Status
agenda+ Implementations Update
agenda+ Level 1 CR
agenda+ Heartbeat Level 2

agenda+ Next Meeting

Mailing List

The subgroup will use public-canvas-api@w3.org to conduct all correspondence. [archives]

Canvas Accessibility: Bugs, Issues & Proposals

(See also Canvas Accessibility Use Cases.)

Implementation Progress

Hit Regions
Supported in Firefox Nightly 32
Chromium Issue 300223009: Implement basic parts of hit regions on canvas2d.
Chromium Issue 328961: Chrome does not support HTML5 Canvas Hit Testing
Bug 63463 - AX: Support HTML5 Canvas AX with hit regions
Chromium Issue 287163007: WIP: <canvas> hit regions
drawFocusIfNeeded()
Supported in Firefox Nightly 32
Supported in Chrome ??
WebKit Bug 132584 - Add support for drawFocusIfNeeded
WebKit Bug 124592 - AX: Support HTML5 Canvas FKA with focus rings

Bugs: a11y

It has been decided that the following bugs will not have the "a11ytf" keyword applied to them at this time. This does not mean the task force has no interest in them. But they are bugs with no immediate task force work plan. The task force may review them in the future.

HTMLWG Issues

Resources