W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > July 2011

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

From: <bugzilla@jessica.w3.org>
Date: Tue, 12 Jul 2011 22:41:47 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1QgleF-0001wb-9u@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13176

--- Comment #4 from Charles Pritchard <chuck@jumis.com> 2011-07-12 22:41:46 UTC ---
(In reply to comment #3)
> I don't understand the subject matter well enough to resolve this, and it seems
> like none of the other editorial assistants do either (or they're not

Technical summary
http://lists.w3.org/Archives/Public/public-canvas-api/2011JulSep/0187.html

Authors require the ability to pass path information to the UA accessibility
API in order to identify the screen location of elements in the shadow dom to
assistive technologies.

The most basic information expressed is a bounding box.

An AT may navigate the DOM and select an element of interest (such as selecting
a form element), for example: <canvas><button /></canvas> - it may examine the
bounding box of the dom element and do something with that information such as
drawing a big high contrast ring around the area or scrolling to the area.

When canvas is active, the shadow dom is not visible to the end user, but it
can be navigated. Were the canvas author able to run a method, similar to
drawFocusRing(element), they could inform the UA accessibility API of the
bounds of the element. I've proposed setElementPath as the method name.

-- 
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 Tuesday, 12 July 2011 22:41:52 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 16:31:13 UTC