Why does accessibility need watching instead of a one-time fix?

A Shopify store changes constantly: theme updates, app installs, new content, seasonal templates. Each change can reopen closed issues. A one-time fix degrades within weeks, silently. Watching keeps the store conformant and, just as important, keeps proving it, which is what matters when a demand letter arrives.

What WCAG version does AccessWatchHQ test against?

WCAG 2.2 Level AA, the standard courts and the DOJ reference for web accessibility. Scans cover the criteria that automated tooling can reliably evaluate, and flag the ones that need human judgment, like whether link text is meaningful, for a documented manual review pass with a named reviewer.

Can I share the score trend with my board or insurer?

Yes, that is what it is for. The monthly report is formatted as a standalone document: methodology, scan dates, score trends, and a dated fix log. Brands use it in board risk updates, cyber and EPLI insurance renewals, and acquisition diligence, where an accessibility lawsuit history is a standard question.

What happens when the score drops?

You get an alert naming the template, the failing criterion, and the change window. Because the watch stores history, you can see exactly which week introduced the problem and which fix closed it. The drop and the recovery both land in the monthly report, showing an active program rather than a lapse.

Does AccessWatchHQ fix the issues for me?

No, and that is deliberate. Your developer or agency fixes issues using the per-issue guidance: criterion, component, theme file, and concrete step. A monitor that also sells fixes grades its own homework. AccessWatchHQ verifies every fix by rescan and stamps it with a date instead of selling hours.

How much does AccessWatchHQ cost?

Every engagement starts with a free accessibility audit, so your starting score and issue list are on the table before anything else. Ongoing monitoring is quoted per storefront after the audit, based on how many stores you run and how often you want them scanned. No long-term contract.

Watching Age Verification Prompts for Barriers That Lock People Out

October 29, 2026

Age gates fail hard: modal date pickers nobody can type into, ID upload steps with no instructions, and sessions that reset before a screen reader user finishes. Here is what to watch.

Most prompts ask and move on. An age verification prompt decides. Get it wrong and the shopper is not slowed down, they are out, often with no explanation and no second route. That makes its accessibility failures different in kind from a badly labelled button elsewhere on the site.

Watch these prompts the way you would watch checkout, because for regulated products they are part of checkout. A spinning date wheel that only works by touch, a document upload with no stated file types, a verification vendor iframe with no title: each one ends the purchase for someone, quietly, with no error in your analytics except a lost session.

Let people type the date

Date of birth entry is where age gates fail first. A three wheel picker is slow for everyone and unusable for many switch and voice control users. Offer three plain text fields, or one field with the format stated in words, and accept what people actually type. Validate gently and say what is wrong in text.

Do not clear the fields after an error. A shopper who mistyped the year should not have to re enter the month and day as well, and on a timed session that punishment is worse. Which brings up the timer: if the vendor session expires in a few minutes, warn before it does and let the shopper extend it.

Explain the ID step before starting it

Document checks ask for a lot: a photo of identification, sometimes a selfie, on a phone camera, in good light. State all of that before the shopper starts, list accepted documents, and say what happens to the images. People using magnification or a screen reader need to plan the step, find the document, and often find help.

Give the failure a route too. A rejected photo with only the words verification failed leaves the shopper guessing whether it was glare, cropping, or the document type. Name the likely cause the vendor returns, offer a retake, and offer a human review path for people who cannot complete the camera step.

Log the drop off by step

You cannot watch what you do not count. Track starts, completions, and abandonment at each stage: date entry, document upload, result. A spike at the upload stage after a vendor update is a regression signal, and it is the evidence that gets a vendor to look.

Pair the counts with a manual pass using a keyboard and a screen reader each time the vendor changes the flow. Vendor release notes rarely mention accessibility, so your own dated check is the only record that the change broke something.

Frequently asked questions

What is the most accessible way to collect date of birth?

Plain text fields with the format stated in words, generous validation, and no clearing of correct entries after an error. Avoid wheel pickers as the only option, and always allow typing as an alternative to any picker.

Does an age gate need a non camera alternative?

In practice yes for many shoppers. Some people cannot align a document in a frame or take a usable selfie. A manual review route, even a slower one, prevents a total lockout and is the option practitioners look for.

How should a timed verification session behave?

Warn the shopper before time runs out and provide a way to extend it. Sudden expiry that deletes entered information is a barrier, particularly for people using assistive technology who need more time per step.

Who is responsible when a verification vendor's flow is inaccessible?

The store that requires the check. Choose vendors on their conformance evidence, test the embedded flow yourself, and keep a fallback route for shoppers the automated flow cannot serve.