
How to Design an Accessible Scrolling Ticker
Design motion that can be paused, read, navigated, and understood with keyboard controls, screen readers, reduced-motion settings, strong contrast, and static alternatives.
Interface design
Use motion as an optional enhancement over a complete, semantic, keyboard-friendly, responsive, and readable static component.
A ticker’s content should form a complete list, table, or set of cards before animation begins. That static structure supplies a logical reading order, supports keyboard navigation, survives script failures, and gives reduced-motion users an equivalent experience.
Provide a visible pause and resume control that works with keyboard and touch. Preserve the chosen state when practical. Do not restart motion merely because focus changes, and do not hide the control until hover.
Use the user’s motion preference to disable continuous scrolling and nonessential transitions. Reveal a static row, wrap items, or paginate manually. The design should not require a reader to change system settings to escape motion on the page.
Combine color with a plus or minus sign, arrow, word, or accessible status. Differentiate zero change, missing data, stale data, and closed sessions without relying on red and green alone.
Cloned items used to create an infinite visual loop should be hidden from assistive technology. Automatic updates should not continuously interrupt screen readers. Every linked item needs a meaningful accessible name and visible focus state.
On narrow screens, switch from a long horizontal crawl to wrapping rows, stacked cards, or a manually controlled panel. At high zoom, content must reflow without requiring two-dimensional scrolling for ordinary reading.
Keep reading
Move from the overview into focused implementation and review checklists.

Design motion that can be paused, read, navigated, and understood with keyboard controls, screen readers, reduced-motion settings, strong contrast, and static alternatives.

Fix the most common ticker problems: excessive speed, clutter, color-only meaning, stale data, missing pause controls, weak mobile layouts, unstable animation, and deceptive live states.

A start-to-finish checklist covering purpose, fields, data source, disclosures, responsive layout, motion controls, stale states, accessibility, performance, SEO, testing, and operations.
Questions
Clear labels and defined behavior make a ticker easier to trust, test, and maintain.
It is essential for continuous movement, but the design also needs a complete static state, reduced-motion behavior, readable speed, and focus-safe interaction.
Usually not for every price or headline update. Frequent announcements can overwhelm screen-reader users. Reserve live regions for important, intentionally prioritized status messages.
Reflow into static rows, cards, or a manually controlled panel rather than forcing a wide continuous crawl into a narrow viewport.