Those "Someone Just Bought This" Popups Might Be an Accessibility Problem

If you run an online store, you have almost certainly seen — or installed — one of those little popups that slide up from the corner of the screen: “Sarah from Ohio just purchased the Deluxe Bundle,” “12 people are viewing this right now,” “Only 3 left in stock!” They are called social proof or sales notification widgets, and they are sold as a quick conversion boost. You add an app like Fomo, Nudgify, TrustPulse, Provely, or one of the dozens built into Shopify and WooCommerce, flip a switch, and the little notifications start appearing.

Here is the part nobody mentions in the app store listing: these widgets are added on top of your site by a third party, and many of them are built with almost no attention to accessibility. For a shopper using a screen reader, a keyboard, or a screen magnifier, a badly built social proof popup can be anything from mildly annoying to a genuine barrier — and because it is a customer-facing feature that pressures people to buy, it is exactly the kind of thing that shows up in accessibility complaints and demand letters.

You do not need to code to understand what goes wrong here, or to check your own store. This guide walks through the specific problems, why they matter legally and commercially, and what to look at today.

What these widgets actually do to a page

A social proof popup is a small box that appears, usually in a bottom corner, without the shopper doing anything. It shows up on a timer, disappears after a few seconds, and then another one appears. That “appears on its own, disappears on its own” behavior is the root of most of the accessibility problems.

Think about how different people experience that same little box:

  • A sighted mouse user glances at it, maybe reads it, and ignores it. It is background noise.
  • A screen reader user may have the text of every single popup read aloud, interrupting whatever they were actually trying to do — reading a product description, filling in the checkout form, comparing two items. Imagine a voice cutting in every eight seconds to say “Sarah from Ohio just purchased” while you are trying to enter your credit card number.
  • A keyboard user may hit Tab and find their focus jumping into the popup’s close button, or worse, getting stuck somewhere unexpected because the widget grabbed focus.
  • A person with a vestibular disorder or attention-related disability may find the constant motion and interruption genuinely disorienting, making the whole page harder to use.

None of these people did anything to summon the popup. It arrived uninvited, and for some of them, it does not leave cleanly.

The three most common failures

1. It interrupts screen readers constantly

Many of these widgets are implemented as what developers call a “live region” — an area of the page that announces itself to assistive technology whenever its content changes. That is the right tool for something urgent, like “your payment failed.” It is completely the wrong tool for “Marcus in Denver just bought a candle.”

When a marketing popup is set to announce assertively, it barges in front of whatever the screen reader was saying and reads the sales message instead. New popup every few seconds means a new interruption every few seconds. A shopper trying to read your return policy or complete checkout is fighting your own marketing widget for the right to hear the page.

The related WCAG guideline here is 4.1.3 Status Messages (Level AA), which is about appropriate announcements — and 2.2.2 Pause, Stop, Hide (Level A), which says that moving, auto-updating content must have a way to pause or dismiss it. A stream of popups the user cannot stop fails that basic expectation.

2. The close button does not work by keyboard — or has no accessible label

Almost every popup has a little ”×” to dismiss it. Check two things:

  • Can you reach and activate it with only the keyboard? Try Tab and Enter. If the only way to close the popup is to click the tiny × with a mouse, keyboard-only users — including many people with motor disabilities — are stuck with it.
  • What does a screen reader call that button? If it is just a decorative ”×” character with no text alternative, a screen reader may announce “button” with no idea what it does, or read the raw symbol. The button needs an accessible name like “Close notification.”

This maps to WCAG 2.1.1 Keyboard (Level A) and 4.1.2 Name, Role, Value (Level A). A control everyone else can use with one click should not be a dead end for someone on a keyboard.

3. It covers content and steals focus on mobile

On a phone, that corner popup is proportionally huge. It frequently covers the “Add to cart” button, a form field, or the checkout total — the exact things the shopper is trying to reach. If the popup also captures keyboard focus when it appears, someone navigating by keyboard or switch device can be yanked away from the field they were filling in, then dropped somewhere else when it disappears.

There is also a contrast trap: many of these widgets use light grey text on a white card, or a faint timestamp like “2 minutes ago,” that fails the 4.5:1 contrast minimum in WCAG 1.4.3 (Level AA). You can have a perfectly accessible store and then bolt on a third-party widget that quietly reintroduces contrast failures across every page.

Why this is a real risk, not a nitpick

It is tempting to think “it’s just a little popup.” But two things make social proof widgets riskier than they look.

