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: Wed, 27 Jul 2011 18:32:59 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1Qm8uh-0002af-B2@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13176

Rich Schwerdtfeger <schwer@us.ibm.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |a11y
           Severity|enhancement                 |major

--- Comment #5 from Rich Schwerdtfeger <schwer@us.ibm.com> 2011-07-27 18:32:58 UTC ---
To Areyh, I understand you are not a subject matter expert. Consequently, I put
its importance back to major. 

That said, Jonas Sicking has a proposal is close to what I had been asking for
on the list. I will be working with Jonas to incorporate what he is changing
into the same change proposal:

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

The net of this is that the path association with the element is sufficient to
allow the user agent to use the path to compute the bounds of an object and set
it in the platform accessibility API implementation. Furthermore, a future API
modification for web apps might be to scroll an element into view based on the
bounds of the object stored in the browser. This capability will be of
particular assistance to Google which is targeting AT browser extensions.

-- 
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, 27 July 2011 18:33:00 UTC

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