[Bug 13176] The bounds of canvas fallback content, as rendered on the canvas, are not provided by the user agent to an assistive technology.


Ian 'Hixie' Hickson <ian@hixie.ch> changed:

           What    |Removed                     |Added
             Status|NEW                         |RESOLVED
         Resolution|                            |WONTFIX

--- Comment #15 from Ian 'Hixie' Hickson <ian@hixie.ch> 2011-09-21 22:42:35 UTC ---
For touch and keyboard navigation, it's up to the author to implement the
appropriate feedback mechanisms; it doesn't need extra help from the system
accessibility API. For example, CSS3 UI's properties can be used to specify the
elements in various navigation directions.

Zooming is handled already by the focus ring APIs.

In general, however, using <canvas> for something that can be sanely interacted
with in non-visual mediums is completely counter to the point of <canvas>. If
your content is media-independent, then use HTML, that's what it's for.

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: Rejected
Change Description: no spec change
Rationale: Already sufficiently supported.

Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Wednesday, 21 September 2011 22:42:42 UTC