Re: questions arising from AT vendor in regards to Mozillas implementation of the canvas subdom

Dominic,

That is true.

Another API function could be provided to do this in a later version of
canvas 2D API but I would like to see us get caret, selection, and hit
testing support in. Those use cases will hit the broadest set of use cases
for canvas today. Just getting those features in has been a battle.

Rich


Rich Schwerdtfeger



From:	Dominic Mazzoni <dmazzoni@google.com>
To:	Charles Pritchard <chuck@jumis.com>,
Cc:	Richard Schwerdtfeger/Austin/IBM@IBMUS, Steve Faulkner
            <faulkner.steve@gmail.com>, Frank Olivier
            <franko@microsoft.com>, public-canvas-api@w3.org,
            dbolter@mozilla.com
Date:	02/21/2012 01:46 AM
Subject:	Re: questions arising from AT vendor in regards to Mozillas
            implementation of the canvas subdom



On Sun, Feb 19, 2012 at 5:42 PM, Charles Pritchard <chuck@jumis.com> wrote:
  Those are the issues, not character boundary maps. Nobody passes those to
  ATs. There is no AT that receives an integer array with the location of
  every character on the screen.

I don't think that's true - AT can call IAccessibleText::characterExtents
to query the exact bounding rectangle of any arbitrary character on the
screen, isn't that basically the same thing?


http://accessibility.linuxfoundation.org/a11yspecs/ia2/docs/html/interface_i_accessible_text.html#ab7f7ac52f4950d096856e59b0b008d1

- Dominic

Received on Tuesday, 21 February 2012 14:36:22 UTC