Repository navigation
2.2.2 Pause, Stop, Hide interpretation : Is permanent stop via manual interaction on arrows buttons (no explicit play\pause button) sufficient on header announcement bar #5141
Unanswered
juliettefranc
asked this question in
Q&A
Replies: 1 comment
|
@juliettefranc Do you have a live URL that you can share? Given that 2.2.2 includes “there is a mechanism for the user to pause, stop, or hide” and as described, the “A keyboard user who needs to stop the animation has a functional means to do so” what you describe is conforming. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Description:
I'm an accessibility consultant seeking clarification on whether a specific implementation of an announcement bar can be considered compliant with SC 2.2.2 (Pause, Stop, Hide) without an explicit pause/play button.
Component behavior:
The component is an announcement bar with multiple messages that auto-scroll. Arrow buttons are available on all devices.
The conformance question:
For keyboard users who tab through the banner without activating the arrow buttons, the animation resumes after focus leaves. However, the arrow buttons are fully keyboard-accessible (focusable, operable with Enter/Space) and activating them stops the animation permanently.
Can the arrow buttons be considered a sufficient mechanism under SC 2.2.2, given that:
Or does the fact that a keyboard user who only traverses the banner without interacting will experience the animation resuming make this implementation non-compliant?
References consulted:
Thank you for any clarification or guidance.
All reactions