It is launch day. The theme is picked, the apps are installed, and the countdown banner is already live on the homepage. Everyone on the team has an assigned job: confirm the payment gateway, check the shipping rates, proof the copy one more time. Nobody has "accessibility" on their list, because nobody ever assigned it to anyone.
That is not a moral failing. It is a checklist failure. Accessibility gets skipped on launch day for the same reason typos slip into a press release: it is not anyone's explicit job, so everyone quietly assumes someone else already checked it. The fix is not a heroic last-minute audit the night before. It is a short, specific gate that sits between "ready to launch" and "actually live," the same way a deploy gets gated on passing tests before it ships.
The Stat: Roughly 1 in 4 US adults, 28.7%, report living with a disability. (Source: CDC)
Why This Belongs at the Gate, Not the Backlog
Most stores treat accessibility as a "someday" ticket. It sits in the backlog behind the next theme redesign, waiting for a customer complaint or a support ticket to bump its priority. The problem with that approach is timing. A store's first impression is permanent for a portion of the people who land on it that day, and you do not get to quietly go back and fix launch day after the fact for the customer who already left.
A gate works differently than a backlog item. It is a short, non-negotiable list that has to be checked before the "publish" button gets pressed, not sometime after. It does not require a full audit or a specialist on staff. It requires someone on the team owning six specific checks and refusing to ship until they pass, the same way you would not ship a store with a broken payment gateway just because the launch date arrived.
The Six-Point Pre-Launch Gate
Here is the actual list, in the order it is fastest to check.
1. Theme contrast checked against your real colors, not the theme demo
Shopify theme marketplaces show demo content with safe, high-contrast defaults. The moment a merchant swaps in brand colors, a custom hero image, or a sale banner, that contrast can collapse. Text over a busy product photo, a light gray "Add to Cart" button, or a pastel sale badge are the usual culprits.
The rule of thumb from WCAG is a contrast ratio of at least 4.5:1 for normal body text and 3:1 for large text and interactive UI components like buttons and form borders. Do not eyeball this. Pull the actual hex values from your theme editor and run them through the WebAIM contrast checker before launch, including any text sitting on top of images.
2. Product image alt text that describes the product, not the file name
Alt text is the only way a screen reader user knows what a product photo actually shows. "IMG_4021.jpg" or a repeat of the product title tells them nothing they do not already have. Good alt text names the color, pattern, material, or distinguishing detail that is visible in that specific photo, especially for a product with multiple images showing different angles or use cases.
The W3C's guidance on non-text content is the right reference here: alt text should serve the same purpose the image serves for a sighted shopper. If a product photo is purely decorative, like a background texture, it should be marked so screen readers skip it rather than reading a meaningless description aloud.
3. Cart and checkout tested with a keyboard alone, no mouse
Unplug the mouse, or just do not touch it, and try to add a product to the cart, change the quantity, apply a discount code, and reach the final payment step using only Tab, Shift+Tab, and Enter. This single test surfaces more launch-blocking issues than almost anything else on this list.
Watch for two failures specifically: a visible focus indicator disappearing at any point in the flow, and a keyboard trap, where Tab gets stuck inside a cart drawer or upsell popup and can never reach the checkout button. Both are common in themes and apps that were only ever tested with a mouse.
4. Every form field has a real, programmatically linked label
Placeholder text that disappears the moment someone starts typing is not a label. Neither is a label that merely sits visually near a field but is not connected to it in the underlying markup. Account creation, newsletter signup, and discount code fields are the ones merchants add last and check least, and they are exactly where an unlabeled input tends to slip through.
Confirm every input on the storefront, not just checkout, has a label a screen reader will actually announce when the field receives focus.
5. App-added widgets audited after they are installed, not assumed compliant
A theme can pass every check above and still fail at launch because of what gets bolted on afterward. Review widgets, upsell popups, countdown timers, live chat bubbles: these are typically added in the final days before launch, after the "accessibility pass" already happened on the bare theme.
Each one deserves its own quick check. Can the popup be closed with a keyboard? Does the countdown timer's badge meet the same contrast standard as the rest of the page? Does the chat widget have a labeled, focusable button rather than an icon with no accessible name? Treat every app you install in launch week as untested until you have actually tested it.
6. The full page checked at 200% zoom
Some shoppers do not use assistive technology at all. They zoom their browser to 200% because that is how they read comfortably. WCAG's reflow requirement expects a page to remain usable at that zoom level: no horizontal scrolling to read a sentence, no navigation menu that overlaps the page content, and no sticky header that eats half the visible screen.
Shopify themes with mega-menus and sticky headers are especially prone to breaking here, since those elements are usually designed and tested at 100% zoom and never revisited afterward.
How We Actually Run This Gate
When our team runs this check for a client ahead of a launch, we do it in the order above, on the actual production theme with real content in it, not a staging demo. We do not run a full audit at this stage. We are looking specifically for the handful of issues that would block a customer from completing a purchase or understanding a product on day one, because those are the ones that cannot wait for a post-launch fix cycle.
If you would rather have someone run this gate for you before your countdown clock hits zero, that is exactly what our Shopify accessibility service is built to do as a focused, pre-launch check rather than a lengthy audit.
What This Gate Won't Catch, and Where to Look Next
This list is deliberately narrow. It is meant to catch the issues that would embarrass or block a customer on launch day, not to replace a full accessibility review. If you want to see how popular Shopify themes hold up even after a check like this one, 7 Shopify Themes That Fail WCAG Out of the Box walks through exactly where common themes still fall short.
And if you want a sense of what a deeper, ongoing review actually surfaces once a store is live and taking real orders, I Rebuilt a Shopify Store's Checkout With a Screen Reader On is a first-person account of running a full checkout flow with a screen reader, warts and all.
Before You Hit Publish
Print this list, assign each of the six items to a specific person on your launch team, and do not publish until all six are checked, not assumed. It takes less time than proofing the copy one more time, and it is the difference between a launch day that works for every visitor and one that quietly does not.
If you want a second set of eyes on your store before the countdown ends, email experts@wcag.world and a real person on our team will walk through this gate with you, or visit our Shopify accessibility solutions page to see how we run it.