Watching Age Verification Modals for Barriers
Age gates block every shopper at the door, and their date fields and modal behaviour often block assistive technology users completely. What to watch.
An age verification modal is the first thing every visitor meets, so a barrier there is total: no browsing, no buying, no workaround. Date pickers that need a pointer, modals that trap screen readers incorrectly, and error messages shown only in colour are common findings.
Stores add age gates for legal reasons and then rarely test them, because staff pass through once and forget them. Watching them deliberately is the only way they stay usable.
Date entry is where most gates fail
A date of birth entered through three dropdowns, a calendar grid, or separate fields each behaves differently with a keyboard and screen reader. Every field needs a clear label and an example format, and the order, day month year or month day year, must be stated, not assumed.
Errors need words. A field outline turning red tells many shoppers nothing. Say what is wrong, an incomplete date, a date under the threshold, and keep the entered values so the shopper can correct one field instead of starting again.
Modal behaviour decides who gets in
The gate should hold focus inside itself until answered, be announced as a dialog, and be dismissible only by answering, where the law requires that. But its controls must all be reachable by keyboard, including any confirm and exit buttons.
Remember the returning visitor. If verification is stored, say for how long and do not re ask on every page. Repeated gates punish everyone and train shoppers to enter any date that works, which defeats the purpose.
Test the gate cold, every release
Clear cookies and test as a new visitor with keyboard only, then with a screen reader, then on a phone. Note time to complete and any step that needed a mouse to rescue it, and log those findings with the release.
Also test refusal: an under age date should produce a respectful, readable explanation and a way to leave. That page is part of your store's manners as well as its compliance.
Related reading
If this topic is useful, these earlier guides go deeper on connected questions: Watching Third Party Review Widgets on Product Pages, Watching Exit Intent and Timed Popups for Harm, and Watching Embedded Forms in Newsletter and Signup Blocks.
Frequently asked questions
Why are age gates such a high risk for accessibility?
Because they sit in front of everything. A small defect in a product page affects one product; a defect in the gate locks assistive technology users out of the entire store.
What is the most accessible way to ask for a date of birth?
Labelled text fields with the format stated and an example, accepting typing rather than forcing a calendar picker. Dropdowns can work if fully labelled, but typing with clear guidance suits most users best.
Should an age gate remember verification?
Where the law allows, yes, for a stated period. Re asking on every visit adds friction for everyone and encourages false entries, while a remembered check keeps the barrier proportionate.
What should an under age visitor see?
A clear, calm message explaining they cannot enter, written in plain text, with no way for the message to be missed by a screen reader, and a normal way to leave the site.