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

Fw: Use of ARIA markup for rich text editing

From: Richard Schwerdtfeger <schwer@us.ibm.com>
Date: Tue, 14 Dec 2010 16:35:02 -0600
To: franko@microsoft.com, Charles Pritchard <chuck@jumis.com>, public-canvas-api@w3.org
Cc: david.bolter@gmail.com, public-html-a11y@w3.org, faulkner.steve@gmail.com, cyns@exchange.microsoft.com
Message-ID: <OF4DA4EF02.B9E989D4-ON862577F9.007A67AA-862577F9.007C0EF0@us.ibm.com>

I think David solved our caret problem:

<mark aria-selected="true"></mark>  would represent a collapsed selection
and therefore a caret similar to the terminology used in webkit and

This, in principle, seems to solve our problem with rich text editing. We
simply need to make sure we address the proper API mapping in the
accessibility API (I am cc'ing Steve and Cynthia as this may impact our API
mapping document for ARIA in HTML 5).


Rich Schwerdtfeger
CTO Accessibility Software Group
----- Forwarded by Richard Schwerdtfeger/Austin/IBM on 12/14/2010 04:16 PM

From:	Richard Schwerdtfeger/Austin/IBM
To:	franko@microsoft.com, david.bolter@gmail.com
Cc:	Charles Pritchard <chuck@jumis.com>, public-canvas-api@w3.org
Date:	12/14/2010 03:41 PM
Subject:	Use of ARIA markup for rich text editing

Hi Frank, David

I spoke with Charles and I think we can reproduce the same functionality
with existing ARIA attributes on existing HTML elements in canvas using


We could basically have:

<mark aria-invald="grammar"> See Spot fast run </mark>


<mark aria-invald="spelling"> See Spot fast run </mark>


<mark aria-selected="true"> See Spot fast run </mark>

This eliminates the need for any new HTML 5 tags. It uses existing ARIA
markup. We would simply need to define its API mapping in the HTML 5
accessiblity mapping document.

These can then be wired to the <canvas> UI and we don't need to make use of
any new API calls. Authors would be required to mark the areas accordingly.

Would you support this approach? To me this is low impact comparative to
any other solution we have now.

The only think we don't address is a replacement for the caret found in
contenteditable areas. So, to have a caret we would need to use either a
textfield or a contenteditable area - unless we add a feature.


Rich Schwerdtfeger
CTO Accessibility Software Group
Received on Tuesday, 14 December 2010 22:36:47 UTC

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