W3C home > Mailing lists > Public > public-canvas-api@w3.org > January to March 2011

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

From: Charles Pritchard <chuck@jumis.com>
Date: Mon, 24 Jan 2011 09:56:26 -0800
Message-ID: <4D3DBD4A.30008@jumis.com>
To: "public-canvas-api@w3.org" <public-canvas-api@w3.org>
CC: Richard Schwerdtfeger <schwer@us.ibm.com>, dmazzoni@google.com
To reduce some of the confusion I caused (sorry about that):

Microsoft enabled audio interfaces by supporting the Canvas shadow dom, 
and following WAI-ARIA 7.3:
"provide support for the author to make all interactive elements 
focusable, that is, any renderable or event-receiving elements"
http://www.w3.org/TR/wai-aria/host_languages

The drawFocusRing was the "stalking horse" that motivated support.
As Richard has pointed out, it is likely not sufficient for screen 
magnifiers.

Gecko and WebKit developers are aware of the importance of the 
shadow-dom and WAI-ARIA 7.3;
and I'm looking forward to seeing them catch up.

Hopefully, we'll have consensus about setCaretSelectionRect by that 
time, and have a working example
of screen magnifiers interacting with the data.

-Charles


On 1/24/2011 9:42 AM, Charles Pritchard wrote:
> Agreed there; I was only referring to focus in relation to JAWS, not 
> magnification.
> With ARIA, drawFocusRing, and CSS semantics, I think there's decent 
> support for auditory user interfaces.
>
> As you've pointed out: setCaretSelectionRect is intended to 'extend' 
> support to screen magnifiers,
> as drawFocusRing alone is insufficient for more complex interactive 
> elements.
> [more complex than a checkbox].
>
> This library seems intended to follow a11y specs as they're exposed:
> http://code.google.com/p/google-axsjax/
> http://code.google.com/p/google-axsjax/wiki/Showcase
>
>
>
> On 1/24/2011 9:36 AM, Richard Schwerdtfeger wrote:
>>
>> The existing spec. has a caret position in drawFocusRing(); I can't 
>> imagine it supporting a magnifier based on the existing spec.
>>
>>
>> Rich Schwerdtfeger
>> CTO Accessibility Software Group
>>
>> Inactive hide details for Charles Pritchard ---01/24/2011 10:39:22 
>> AM---They're implemented to the existing spec. They have theCharles 
>> Pritchard ---01/24/2011 10:39:22 AM---They're implemented to the 
>> existing spec. They have the shadow dom working, with focus, so that JAWS
>>
>> From: Charles Pritchard <chuck@jumis.com>
>> To: Richard Schwerdtfeger/Austin/IBM@IBMUS
>> Cc: dmazzoni@google.com, "public-canvas-api@w3.org" 
>> <public-canvas-api@w3.org>, public-canvas-api-request@w3.org
>> Date: 01/24/2011 10:39 AM
>> Subject: 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>_
>>       <mailto:chuck@jumis.com>
>>       To: _"public-canvas-api@w3.org"_
>>       <mailto:public-canvas-api@w3.org>_<public-canvas-api@w3.org>_
>>       <mailto:public-canvas-api@w3.org>
>>       Cc: Richard Schwerdtfeger/Austin/IBM@IBMUS,
>>       _dmazzoni@google.com_ <mailto: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_
>>       <mailto: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! 
>>
>>
>
Received on Monday, 24 January 2011 17:57:05 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 24 January 2011 17:57:05 GMT