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

Re: Working Group Decision on ISSUE-131 caret-location-api

From: Benjamin Hawkes-Lewis <bhawkeslewis@googlemail.com>
Date: Fri, 29 Apr 2011 09:19:26 +0100
Message-ID: <BANLkTi=1S-ZQoABze7-D0gFc=M694muYJQ@mail.gmail.com>
To: Jonas Sicking <jonas@sicking.cc>
Cc: Maciej Stachowiak <mjs@apple.com>, Richard Schwerdtfeger <schwer@us.ibm.com>, HTMLWG WG <public-html@w3.org>
On Fri, Apr 29, 2011 at 8:35 AM, Jonas Sicking <jonas@sicking.cc> wrote:
> The current (pre applying WG decision) syntax:
> // Example A
> cx.beginPath();
> cx.rect(x,y,w,h);
> cx.drawFocusRing(elem);
> This would draw a OS-styled focus ring on the coordinates x,y,w,h as
> well as tell AT that focus is currently located at those coordinates
> as to enable it to magnify that part of the screen if desired.
> What I'm proposing is that we enable the following syntax *as well*:
> // Example B
> cx.beginPath();
> cx.rect(x,y,w,h);
> cx.drawFocusRing(elem);
> cx.setCaretSelectionRect(elem,x-10,y-10,w+20,h+20);
> This would draw the focus ring on the coordinates x,y,w,h but tell AT
> that a somewhat larger area is what needs to be magnified.
> However, if someone just writes the code as in example A, it would
> still inform AT that x,y,w,h is the area that should be magnified.

The Decision, and the Change Proposal it draws on, already do this

Specifically in drawFocusRing():

"2. If supporting an accessibility API, implementors may use the drawing
path to form a best fit rectangle in screen coordinates and apply it to
the bounding rectangle of the associated accessible object."


Magnifiers use the bounding rectangle in the accessibility API to work
out the area to be magnified.

If I've misunderstood you, can you clarify what changes to the Change
Proposal's text you'd want to see to get the functionality you're
asking for?

Benjamin Hawkes-Lewis
Received on Friday, 29 April 2011 08:19:53 UTC

This archive was generated by hypermail 2.4.0 : Saturday, 9 October 2021 18:45:37 UTC