W3C home > Mailing lists > Public > public-agwg-comments@w3.org > March 2020

Re: Focus Visible (SC 2.4.7 and SC 2.4.11 in WCAG 2.2 draft)

From: Alastair Campbell <acampbell@nomensa.com>
Date: Tue, 3 Mar 2020 15:37:46 +0000
To: Christophe Strobbe <strobbe@hdm-stuttgart.de>, "public-agwg-comments@w3.org" <public-agwg-comments@w3.org>
Message-ID: <1514FA3C-FA92-4C63-B397-3F4D0FEA8DC5@nomensa.com>
Thanks Christophe,

I've added that as an issue here:
https://github.com/w3c/wcag/issues/1064 

We'll deal with all the public comments there.

Kind regards,

-Alastair

´╗┐On 03/03/2020, 15:28, "Christophe Strobbe" <strobbe@hdm-stuttgart.de> wrote:

    Dear AGWG,
    
    The proposed SC 2.4.11 closes an important loophole but neither SC 2.4.7
    nor the new SC 2.4.11 require that the focus indicator remains visible
    until the link or UI component loses focus again. (It is technically
    possible to indicate focus by means of a glow effect or another visual
    effect that disappears within seconds.)
    
    In SC 2.4.7, the following rewording would solve this:
    
    "Any keyboard operable user interface has a mode of operation where each
    UI component's keyboard focus indicator is visible until the component
    loses focus."
    
    In SC 2.4.11, the issue can be addressed by adding the following condition
    
    * "The focus indicator remains visible until the UI component loses focus."
    
    Alternatively, in order to avoid repetition, one might add a definition
    for "keyboard focus indicator" that includes a requirement for its
    visibility.
    
    Best regards,
    
    Christophe Strobbe
    
    -- 
    Christophe Strobbe
    Akademischer Mitarbeiter
    Responsive Media Experience Research Group (REMEX)
    Hochschule der Medien
    Nobelstra├če 10
    70569 Stuttgart
    Tel. +49 711 8923 2749
    
    
    

Received on Tuesday, 3 March 2020 15:38:03 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 3 March 2020 15:38:04 UTC