November 14, 2026

Keep, Dismiss, or Drop the Announcement Bar?

Decide whether a thin sitewide notice bar should stay, be dismissible, or come off the page. Give the message a job, and a point at which it stops.

A white web page card in an aluminum stand with a pink strip clipped across its top by two chrome binder clips, beside a chrome hourglass almost run out, on an orange background.
In this guide

The fictional Finch & Field shop added a thin bar above the header to warn visitors that a collection was being rearranged, and that some pickup times would change. The work finished two weeks ago. The bar is still there, stacking with the header on a phone, and it cannot be dismissed.

Decide whether a thin sitewide notice should stay, be dismissible, or come off the page. Give the message a job, and a point at which it stops.

The Finch & Field example is fictional, not a test result.

Decide Who Needs the Notice and When

This guide uses announcement bar as its own term for a thin strip across the top of the page, usually above the header, carrying one short message. Sources talk about promo banners, notification banners, and install-app strips. They do not define “announcement bar,” so the label is ours.

Nielsen Norman Group, in 2019 ecommerce research, advises communicating sitewide promotions on every page, for example with banners at the top of every page, and not making the content look too much like an advertisement, in order to avoid banner blindness. In 2018 eyetracking, they reported that users have learned to ignore content that resembles ads, is close to ads, or appears in locations traditionally dedicated to ads. That is a reason to keep a real notice looking like a notice, not a claim that every bar is ignored.

If the same message is covering the first view as a pop-up, start with When Pop-ups and Banners Block the First View. Nielsen Norman Group recommends a thin, easy-to-dismiss top banner as an alternative to a blocking popup, which is one reason this pattern exists.

Keep, Dismiss, or Drop

The sources below cover related banners and strips, not announcement bars as a distinct pattern. They do not establish a height or message-length rule. Use these questions to decide whether the notice is current, needed, and dismissible.

Question A useful direction
Why does this message need to appear now, and for whom? Keep it if it is genuinely sitewide and needed before the visitor acts, such as a change to pickup times
Can visitors dismiss it, and does it stay dismissed? If it stays, let people close it. Ask the team to keep the same, unchanged notice from coming back after dismissal. A materially updated notice is a separate question
When does it stop being relevant? Drop it when the event is over, as with Finch & Field’s finished rearrangement
Does it duplicate the hero, or stack with other bars? Ask which message still needs to appear, and where, before you recommend dropping or merging one

GOV.UK tells teams to use notification banners sparingly, because there is evidence that people often miss them, and using them too often is likely to make this worse. It also says to avoid showing more than one notification banner on the same page. That guidance comes from a government service design system.

Baymard’s 2019 work on top-of-page “Install App” strips found that those bars cover content and narrow the viewport, and advised that they should not be permanent, should be removed after navigation or time, and should not reappear after dismissal. That advice is about install-app strips, not a general announcement-bar study. The dismissal point still travels: if someone has closed the same, unchanged notice, ask the team to keep it from returning.

Review the Space It Occupies Across Widths

Look at the bar together with the header, especially at a phone width. Should Your Header Stay Visible While You Scroll? already notes that a banner under the header can double the space in use. This guide does not reopen the sticky-header decision. It only asks whether this strip earns the height it takes, and what it pushes down or wraps.

Paste the page address into Online Website Previewer and press Preview. Start at 390 by 844 CSS pixels, then compare 820 by 1180 and 1920 by 1080, the tool’s tablet and desktop sizes. Look at whether the bar wraps, what it pushes down, and how it sits with the header in each view.

If the bar rotates several messages on its own, flag that rotation for an accessibility review. WCAG 2.2 Success Criterion 2.2.2, at Level A, covers moving content that lasts more than five seconds, and the Understanding page also lists auto-advancing messages under auto-updating content. A short rotation interval is not a reason to skip a pause control. If the strip has become a multi-item rotator, Homepage Carousels: Keep, Fix, or Drop? is the better guide. A sticky bar must also not entirely hide a focused control, which is the 2.4.11 question already noted in the pop-ups guide.

A useful note might say: “On Finch & Field at [address], in the 390 by 844 preview, a rearrangement notice is still in the announcement bar two weeks after pickup times returned to normal, it cannot be dismissed, and it stacks with the header. Please remove the expired notice. For future notices, agree on when each one should come down and let visitors dismiss it while it remains relevant.”