Talk:SC1-4-2-audio-control-audio

Open issues

None.

Ready for review

None.

Closed issues

• What happens if the video-element is video only? Do we have to check that the video actually contains sound? - Added an extra step (step 5).

Annika Nietzio (talk) 13:58, 23 April 2015 (UTC)

• Do we have to check to make sure the sound is actually playing more then 3 seconds? Scripts may be doing something we're not aware of?
• Step 5: This sentence "Check if a mechanism to control the sound is provided as one of the first five links on the page." should be part of the test question. As this can not be automated, it should be part of what we ask the user to do.
• Step 5 should probably have a different word then 'link'. This can also be a button or slider or something like that. - Changed to 'links or buttons'.
• Shouldn't the first 4 steps return inapplicable instead of pass? Because if nothing is playing, there is no problem - Decision: the outcome remains passed.

Wilco Fiers (talk) 13:41, 16 April 2015 (UTC)

• Selector: XPath for the tags would be //*[self::audio or self::video]
• Background: G171 is doubled (G171: G171)

Frank Berker (talk) 13:35, 16 April 2015 (UTC)

• Step 2 and 4: muted and loop are also properties
• Background: G171 - text is the link, should be "G171: Playing sounds only on user request"
• Step 5: should be context-sensitive

Frank Berker (talk) 12:21, 9 April 2015 (UTC)

• Step 5: I can find no hint that the link must be the first one. G170 indicates it should be "located early in the tab and reading order" and the expression Wilco cited below. Maybe we need a reasonable threshold or a help text like it should be in the header. - Changed to 'as one of the first five links on the page'.
• Selector: Wilco is right, everything can be done by script. Else e.g. the selector //audio[@autoplay and @loop and not(@muted)] could fail on all matches automatically and the selector //audio[@muted] could pass on all matches automatically. But caused by the scripting possibilites, the selector should be simply //audio and it should be checked for the paused and muted property.
• Step 2: The duration property should be mentioned.
• Background: Add G60, G170, G171 and F23 for completeness.

Frank Berker (talk) 14:22, 26 March 2015 (UTC)

• Step 5: The term "near the beginning of the web page" is very vague. This is sufficient for expert auditors to figure out but I think we should be a little more explicit. Though I'm not sure how. - Changed to 'as one of the first links on the page'.
• For audio that doesn't have autoplay, this can still be started automatically through scripts. We should consider this.
• It seems to me this test wouldn't change if we were to look at the <video> element in the selector as well. Please consider adding this element -
• How should a user test if the audio lasted more then 3 seconds? Should they guess? - This no longer applies because this step is automatic.
• Merge step 1 into the selector, inapplicable should not be part of the test if it can be avoided.
• We can automatically test the length of the audio, as long as it doesn't loop that should be fine.
• Please move this test case to it's own page, not the page for the success criterion.
• Step 3 question: The sentence isn't structured correct, use "Does the audio stop within 3 seconds?"

Wilco Fiers (talk) 14:33, 19 March 2015 (UTC)