Why does my Shopify theme keep failing Theme Store review, and what are they actually looking for?
Shopify grades theme submissions against a published checklist covering performance, accessibility, keyboard and screen-reader support, and editor UX, so most rejections that feel random trace back to a gap between what you tested and what reviewers actually test.
What's going on
You submit a theme to the Shopify Theme Store, wait, and get bounced back with feedback that feels vague or inconsistent with what you tested locally, or with what got a different theme approved last year. It's especially frustrating when you ran a Lighthouse audit, it looked fine, and you still failed on performance or accessibility grounds you didn't expect.
Part of the confusion is real: review has multiple stages, and accessibility, performance, and merchant-editor UX increasingly come up as reasons for rejection or revision requests, not just broken functionality. But the bar itself isn't secret. Shopify publishes numeric thresholds and a running list of common rejection causes, and most rejections that feel unpredictable turn out to be a mismatch between how a developer tested (empty sections, automated scanners only, desktop-only) and how Shopify actually tests (populated real content, both viewports, manual keyboard and screen-reader checks).
Why it happens
Shopify has tightened Theme Store requirements over time to protect the merchant experience storewide, layering explicit performance and accessibility gates on top of the older functional and design checklist. Many developers test against a dev theme loaded with default demo content, which is lighter and cleaner than a real merchant's populated store, so a theme that scores well locally can still fail once real product images, longer titles, and full navigation are loaded in.
The other recurring cause is that automated accessibility scanners only catch a portion of what real accessibility guidelines require. They tend to miss keyboard traps, illogical focus order, and placeholder-only form labels that a manual keyboard pass or screen reader test would catch immediately, and that human reviewers do catch.
5 ways to fix it
Start with Shopify's actual Theme Store requirements page, not secondhand advice
Shopify publishes a specific, testable checklist at shopify.dev covering Theme Store requirements and common theme rejections. Don't submit based on what worked a year ago or what a blog post summarized — the bar changes, and reviewers grade against the current published list line by line. Treat it as your acceptance criteria, and re-check it right before you submit, not just when you started building.
Test performance on real, populated pages, not empty demo sections
Shopify's requirements set minimum average Lighthouse scores for performance and accessibility, measured across your product, collection, and home pages on both desktop and mobile. Reviewers test sections filled with real images and content, not blank placeholder blocks, so a theme that scores well empty can still fail once a merchant loads it with real products. Run Lighthouse yourself against a populated benchmark shop before you submit, on every template, in both viewports.
Fix the accessibility gaps that come up again and again
Beyond the raw Lighthouse score, reviewers check for labeled interactive elements, full keyboard navigation, visible focus states, and adequately sized touch targets. Recurring failure points include low color contrast, missing or placeholder-only form labels, missing image alt text, empty links or buttons, and a missing page-language attribute. Test with an actual keyboard, tabbing through every interactive element, and ideally a screen reader too — automated scanners only catch a fraction of real accessibility issues.
Write down how your theme differs before a reviewer has to ask
A meaningful share of rejections in later review stages come down to design and UX judgment, not hard technical failures: layouts that feel duplicative, an unclear editor experience, or features that don't clearly differ from existing Theme Store themes. Document what your theme's merchant-editor experience does differently and why each customization exists, and include that context in your submission notes. It speeds up the review conversation and forces you to catch UX weak points yourself first.
Build slack into your timeline for at least one revision round
Theme review happens in stages: early stages catch technical requirement failures, and deeper design and UX feedback tends to arrive later in the process. If you're aiming for a launch date, submit early in the week and build in time for a revision round — getting sent back after an in-depth later-stage review is normal, not a sign you did something unusually wrong.
Bottom line
This isn't guesswork on Shopify's side: the performance and accessibility bar is a published checklist with numeric thresholds, tested against populated pages, plus a documented list of common rejection causes. The "unpredictability" merchants and theme developers run into is usually a gap between what they tested (empty sections, automated scans only, no real keyboard pass) and what Shopify actually tests. Work through the official requirements and common-rejections pages directly, test with real content and a keyboard, and most rejections become previewable before you ever submit. This is a build-and-test problem, not something an app fixes for you, and BesPoP doesn't have a specific app for theme store submission.
Browse the rest of the problem library, run a free storefront scan to catch issues like this automatically, or email us and we'll work out a custom solution for it.