Success Criterion 1.4.2 - Audio Control - Level A

[JJdeGroot]

MATF meeting on July 17, 2024

Source

Independent from system volume? Super weird

I would say we should follow the current WCAG structure - otherwise we could rewrite a lot of the success criteria.

JJ; There is some overlap, but this is under perceivable and focused specifically on audio, as opposed to operable and more general

+1 Mick

+1 to Mick

JJ: What about Splash screens?

I see (hear) it on spa and salon websites a lot still in the US

Chromium and other browsers have the ability to mute now, but that would fall under UAAG IMO

Jamie: Do we need to discuss this, what do we need to change

Tori: Building on what Jamie said - a lot of these are general - these are the areas that are fairly agnostic

+1 to Tori,, and we need an actionable item from Agendum 2

JJ agrees

I do feel that since phones have a dedicated rocker for volume that it should respect the user settings

Jamie: Can we add action items for agenda 1 + 2 to take ownership for 1.4.1 and 1.4.2?

ACTION: Create subgroup to discuss 1.4.1 and 1.4.2 within the Github repo

move to previous agendum

WCAG2ICT guidance: https://w3c.github.io/wcag2ict/#audio-control

Share your thoughts for applying to mobile apps as a comment below.

[qbalsdon]

The only thing I would like to discuss here is why 2.2.2 Pause, Stop, Hide can't cover this criterion? I'm nothing if not redundant, but it seems a bit odd.