Fixes
Each fix already written in your store's own code, waiting for your yes.
- Who reads it
- Your developer
- When it comes
- As each fix is written
- Which plans
- Every plan
Fix: Make the cart table headings dark enough to read, Our store. Written on October 9, 2026
What it's for
F-1 The Product heading over the cart is too pale to read, and 5 more findings with the same cause 1.4.3 Contrast (Minimum)
assets/component-cart-items.css.cart-items th { text-align: left; padding-bottom: 1.8rem; Taken out: opacity: 0.85; font-weight: normal; }The note
The small headings over the cart (Product, Quantity, Total), on the cart page and in the cart drawer, measured 4.38:1 on the cream background, under the 4.5:1 that WCAG 1.4.3 needs for small text. …
- Written, By our software, October 9, 13:07 UTC
- Confirmed by a person, October 9, 15:24 UTC
- Where it waits, It waited on Even Entry fix NAGABA: Make the cart table, an unpublished copy of the theme, from October 10, 11:46 UTC.
- Where it stands, We published that copy on our own store. It was first seen live on October 10, 11:52 UTC. The problem was no longer found on October 10, 11:53 UTC.
- Live theme read: the change is in it, October 12, 11:06 UTC
Our test store's fix for its pale cart headings: one line taken out of a file the cart page and the cart drawer both use. It covers six problems with one cause. We've trimmed the note to fit here.
Your fix, written and ready to read
Written for your developer, in the order they'll read it.
- What it's for
-
The problem it fixes, or several, when they share a cause.
- The note
-
What changed and why, in plain words.
- The change
-
Every line it adds to or takes out of your theme's files, in the format developers already use for changes.
We don't touch the file that holds the choices you've made in your theme.
- Where it waits
-
An unpublished copy of your live theme, with a link to preview it.
WooCommerce or Webflow: a private copy for testing; BigCommerce: uploaded, and not applied until you approve it; your own code: as agreed.
- Where it stands
-
Written, then on the copy and checked there, then live, then confirmed.
It reaches your developer once our checks no longer find the problem on the copy.
Why nothing changes until you say yes
No widget, no script, nothing added. Just your theme's own code.
-
Every line in view
Nothing in a fix is hidden from your developer.
How you can check it
Your developer can read every line of it, file by file.
-
A copy first, always
We never put a fix straight onto your store: it waits on an unpublished copy until you say yes.
How you can check it
Open the preview link and you'll see the fix on the copy before anything goes live.
-
Before and after, kept
We keep your theme's files from before and after each fix, so the change can be shown years later.
How you can check it
Ask for the before and after of any fix, and you'll see both versions of each file.
-
Reviewed before the copy
A person checks every fix first, before it goes on the copy.
How you can check it
You'll see who wrote each fix, and who reviewed it, in your record.
For your developer: Each fix goes on an unpublished duplicate of your live Shopify theme. You create the password we use, and it works only on your themes. We keep the files from before and after, each named by its fingerprint.
Where it fits
It sits between a problem found and a problem gone, waiting only on your yes.
- We check your store
- We start near checkout
- We check every fix , This comes from here
- We confirm it works
- You keep the record
By plan
On Engage, your developer puts each fix live once you say yes, by publishing its copy or copying the change in. If your theme has changed since the fix was written, we tell you, and your developer copies the change in by hand. On Resolve and Defend, we publish it once you say yes.
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.