Skip to content
GDPR compliant. Hosted in the EU.
14-day free trial →
WCAG 2.2.1 and 2.2.2Black WeekBFSG
Compliance 16 min read 15 Nov 2026

Countdowns and cart timers: making time limits accessible

Countdown bars and cart reservations for Black Week: what WCAG 2.2.1 and 2.2.2 require, how pause and extend controls work and what an automated scan detects.

X

XICTRAQ®

XICTRAQ®

AccessibilityWCAG 2.2Black WeekBFSG
20 s
minimum time to extend a time limit after the warning (W3C, WCAG 2.2)
9.4 %
of people in Germany had a severe disability at the end of 2025 (Destatis)
3
axe-core rules for 2.2.1 and 2.2.2, none of them checks a JavaScript countdown (axe-core)
Countdown and cart timer under WCAG 2.2Black Week campaign page: pause control on the bar, reservation with an extend buttonshop.example/black-weekBlack Week ends in · hrs : min : sec021437::PauseHideSaleLive stockReservation expires in 01:52Warning before expiry, extend with one clickExtend2.2.2 Pause, Stop, HidePause control next to the displayHide without a focus trapControl the update frequency!no 5-second exception2.2.1 Timing AdjustableWarning before expiryat least 20 seconds to extendcan be extended at least 10 timesalternatively: turn off, adjustchecked automatically (axe-core)meta-refresh · blink · marqueecheck manuallyCountdown and timer built in JavaScriptSource: W3C, WCAG 2.2, success criteria 2.2.1 and 2.2.2; axe-core 4.12, rule descriptions
For Black Week, many shop pages gain new widgets: a countdown bar above the header, a stock indicator that updates on its own and a cart timer that holds items for a limited time only. For accessibility, these are not design details. Under WCAG 2.2, a countdown that starts on its own and sits next to other content is auto-updating information that users must be able to pause, stop or hide, or whose update frequency they must be able to control (W3C). A reservation period in the cart is a time limit that users must be able to turn off, adjust or extend with a simple action (W3C). This article explains what success criteria 2.2.1 and 2.2.2 require, how to build both widgets accessibly, what an automated scan detects and which checks remain manual.

New campaign widgets just before Black Week

Campaign widgets are rarely planned far in advance. A few days before launch, a plugin or theme component arrives that is meant to create urgency. Three forms are typical: a bar that counts down to the end of the sale, a notice such as "Only a few left in stock" that changes on its own, and a cart that reserves items for a fixed period and then releases them.

All three work with time, and that is exactly where the barrier lies. According to the W3C explanations, people who are blind and use a screen reader may need more time to understand the layout of a page, find information and operate controls (W3C). People with physical disabilities often need more time to react, type and complete tasks (W3C). Blinking notices particularly distract people with attention deficit disorders and make it hard for them to concentrate on other parts of the page (W3C).

The group affected is not small. At the end of 2025, a little more than 7.8 million people with a severe disability lived in Germany, 9.4 percent of the population (Destatis). A little more than a third of them were 75 or older (Destatis). The count only includes people who have been assessed with a degree of disability of at least 50 and issued a valid ID card (Destatis); anyone who needs more time without such a card is missing from this figure. If you keep the campaign page at the same address every year, as described in the article on the Black Friday page with a permanent URL, last year's fixes are not lost.

What the BFSG and WCAG require from online shops

The German Accessibility Strengthening Act applies to a defined list of services provided to consumers after June 28, 2025 (BFSG, Section 1(3)); the list includes services in electronic commerce (BFSG, Section 1(3) No. 5). An offering is accessible if people with disabilities can find, access and use it in the usual way, without particular difficulty and generally without help from others (BFSG, Section 3(1)).

The ordinance is more specific: websites must be perceivable, operable, understandable and robust (BFSG ordinance, Section 12 No. 3). In electronic commerce, this explicitly also applies to identification, security and payment functions (BFSG ordinance, Section 19 No. 2). A cart that expires during payment therefore affects the checkout itself.

