W3C home > Mailing lists > Public > public-html-a11y@w3.org > August 2013

Fw: drawSystemFocusRing and drawCustomFocusRing in Google Chrome Canary today

From: Richard Schwerdtfeger <schwer@us.ibm.com>
Date: Thu, 1 Aug 2013 18:25:44 -0500
To: franko@microsoft.com, dbolter@mozilla.com, "James Craig" <jcraig@apple.com>
Cc: "Paul Cotton" <Paul.Cotton@microsoft.com>, public-html-a11y@w3.org, janina@rednote.net, cyns@exchange.microsoft.com
Message-ID: <OF7BCF755A.3680E4DA-ON86257BBA.00808CB0-86257BBA.0080B2A1@us.ibm.com>


Rich Schwerdtfeger
----- Forwarded by Richard Schwerdtfeger/Austin/IBM on 08/01/2013 06:24 PM

From:	Dominic Mazzoni <dmazzoni@google.com>
To:	Richard Schwerdtfeger/Austin/IBM@IBMUS, Charles Pritchard
Date:	08/01/2013 05:59 PM
Subject:	drawSystemFocusRing and drawCustomFocusRing in Google Chrome
            Canary today

Hi Rich, Chuck,

You can try drawSystemFocusRing and drawCustomFocusRing in Google Chrome
Canary today.

You have to run Chrome with a flag for it to work. You can go to
chrome://flags and enable "Enable experimental canvas features" (and then
restart the browser), or else run Chrome with
the --enable-experimental-canvas-features command-line flag.

It works - including magnifier support - but I'm aware of a couple of

* The focus outline width is too small. That was a minor oversight, will be
fixed promptly.
* If the location of the element changes dynamically, the accessibility
tree doesn't get updated right away. I'll work on fixing this, but if you
tab away and tab back it should be fixed in the meantime.

In order to launch this (i.e. get rid of the flag), it would really help to
see a few pages on the public web actually taking advantage of this. Of
course, having other browsers implement it would also help.

- Dominic
Received on Thursday, 1 August 2013 23:26:17 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:56:27 UTC