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

>>Browsers provide a control to mute all sound in any tab page. Would that
be considered a way to meet this?

I'm guessing you mean this
http://www.howtogeek.com/231959/how-to-mute-individual-browser-tabs-in-chrome-safari-and-firefox/

I don't know.
​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 :(

>>While I would be concerned about enumerating "how many" tab stops, I
agree with the general idea, and with media in particular.

I agree it might be a bit arbitrary to specify a number of tab stops... but
we have some precedence of arbitrary
​,​
but well th
​o​
ught out
​,​
thresholds (20 hour time out exception)
​.

>>I wonder if adding a "No Auto-Start" under SC 2.2.2 might be worth
considering? (Is there much of a difference between auto-start and
auto-updating as noted in the current SC?)

I​
might be hard to require "no auto start" in 2.2.2 ...
​ personally I'd go for it, but some stakeholders may feel  it is important
to autoplay, and may feel we are stepping on their marketing attempts...

I do wish this was easier for users
​ to pause stop etc...​


>I like that idea…for 2.1 right? If technology becomes able to address it
reliably, it can be easily viewed as easily passed – but it covers the
instance where that is not the case…

That's right, it would be a modification of the current requirement
​ in 2.1...​ and "a mechanism is available" wording could be used, so that
when browsers get it together, it would be overcome.

"a mechanism is available to stop auto play sounds..."

​but we still have the problem of some key combination that is unknown to
the end user, and they have to figure this combination out when music/sound
is playing.​ That is one reason an interactive element that is well
labelled near the top of the tab order is attractive... OR a simple fix in
user agents with a standard key combination




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 4:42 PM, John Foliot <john.foliot@deque.com> wrote:

> Hi David,
>
> > ensure the mechanism to stop auto play of music is easy to find and get
> to
>
> Perhaps something here:
> https://www.w3.org/TR/media-accessibility-reqs/#access-to-interactive-controls-menus
> ?
>
> > force other system sounds to drop in volume when AT is running
>
> Hmmm, that kind of feels more like an AT/User Agent requirement than a
> Content requirement. However, somewhat related, we have this in the MAUR as
> well: https://www.w3.org/TR/media-accessibility-reqs/#clean-audio
>
> However, because this very much feels like a system requirement (which is
> where we recorded it in the MAUR) we may have to defer that to "Silver".
>
> > Personally, I'd like to require the mechanism to stop auto play audio in
> the the first few tab stops, or some other easily discoverable way.
>
> While I would be concerned about enumerating "how many" tab stops, I agree
> with the general idea, and with media in particular. I wonder if adding a
> "No Auto-Start" under SC 2.2.2 might be worth considering? (Is there much
> of a difference between auto-start and auto-updating as noted in the
> current SC?)
>
> JF
>
> On Mon, Jul 11, 2016 at 2:55 PM, David MacDonald <david100@sympatico.ca>
> wrote:
>
>> Do we want to look at 1.4.2 for WCAG 2.1 to ensure the mechanism to stop
>> auto play of music is easy to find and get to... currently the mechanism
>> can be anywhere...
>>
>> or should we look at the advances in Screen Readers (VO etc...) that
>> force other system sounds to drop in volume when AT is running, as a
>> positive step towards overcoming the problem in AT and user agents and not
>> make any changes in 2.1?
>>
>> Personally, I'd like to require the mechanism to stop auto play audio in
>> the the first few tab stops, or some other easily discoverable way...
>>
>> 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>
>>
>
>
>
> --
> John Foliot
> Principal Accessibility Strategist
> Deque Systems Inc.
> john.foliot@deque.com
>
> Advancing the mission of digital accessibility and inclusion
>

Received on Monday, 11 July 2016 21:51:38 UTC