W3C home > Mailing lists > Public > public-html@w3.org > September 2010

ISSUE-74 canvas-accessibility and ISSUE-105 canvas-usemap

From: Maciej Stachowiak <mjs@apple.com>
Date: Tue, 21 Sep 2010 15:01:24 -0700
Message-id: <758DEFE6-1CD1-4A4C-9E89-D7B7E8FEF977@apple.com>
To: "public-html@w3.org WG" <public-html@w3.org>

The two issues relating to canvas accessibility have a number of Change Proposals submitted:

http://dev.w3.org/html5/status/issue-status.html#ISSUE-074
http://dev.w3.org/html5/status/issue-status.html#ISSUE-105

In reviewing these, the Chairs find that there are a number of separate questions that are not in perfect alignment with the Change Proposals or the issues:

(1) Should we add a caret location API to canvas, or is the focus API sufficient?

Supported by: http://www.w3.org/html/wg/wiki/ChangeProposals/canvasaccessibility
Opposed by: http://lists.w3.org/Archives/Public/public-html/2010Jul/0219.html
Partially opposed by: http://www.w3.org/html/wg/wiki/ChangeProposals/Map4NotAdom

(2) Should we add a boolean nonav attribute to the canvas to hide its contents from AT and keyboard navigation?

Supported by: http://www.w3.org/html/wg/wiki/ChangeProposals/canvasaccessibilitynonav
Opposed by: http://www.w3.org/html/wg/wiki/ChangeProposals/Map4NotAdom
Opposed by: http://lists.w3.org/Archives/Public/public-html/2010Jul/0219.html

(3) Should we remove the ability to use the children of canvas as an accessible dom entirely, in favor of other techniques, such as usemap?

Supported by: http://www.w3.org/html/wg/wiki/ChangeProposals/Map4NotAdom
Opposed by: http://www.w3.org/html/wg/wiki/ChangeProposals/canvasaccessibilitynonav
Opposed by: http://lists.w3.org/Archives/Public/public-html/2010Jul/0219.html

(4) Should we add advisory text explaining how to use the focus rect API for efficient caret position notification, and change nothing else?

Supported by: http://lists.w3.org/Archives/Public/public-html/2010Jul/0219.html
Opposed by: http://www.w3.org/html/wg/wiki/ChangeProposals/canvasaccessibility

(5) Should we add image map / usemap support as a possible way to represent focusable regions on the canvas?

Supported by: http://www.w3.org/html/wg/wiki/ChangeProposals/addimagemaptocanvas
Supported by: ttp://www.w3.org/html/wg/wiki/ChangeProposals/Map4NotAdom


The Chairs think it would be best to survey each of these questions separately. If the Working Group is amenable to that approach, we will likely issue a five-part survey. If you have any comments or suggestions regarding this plan, please submit them by a week from today (Tuesday, September 28).

This is also a final opportunity for authors of the referenced Change Proposals to update their Change Proposals with any additional material they think is relevant or helpful to the decision.


Regards,
Maciej
Received on Tuesday, 21 September 2010 22:02:04 GMT

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