Hey Alastair,
I'm glad Andrew raised this. I didn't quite realize what that's doing. We
shouldn't make the assumption that everything that's focusable is a user
interface component. In particular landmarks are often used as the target
of skip links. Changing to component or element as you suggest would mean
those are then in scope of the SC.
On Fri, Jan 28, 2022 at 5:02 PM Alastair Campbell <acampbell@nomensa.com>
wrote:
> Hi everyone,
>
>
>
> (And particularly Andrew and Bruce who raised this.)
>
>
>
> We were discussing the start of focus-appearance. The published version is:
>
> “When user interface components
> <https://w3c.github.io/wcag/guidelines/22/#dfn-user-interface-components>
> receive keyboard focus, an area of the focus indicator meets the following:”
>
>
>
> The proposed update was:
>
> “When components receive keyboard focus, an area of the focus indicator
> meets the following:”
>
>
>
> With the note, that was intended to scope it to the underlying component
> rather than the perceived component.
>
>
>
> As an alternative, how about borrowing from 4.1.1 and using element:
>
>
>
> “When *elements* receive keyboard focus, an area of the focus indicator
> meets the following:”
>
>
>
> And then swapping ‘element’ in for component in each subsequent usage.
>
>
>
> Kind regards,
>
>
>
> -Alastair
>
>
>
> --
>
>
>
> @alastc / www.nomensa.com
>
>
>
>
>
>
>
--
*Wilco Fiers*
Axe-core & Axe-linter product owner - WCAG 3 Project Manager - Facilitator
ACT Task Force
