Re: Working Notes: 2011-01-23 Canvas Accessibility Working Group

They're implemented to the existing spec.

They have the shadow dom working, with focus, so that JAWS can read 
what's going on.

I'd imagine they can revise it to meet the revised spec, with minimal work;
but should wait until we've reached a conclusion on 
setCaretSelectionRect, as it
is intended to interoperate.



On 1/24/2011 6:48 AM, Richard Schwerdtfeger wrote:
>
> Chuck,
>
> Is it IE9's focusRing implemented via our changes to it or the 
> existing spec?
>
> Rich
>
>
> Rich Schwerdtfeger
> CTO Accessibility Software Group
>
> Inactive hide details for Charles Pritchard ---01/23/2011 07:39:22 
> PM---Current agenda: "form a task force ... that will resultCharles 
> Pritchard ---01/23/2011 07:39:22 PM---Current agenda: "form a task 
> force ... that will result in canvas content being natively
>
> From: Charles Pritchard <chuck@jumis.com>
> To: "public-canvas-api@w3.org" <public-canvas-api@w3.org>
> Cc: Richard Schwerdtfeger/Austin/IBM@IBMUS, dmazzoni@google.com
> Date: 01/23/2011 07:39 PM
> Subject: Working Notes: 2011-01-23 Canvas Accessibility Working Group
> Sent by: public-canvas-api-request@w3.org
>
> ------------------------------------------------------------------------
>
>
> Last meeting:
>
> We reached consensus on " context . drawFocusRing(element) " as an
> improvement to the present whatwg draft.
> http://www.w3.org/2011/01/17-html-a11y-minutes.html
>
> Ian Hickson originally published drawFocusRing with four arguments:
> " context . drawFocusRing(element, x, y, [ canDrawCustom ]) "
> http://www.whatwg.org/specs/web-apps/current-work/multipage/the-canvas-element.html#focus-management-0
>
> "canDrawCustom" was dropped, as redundant and problematic.
> "x, y" now defaults to the centroid of the polyline / the center of the
> path.
>
> drawFocusRing has been successfully demonstrated in IE9 preview releases
> with the JAWS screen reader.
> Congratulations Microsoft IE Team!