RE: Possible draft of 3.2.7

I agree that a good next step would be to work from a draft that attempts to solve the ambiguity and then, in light of the new SC wording, re-do the survey this time asking for pass/fail (or do something similar to the survey in a meeting) and see if there is consistency. 

Perhaps COGA could first provide the desired pass/fail answers to the examples so we can ensure that we not only reach consistent review results but also reach the intended review results. Even if this doesn’t get into the next version, this effort would help with what could be one of the first new outcomes for WCAG 3.

From: Sarah Horton <> 
Sent: Wednesday, April 27, 2022 4:48 AM
To: w3c-waI-gl@w3. org <>; public-cognitive-a11y-tf <>
Cc: Gregg Vanderheiden <>; Alastair Campbell <>
Subject: Re: Possible draft of 3.2.7

Hi, all.

I had suggested in previous emails redoing the survey, as the original survey question and response options were not clear. Could the chairs facilitate that? It might be useful to revisit the examples in light of recent discussions and email debates.

In answer to Alastair's questions below, I would respond, “Yes” to all! On the note about the problem, “what people bring to it affects the results,” that’s a challenge with all the SCs. We need to trust designers and developers judgment and give them agency in meeting SCs in a way that’s appropriate for the context and current conventions. For example, there was a time when not underlining menu links was not sufficient to indicate them as controls. Now it is.

Gregg’s proposed changes to the SC name and description seem like a positive step toward clarifying the intent of the SC.

I hope we can take this work forward and help address this user need. I think the SC does that.



On Apr 26, 2022, at 6:58 PM, Alastair Campbell < <> > wrote:

Hi Gregg,

The key thing we haven’t worked out is a common way of understanding what a ‘visible indicator’ is.

This doc includes a mix of the original examples and things I found from a search for interfaces using on-hover interactions: <> 

Put aside pass/fail, what would constitute a visible indicator in each case, and does it have one?

The only one that all 12 people who answered the survey <>  agreed was SquareSpace’s (old?) interface where it just looks like a rendered page, but hovering over things provides edit-controls.

Part of the problem is what people bring to it affects the results. For example, hovering over a video thumbnail is a very common way of providing controls on-hover. Is the video itself an indicator? Is that enough?

Is the context of a menu enough to signify drop-down options? What if some menu items have drop-downs and some don’t? Are we trying to require an icon (or equivalent) for every menu item which has drop-downs?

Is the context of a photo-editing interface context enough that you would assume there are on-hover interactions?

Without creating a catalogue of examples (which I don’t think would scale or internationalise), we don’t seem to be able to come to a reliable answer.


From: Gregg Vanderheiden < <> >
Date: Tuesday, 26 April 2022 at 17:42
To: w3c-waI-gl@w3. org < <> >
Subject: Possible draft of 3.2.7

This is a rough first draft of an alternative for Success Criterion 3.2.7 

Please anyone send me comments on how to improve this — or problems I missed.



Success Criterion 3.2.7 Controls Visible as Controls (Level AA): When user interface components are invisible or not visually indicated as controls until hover or focus, provide a visible indicator that the components are available and are controls, except when:

·       The same functionality is available through a component on the same page, or on a different step in a multi-step process, without requiring pointer hover or keyboard focus to make it visible as a control;

·       The component provides keyboard-only functionality;

·       A mechanism is available to make the components persistently visible as a control;

·       A mechanism makes controls visible as controls whenever a pointer is moved within or over the page, page is clicked anywhere, or keyboard is used – and stays visible for at least 3 seconds after movement or keyboard operation stops

·       Hiding the visibility of the control as a control is essential to the purpose of the page. 

Examples of problems that fail

·      Controls are hidden unless the person points directly to the control

·      Page where links are not visible until the person tabs to them

Examples that pass

·      Movie where all controls are hidden but show up as soon as mouse is moved, person touches the screen anywhere, or the keyboard is used.

·      Page where links are hidden but show up as soon as mouse or keyboard are used within or over the page.



Gregg Vanderheiden <> 


Professor, University of Maryland, College Park
Founder and Director Emeritus , Trace R&D Center, UMD

Co-Founder Raising the Floor. <;;sdata=LBEUZXyYOC%2F1plKpvnuc5KQ53H8Cll%2FuiR%2FyQSB0o6U%3D&amp;reserved=0> 
The Global Public Inclusive Infrastructure (GPII) <;;sdata=YxK72xgMXw3lZtoTSZbdnbeQvpTH0RqFCzL7JulbAs4%3D&amp;reserved=0> 
The Morphic project <;;sdata=P3dOiRE6nM4iOCLD9SqeiE33U0qzlyufHAKBT8Qj6fo%3D&amp;reserved=0> 


Received on Wednesday, 27 April 2022 15:28:19 UTC