Re: Agenda: January 24, 2011 Canvas Accessibility Working Group

All, thought it'd be helpful to hit reply, so the number and channel are 
easily accessible in your e-mail client.

I've revised the Canvas Rendering Context 2D document that Richard 
attached, in relation to the setCaretSelectionRect proposal,
removing many references to "text". They were not intended for 
implementers. The concept of "selected" is defined in ARIA,
so I hope that using "selection" as a word, has more firm ground. I've 
kept the word "caret" in the proposal.


-Charles

On 1/21/2011 8:52 AM, Richard Schwerdtfeger wrote:
>
> Agenda: January 24, 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. Group review on proposed change proposals encompassing (Need 
> consensus on this call):
> - Canvas 2D API: focusring, caret positioning, blink rate, text
> extent.These are needed regardless of text fields.
> Note: Group reached consensus on drawFocusRing(). I have attached the 
> updated document.
>
> Chuck indicated that he would like to see it reviewed by WhatWG 
> members as well before submitting
> it for formal proposal. Rich note: Ian is not in favor of an API to 
> set the
> caret position that is not linked to drawing yet we have no 
> alternative. Also, note that the
> current 2D API specification has caret position and focus ring in the 
> same location
>
> - Canvas: Initialization of resources (such as IFrame) in canvas
> Note Chuck Pritchard's latest post:
> _http://lists.w3.org/Archives/Public/public-canvas-api/2011JanMar/0015.html_
>
> 2. Chuck to provide link to Google Canvas IME work
>
> 3. Rich Text editing supportCaret, Selection, Grammar errors, spelling
> Annotation
> - Do the user agent manufacturers agree to do further work on rich text
> editing?
> - Where we are:
> - Rich proposal for marking caret, selected content, grammar errors,
> spelling errors using HTML 5 and ARIA with modifications
>
> _http://lists.w3.org/Archives/Public/public-canvas-api/2011JanMar/0001.html_
> - Positioning information of content is required - per AISquared feedback
> (See minutes from last meeting)
> 4. Additional Use Cases from Artur Ortega
>
> GTK client on HTML5 canvas:
> _http://blogs.gnome.org/alexl/2010/11/23/gtk3-vs-html5/_
>
> noVNC - VNC client using HTML5 Canvas:
> _http://kanaka.github.com/noVNC/_
>
> 5. Action Items
> - Frank: what API does IE use to track content selection and
> carets in content editable areas?
>
> _http://lists.w3.org/Archives/Public/public-canvas-api/2010OctDec/0057.html_
>
>
> Reference Material APIs:
> - Browser API Comparisons for Caret Tracking and Content Selection:
> _http://www.quirksmode.org/dom/w3c_range.html_
> - Getting the selection object:
> _https://developer.mozilla.org/en/DOM/window.getSelection_
> - sel = window.getSelection() //sel is a Selection object
> - rangex = sel(0);
> - rangex.collapsed(); //If it is collapsed it is a caret
> - reangex.collapse();
>
>
> Reference: revisions to 2D Context API - modifications
>
> _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_
> _http://www.w3.org/Bugs/Public/show_bug.cgi?id=11242_
> _http://www.w3.org/Bugs/Public/show_bug.cgi?id=11328_
> _http://www.w3.org/Bugs/Public/show_bug.cgi?id=11329_
> _http://www.w3.org/Bugs/Public/show_bug.cgi?id=11342_
>
>
>
> Minutes last call:
> http://www.w3.org/2011/01/17-html-a11y-minutes.html
>
> /(See attached file: HTML_Canvas_Element.html)//(See attached file: 
> HTML Canvas 2DContext101711.html)//(See attached file: CanvasEditor.html)/
>
>
>
> Rich Schwerdtfeger
> CTO Accessibility Software Group
>