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?

(Personally this is my go-to approach when I find a noisy page these days rather than struggling to find the media player in the page)

Regards,
James. 

> On Jul 11, 2016, at 13:11, Katie Haritos-Shea GMAIL <ryladog@gmail.com> wrote:
> 
> 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…
>  
> ​​​​​
>  
>  
>  
> * katie *
>  
> Katie Haritos-Shea 
> Principal ICT Accessibility Architect (WCAG/Section 508/ADA/AODA)
>  
> Cell: 703-371-5545 | ryladog@gmail.com | Oakton, VA | LinkedIn Profile | Office: 703-371-5545 | @ryladog
>  
> From: David MacDonald [mailto:david100@sympatico.ca] 
> Sent: Monday, July 11, 2016 3:56 PM
> To: WCAG <w3c-wai-gl@w3.org>
> Subject: 1.4.2 audio control, do we want to require the stop mechanism to be more discoverable?
>  
> 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
>  
> CanAdapt Solutions Inc.
> Tel:  613.235.4902
> LinkedIn 
> twitter.com/davidmacd
> GitHub
> 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