• Skip to primary navigation
  • Skip to main content
  • Skip to primary sidebar
Digital A11Y

Digital A11Y

Your Accessibility Partner

  • About
  • Articles
  • WAI-ARIA
  • WCAG
  • Resources
    • Cheat Sheets
    • A11Y Blogs
    • A11Y Toolkit
  • Contact
You are here: Home / Web Accessibility / WCAG / Understanding SC 2.2.2 Pause, Stop, Hide

Understanding SC 2.2.2 Pause, Stop, Hide

Last Modified: April 30, 2018 by Raghavendra Satish Peri 1 Comment

2.2.2 Pause, Stop, Hide: For moving, blinking, scrolling, or auto-updating information, all of the following are true: (Level A)

  • Moving, blinking, scrolling: For any moving, blinking or scrolling information that (1) starts automatically, (2) lasts more than five seconds, and (3) is presented in parallel with other content, there is a mechanism for the user to pause, stop, or hide it unless the movement, blinking, or scrolling is part of an activity where it is essential; and
  • Auto-updating: For any auto-updating information that (1) starts automatically and (2) is presented in parallel with other content, there is a mechanism for the user to pause, stop, or hide it or to control the frequency of the update unless the auto-updating is part of an activity where it is essential.
  • This success criterion intends to avoid distractions when the users are interacting with any web page. Moving. Blinking an automatically updating contents such as motion pictures, animations, real-time games, multimedia presentations and auto-updating stock tickers cause problems for screen reader users, users with reading difficulties, low vision users, users with attention deficit disorder and other cognitive disabilities while they operate and consume the content.

    This success criterion doesn’t prevent such contents with such designs being used. But it just instructs that Blinking, moving & scrolling content that lasts more than 5seconds and Parallelly presented must be provided with pause, stop or hide button. While blinking content is not equivalent to flashing content if the content that blinks more than 3 times per second it is considered as flashing content. It is a best practice to avoid content that is blinking, moving or scrolling.

    When Auto updating content is found on news websites, live sports sites that update scores etc., even this content should be provided with pause button or provide a mechanism where the user can set the interval of when the update of the live region can take place. Sometimes the auto updating content might refresh entire page or only the portion of the content that is being updated. Note that when a live score or such live update happens and if the user resumes from pause state, it is not necessary to resume where the user has paused but to resume where the live event is at the point of resume.

    Points to remember

    • Avoid moving, blinking scrolling content if possible.
    • Content should not blink more than 3 times per second, if it does blink 3times per second then it is considered as flashing & will fail WCAG.
    • Auto updating content should be provided with a pause button or provide a mechanism for the user to specify when the update can happen.
    • If the entire page contains moving, blinking, scrolling & auto updating content then pause, stop or hide buttons are not required as there is no parallel content.
    • Animation that conveys the users that a page or content is loading doesn’t require to meet this success criterion.

    References

    Understanding Success Criterion 2.2.2

    Share A11Y Love

    • Twitter
    • LinkedIn
    • Facebook
    • Reddit

    More Accessibility Articles

Filed Under: WCAG Tagged With: A11Y, accessibility, Blinking Content, Moving Content, Play/pause, WCAG

About Raghavendra Satish Peri

Raghavendra Satish Peri is a digital accessibility evangelist working at Deque Systems as Senior Accessibility Consultant breaking web accessibility & mobile accessibility challenges. He authors an Accessibility Blog & is galvanizing the adoption of accessibility by inspiring the local tech community with meetups and mentorship. He propelled this thought by founding HelloA11y, a community of accessibility professionals, developers and enthusiasts. When away from his computer, Raghava can be found at local cafes & restaurants sampling cuisines, attending local meetups, listening to audio books or writing on his Personal Blog. Raghavendra Satish Peri also helps small business & individuals with Digital Marketing Trainings & SEO consulting… He has been building websites & doing SEO Consulting for more than 14years.

Reader Interactions

Comments

  1. Kameshwari says

    April 30, 2018 at 7:26 am

    Well explaned Raghava.

    Reply

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Primary Sidebar

Get Digital A11Y in Your Inbox

Recent A11Y Articles

  • Understanding SC 4.1.3 Status messages
  • Understanding SC 2.5.4 Motion Actuation
  • Understanding SC 2.5.3 Label in Name
  • Knowbility looking for mentors in its Accessible Internet Rally
  • Understanding SC 2.5.2 Pointer Cancellation

Recent Comments

  • Al on Understanding SC 4.1.2 Name, Role, Value
  • Randy on Screen Readers & Browsers! Which is the Best Combination for Accessibility Testing?
  • Raghavendra Satish Peri on Screen Readers & Browsers! Which is the Best Combination for Accessibility Testing?
  • Raghavendra Satish Peri on Understanding SC 1.4.12 Text Spacing
  • Raghavendra Satish Peri on Understanding SC 4.1.2 Name, Role, Value

A11Y Categories

  • Design
  • Events
  • HTML
  • IOS
  • Mobile Accessibility
  • News
  • Tools
  • Uncategorized
  • WAI-ARIA
  • WCAG
  • Web Accessibility

  • Privacy Policy
  • Sitemap
© 2021 Digital A11Y