ADA Risk in Age Gates and Date of Birth Fields

Age gates look like a single date field and fail like a form, a modal, and a timer combined. Split fields, error handling, and gates that lock screen reader users out entirely.

An age gate is a compliance feature that creates its own compliance problem with some regularity. A shopper lands on a site selling alcohol, supplements, or age restricted products, meets a modal asking for a date of birth, and cannot get past it with a keyboard or a screen reader. The business added the gate to satisfy one rule and, in the implementation, broke Title III of the ADA for the same visitor.

The failure modes are consistent. Three unlabelled boxes for day, month, and year. A single field that demands one exact format and rejects every other. A modal that opens without moving focus into it, or that removes the close option for anyone who cannot use a mouse. Each is small in the code and total in its effect, because a gate that cannot be passed ends the visit.

Format is the first barrier

Date fields fail on format more than on any other point. A gate that only accepts MM/DD/YYYY, says nothing about that expectation, and answers 03/04/1990 entered the European way with a silent reset has failed 3.3.1 Error Identification and wasted the shopper's effort. State the format in text next to the field, accept common separators where you can, and if you reject an entry, say what was wrong with it.

Split fields are not automatically better. Day, month, and year boxes each need their own visible label, not one label for the group and two mysteries beside it. And auto advancing focus from box to box, which feels helpful in a demo, can disorient a screen reader user who has not finished reviewing what they typed. Predictable beats clever in a gate.

A modal you cannot leave or enter properly

Focus management decides whether the gate works at all. When the modal opens, focus should move into it, normally to its heading or first field. When it closes after a successful entry, focus should land somewhere sensible on the page behind it. A gate that leaves focus on a page the modal is covering lets a keyboard user Tab through content they cannot see.

The harder question is refusal. A shopper who enters an underage date, or who simply does not want to give a date of birth to browse, needs a clear outcome in text, not a modal that quietly reopens in a loop. If browsing without verification is permitted for part of the site, say so and provide that route as a real, labelled control.

Remember the entry, within reason

Making a returning shopper re enter a date of birth on every visit, and on every device, is not an accessibility criterion, but it multiplies the chance that any small barrier in the form becomes a recurring one. Where the applicable rules allow the site to remember a verification, doing so reduces the exposure for everyone, and it reduces it most for the users the form is hardest for.

Log gate findings with the restricted category and the jurisdiction in mind, because age verification duties differ by product and by state. The accessibility point does not change with those differences, though. Whatever the gate is legally required to collect, it has to be collectable by a disabled shopper using their own technology.

Related reading: ADA Risk in Embedded Size Charts, Fit Guides, and Care PDFs, Testing Contrast in Sale Countdown Timers and Urgency Badges, Testing Target Size: The Small Buttons That Block Mobile Checkout.

Frequently asked questions

Why is an age gate an accessibility risk?

Because it is a mandatory modal form placed in front of the whole site. If its fields are unlabelled, its errors unexplained, or its focus handling broken, a disabled shopper cannot browse at all, which makes a small form defect a total barrier.

Should date of birth use one field or three?

Either can work if it is done properly. A single field must state the expected format and explain rejections. Three fields each need their own label. What fails is an unlabelled version of either pattern.

What should happen when someone enters an underage date?

The outcome should be stated in clear text, and any permitted alternative, such as browsing unrestricted parts of the site, should be offered as a real control. Silently reopening the gate or looping the modal leaves the user with no information.

Does remembering an age verification help accessibility?

Where the rules for the product category allow it, yes. It reduces how often every shopper has to clear a difficult form, and it helps most the users for whom that form is hardest to complete.