The act does not name a WCAG version. It presumes that services meet the requirements if they conform to harmonized standards whose references have been published in the Official Journal of the European Union (BFSG, Section 4). How EN 301 549 comes into play and why WCAG 2.2 belongs in the test profile now is explained in the article on the test profile under the new version of EN 301 549. For countdowns and reservations, the version hardly matters: both criteria are Level A and neither is new in WCAG 2.2 (W3C).

Microenterprises that offer or provide services are exempt (BFSG, Section 3(3)), meaning companies with fewer than ten employees and annual turnover or a balance sheet total of no more than 2 million euros (BFSG, Section 2 No. 17). Anyone offering a service that does not meet the requirements risks a fine of up to 100,000 euros (BFSG, Section 37). How market surveillance proceedings work and how to document a remediation is covered in the article on accessibility enforcement and evidence. Whether a specific offering is covered is a matter for legal advice.

Two success criteria, two different questions

Both criteria sit under the guideline "Enough Time", but they ask different questions. 2.2.2 asks whether moving or auto-updating content can be tamed so it does not disrupt the rest of the page. 2.2.1 asks whether a time limit locks out people who need longer to complete a task.

The countdown falls under 2.2.2: it starts on its own, updates at fixed intervals and sits next to other content. According to the W3C explanations, 2.2.1 is generally not applicable to content that repeats or is synchronized with other content, as long as users can control it, for example scrolling text or carousels with the controls of 2.2.2 (W3C). The cart reservation, on the other hand, runs out for each visitor individually, and whoever misses it loses the item. Any process that happens without user initiation after a set time or on a periodic basis counts as a time limit (W3C).

WidgetRelevant criterionWhat is requiredCommon mistake
Countdown bar2.2.2, auto-updating partpause, stop, hide or control the frequencyticking every second without a control
Live stock indicator2.2.2, auto-updating partthe same, once it changes on its ownevery new value is read aloud
Cart reservation2.2.1 Timing Adjustableturn off, adjust or extend before expiryitems disappear without warning
Session timeout in checkout2.2.1, set by the serversame as the reservationentries are lost after expiry
Scrolling text with a discount code2.2.2, moving, blinking, scrolling partpause if it runs longer than five seconds (W3C)ticker without a stop

The part on moving content also applies to product videos that start automatically; the thresholds for video and audio are covered in the article on analyzing product images and videos.

The countdown bar: pause, stop, hide

For auto-updating information that starts automatically and is presented in parallel with other content, WCAG 2.2 requires a mechanism that lets users pause, stop or hide it, or control the frequency of the update, unless the updating is essential to the activity (W3C). A countdown starts when the page loads and runs next to products and the cart.

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.

— W3C, WCAG 2.2, Success Criterion 2.2.2 Pause, Stop, Hide, auto-updating part

One detail is often overlooked. For moving and blinking content, a mechanism is only required if it lasts more than five seconds (W3C). For auto-updating content this exception does not exist, because it makes little sense to auto-update for a few seconds and then stop (W3C). A countdown that ticks every second therefore needs a control from the start.

  • Pause: A "Pause countdown" button freezes the display. On resume, it jumps to the current time; the W3C names an auction timer as an example of content that would otherwise show outdated and misleading values after a pause (W3C).
  • Stop: The countdown is replaced by a fixed statement such as "Sale ends Monday, 11:59 pm".
  • Hide: A button removes the bar; the end of the sale then appears on the campaign page itself.
  • Control the frequency: Users choose how often the display changes, for example once a minute. The criterion explicitly allows this option for auto-updating content (W3C).

The mechanism must not tie up the user or the focus so that the page can no longer be used (W3C). A countdown that only stops while the mouse pointer or keyboard focus rests on it is therefore not enough. The button belongs right on the bar, can be reached by keyboard and has a clear name. How to check reachability and visible focus is shown in the article on keyboard navigation and focus testing.

One control for everything that moves

If there are several moving or auto-updating elements, the W3C recommends as good practice a single control that pauses all of them at once (W3C). With a countdown, a stock counter and a ticker, this is more convenient than three separate controls.

Stock levels and other live indicators

A stock indicator that regularly queries the server and shows the new value is auto-updating content too: this refers to content that updates or disappears based on a preset time interval (W3C). The same applies to notices such as "Just bought in Hanover" that disappear on their own after a short time.

