Why does accessibility need watching instead of a one-time fix?

A Shopify store changes constantly: theme updates, app installs, new content, seasonal templates. Each change can reopen closed issues. A one-time fix degrades within weeks, silently. Watching keeps the store conformant and, just as important, keeps proving it, which is what matters when a demand letter arrives.

What WCAG version does AccessWatchHQ test against?

WCAG 2.2 Level AA, the standard courts and the DOJ reference for web accessibility. Scans cover the criteria that automated tooling can reliably evaluate, and flag the ones that need human judgment, like whether link text is meaningful, for a documented manual review pass with a named reviewer.

Can I share the score trend with my board or insurer?

Yes, that is what it is for. The monthly report is formatted as a standalone document: methodology, scan dates, score trends, and a dated fix log. Brands use it in board risk updates, cyber and EPLI insurance renewals, and acquisition diligence, where an accessibility lawsuit history is a standard question.

What happens when the score drops?

You get an alert naming the template, the failing criterion, and the change window. Because the watch stores history, you can see exactly which week introduced the problem and which fix closed it. The drop and the recovery both land in the monthly report, showing an active program rather than a lapse.

Does AccessWatchHQ fix the issues for me?

No, and that is deliberate. Your developer or agency fixes issues using the per-issue guidance: criterion, component, theme file, and concrete step. A monitor that also sells fixes grades its own homework. AccessWatchHQ verifies every fix by rescan and stamps it with a date instead of selling hours.

How much does AccessWatchHQ cost?

Every engagement starts with a free accessibility audit, so your starting score and issue list are on the table before anything else. Ongoing monitoring is quoted per storefront after the audit, based on how many stores you run and how often you want them scanned. No long-term contract.

Watching Countdown Timers and Live Sale Clocks

October 29, 2026

Sale countdowns announce every second to screen readers, vanish at 200 percent zoom, and create pressure that timed checkout steps then punish. Here is how to watch them during a promotion.

A countdown clock is meant to create urgency. Built carelessly, it creates noise instead: a live region that reads the remaining time every second, a timer that ends a discount while a shopper is still working through a slow, assistive checkout, a number that updates under a magnifier until the reader loses it entirely.

Sales periods are when stores change pages fastest and test least, so timers deserve their own watch during a promotion, not a line in an annual audit. The failures are specific and checkable in ten minutes, if someone is assigned to look while the sale is live.

Keep the timer quiet

A timer should be readable on demand, not announced constantly. Do not put a per second live region on it. Screen reader users can find and read the remaining time when they want it. An aria live region updating every second drowns out everything else on the page, including the product price and the buy button.

The same goes for visual motion. A flashing or pulsing timer is a distraction for many readers and a risk for some. Keep the digits still, keep contrast at least at the normal text standard, and do not shrink the type to fit a banner strip. If it matters enough to show, it matters enough to read.

Do not let the clock punish a slower checkout

Urgency ends badly when it meets a time limit. If a price or a held item expires, warn well before it does, and extend the time when a shopper is actively checking out. WCAG's timing criterion is blunt about this: time limits set by content need to be adjustable, or essential, and a marketing deadline is hard to argue as essential.

Also state, in words near the timer, what happens when it ends. Price changes, sale ends, code stops working. A shopper who knows the consequence can decide. A shopper staring at a bare clock is just being hurried.

Check it at sale size, not design size

Test the timer where it will actually be seen: on a phone, at 200 percent zoom, under a sticky header, next to the announcement bar it probably shares space with. Timers get cut in half, overlap the menu, or push the discount message off screen in exactly the conditions low vision shoppers use every day.

While you are there, check the sale badge contrast too, and confirm the discounted price is written as text in the product details, not only implied by a strikethrough a screen reader may not convey clearly.

Frequently asked questions

Should a countdown timer use aria live?

Not per second. Constant announcements overwhelm screen reader users. Make the remaining time available as normal readable text, and only announce meaningful changes, such as a final warning before a held item or price expires.

Are countdown timers allowed under WCAG?

A visible timer itself is not banned. Problems arise with flashing, low contrast, constant live announcements, and especially with time limits that cut off a task without warning or a way to extend the time.

What should happen when a sale timer ends during checkout?

The shopper should have been warned beforehand, and an active checkout should be extended or honoured where possible. Silently changing the price at the payment step is both an accessibility failure and a trust problem.

How often should sale elements be checked?

Every promotion, while it is live. Sale pages are assembled quickly from banners, timers, and badges that may never have been tested together, so a pre sale audit from months ago does not cover them.