Launching Your Shopify Store Accessible from Day One: Pre-Launch Checklist

Accessibility is dramatically cheaper to build in at launch than to retrofit after a demand letter arrives. The pre-launch window is the single highest-leverage opportunity to ship a Shopify store with WCAG 2.2 Level AA conformance baked in. This checklist gives the pre-launch sequence: theme selection criteria, brand-color contrast lock-in, content QA discipline, app vetting, the gating accessibility audit, and the launch-day documentation. Run it before launch and your store ships in the active-remediation tier rather than the demand-letter-target tier.

Why Does Launching Accessible Matter More Than Retrofitting?

Three reasons. The lawsuit clock starts at launch. Your store does not need traffic, brand recognition, or revenue to be named in a demand letter — it needs an indexable URL and a scanner-detectable WCAG violation. Plaintiff firms run automated scanners against URL lists; new stores appear in the lists within weeks of launch. According to Seyfarth Shaw's ADA Title III tracking, 67% of 2024 cases targeted businesses with under $25 million in annual revenue. New stores are not flying under the radar.

Theme and brand-color decisions are nearly irreversible. Theme selection, brand-color contrast, and customization patterns set the floor on every subsequent accessibility decision. Retrofitting after launch is engineering-expensive; getting it right at launch is nearly free. Content discipline scales with content velocity. Editorial habits set in pre-launch (alt text on every image, proper heading hierarchy, accessible link copy) become defaults for the next thousand pieces of content. Setting them poorly creates compounding debt.

For broader new-store context, see our new Shopify store ADA compliance day-one plan.

Step 1: Theme Selection — Five Evaluation Criteria

Your theme determines roughly 16-22% of your WCAG coverage out of the box, plus the difficulty of the remaining 78-84%. Five criteria for evaluation. Semantic HTML by default. Theme uses `<button>` not `<div onclick>`, `<nav>` for navigation, `<main>` for primary content, `<footer>` for footer. Run axe DevTools on the theme demo store; structural violations indicate semantic-markup weakness. Proper heading hierarchy. One `<h1>` per page; `<h2>` through `<h6>` in nested order with no skips. Verify on the theme's homepage, product page, and collection page demos.

Native form elements. Theme uses `<input>`, `<select>`, `<textarea>` rather than custom JavaScript-rendered alternatives. Native elements ship with keyboard support, screen reader compatibility, and ARIA defaults; custom alternatives require explicit accessibility engineering. Meaningful default focus styles. Theme ships with visible focus indicators rather than `outline: 0` everywhere. Test by tabbing through the theme demo. Published accessibility documentation. Theme vendor publishes a VPAT, accessibility statement, or substantive accessibility documentation. Verbal claims of accessibility without documentation are a red flag.