For screen readers, a second question arises. WCAG 2.2 requires status messages to be programmatically determinable through role or properties, so assistive technologies can present them without moving focus (W3C). The W3C gives the example of a cart where the new item count appears next to the cart icon after an item is added and is announced (W3C). A stock indicator that is read aloud on every change, by contrast, drowns out whatever the user is reading.

The rule of thumb: announce only changes the customer is meant to react to, such as "Item now only available in size M", and update pure counter values silently. The most common problems with names, labels and contrast are summarized in the overview of the most common WCAG 2.2 errors on business websites.

Cart reservation: a time limit under 2.2.1

If a shop reserves items for a certain time, the content sets a time limit. For it, WCAG 2.2 requires at least one of six conditions to be met (W3C): three solutions and three exceptions. According to the W3C explanations, turning a limit off is better than adjusting it, and adjusting is better than extending (W3C).

Turn off

The user can turn off the time limit before encountering it (W3C). In a shop, for example, a cart without expiry; the checkout shows whether the items are still available.

Adjust

The user can set the limit in advance to at least ten times the default (W3C). With a 15-minute reservation, 150 minutes must therefore be selectable.

Extend

The user is warned before time expires, has at least 20 seconds to extend the period with a simple action (W3C) and can do so at least ten times (W3C).

The exceptions are narrow: real-time events such as an auction, limits where extending would invalidate the activity, and time limits longer than 20 hours (W3C). As an essential limit, the W3C describes a ticket site that gives the user two minutes to confirm a purchase before the seats are returned to the general pool (W3C). For an ordinary cart with sale items, this reasoning usually carries less weight, because a sweater is not a specific seat. Without that exception, the extension is the minimum.

Even with an essential limit, the example shows a way out: the ticket site moves as much of the process as possible out of the time-critical period and lets users enter their name and payment method beforehand (W3C). In a shop, that means collecting the address and payment method before the reservation or taking them from the customer account.

The session timeout in checkout counts too. Time limits set by web servers are under the control of the organization and are covered by the criterion (W3C). Criterion 2.2.6 at Level AAA is stricter: users are to be warned of any inactivity period that could cause data loss, unless the data is preserved for more than 20 hours (W3C). This is not required at Level AA, but it is a useful benchmark for checkout.

  1. State the period: When an item is added, the reservation period appears as text.
  2. Warn in time: Before expiry, a notice appears that is announced as a status message and leaves at least 20 seconds to respond (W3C).
  3. Extend easily: An "Extend" button that can be reached by keyboard, without re-entering data.
  4. Extend often enough: The extension is possible at least ten times (W3C).
  5. Lose nothing: If the period expires, entries are kept, and a notice names the items that are no longer reserved.

Screen readers: announcing timers without disruption

WAI-ARIA has a dedicated role for countdowns. The timer role describes a live region with a counter for elapsed or remaining time (WAI-ARIA 1.2). Elements with this role have an implicit aria-live value of off (WAI-ARIA 1.2). That is intentional: a screen reader should not read out a new number every minute. Setting aria-live on the countdown to polite creates exactly that constant chatter.

The shop should only announce events the customer can react to, such as the warning before the reservation expires. A status region whose content is read without moving focus is suitable for this (W3C). The example shows the basic pattern with the end of the sale as text, a pause button, a hide button and a warning:

sale-countdown.html
<div class="promo-bar" role="region" aria-label="Black Week sale">
  <p>Sale ends on <time datetime="2026-11-30T23:59">November 30 at 11:59 pm</time></p>
  <p role="timer" id="countdown"></p>
  <button type="button" id="countdown-toggle">Pause countdown</button>
  <button type="button" id="promo-hide">Hide bar</button>
</div>
<div role="status" id="cart-status"></div>

