Checks that fixes work
Each fix, seen working on your live store, and watched after.
- Who reads it
- You, and your developer
- When it comes
- After every check
- Which plans
- Every plan
Our walk to checkout, at the cart, Our store, as of October 16, 2026
Fix: the cart's small headings
F-1 The Product heading over the cart is too pale to read
- October 9, 04:37, Daily check: found on the cart page and in the cart drawer Entry 1765
- October 9, 13:07, Fix written Entry 1799
- October 10, 01:07, Daily check: still found, before the fix was live
- October 10, 11:46, Fix on an unpublished copy of the theme Entry 1880
- October 10, 11:52, A check first saw the store serving the copy Entry 1913
- October 10, 11:53, Same check: no longer found Entry 1917
- October 11, 08:18, Daily check: not found on the cart page or in the drawer
- October 12, 04:33, Daily check: not found on the cart page or in the drawer
- October 12, 11:06, Live theme read: it carries the change Entry 2273
- October 13, 00:50, Daily check: not found on the cart page or in the drawer
- October 13, 21:07, Daily check: not found on the cart page or in the drawer
- October 14, 17:24, Daily check: not found on the cart page or in the drawer
- October 15, 13:42, Daily check stopped after the cart, before its end: not found
- October 16, 09:58, Daily check: not found on the cart page or in the drawer
Status Confirmed on October 10, 2026
From October 9 to 16, 2026, here's every daily check on our test store that reached the cart. Each one went from the homepage toward checkout, as a shopper would. The fix's own steps, from written to live, sit between them.
Whether the fix held, check by check
It follows one fix from the day it went live to today.
- The fix
-
The fix, and the problem it was written for.
- Seen live
-
The moment the fix first showed up on your live store, however it got there.
- The check that confirmed it
-
The first check after it went live that no longer found the problem.
It looked at the same pages, at the same widths.
- Every check since
-
Each later check that reached the pages where the problem was.
A check that doesn't reach those pages says nothing about the fix either way.
- Its status
-
Confirmed, or back again if the problem returns.
A fix only counts once we've seen it work
We count what the checks saw, and nothing else.
-
Only a check closes it
A problem closes when a check stops finding it, not when someone marks it fixed.
How you can check it
Look at the entry in your record that closes it: it says which checks closed it.
-
Live means seen live
A fix counts as live from the moment we saw your store carry it, not when someone said it was published.
How you can check it
Look at the "Seen live" time: it names the check that saw it first, or the time we looked at your theme's code.
-
Another fix counts too
If your developer fixes the problem another way, it still closes, just not as our fix.
How you can check it
Your record shows when the fix went live, and when the problem stopped turning up.
-
Back again, with its history
If the problem returns, it comes back with its history, and you hear from us, after a person has read it.
How you can check it
You'll see it reopened in your record.
For your developer: The checks are a set of automated accessibility checks, plus our own, run on every page loaded in full at three widths. In the sample, times are in UTC.
Where it fits
It's the last step of each fix: the one that closes the problem, and keeps an eye on it after.
- We check your store
- We start near checkout
- We check every fix
- We confirm it works , This comes from here
- You keep the record
By plan
It's the same on every plan, whoever publishes the fix.
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.