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

Re: February 14, 2011

From: Charles Pritchard <chuck@jumis.com>
Date: Mon, 14 Feb 2011 10:59:36 -0800
Message-ID: <4D597B98.1030201@jumis.com>
To: Richard Schwerdtfeger <schwer@us.ibm.com>
CC: public-canvas-api@w3.org, dmazzoni@google.com, david.bolter@gmail.com, franko@microsoft.com, Benjamin Hawkes-Lewis <bhawkeslewis@googlemail.com>, public-html-a11y@w3.org
On 2/13/2011 2:07 PM, Richard Schwerdtfeger wrote:
> Agenda: February 14, 2011 Canvas Accessibility Working Group
> Time of meeting is 3:00PM EST, 20:00 UTC, duration is 1 hour
> Zakim Bridge +1.617.761.6200, conference 2119 ("A11Y")
> IRC: server: irc.w3.org, port: 6665, channel: #html-a11y.
> 1. Caret/Selection Position and Blink Rate.
> Are people satisfied with the changes to the caret/selection Position 
> attached? Rich separated out definitions for caret and selection 
> position (per Benjamin's request) and made some changes to the user 
> agent caret and selection tracking. Content selection does not always 
> mean an element has to have focus - unlike the caret.
Seems to complicate things, but it's a positive change.

> 2. SVG caret/selection pos. At the last call Chuck preferred to NOT 
> have caret and selection position reflect the drawing path so it was 
> not changed. Benjamin suggested that we move caret/selection position 
> to the James Craig proposal to add support for SVG but we don't know 
> what will become of that proposal. Do we stick our current proposal? 
> If so, Rich will update the change proposal and send out to group this 
> week.
When ARIA is revisited regarding html 5, I think a role="caret" type 
will be appropriate for SVG use cases.

> 3. Chuck do you have a working modification to Chrome for focus ring 
> and caret/selection pos that we can send to AISquared for testing?
No. I'll send up a flare when I do.

> 4. Review outstanding bugs to re-assign and or agree on closure.
> _http://www.w3.org/Bugs/Public/show_bug.cgi?id=11238_
> _http://www.w3.org/Bugs/Public/show_bug.cgi?id=11239
> __http://www.w3.org/Bugs/Public/show_bug.cgi?id=11240_
> _http://www.w3.org/Bugs/Public/show_bug.cgi?id=11241_

Duplicates; Issue-131.
Addressed by setCaretSelectionRect, drawFocusRing
__ <http://www.w3.org/Bugs/Public/show_bug.cgi?id=11241>
> _http://www.w3.org/Bugs/Public/show_bug.cgi?id=11242_
Resolved. No need to restrict the subdom.
> _http://www.w3.org/Bugs/Public/show_bug.cgi?id=11328_
Mozilla + Ian are against the use case, stating that future
versions of Canvas will automatically scale.

This can be addressed through a better CSSOM model.
> _http://www.w3.org/Bugs/Public/show_bug.cgi?id=11329_
Seems to be a simple spec issue. No arguments, just hasn't happened.
> _http://www.w3.org/Bugs/Public/show_bug.cgi?id=11342_
Editor is factually incorrect, as can be seen by the source code
of many CanvasRenderingContext2D implementations.
Factors are already exposed in textBaseline methods.
Received on Monday, 14 February 2011 19:00:07 UTC

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