Accessible popups. Everyone gets the offer.

A popup is one of the hardest parts of a store to use without a mouse or a screen. It appears on top of the page, takes focus, asks for typing, and has to be closed. Done carelessly, it locks keyboard users in, goes unannounced to screen readers, and hides the store behind a box nobody can dismiss. This guide walks through the WCAG 2.2 criteria that matter for an email signup popup, how to test each one, and where the law stands.

By the numbers

WebAIM tests home pages with automated tools, which find only some failures. UsableNet counts lawsuits filed in federal court and in New York and California state courts.

Why popups fail more often

Most accessibility problems on a page stay put. A popup moves focus, covers content and waits for an answer, so a small mistake blocks the whole store. The WebAIM Million found detected WCAG failures on 95.9% of the top 1 million home pages in 2026, with 51% carrying unlabeled form fields and 83.9% carrying low-contrast text. A signup popup can carry both of those problems in one small box. The checks below follow the criteria in WCAG 2.2, the current W3C standard, at levels A and AA unless noted.

Announce it as a dialog

A screen reader user needs to know a dialog has opened and what it is. The W3C's dialog pattern gives the container role="dialog", aria-modal="true" for a popup that blocks the page, and a name from aria-labelledby or aria-label. Veya's popup carries role="dialog" and the name "Signup form". A flyout that leaves the page usable is marked aria-modal="false", because the page behind it stays live.

Move focus in, keep it there, give it back

When a modal dialog opens, focus should move inside it; Tab and Shift+Tab should cycle within it; and when it closes, focus should return to where it was (WCAG 2.4.3, Focus Order). The trap must have an exit: 2.1.2, No Keyboard Trap, requires that focus can leave using the keyboard alone, which for a dialog means Escape or a close button. Veya's modal popup focuses its first field, keeps Tab inside the form, closes on Escape and returns focus to the element that had it. A flyout does not take focus or trap Tab, so someone reading the page is not pulled away from it.

A close button people can find and hit

The close button needs a name a screen reader can say, not just an "×". It needs to be large enough to tap: WCAG 2.5.8, Target Size (Minimum), new in 2.2, asks for at least 24 by 24 CSS pixels, and 44 pixels is a more comfortable size for a thumb. Veya's close button is announced as "Close signup form", sits pinned to a corner of the visible screen, and is a real button, so Enter and Space work. If a design delays the close button, Escape still closes the form during the delay.

Label every field

Placeholder text is not a label: it disappears as soon as someone types, and some screen readers skip it. WCAG 3.3.2, Labels or Instructions, asks for a label or instruction wherever a form needs input. Give the email field a visible label or an accessible name, and use type="email" with autocomplete="email" so phones offer the right keyboard and autofill. Veya's email field is always type="email", autocomplete="email" and required, and multi-step questions are grouped with a fieldset and legend so each choice is read in context.

Announce errors and success

When someone submits and the form says "Check your email address" or "You're in", a screen reader user has to hear it without hunting for it. WCAG 4.1.3, Status Messages, asks that such messages be announced without moving focus. Veya's status line is a polite live region, so errors and confirmations are read aloud, and after a signup focus moves to the copy-code button or the close button, the next thing the shopper is likely to want.

Contrast that survives a photo

Body text needs a contrast ratio of at least 4.5:1 against its background, and large text 3:1 (WCAG 1.4.3). Popups break this most often with text laid over a product photo, pale placeholder text, and a light button label on a brand color. Check every state: the field, its placeholder, the error message and the button. Nothing in Veya checks contrast automatically, so ask for a revision if any text on your design falls short, and check it yourself with a contrast checker before publishing.

Respect reduced motion

Popups like to bounce, slide and spin. For people with vestibular disorders that motion can cause nausea. WCAG 2.3.3, Animation from Interactions (level AAA), asks that motion triggered by interaction can be turned off, and the operating-system setting prefers-reduced-motion is the way people ask. Under that setting, Veya skips the entrance, stops the design's animations and transitions, and keeps only what a game needs to play; a merchant can also turn motion off for everyone.

Flyouts and the focused field

WCAG 2.2 added 2.4.11, Focus Not Obscured (Minimum): when something on the page has keyboard focus, it must not be entirely hidden by content the site added. A flyout docked to the bottom of a phone screen can cover the field or link someone is tabbing to. Keep flyouts small, make them easy to close, and tab through the page with the flyout open to check nothing focused disappears behind it.

What the law expects

In the US, UsableNet counted 5,114 ADA digital accessibility lawsuits in 2025, 70% against ecommerce, and found that 36% of the top 500 ecommerce retailers had been sued at least once. In the EU, the European Accessibility Act has applied since June 28, 2025 to e-commerce services offered to consumers, with an exemption for microenterprises of fewer than 10 people and no more than €2 million in turnover. A popup is part of the store, so it is part of the obligation. Nothing here is legal advice, and Veya does not certify designs as WCAG conformant.

Test it in five minutes

Unplug the mouse and open the popup: can you reach the field, submit, read the result and close it with Tab, Enter and Escape alone, and does focus land back on the page? Turn on VoiceOver or NVDA and listen to what is announced when it opens and after you submit. Zoom the browser to 200% and check nothing is cut off. Turn on reduced motion in your system settings and reload. Then run a contrast checker over every text color in the design.

Questions

Are popups accessible?

They can be. An accessible popup is announced as a dialog, takes focus when it opens, keeps keyboard focus inside until it closes, closes with Escape and a labelled button, labels every field, announces errors and success, meets contrast minimums and respects reduced motion.

Which WCAG criteria apply to a popup?

The main ones are 2.1.2 No Keyboard Trap, 2.4.3 Focus Order, 2.4.11 Focus Not Obscured, 1.4.3 Contrast (Minimum), 2.5.8 Target Size (Minimum), 3.3.2 Labels or Instructions and 4.1.3 Status Messages, plus 2.3.3 Animation from Interactions at level AAA.

Should a popup trap keyboard focus?

A modal popup should keep Tab inside the dialog while it is open, as the W3C dialog pattern describes, but it must always offer a way out with the keyboard, usually Escape and a close button. A non-modal flyout should not trap focus.

How big should a popup close button be?

WCAG 2.2 asks for a target of at least 24 by 24 CSS pixels at level AA. On a phone, 44 pixels or more is a safer size for a thumb.

Does the European Accessibility Act apply to my store?

From June 28, 2025 it applies to e-commerce services offered to consumers in the EU, including the website and its forms. Microenterprises with fewer than 10 employees and no more than €2 million in turnover are exempt. Check with a lawyer for your situation.

How do I test a popup with a screen reader?

Open the page with VoiceOver on a Mac or iPhone, or NVDA on Windows, wait for the popup, and listen: it should announce a dialog with a name, read the field's label, announce any error after submitting, and return you to the page when closed.

Sources

Figures checked November 12, 2026.

Your next popup?
We’ll build it for you.

14-day free trial on every plan. Custom design and revisions included.