- From: Alastair Campbell <acampbell@nomensa.com>
- Date: Tue, 26 Apr 2022 17:58:00 +0000
- To: Gregg Vanderheiden <gregg@raisingthefloor.org>
- CC: "w3c-waI-gl@w3. org" <w3c-wai-gl@w3.org>
- Message-ID: <PR3PR09MB53478743562C312F70EAC729B9FB9@PR3PR09MB5347.eurprd09.prod.outlook.com>
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: https://docs.google.com/document/d/1Cn9SvuOiu_m-phcyK5IdtipNzyoM2pkcCHbnWfcqsNc/edit# 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<https://www.w3.org/2002/09/wbs/35422/wcag22-visible-controls/results#xq19> 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. -Alastair From: Gregg Vanderheiden <gregg@raisingthefloor.org> Date: Tuesday, 26 April 2022 at 17:42 To: w3c-waI-gl@w3. org <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. Thanks Gregg 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 ——————————— Gregg Vanderheiden gregg@vanderheiden.us<mailto:gregg@vanderheiden.us> gregg ——————————— Professor, University of Maryland, College Park Founder and Director Emeritus , Trace R&D Center, UMD Co-Founder Raising the Floor. http://raisingthefloor.org<https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fraisingthefloor.org%2F&data=05%7C01%7Cacampbell%40nomensa.com%7C7fad4d8beb1a437b48d408da27a388c3%7Cebea4ad6fbbf43bd8449c56e26692c35%7C0%7C0%7C637865881311318349%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=LBEUZXyYOC%2F1plKpvnuc5KQ53H8Cll%2FuiR%2FyQSB0o6U%3D&reserved=0> The Global Public Inclusive Infrastructure (GPII) http://GPII.net<https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fgpii.net%2F&data=05%7C01%7Cacampbell%40nomensa.com%7C7fad4d8beb1a437b48d408da27a388c3%7Cebea4ad6fbbf43bd8449c56e26692c35%7C0%7C0%7C637865881311318349%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=YxK72xgMXw3lZtoTSZbdnbeQvpTH0RqFCzL7JulbAs4%3D&reserved=0> The Morphic project https://morphic.org<https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmorphic.org%2F&data=05%7C01%7Cacampbell%40nomensa.com%7C7fad4d8beb1a437b48d408da27a388c3%7Cebea4ad6fbbf43bd8449c56e26692c35%7C0%7C0%7C637865881311318349%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=P3dOiRE6nM4iOCLD9SqeiE33U0qzlyufHAKBT8Qj6fo%3D&reserved=0>
Received on Tuesday, 26 April 2022 17:58:15 UTC