W3C home > Mailing lists > Public > public-html-a11y@w3.org > January 2015

CfC Re: Close bug 13738

From: <chaals@yandex-team.ru>
Date: Fri, 09 Jan 2015 03:56:19 +0300
To: HTML Accessibility Task Force <public-html-a11y@w3.org>
Message-Id: <184951420764979@webcorp01f.yandex-team.ru>
Just noting in the subject this is a call for consensus.

09.01.2015, 03:40, "chaals@yandex-team.ru" <chaals@yandex-team.ru>:
> Hi,
>
> This is a call for consensus on the proposal: close bug 13738 - https://www.w3.org/Bugs/Public/show_bug.cgi?id=13738
>
> Positive response is preferred, all responses should be by email in reply to this message, and are due by the end of day Friday 16 January.
>
> Further information:
>
> (I presume bug 13738 was reopened for checking).
>
> The bug requests that the spec not suggest you can hide a focus ring with CSS instead of by using the blur() method. It was marked "WorksForMe" by Hixie, saying that it seemed to have been fixed. I agree with him - the spec now says:
>
> [[[
> Do not use this method to hide the focus ring. Do not use any other method that hides the focus ring from keyboard users, in particular do not use a CSS rule to override the 'outline' property. Removal of the focus ring leads to serious accessibility issues for users who navigate and interact with interactive content using the keyboard.
> ]]] - http://www.w3.org/TR/html5/editing.html#element-level-focus-apis
>
> which seems like a comprehensive statement along the lines the bug requested.
>
> cheers
>
> Chaals
>
> --
> Charles McCathie Nevile - web standards - CTO Office, Yandex
> chaals@yandex-team.ru - - - Find more at http://yandex.com

--
Charles McCathie Nevile - web standards - CTO Office, Yandex
chaals@yandex-team.ru - - - Find more at http://yandex.com
Received on Friday, 9 January 2015 00:56:49 UTC

This archive was generated by hypermail 2.3.1 : Friday, 9 January 2015 00:56:49 UTC