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

RE: FW: update to at risk features in Canvas

From: Rik Cabanier <cabanier@adobe.com>
Date: Sun, 29 Sep 2013 19:25:01 +0000
To: "Michael[tm] Smith" <mike@w3.org>
CC: "mark@w3.org" <mark@w3.org>, "schwer@us.ibm.com" <schwer@us.ibm.com>, "dbolter@mozilla.com" <dbolter@mozilla.com>, "dmazzoni@chromium.org" <dmazzoni@chromium.org>, "franko@microsoft.com" <franko@microsoft.com>, "public-html-a11y@w3.org" <public-html-a11y@w3.org>, "janina@rednote.net" <janina@rednote.net>
Message-ID: <83F37C1A4497B54589EAEDC750D03A9474CF5059B2@nambx09.corp.adobe.com>
> Because it's not actually following the spec?
They are following the spec. 

> I assume it's what's defined for DrawCustomFocusRing in the current spec.
Good. That's what Dominic and I implemented.

> Is that exactly what the current spec says it should do?
Yes, come to think of it, the "high contrast focus ring" is probably the rectangle that is drawn by the operating system's accessibility's subsystem. Can someone from the a11y team confirm that that is the intent?
If this is so, we've implemented the APIs per the spec.

Rik
________________________________________
From: Michael[tm] Smith [mike@w3.org]
Sent: Sunday, September 29, 2013 10:07 AM
To: Rik Cabanier
Cc: mark@w3.org; schwer@us.ibm.com; dbolter@mozilla.com; dmazzoni@chromium.org; franko@microsoft.com; public-html-a11y@w3.org; janina@rednote.net
Subject: Re: FW: update to at risk features in Canvas

Hi Rik,

Rik Cabanier <cabanier@adobe.com>, 2013-09-29 09:51 -0700:

> > It seems to me the reason for the renaming suggestion was not just to make
> > it less confusing but because it's actually not itself drawing a custom focus
> >ring at all, and is not even ensuring at all that one will actually be drawn.
>
> That's correct. This API is more like a question "Should the author draw a focus ring?"
> However, it seems that this has been discussed quite a bit already and
> it's been in the spec for years. Why pull it out/rename it now?

Because it's not actually following the spec?

> > Does that actually meet the original requirement that was stated for
> > drawing custom focus rings, or is it doing something different?
>
> What is the original requirement?

I assume it's what's defined for DrawCustomFocusRing in the current spec.

> The APIs notify the accessibility code and optionally draw a ring.

Is that exactly what the current spec says it should do?

  --Mike

--
Michael[tm] Smith http://people.w3.org/mike
Received on Monday, 30 September 2013 03:55:38 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:05:35 UTC