RE: Visible controls updates

I agree with Alastair that requiring where and how will be too difficult at this stage to get passed/figure out correctly as this was not something that some of us understood was previously covered.

Jonathan

From: Alastair Campbell <acampbell@nomensa.com>
Sent: Friday, November 19, 2021 10:32 AM
To: Wilco Fiers <wilco.fiers@deque.com>
Cc: WCAG list (w3c-wai-gl@w3.org) <w3c-wai-gl@w3.org>
Subject: RE: Visible controls updates

CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.

> "provide a visible indication of where the components are available, or how they can be revealed"

In a little role-reversal, I'm concerned about the testability of that.

Just some examples that came up during conversation:

  *   A video can itself be the indicator, whereas reading the above I think people would then require an icon to indicate the video controls.
  *   A menu button can be the indicator, but it wasn't the intent to require an icon as well.
  *   The "or" sets up some odd situations, where you could say how to reveal something without saying where it is.

So my question is whether it is worth complicating it further, or we set a baseline of providing an indicator and the people implementing can choose the best option in their scenario.

Cheers,

-Alastair