Hey Alastair,
Can we include something in the SC text then to make this clear? Maybe
something along the lines of:
"provide a visible indication of where the components are available, or how
they can be revealed"
On Thu, Nov 18, 2021 at 11:26 AM Alastair Campbell <acampbell@nomensa.com>
wrote:
> > This is all very nuanced. Can we more on principle agree whether or not
> the indicator, whatever it is, has to provide some information on how to
> find/reveal the hidden control? It seems to me the answer is yes, so can we
> do something to make that clearer in the wording of the SC?
>
>
>
> Yes, the indicator *should* provide some information on how to
> find/reveal the control, but we haven’t tried to make that a strong part of
> the SC text because there is a great variety in how that could work.
>
>
>
> If you have a look through the understanding doc
> <https://w3c.github.io/wcag/understanding/visible-controls.html>
> (particularly the paragraph above the Benefits heading) it isn’t really
> possible to dictate how that would be done.
>
>
>
> In that sense, ‘indictor’ is probably the best term, it implies a
> location/directions without saying how to do it.
>
>
>
> -Alastair
>
--
*Wilco Fiers*
Axe-core & Axe-linter product owner - WCAG 3 Project Manager - Facilitator
ACT Task Force
