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

RE: drawSystemFocusRing and drawCustomFocusRing in Google Chrome Canary today

From: Suzanne Taylor <suzanne.taylor@pearson.com>
Date: Fri, 2 Aug 2013 12:06:08 -0400
Message-ID: <f2f9d8928f49d1106b26e6dc4705b2f2@mail.gmail.com>
To: Richard Schwerdtfeger <schwer@us.ibm.com>, 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
I think I see a couple of additional issues:

There seem to be 2 types of focus events.

Type 1: Events where focus was last on the address bar, and tab or
shift-tab jumps directly into a canvas fallback item

Type 2: Events where focus was elsewhere on the page (including being on
any canvas fallback item) and moves to a canvas fallback item

For type 1, onfocus seems to fire multiple times (4 or 5 times) and
drawSystemFocusRing() works.

For type 2, onfocus fires just once and drawSystemFocusRing() does not
work. Although test if (drawSystemFocusRing) is true.

The differences between number of times onfocus fires also exist in
Chrome 28.0.1500.95

I modified this test page to help illustrate these issues. It has
instructions under the heading “Problems” for seeing this:



*From:* Richard Schwerdtfeger [mailto:schwer@us.ibm.com]
*Sent:* Thursday, August 01, 2013 7:26 PM
*To:* franko@microsoft.com; dbolter@mozilla.com; James Craig
*Cc:* Paul Cotton; public-html-a11y@w3.org; janina@rednote.net;
*Subject:* Fw: drawSystemFocusRing and drawCustomFocusRing in Google Chrome
Canary today


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 Friday, 2 August 2013 16:07:55 UTC

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