- From: Terrill Thompson <tft@uw.edu>
- Date: Mon, 5 Dec 2016 15:17:44 -0800
- To: "w3c-wai-ig@w3.org" <w3c-wai-ig@w3.org>
- Message-ID: <CAC7M+woew5hVa5xtGTMrOBYWh-Yzisyad0GAc+G5zF=2DQKeoA@mail.gmail.com>
Hi All, I'm trying to make a case in opposition of visibly hidden controls. Are there any WCAG 2.0 success criteria that controls to be visible without the user having to work hard to discover them? Chromeless media players are a common example. By default there are no controls other than (perhaps) a large play button that's overlaid over a poster image. When the video is playing there are no controls at all. However, if a mouse user hovers over the video a control bar appears. Depending on how it's coded the control bar might be accessible to screen reader users, and might even be visibly exposed to keyboard users once it receives focus, but from my perspective if it's not visible, keyboard users won't necessarily know they can tab to it. The same applies to speech-to-text users. How do they know they can say "Click mute" if the media player has no visible Mute button? Does WCAG 2.0 offer any support for my position that controls should be visible? I'm also willing to consider opposing arguments if anyone disagrees (perhaps a clean, simple interface is more or equally justifiable). Thanks, Terrill --- Terrill Thompson Technology Accessibility Specialist DO-IT, Accessible Technology Services UW Information Technology University of Washington tft@uw.edu
Received on Monday, 5 December 2016 23:19:15 UTC