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


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

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

--- Comment #16 from Rich Schwerdtfeger <schwer@us.ibm.com> 2011-09-22 11:38:43 UTC ---
Ian, screen magnifiers have the requirement to zoom to any object on the canvas
without changing focus. This requirement came form AI Squared - the producer of
the leading screen magnifier on Windows. To do this they require the bound of
an object as they have come to expect from platform accessibility API since
1995. Moving focus does not resolve this issue. 

Touch creates an additional problem in that moving your fingers across the UI,
and zooming, would require an association with the bounds of the object on
canvas which is also not supplied.  In the case of VoiceOver for screen reading
a use is able to move their fingers across HTML content and associate the
object with the rendered position so that VoiceOver may speak the object under
which the user is pointing. When this occurs, the focus is NOT moved. In fact
the user wants to be able to browse without moving focus. In <canvas> no such
positioning information exists. Canvas is indeed used to render objects. They
don't even need to be interactive, yet the user still needs to know their

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 Thursday, 22 September 2011 11:38:51 UTC