<script>
  const end = new Date('2026-11-30T23:59:00+01:00');
  let paused = false;

  function render() {
    if (paused) return;
    const minutes = Math.max(0, Math.floor((end - Date.now()) / 60000));
    document.getElementById('countdown').textContent =
      Math.floor(minutes / 60) + ' hrs ' + (minutes % 60) + ' min left';
  }
  render();
  setInterval(render, 60000); // calmer rhythm: one minute instead of one second

  document.getElementById('countdown-toggle').addEventListener('click', (event) => {
    paused = !paused;
    event.currentTarget.textContent = paused ? 'Resume countdown' : 'Pause countdown';
    render(); // on resume, show the current remaining time right away
  });

  document.getElementById('promo-hide').addEventListener('click', () => {
    document.querySelector('.promo-bar').hidden = true;
  });

  // Reservation: warn in time, extend without re-entering data.
  // Call this once the reservation has two minutes left.
  function warnReservation() {
    document.getElementById('cart-status').textContent =
      'Your reservation expires in two minutes. Select "Extend" in the cart to keep your items.';
  }
</script>

Here, 2.2.2 is met by the pause button and the hide button. The one-minute rhythm alone would not suffice because the user does not control it, but it makes the display calmer. The end of the sale stays readable as text, and the status region is already in the document when the page loads, so assistive technologies notice the warning. After hiding the bar, focus should land in a sensible place, such as the start of the main content.

Real deadlines instead of artificial urgency

A countdown also has a competition law side. Under the annex to the German Act Against Unfair Competition, it is unlawful per se toward consumers to falsely state that certain goods or services are only available for a very limited time in order to prompt an immediate decision without leaving time and opportunity to decide on an informed basis (UWG, Annex No. 7). A countdown that starts over after every reload can be exactly such a statement.

For accessibility and competition law, the conclusion is the same: a deadline should be real and stated as text on the page; the countdown is only an additional presentation. If you show strikethrough prices during the sale, you should also be able to document the reference price, see the article on strikethrough prices on Black Friday.

Have the individual case reviewed

Whether a design is misleading depends on the overall impression; this classification is not legal advice. Technically, it helps to maintain the end of the sale in one place and output it from the same source in the countdown and the text.

What an automated scan detects and what it does not

For 2.2.1 and 2.2.2, version 4.12 of axe-core lists exactly three rules: meta-refresh for 2.2.1, and blink and marquee for 2.2.2 (axe-core). The first is triggered when a page reloads or redirects with a delay via <meta http-equiv="refresh"> and is rated critical. The other two find obsolete elements for blinking and scrolling text and are rated serious (axe-core).

A JavaScript countdown slips through this grid. No rule assesses whether there is a pause control or whether a reservation warns before it expires, and XICTRAQ® does not recognize such a countdown as a time limit either. Whether a control stops the update can only be shown by operating it.

The scan is still worthwhile for new campaign widgets. A pause button without a name, a bar with insufficient contrast or a close icon with a tiny target are found by axe-core through general rules. XICTRAQ® checks with axe-core against WCAG 2.0, 2.1 and 2.2 Level AA with more than 60 rules (XICTRAQ). The scope is described on the accessibility feature page; for a spot check, the free accessibility check is enough.

CheckAutomated with axe-coreManual
Delayed reload via meta refresh (2.2.1)yes, rule meta-refreshno
blink and marquee elements (2.2.2)yes, rules blink and marqueeno
JavaScript countdown can be paused (2.2.2)noyes
Reservation warns and can be extended (2.2.1)noyes
Name of the pause button (4.1.2)yes, rule button-namecheck the wording
Contrast of the bar (1.4.3)yes, rule color-contrastfor gradients and images
Target size of the controls (2.5.8)yes, rule target-sizeuncertain cases
Announcement of the warning (4.1.3)nowith a screen reader
What the scan does not certify

A run without findings only means that the automatable rules passed. Whether a countdown can be paused and whether a reservation warns in time remains a manual check.

Manual check before the sale starts

The check makes sense on a preview with an active countdown and again on the first day of the sale, because plugins and marketing tools often add something at that point.

  • Observe: Note everything that moves, counts or appears and disappears on its own.
  • Find the control: For each element, use the Tab key to reach a control for pausing, stopping or hiding it, and activate it. If there is none, 2.2.2 is open.
  • Check the effect: Once paused, the display stays still, even when focus moves on.
  • Check resume: Afterwards, the countdown shows the current remaining time.
  • Screen reader: Stay on the page for a minute. If numbers are read out continuously, the live region is set up incorrectly.
  • Reservation: Let the period run out and check whether a warning comes first, whether it is announced and whether at least 20 seconds remain to extend (W3C).
  • Repeat the extension: It must be possible at least ten times (W3C).
  • Expiry without loss: Entries are kept, and the notice explains what happened.

