- From: Detlev Fischer <detlev.fischer@testkreis.de>
- Date: Tue, 10 Jan 2023 18:42:23 +0100
- To: WCAG group <w3c-wai-gl@w3.org>
- Message-ID: <2d0125b3-ca19-1322-64c9-8c6fd17c028e@testkreis.de>
Just that it doesn't get lost (since discussion was cut short in the telco): My concern about the rule "Element in sequential focus order has visible focus" ( https://www.w3.org/WAI/standards-guidelines/act/rules/oj04fd/proposed/ ) ...is that it refers to ANY element taking fokus while the normative text of 2.4.7 to which this rule is tied states: "2.4.7 Focus Visible: Any *keyboard operable user interface* has a mode of operation where the keyboard focus indicator is visible." To me, non interactive elements taking focus due to tabindex="0" should be out of scope for the rule since they are not part of the user interface (they are not tied to any action). So giving the SC a strict reading, I think the rule should be scoped to just user interface (i.e. interactive) elements, and say nothing about tab stops that are not on user interface elements. Needless to say that invisible tabstops are to be avoided, but a single invisible tab stop where the overall focus visibility is good strikes me as a rather minor accessibility issue. Whatever take you have on that, it seems it would need another rule to cover focus on elements that are not part of the user element (whether they should recieive focus at all, and if they do, whether that focus must be visible). -- Detlev Fischer DIAS GmbH (Testkreis is now part of DIAS GmbH) Mobil +49 (0)157 57 57 57 45 http://www.dias.de Beratung, Tests und Schulungen für barrierefreie Websites
Received on Tuesday, 10 January 2023 17:42:37 UTC