- From: Claire Ryberg <contact@claireryberg.com>
- Date: Wed, 31 May 2023 10:49:55 +0200
- To: w3c-wai-ig@w3.org
- Message-ID: <CAFgSZiEZpGM6_OOwqNdFe+Fb0vmB3PiVU=9OCvUURqenn7BX6g@mail.gmail.com>
Hi all, I’m hoping someone can help clarify SC WCAG 2.4.7 Focus Visible ( https://www.w3.org/WAI/WCAG21/Understanding/focus-visible.html) so my team can best meet the requirement on our web platform. Currently on the application, a focus border is displayed on many of our interactive elements when they receive focus from a screen reader or a keyboard. This border, however, also shows up after clicking the elements when using a mouse or tapping it using a mobile device. We’re debating if the focus state when using a mouse or tapping is required to comply with WCAG guidelines for focus states. Design team: “Focus states should only be displayed for input type fields or when using assistive tooling. Focus states after clicking/tapping are not wanted or necessary.” Development team: “After interacting with an element in any way, the element should receive focus, and therefore display a focus state.” What’s your view on this behavior? Is it expected to visualize a focus border after interaction (independently of the input method) to comply with the guidelines or does it suffice to only show the focus border when specifically using assistive tooling? To be clear: we all agree that the focus state should appear for assistive tools such as keyboard and screen readers. The debate is about if it should also appear for tools such as a mouse, touch devices etc. The interactive elements we are discussing are things like: buttons, checkboxes, tabs, custom widgets, etc… Thanks in advance, Claire
Received on Thursday, 1 June 2023 16:09:10 UTC