W3C home > Mailing lists > Public > public-cognitive-a11y-tf@w3.org > July 2016

Re: 1.4.2 audio control, do we want to require the stop mechanism to be more discoverable?

From: John Foliot <john.foliot@deque.com>
Date: Tue, 12 Jul 2016 10:42:07 -0500
Message-ID: <CAKdCpxxaZj=ZKGZyRa3qoxQLfXmsJRJDOb3Y+JzRTKbGrFZ1GA@mail.gmail.com>
To: Katie Haritos-Shea GMAIL <ryladog@gmail.com>
Cc: Mike Elledge <melledge@yahoo.com>, David MacDonald <david100@sympatico.ca>, "White, Jason J" <jjwhite@ets.org>, public-cognitive-a11y-tf <public-cognitive-a11y-tf@w3.org>, WCAG <w3c-wai-gl@w3.org>
> And, I might point out that auto-playing of audio is extremely
distracting an disorienting for persons with cognitive and emotional
disabilities – especially when the mechanism to turn off autoplay is not
extremely clear…..

Agreed, although thinking about this, maybe the answer is not "no
auto-play" but rather, "no auto-volume" (without user input). We have
great precedence here for that already, as this is what Facebook does
with embedded videos today, and I've seen examples of video ads inserted on
pages with the same functionality: the video is "playing" but the audio is
muted until the end user adjusts the volume. (One of the other awesome
things I'm noting is that, because of this default behavior in FaceBook,
more videos are including captions, often artistically as part of the
video, to further entice users to turn the audio up. Yay!)

So... is this a one-stop issue? Are we looking for a mechanism to silence
the audio quickly (and should we be contemplating a new SC for that?), or
is the ability to actually stop the motion of the video quickly (i.e. it's
more than just the audio conflict introduced by auto-start?) the same
requirement, or a different one?

JF

On Tue, Jul 12, 2016 at 9:50 AM, Katie Haritos-Shea GMAIL <ryladog@gmail.com
> wrote:

> And, I might point out that auto-playing of audio is extremely distracting
> an disorienting for persons with cognitive and emotional disabilities –
> especially when the mechanism to turn off autoplay is not extremely clear…..
>
>
>
> ​​​​​
>
>
>
>
>
>
>
> ** katie **
>
>
>
> *Katie Haritos-Shea*
> *Principal ICT Accessibility Architect (WCAG/Section 508/ADA/AODA)*
>
>
>
> *Cell: 703-371-5545 <703-371-5545> **|* *ryladog@gmail.com*
> <ryladog@gmail.com> *|* *Oakton, VA **|* *LinkedIn Profile*
> <http://www.linkedin.com/in/katieharitosshea/> *|* *Office: 703-371-5545
> <703-371-5545> **|* *@ryladog* <https://twitter.com/Ryladog>
>
>
>
> *From:* Mike Elledge [mailto:melledge@yahoo.com]
> *Sent:* Tuesday, July 12, 2016 9:21 AM
> *To:* David MacDonald <david100@sympatico.ca>; White, Jason J <
> jjwhite@ets.org>
> *Cc:* WCAG <w3c-wai-gl@w3.org>
> *Subject:* Re: 1.4.2 audio control, do we want to require the stop
> mechanism to be more discoverable?
>
>
>
> It seems to me that Mute, though helpful, isn't the same thing as
> preventing autoplay. There are times when I may want to postpone, rather
> than mute, audio or video. Could an easy-to-discover method be added to
> Techniques? We already cover user control over media in WCAG 2.0.
>
>
>
> On Tuesday, July 12, 2016 2:54 AM, David MacDonald <david100@sympatico.ca>
> wrote:
>
>
>
> Yup, works in FF on MAC and Windows.
>
> Any way to do this with a keyboard in Chrome, Safari and other browsers?
> If so, perhaps EO can help find a way to get the word out to other users
> ... I don't think many know about it, and plenty of users are dogged with
> autoplay messing up their screen readers.
>
> It seems to me, given that CTL+M does it, that no site can fail 1.4.2
> because a mechanism is available in at least one accessibility supported
> stack.
>
>
> Cheers,
> David MacDonald
>
>
>
> *Can**Adapt* *Solutions Inc.*
>
> Tel:  613.235.4902
>
> LinkedIn
> <http://www.linkedin.com/in/davidmacdonald100>
>
> twitter.com/davidmacd
>
> GitHub <https://github.com/DavidMacDonald>
>
> www.Can-Adapt.com <http://www.can-adapt.com/>
>
>
>
> *  Adapting the web to all users*
>
> *            Including those with disabilities*
>
>
>
> If you are not the intended recipient, please review our privacy policy
> <http://www.davidmacd.com/disclaimer.html>
>
>
>
> On Mon, Jul 11, 2016 at 7:54 PM, White, Jason J <jjwhite@ets.org> wrote:
>
>
>
>
>
> *From:* David MacDonald [mailto:david100@sympatico.ca]
> *Sent:* Monday, July 11, 2016 5:51 PM
>
> perhaps it is sufficient... I've never heard of an end user doing that,
> and I've heard plenty of complaints about auto play....
>
> ​
>
> Maybe we should ask some people who are blind... not sure how discoverable
>
> ​by keyboard it is
>
> I don't see a shortcut
> https://support.google.com/chrome/answer/157179?hl=en
>
> I see the letter "M" in MUTE is underlined in Windows, but ALT-M didn't do
> it... ​don't see any hints on a mac.
>
> It's super easy with mouse :(
>
> *[Jason] Ctrl-m did it for me under Mozilla Firefox. It worked as
> documented. Thank you for the reference.*
>
>
>
>
> ------------------------------
>
> This e-mail and any files transmitted with it may contain privileged or
> confidential information. It is solely for use by the individual for whom
> it is intended, even if addressed incorrectly. If you received this e-mail
> in error, please notify the sender; do not disclose, copy, distribute, or
> take any action in reliance on the contents of this information; and delete
> it from your system. Any other use of this e-mail is prohibited.
>
>
>
> Thank you for your compliance.
> ------------------------------
>
>
>
>
>



-- 
John Foliot
Principal Accessibility Strategist
Deque Systems Inc.
john.foliot@deque.com

Advancing the mission of digital accessibility and inclusion
Received on Tuesday, 12 July 2016 15:42:40 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 12 July 2016 15:42:40 UTC