Part of this can be repeated as a scenario. In browser monitoring, available from the Business plan, a real Chromium browser clicks through a defined flow and checks texts and visible elements. If you set up the step "Pause countdown" with a text check for "Resume countdown", you will find out when an update removes the button. The operator creates the scenario; it does not detect countdowns on its own and does not check screen reader announcements.

End of sale as text, countdown as a bonus

If you state the end of the sale as fixed text, you have already delivered the most important information accessibly. The countdown becomes a bonus that can be paused or hidden.

Keeping campaign widgets in view after launch

Many barriers only appear with the third change: marketing swaps the banner, a plugin update changes the bar, a new notice slides over the pause button. How such regressions arise after a deploy is described in the article on monitoring WCAG regressions.

In XICTRAQ® monitoring, the accessibility scan runs daily on the Free plan and every 12 hours on all other plans (XICTRAQ). If the axe-core score drops below 50, monitoring creates an alert, and below 30 it is rated critical (XICTRAQ). The scan checks the monitored address itself, not its subpages, so for Black Week the campaign page belongs in monitoring as a separate website. Which hours are less suitable for changes is shown by analyzing visitor times by hour.

The automated part is handled by the XICTRAQ® accessibility check with regular runs, score history and alerts; you can start your own test with a free registration. The rest is the manual check: pause, resume, extend and listen to what the screen reader says.

Sources and legal basis

This article is based on: W3C, Web Content Accessibility Guidelines (WCAG) 2.2, Recommendation of December 12, 2024, success criteria 2.2.1, 2.2.2, 2.2.6 and 4.1.3; W3C, Understanding WCAG 2.2 for Timing Adjustable, Pause, Stop, Hide and Status Messages; W3C, WAI-ARIA 1.2, timer role; German Accessibility Strengthening Act (BFSG), Sections 1, 2, 3, 4 and 37; Ordinance on the Accessibility Strengthening Act (BFSG ordinance), Sections 12 and 19; German Act Against Unfair Competition (UWG), Annex No. 7; Federal Statistical Office (Destatis), press release No. 246 of July 13, 2026; axe-core, rule descriptions for version 4.12; XICTRAQ, accessibility feature page, pricing overview and compliance documentation. This article is not legal advice.

Does every countdown on a shop page have to be pausable?
If it starts automatically, updates itself and is presented next to other content, WCAG 2.2 requires a mechanism to pause, stop or hide it or to control its frequency (W3C). The only exception is essential updating; for a sale countdown, this is usually not the case.
Is it enough if the countdown stops after five seconds?
There is no five-second threshold for auto-updating content; it only applies to moving, blinking and scrolling content (W3C). A frozen countdown also shows the wrong remaining time. A pause button is the more sensible approach.
What is the minimum duration for a cart reservation?
WCAG 2.2 does not set a minimum duration. Users must be able to turn off the period, set it in advance to at least ten times the default or extend it after a warning; at least 20 seconds remain to do so, and extending must be possible at least ten times (W3C). Periods of more than 20 hours are exempt.
Does an automated scan detect a countdown without a pause button?
Usually not. For 2.2.1 and 2.2.2, axe-core checks delayed reloads via meta refresh and the blink and marquee elements (axe-core). A JavaScript countdown is checked manually; the scan still finds errors such as a button without a name.
Does the BFSG also apply to small online shops?
It covers services in electronic commerce for consumers (BFSG, Section 1(3) No. 5). Microenterprises with fewer than ten employees and annual turnover or a balance sheet total of no more than 2 million euros are exempt (BFSG, Section 2 No. 17). The individual case should be clarified by legal advice.
Can a countdown restart after the page reloads?
Technically yes, but it is risky under competition law. Falsely stating that an offer is only available for a very short time in order to prompt an immediate decision is one of the commercial practices that are unlawful per se (UWG, Annex No. 7). A countdown should therefore show a real end of the sale.

Related in XICTRAQ®

Start in 60 seconds

Let XICTRAQ® watch your website.

Free plan with no fixed term available. No credit card, no installation, no hidden fees.