The monthly report
What's fixed, what's still open and whose turn each one is. One page.
- Who reads it
- You, and your developer for the to-do list
- When it comes
- Every month
- Which plans
- Every plan
Monthly report, September 2026
- Where the store stands
- 25 problems at the end of the month, 10 of them in the store's emails. 10 sit on the path to a sale: the home page, product pages, collection pages, the cart and search results.
- What is open, and whose move it is
-
What is open, and whose move it is What a visitor meets Where Whose move WCAG Some controls contain other controls, which screen readers and keyboards can skip or announce wrongly. information pages, the home page, the cart, blog pages, policy pages, product pages, search results and collection pages; from Shopify Forms The app's vendor: Shopify Forms. We document it and help you take it to them; we cannot change their code. 4.1.2 Some text has too little contrast with its background to be read easily, especially by people with low vision. the home page, product pages and collection pages Ours: a fix to write in the theme's code. 1.4.3 Some links have no text, so a screen reader cannot say where they go. the home page Ours: a fix to write in the theme's code. 2.4.4, 4.1.2 Some text has too little contrast with its background to be read easily, especially by people with low vision. pop-ups; from Shopify Forms The app's vendor: Shopify Forms. We document it and help you take it to them; we cannot change their code. 1.4.3 Some images have no text description, so people using a screen reader do not know what they show. the store's emails Ours: to trace in the email's template. 1.1.1 Some links inside text are told apart from the text only by color. the store's emails Ours: to trace in the email's template. 1.4.1 Some of the store's emails are laid out with tables that screen readers announce as data tables. the store's emails Ours: to trace in the email's template. 1.3.1 Some pages do not say what language they are in, so screen readers may read them with the wrong pronunciation. the store's emails Ours: to trace in the email's template. 3.1.1 Some text has too little contrast with its background to be read easily, especially by people with low vision. the store's emails Ours: to trace in the email's template. 1.4.3 - What changed
-
September 24
- Checks began: the live theme was "test-data" (Generated Data Theme).
- Judge.me Product Reviews was seen on the store for the first time.
- Shopify Forms was seen on the store for the first time.
- Shopify Inbox was seen on the store for the first time.
- New: Some text has too little contrast with its background to be read easily, especially by people with low vision. (the home page, product pages and collection pages; WCAG 1.4.3)
- New: Some areas that scroll cannot be reached with a keyboard in some browsers. (product pages; WCAG 2.1.1, 2.1.3)
- New: Some controls contain other controls, which screen readers and keyboards can skip or announce wrongly. (information pages, the home page, the cart, blog pages, policy pages, product pages, search results and collection pages; from Shopify Forms; WCAG 4.1.2)
- New: Some text has too little contrast with its background to be read easily, especially by people with low vision. (pop-ups; from Shopify Forms; WCAG 1.4.3)
And 18 more changes on 3 more days, up to September 28: problems found or gone, apps seen, fixes written.
- Fixed this month
- Product gallery reachable by keyboard
For your developer: the queue
- Fix
- Product gallery reachable by keyboard
- File
snippets/product-media-gallery.liquid- State
- Verified: live, and the checks no longer find the problem
- Dates
- Written September 27, staged September 27, seen live September 28, verified September 28
The same list comes as a spreadsheet, for your developer's own tools.
The change log
- September 27, 17:27 UTC, A fix was written: Product gallery reachable by keyboard.
- September 27, 17:27 UTC, The fix "Product gallery reachable by keyboard" was staged on an unpublished copy of the theme.
- September 28, 12:20 UTC, Theme published: "Even Entry fix TVEBGH: Product gallery reachable b" (Generated Data Theme)
- September 28, 12:20 UTC, The copy with the fix "Product gallery reachable by keyboard" was seen live on the store.
- September 28, 12:55 UTC, The checks no longer find what the fix "Product gallery reachable by keyboard" was written for.
And 32 more rows from September 24 to September 28: each problem found or gone, and each app seen.
This is our test store's report for September 2026, made by our software the same way yours is. It shows an older theme full of made-up test data. That month's one fix went live on the product gallery.
Your month, and who does what next
Read it in a few minutes. No scores, just what's true this month.
- Where the store stands
-
How many problems are open at the month's end, and how many sit on the way to a sale, from homepage to checkout.
- What is open, and whose move it is
-
Each problem in a sentence, where it is, and whether it's our move, your developer's or an app maker's.
- What changed
-
Day by day: new problems, confirmed fixes, anything that came back, and any theme change or new app we saw.
- Fixed this month
-
Every fix that's live and checked.
- The queue
-
Your developer's to-do list: each fix, the file it changes and how far along it is.
It also comes as a spreadsheet inside the report, for your developer's own tools.
- The change log
-
Every change on your store that month, dated, with what changed just before each new problem appeared.
Why you can trust what it says
Every line comes from your record of problems, fixes and checks, each one dated.
-
Built from your record
We draw each report straight from your record. Nobody retypes it, so nothing gets lost on the way.
How you can check it
Pick any change it lists, and you'll find it in your record with its date.
-
Kept exactly as sent
Once we send it, it never changes.
How you can check it
Ask us to compare any copy you're sent with the one in your record.
-
Each problem names its rule
We put each problem in plain words that match what its rule says.
How you can check it
Look beside each problem and you'll see its rule named, so you can read it yourself.
-
Read by a person first
A person reads every report before it reaches you, and signs off any step our software took.
How you can check it
Your record shows who signed off each step.
For your developer: Each report carries your record's latest fingerprint. The report's own fingerprint sits in your record, dated by an outside service, so a changed copy wouldn't match.
Where it fits
It's your month, put together to read in a few minutes.
- We check your store , This comes from here
- We start near checkout , This comes from here
- We check every fix , This comes from here
- We confirm it works , This comes from here
- You keep the record , This comes from here
By plan
On Engage, your developer publishes the fixes on its to-do list. On Resolve and Defend, we do. Otherwise, the report's the same on every plan.
See it on your own store
On the call, we show you the problems we found on your store, with pictures. You hear your price before you sign anything. No surprises.