W3C home > Mailing lists > Public > public-canvas-api@w3.org > July to September 2010

Re: Proposal: User Interface Independence for Accessible Rich Internet Applications

From: James Craig <jcraig@apple.com>
Date: Thu, 2 Sep 2010 10:53:45 -0700
To: public-canvas-api@w3.org
Message-Id: <D0F4AD01-787A-48BD-8B96-E8A45AB9DD86@apple.com>
Any comments on the Magnifier Interface? The focusPosition method was specifically added for canvas.

Cite: http://lists.w3.org/Archives/Public/public-canvas-api/2010JulSep/att-0006/UserInterfaceIndependence.html#identification

> Methods for Interface Magnifier
> 
> window.navigator.accessibility.magnifier.focusPosition ( element, cursorRect, selectionPolygon )
> Returns void. Allows the web author to send an explicit notification informing the screen magnifier to update its cache of the cursor location. Web authors should call this method when updating the display or cursor position of custom views.
> 
> Parameters for Magnifier.focusPosition
> 1. DOMElement element
> Required reference to the element (e.g. canvas) that has focus.
> 2. optional array cursorRect
> Optional array representing the rectangular cursor location relative to the [0,0] position of focused element. [ x1, y1, x2, y2 ]
> 3. optional array selectionPolygon
> Optional array representing the selection polygon relative to the [0,0] position of focused element. [ x1, y1, x2, y2, ... xn, yn ]
> Editorial Note: It may be better if the optional params are shape objects with a coords array and a type string like 'rect' or 'poly'. That would allow the author to decide if they wanted to provide the extra polygon coords, or just use a simple shape.
> 
> Note: The focusPosition() method would be necessary for screen magnifiers to work with canvas-based web apps like Bespin or the 280 North projects. This method is not necessary for text views managed by the user agent, including contentEditable views.



On Aug 30, 2010, at 2:08 AM, James Craig wrote:

> The following proposal is for consideration by the PF Working Group, DOM Working Group, and HTML Working Group. It specifically solves a few outstanding accessibility problems, but has much broader implications, and could affect several recommendations, including ARIA 2, DOM 3, and HTML 5. (Note: duplicate emails are going out to a few relevant lists.)
> 
> Thanks,
> James Craig
> 
> <UserInterfaceIndependence.html>
> 
Received on Thursday, 2 September 2010 17:54:21 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:31:50 UTC