- From: Charles Pritchard <chuck@jumis.com>
- Date: Thu, 07 Oct 2010 16:59:16 -0700
- To: Benjamin Hawkes-Lewis <bhawkeslewis@googlemail.com>
- CC: Ian Hickson <ian@hixie.ch>, "public-canvas-api@w3.org" <public-canvas-api@w3.org>
On 10/6/2010 12:16 AM, Benjamin Hawkes-Lewis wrote: > 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> > My reference wasn't well defined: I was referring to <canvas><table>...</table></canvas> as a use case. Another use case might be, and pardon my use of aside: <canvas><img src="scan.png" /><aside>Transcription of scanned document.</aside></canvas> This use case is certainly seen in-the-wild, with most uses of scanned documents. The image is intended to be seen, but lacking additional scripting, its content can not be selected. This demonstrates a shadow dom, which works well with non-supporting browsers and screen readers, and demands an accessibility UI, so that a user may position a caret for selection of content, for enhanced viewing, screen reading, or simply, selection of content for copy/paste and drag events. > * 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. Ian, are any of these sufficient, do we need more use cases? -Charles
Received on Thursday, 7 October 2010 23:59:49 UTC