Alternative rewording of the normative text for 1.4.2 Audio control #1825
Conversation
In contrast to #1824 this rewording accepts that the mechanism does not necessarily have to be implemented by the web page itself, but - per the definition of mechanism - can also be provided by the user agent/system. What this change does implement though is the clarification for the pause/stop clause that the pausing/stopping must be *independent* from any other audio output (which does address @jake-abma's original concern that a system wide general mute/audio off would automatically satisfy the SC, which is not the intended outcome #1533 This still changes the structure of the SC text, as suggested by @bruce-usab, to a more understandable list format. If the change in structure is deemed too radical, the addition of "independenlty from any other audio output" could likely be slotted into the current wording/structure of the SC. while a normative change, I don't believe this actually changes the meaning as intended at the time. Closes #1533
patrickhlauke
added
Errata
in line with the proposed clarification for 1.4.2 #1825 this clarifies that a *mechanism* needs to be available. the mechanism can actually be provided by the UA/system, not necessarily by the Web page. Key here is that it must be possible to turn off the sound *independently* from any other audio output. Closes #1543 Only makes sense to merge if #1825 (or an equivalent/modified version of the PR) is also merged
on second though, this can actually be kept closer to the original by modifying the last part of the sentence, so the "independently..." part applies to both the pause/stop and the volume control mechanism
|
Changed this to be less radical, but still cover the clarification for @jake-abma's concern in #1533, while also incorporating the note along the lines of trusted tester as pointed out by @mraccess77 #1824 (comment) |
|
Any news on this @alastc ? |
ah sorry, meant to do it and then promptly forgot when I made the update to the PR. done now. |
patrickhlauke
force-pushed
the
patrickhlauke-issue1533-alternate
branch
from
889dc61
to
378f488
Compare
|
@patrickhlauke If this hasn't been approved as an errata it should have "Erratum Raised" as the label and only gets the "Errata" label once finalized. |
|
@awkawk i'll leave the tagging up to you and your process ;) |
patrickhlauke
added
ErratumRaised
|
I think this is a more substantial normative change and will need more time to evaluate implications. |
without that, i could claim that going into windows' volume mixer and just muting/changing the volume for Chrome satisfies this, as it's independent of the OS overall |
That is beyond the UA, as is asserting PC mute is an option for audio pause/stop. (Something which, until today, I never would have thought anyone brazen enough to claim.) The audio (which plays automatically) is on the web page, it obviously follows that the mechanism for controlling the audio must be on the web page. But we have a few SC which authors can claim to meet by relying upon browser features. So it is not as tidy as I would like. Asserting use of platform/hardware to meet web page SC is not a loophole just for this SC. I do not agree that the idea warrants any air at all. But if it does, maybe the Conformance Requires need tweaking? |
well, you do you. seems like this PR #2621 is superseding this one anyway |
|
I'm afraid this wasn't seen as a sufficient problem to overcome the friction of an SC update: https://www.w3.org/2022/08/16-ag-minutes.html#t10 I'll close this, but there is an understanding update on the cards. |
|
+1 to this
And we should do this uniformly as an editorial fix for both clarity and uniformity.
Suggest this be added to survey
Proposal
That throughout WCAG 2.2 (as an editorial fix):
All lists that are "any of the following" have each choice end with ; and the last choice end with ; or (or ; OR)
All lists that are "all of the following" have each choice end with ; and the last choice end with ; and (or ; AND)
(The caps MIGHT be justified since it is a logical AND or OR …. )
Gregg Vanderheiden
***@***.***
… On Aug 12, 2022, at 11:49 AM, Bruce Bailey ***@***.***> wrote:
@bruce-usab approved this pull request.
I think the first bullet should end ; or rather than a period.
Unfortunately, 2.0/2.1 is not 100% consistent with its at least one of the following is true pattern.
—
Reply to this email directly, view it on GitHub <#1825 (review)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACNGDXSHCX4M4E2PEOOMGSDVY2MC7ANCNFSM45J75IDQ>.
You are receiving this because you are subscribed to this thread.
|
In contrast to #1824 this rewording accepts that the mechanism does not necessarily have to be implemented by the web page itself, but - per the definition of mechanism - can also be provided by the user agent/system. What this change does implement though is the clarification for the pause/stop clause that the pausing/stopping must be independent from any other audio output (which does address @jake-abma's original concern that a system wide general mute/audio off would automatically satisfy the SC, which is not the intended outcome #1533
while a normative change, I don't believe this actually changes the meaning as intended at the time.
Closes #1533