Re: Visible controls updates

Hey Alastair,
The current wording no longer has a connection between the visual indicator
and the component. I think in the new wording, putting a text on the page
that says "this submit button is available on hover" meets the requirement,
even though it provides no information on where to find that hidden
component.

I don't think the word "identify" does an amazing job of capturing that
case, but I think there's at least an argument to be made that if there's
no information on where to find that component, it isn't "identifying" it.



On Fri, Nov 12, 2021 at 6:25 PM Alastair Campbell <acampbell@nomensa.com>
wrote:

> Hi Wilco & group,
>
>
>
> In the last meeting we discussed the re-write of Visible controls:
>
> https://www.w3.org/2021/11/09-ag-minutes.html#item05
>
>
>
> In the Friday meeting today we’ve updated that, visible in the PR:
>
> https://github.com/w3c/wcag/pull/2019/files
>
>
>
> Wilco made some suggestions during the meeting for the first part of the
> SC text, to say something like “provide visible indicators that identify
> the available components", but in our discussion we thought:
>
>
>
>    - Adding the word “identify” doesn’t seem to add anything that
>    “visible indicator” is not already saying.
>
>    - Adding the verb identify has larger ramifications, e.g. “provide
>    visible indicators that identify the available components”, would mean each
>    available component has to be identifiable from the indicator, which is
>    more than the intent. It doesn’t allow for grouping.
>
>
>
> We’d appreciate a little more info on what the core concern is.
>
>
>
> Kind regards,
>
>
>
> -Alastair
>
>
>
> --
>
>
>
> @alastc / www.nomensa.com
>
>
>


-- 
*Wilco Fiers*
Axe-core & Axe-linter product owner - WCAG 3 Project Manager - Facilitator
ACT Task Force