W3C home > Mailing lists > Public > public-html-a11y@w3.org > January 2011

Agenda: January 24, 2011 Canvas Accessibility Working Group

From: Richard Schwerdtfeger <schwer@us.ibm.com>
Date: Fri, 21 Jan 2011 09:52:43 -0700
To: public-canvas-api@w3.org, franko@microsoft.com, david.bolter@gmail.com, Charles Pritchard <chuck@jumis.com>, public-html-a11y@w3.org
Cc: swarren@aisquared.com, tlalor@aisquared.com, dmazzoni@google.com
Message-ID: <OF87E8025E.4A26474E-ON8625781F.005B77AC-8625781F.005CB7B8@us.ibm.com>

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

- Canvas: Initialization of resources (such as IFrame) in canvas
  Note Chuck Pritchard's latest post:

2. Chuck to provide link to Google Canvas IME work

3. Rich Text editing supportCaret, Selection, Grammar errors, spelling
- Do the user agent manufacturers agree to do further work on rich text
- Where we are:
  - Rich proposal for marking caret, selected content, grammar errors,
spelling errors using HTML 5 and ARIA with modifications

  - 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:

noVNC - VNC client using HTML5 Canvas:

5. Action Items
 - Frank: what API does IE use to track content selection and
carets in content editable areas?


Reference Material APIs:
- Browser API Comparisons for Caret Tracking and Content Selection:
- Getting the selection object:
- 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


Minutes last call:

(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

Received on Friday, 21 January 2011 16:53:32 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:05:17 UTC