In our 2026 review across Shopify themes, Dawn (Shopify's reference theme) scores highest on these five criteria; Sense and Refresh follow closely. Many premium themes prioritize visual customization over semantic markup and score lower. For broader theme context, see our Shopify Dawn theme accessibility and Shopify accessibility playbook: themes, apps, checkout.

Step 2: Brand-Color Contrast Lock-In

The brand-color decision is the most commonly regretted post-launch accessibility decision. Choose accent colors that meet WCAG 1.4.3 contrast ratios (4.5:1 against background for body text, 3:1 for large text and UI components) before locking in the brand. Tools: WebAIM Contrast Checker (legacy WCAG 2.x formula), APCA Contrast Calculator (forward-compatible with WCAG 3.0).

If the brand-approved accent fails contrast on white background, generate a darker variant for body and CTA contexts. Document in the design system: marketing-approved color for hero imagery and brand surfaces, compliance variant for body and CTA text, light variant for dark-background contexts. Brand teams resist this initially; in practice the variants are visually nearly indistinguishable at body sizes. See our WCAG contrast minimum guide.

Step 3: Content QA Discipline

Pre-launch content sets the editorial pattern for everything that follows. Three disciplines to lock in.

Alt text on every image. Product images, hero banners, lifestyle shots, content images, blog post images. Each gets meaningful alt text describing function or content. "Image" or empty alt is not acceptable; product title alone is rarely sufficient. Pattern that scales: describe what the image shows in addition to product context. For decorative images, set `alt=""`. For text-as-images, replace with real HTML text. WCAG 1.1.1 enforcement is highly automated by plaintiffs' scanners; alt text is the single most-cited violation in demand letters. See our how to add alt text to Shopify products in bulk.

Heading hierarchy on every page. One `<h1>` per page (product title on product pages, collection name on collections, article title on blog posts). `<h2>` for major sections, `<h3>` for subsections, no skips. Avoid using heading tags for visual styling; use CSS classes instead. WCAG 1.3.1 evaluates heading structure.

Link copy discipline. Every link describes where it goes ("Learn more about shipping" not "Click here"). WCAG 2.4.4 Link Purpose evaluates this. Marketing copy review at pre-launch catches the patterns.

Step 4: App Vetting Before Install

Every app installed pre-launch should be audited. Run axe DevTools on the app's demo store. Request VPAT or accessibility conformance documentation from the vendor. Test keyboard navigation in the demo. Categories that consistently break accessibility: pop-up and email-capture apps, review apps, search/autocomplete widgets, live chat, and accessibility overlay widgets (which paradoxically often introduce new issues).

Apps that fail pre-install vetting will likely fail post-install audit. Better to skip the app or find a vetted alternative than retrofit accessibility on an installed app. See our third-party Shopify apps and accessibility risks. For evaluating accessibility-app vendors specifically, see our Shopify accessibility apps comparison.

Step 5: Pre-Launch Audit Gate

A gating accessibility audit before launch. Run axe DevTools, WAVE, and Lighthouse Accessibility across the customer journey: homepage, top product, collection, cart, checkout, account creation, customer service contact, accessibility statement page. Plus a manual screen reader pass (NVDA on Windows, VoiceOver on macOS) on the homepage and product page.

Critical-severity findings block launch. Major-severity findings should be fixed before launch where feasible; documented in the accessibility statement otherwise. Moderate and minor findings ship to post-launch backlog. The gate prevents shipping a store with known critical accessibility barriers — which is the pattern that produces demand letters. For the audit deliverable structure, see our accessibility audit report guide (when published).

Step 6: Launch-Day Documentation

Three artifacts publish on launch day. Accessibility statement at /pages/accessibility-statement: WCAG version (2.2) and conformance level (AA), known limitations, contact channel for accessibility issues, date of last review, applicable laws (ADA, EAA where relevant). See our Shopify accessibility statement template generator.

Customer-feedback channel. Email or contact form for accessibility issues, monitored by customer service. Response timelines: acknowledge within 14 days, substantive response within 30 (typical EAA member-state expectation). Continuous monitoring activation. Daily automated scans plus monthly expert manual audits with date-stamped compliance reports for legal counsel. The monitoring catches regressions from post-launch content and app additions before plaintiff scanners do.

In our experience working with 100+ brands, stores launching with this pre-launch checklist plus continuous monitoring report substantially lower demand-letter incidence than stores launching without. TestParty's standard service includes the launch-day infrastructure as part of source-code remediation scope. TestParty was named to the Forbes Accessibility 100 in 2025, with compliance scope spanning ADA, WCAG 2.2, EAA, CIPA, and GDPR.

Frequently Asked Questions

How long does the pre-launch checklist take? For a typical new Shopify store, 7-14 days of focused work plus the audit gate. Theme selection and brand-color lock-in: 2-3 days. Content QA discipline setup: 2-3 days (the discipline scales with content volume after launch). App vetting: 1-2 days. Audit gate: 2-3 days. Documentation: 1 day.

What if I'm already past the launch deadline? Run the same checklist post-launch, in priority order. Theme selection is now sunk cost; verify it's adequate or plan re-theme. Brand colors are sunk cost; deploy compliance variants. Content QA discipline applies going forward. App vetting applies to next install. Audit gate becomes an ongoing monthly process. Most stores can reach pre-launch-equivalent posture within 30-60 days post-launch.

Should I delay launch if the audit gate fails? Critical-severity findings: yes, fix before launch. Major-severity findings: case-by-case (fix if engineering capacity allows; document in statement otherwise). Moderate and minor findings: ship to post-launch backlog with documented remediation timeline. The judgment is risk-tolerance versus launch timing.

What's the budget for pre-launch accessibility work? For DIY stores: $0-$500 (free tools plus founder time). For agency-engaged stores: $3,000-$10,000 for the pre-launch audit and basic remediation. For platform-engaged stores: $600-$1,200/month starting at pre-launch (TestParty's standard tier). The lower-cost paths trade founder time for vendor cost.

Is an accessibility statement legally required at launch? EAA explicitly requires it for EU-customer-serving stores. ADA does not statutorily require but courts and plaintiff counsel increasingly cite the statement in mootness analysis. Best practice: publish at launch regardless of jurisdiction. Template available via W3C accessibility statement generator or our Shopify accessibility statement template.

What about Shopify Plus enterprise stores launching new brands? Same checklist with Plus-specific additions: Checkout Extensibility customization review, B2B catalog accessibility (if applicable), Markets multi-country compliance documentation, contractual SLA accessibility clauses. Plus-tier launch typically extends the checklist timeline to 14-21 days. See our Shopify Plus accessibility enterprise compliance.

Are accessibility overlay widgets a launch shortcut? In our assessment, no. The FTC fined accessiBe specifically $1 million in April 2025 for related marketing claims about overlay capabilities. Overlay-launched stores typically face the same demand-letter exposure as non-remediated stores per Court Listener public records. The pre-launch checklist plus source-code remediation produces the defensible posture that overlay shortcuts don't.

Can I use a paid accessibility platform to handle the pre-launch work? Yes. TestParty's standard service includes pre-launch audit and remediation alongside ongoing monitoring. The pattern: 7-14 day source-code remediation across theme, content, and apps, accessibility statement publication, monitoring infrastructure activation, all timed to launch day. For broader platform context, see our accessibility audit cost framing.

This article was produced using TestParty's cyborg approach — AI-assisted research and drafting, validated and refined by our accessibility team. The analysis above represents TestParty's editorial opinions based on publicly available data. As a competitor in the accessibility market, we have a point of view — but we've cited our sources so you can verify every claim independently.