W3C home > Mailing lists > Public > public-canvas-api@w3.org > October to December 2010

Re: html5 editor responds to Canvas accessibility related bugs

From: Benjamin Hawkes-Lewis <bhawkeslewis@googlemail.com>
Date: Wed, 6 Oct 2010 08:16:13 +0100
Cc: Ian Hickson <ian@hixie.ch>, "public-canvas-api@w3.org" <public-canvas-api@w3.org>
Message-Id: <73567641-BF6D-46A9-AEFC-5CEA11DF0DF9@googlemail.com>
To: Charles Pritchard <chuck@jumis.com>
On 5 Oct 2010, at 23:26, Charles Pritchard wrote:
> This is a clear use case where selection and caret would be appropriate for accessibility purposes:
> http://www.w3.org/html/wg/wiki/ChangeProposals/canvasaccessibilitynonav

In the use-case presented in that proposal, a canvas chart is followed by an equivalent HTML table:

    <canvas></canvas>
    <table>
    
    </table>

Isn't that a case where you'd want caret navigation to treat the canvas as a block, and then skip straight to the HTML table? That's how it traditionally works with a static image:

    <img src="chart.png">
    <table>
    
    </table>

As far as I remember, a text editor like Bespin is the only use case so far presented for caret navigation and selection inside "canvas".

Here are some other real-world use cases for mapping canvas text selection to text in a sub-dom:

   * Wordle : http://benjamin.smedbergs.us/wordmap/wordmap.html
   * Mind map : http://think-app.appspot.com/
   * Names and dates in a genealogical tree : http://bencrowder.net/blog/2009/10/pedigree-chart-using-html5/
   * Labels in diagrams : http://diagramo.com/

These probably do involve text editing, but one could easily imagine non-editable versions, which would still benefit from caret navigation and selection.

--
Benjamin Hawkes-Lewis
Received on Wednesday, 6 October 2010 07:16:50 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 6 October 2010 07:16:51 GMT