W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > January to March 2020

RE: WCAG 2.2 status - Visual indicators

From: Alastair Campbell <acampbell@nomensa.com>
Date: Thu, 16 Jan 2020 18:26:03 +0000
To: David MacDonald <david100@sympatico.ca>, Jonathan Avila <jon.avila@levelaccess.com>
CC: WCAG list <w3c-wai-gl@w3.org>
Message-ID: <HE1PR0901MB1593A6DD10DF3757392DC01EB9360@HE1PR0901MB1593.eurprd09.prod.outlook.com>
I’d just point out there can be some valid cases where people hide the accessible version of a control.

For example, the BBC radio player (in the video link from before) uses a slider (visually & with mouse) for the volume. ARIA based sliders don’t currently work in mobile ATs which is (I assume) why they implemented tab-able buttons in the background to set the volume at different levels.

From the SC text for the CSS-adaptable one, it doesn’t ‘break’, and it does provide a visual indicator of it’s own, so I assume it would pass.

But I would note that as a user, it was odd that most controls took on *my* defined styles (a dark & yellow highlight), including the siblings of the volume control. I’d guess that some COGA folk might assume it was not a control, because it didn’t have the ‘usual’ highlighting. That is the point of the pluggin after all.

Including text to fail that situation would effectively ban non-standard controls, so I don’t see a way around that aspect.


(image/jpeg attachment: image001.jpg)

Received on Thursday, 16 January 2020 18:26:14 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 21:08:34 UTC