First, they appear on every page, including your highest-stakes pages — product pages and checkout. Accessibility problems on a blog post are unfortunate. Accessibility problems that interrupt or block checkout go straight to the heart of whether a disabled customer can actually buy from you, which is precisely what accessibility law is concerned with.

Second, you are legally responsible for third-party content on your site. In the United States, a wave of ADA-related web accessibility demand letters and lawsuits has repeatedly named third-party widgets and plugins as part of the complaint — courts and plaintiffs generally do not care that the barrier came from an app you installed rather than code you wrote. In the European Union, the European Accessibility Act (in force since June 2025) applies to e-commerce services, and “we used an off-the-shelf popup app” is not a defense. The widget is on your store, so it is your problem. (This is general information, not legal advice — talk to a qualified attorney about your specific situation.)

There is a plain commercial angle too. Social proof widgets exist to increase conversions. If yours is actively making the buying experience worse for a slice of your customers — and roughly one in four adults has some form of disability — you may be trading a small lift from some shoppers for lost sales and frustration from others.

How to check your own store (no code)

You can evaluate your popup in about ten minutes with tools already on your computer.

  1. The keyboard test. Load a product page. Wait for a popup to appear. Now, without touching your mouse, press Tab a few times. Can you land on the popup’s close button? Press Enter — does it close? If you cannot reach or dismiss it with the keyboard, that is a real failure.

  2. The screen reader test. Turn on the screen reader already built into your device — VoiceOver on Mac and iPhone (Command+F5 on Mac), or Narrator on Windows (Windows+Ctrl+Enter). Browse a product page normally and just listen. Does the popup interrupt what you are reading? Does it announce itself over and over? Does the close button announce a clear name, or just “button”? Our walkthrough on how to test your website with VoiceOver covers the basics if you have never done this.

  3. The mobile test. On your phone, go to a product page and try to tap “Add to cart” while a popup is showing. Does the popup cover it? Try to complete a checkout with the notifications running. If the popup gets in the way of the thing customers must tap, that is a problem worth fixing.

  4. The contrast glance. Look at the popup text — especially the small timestamp and any secondary line. If it is faint grey on white and hard for you to read, it is failing many of your customers.

What to do about it

You have a few options, in rough order of least to most effort.

Turn it off and measure. The simplest, most honest question: is the widget actually earning its place? Many stores install these on a hunch and never test whether they lift revenue. Turn it off for two weeks, watch your conversion rate, and see if anything changes. If it does not, you have removed a whole category of risk for free.

Slow it down and thin it out. If you keep it, reduce the frequency dramatically. A popup every 30-60 seconds is far less disruptive than one every 8 seconds. Turn off popups on the checkout pages entirely — there is nothing to gain by distracting someone who is already buying, and a lot to lose.

Check the app’s accessibility settings. Some of the better widget apps now include options like “respect reduced motion,” a persistent (not assertive) announcement mode, or a keyboard-accessible close button. Open your app’s settings and look. If the app has no accessibility options and no accessibility statement anywhere, that tells you something about how much they have thought about it.

Ask the vendor directly. Email the app’s support and ask two questions: “Is your notification keyboard-accessible and does it work with screen readers?” and “Do you have a VPAT or accessibility conformance report?” The answer — including a non-answer — helps you decide whether to keep them. If you are weighing third-party tools generally, our guide to third-party widget accessibility has a fuller checklist.

Switch to a quieter form of social proof. The most accessible “social proof” is not an interrupting popup at all. Genuine, well-marked-up customer reviews on the product page, a simple “1,200+ orders shipped” line in your copy, or real ratings do the same persuasive job without hijacking anyone’s screen reader. They live in the normal page content, where every visitor — and every search engine — can read them on their own terms.

The bigger point

Third-party apps are how small stores get big-store features without a developer, and that is genuinely great. But every widget you bolt on is a piece of your site’s accessibility that you have outsourced to someone else — and you are still the one holding the risk. Social proof popups are one of the most common of these add-ons, and one of the most likely to be built carelessly, because they are designed to grab attention rather than to be considerate.

The good news is that this is one of the easier things to get right. Test it for ten minutes. If it interrupts, blocks, or traps your customers, either fix the settings, replace it with quieter social proof, or turn it off and prove it was earning its keep in the first place. Your disabled customers — and your legal exposure — will both be better for it.

We’re building a simple accessibility checker for non-developers — no DevTools, no jargon. Join our waitlist to get early access.