You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
How to handle play/pause or record/stop buttons when the user has a screen reader
#5111
When a website or app plays media, it's common to have a single play/pause or play/stop button that changes the icon, label, and function. If it can record, the record/stop button works the same way.
If I understand WCAG 4.1.2: Name, Role, Value correctly, a button that changes like this should have the change announced by screen readers, but when the button plays or records sound, this means that the screen reader is now talking over the media the user's trying to play or over the user talking. See Spotify for a consistent example, or YouTube for a partial example, since it seems to read the "pause" change the first time you do it during a video.
Should this change be announced if a single button is used for both functions? To avoid the screen reader talking at the same time the media starts playing, should media players use separate play/pause buttons (and recorders use separate record/stop buttons)?
Hi @pwiele
When a screen reader user moves focus to a pause button, you have already have SR audio that may overlap with the video's audio. There should be a feedback after activation that paying has stopped. With single controls that change labels (visually icons) after activation, not all user agents / screen readers seem to expose the changed state, which is why some implementations recommend using separate buttons for play and pause and hiding the one that is not relevant. Using the same button, exposure of the changed label happens in some UA and not in others. It can be forced via aria-live - that works, but it does not seem to be the best fitting semantics (after all, a button label change is not the same as a status message). Not sure whether this contributes to answering your question...
That partially answers my question and is an interesting additional argument in favor of separate buttons. The specific product I work on that led me to ask this has single controls that change labels/icons for both play/pause and record/stop, and we know from testing that screen readers do currently announce the state changes. Good point that the label itself isn't a status message, so maybe that means I was thinking about the original question incorrectly and the answer to my question is that a label change does not need to be announced (just that the new label needs to be available to AT), and the audible confirmation of the user activating the control can be something else?
A "paused"/"stopped" message upon using the pause/stop buttons to disambiguate that effect from other possible reasons the sound stopped (e.g., the media really is silent in that portion, it has finished playing, it is still buffering). The play and record states could receive a brief confirmation beep (something that provides audible feedback without lasting long enough to interfere with listening or recording) even though the beep wouldn't explicitly state what happens, it would at least be learnable (in every situation where our users can listen to or record sound, it can be redone without penalty or time limit) the same way audio indications of app notifications and progress bars are.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
When a website or app plays media, it's common to have a single play/pause or play/stop button that changes the icon, label, and function. If it can record, the record/stop button works the same way.
If I understand WCAG 4.1.2: Name, Role, Value correctly, a button that changes like this should have the change announced by screen readers, but when the button plays or records sound, this means that the screen reader is now talking over the media the user's trying to play or over the user talking. See Spotify for a consistent example, or YouTube for a partial example, since it seems to read the "pause" change the first time you do it during a video.
Should this change be announced if a single button is used for both functions? To avoid the screen reader talking at the same time the media starts playing, should media players use separate play/pause buttons (and recorders use separate record/stop buttons)?
All reactions