# Sale Countdown Timers That Do Not Shut Anyone Out Source: https://storefronta11y.com/blog/2026-10-29-accessible-countdown-timers-sale-banners.html Reviewed October 29, 2026 Countdown timers sit in a specific legal and practical corner of accessibility. WCAG 2.1 success criterion 2.2.1, Timing Adjustable, exists because time limits disadvantage people who read slowly, use assistive technology, or need longer to complete a form. A marketing banner that counts down to the end of a sale is not the same as a session timeout, and the distinction matters: the timer itself usually does not remove the shopper ability to buy. But stores keep building versions that do cause real harm: flashing digits, prices that change mid checkout, and cart holds that expire with no warning or extension. ## Separate the banner from the deadline that actually binds A display timer announcing that a sale ends at midnight is information. A cart reservation that releases held stock after ten minutes is a binding limit. The first needs to be readable and non distracting; the second needs the full timing adjustable treatment: warn the user before expiry, give at least twenty seconds to extend with a simple action, and allow extension more than once. Stores routinely get this backwards, polishing the banner while the cart hold expires silently during a slow, screen reader paced checkout. Audit both. Write down every place in your store where time passing changes what a shopper can do, and test those places first, because that list, not the banner, is where the compliance and revenue risk both live. ## Related reading If this topic is useful, these earlier guides go deeper on connected questions: [Accessible Size Charts and Fit Tables for Storefronts](https://storefronta11y.com/blog/2026-10-28-accessible-size-charts-fit-tables-storefront.md), [Skip Links on Storefronts: A Small Fix With Outsized Impact](https://storefronta11y.com/blog/2026-10-28-skip-links-storefronts-accessibility.md), and [Accessible Modal Dialogs on Storefronts: Focus, Escape, and Labels](https://storefronta11y.com/blog/2026-10-27-accessible-modal-dialogs-storefront.md). ## Stop the motion and the screen reader spam A timer updating every second is a live region accident waiting to happen. If the ticking element is marked as a live region, a screen reader may announce every second or every minute, drowning out everything else on the page. The timer text should not be a live region at all; make it available on demand, readable when the user navigates to it, silent otherwise. Visually, digits that flip, pulse, or flash add a second problem: vestibular and attention issues, covered in practice by reduced motion preferences and by the WCAG flashing thresholds. Honor prefers reduced motion by showing a static time remaining, updated at most once a minute, with no animation. A timer that respects reduced motion loses nothing commercially; the deadline still reads clearly. ## Prices that change mid checkout are a trust and access failure When a sale ends while a cart sits open, some stores reprice the cart at the payment step with no explanation beyond a changed total. For a shopper using assistive technology who has spent twenty minutes completing an address form, that surprise is both an accessibility burden and a reason to abandon and complain. The cleaner pattern is to state the rule before it bites: show the time the quoted prices hold until, keep that promise inside the checkout session, and if a price must change, explain it in text at the point of change with the old and new price. Demand letters and chargebacks both like undocumented mid checkout price changes. A plain language note in the banner and the cart costs nothing and removes most of the argument. ## A timer checklist to run before the next sale Read the banner with a screen reader and confirm it does not announce repeatedly. Turn on reduced motion in your operating system and reload: the timer should be calm and legible. Check color contrast on the timer text against its background at the smallest banner size, including the mobile sticky version. Confirm any cart or stock hold warns before expiring and can be extended without starting checkout over. Finally, let a test cart sit through the sale end and document exactly what changes and what the shopper is told. Run that test before the Black Friday version, not during it, when the team has no time to fix what it finds. ## Frequently asked questions ### Does a sale countdown banner violate WCAG timing rules? A display only banner usually does not, because it does not limit the time a user has to complete an action. The timing adjustable criterion applies when a time limit is set by the content, such as a session timeout, an expiring cart hold, or a form that resets. That said, a banner can still fail other criteria if it flashes, auto updates in a live region, or cannot be read due to contrast. Judge the banner on motion and readability, and judge the store real deadlines on timing adjustable. ### How should we handle a cart that reserves stock for ten minutes? Warn before the hold expires, allow the shopper to extend it with one simple action, and do not wipe the cart contents when the hold lapses. The shopper should be told, in text, that stock is no longer reserved, not discover it at payment. During checkout itself, avoid expiring holds at all if you can; a checkout that takes a screen reader user longer is normal use, not abuse. If fraud controls require a limit, make the extension generous and repeatable. ### Why does our timer make screen readers talk constantly? Because the updating element is probably inside a live region, or the whole banner was given an aria live attribute so the sale message would be announced. Live regions announce changes, and a timer changes constantly. Remove the live region from the ticking element, keep the static sale text available as ordinary content, and if an announcement is truly needed, announce once when the banner first appears. Test with a screen reader running for a full minute and listen for repeat announcements. ### Can we keep urgency without a ticking clock? Yes, and many stores should. A clear end date and time in text, a note on how long prices are held, and honest stock information create the same commercial pressure without motion or timing problems. Urgency built on a deadline the store actually honors is also more defensible if a customer complains. If leadership insists on a visual timer, use the calm version: static digits, minute level updates, reduced motion support, and no live region.