What you get from us, every month
Some of it's for you, some for your developer, and some for the day anyone asks.
We look at your store first, then show you what we found and your price.
Our test store
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
Some controls contain other controls, which screen readers and keyboards can skip or announce wrongly.The app's vendor
Some text has too little contrast with its background to be read easily, especially by people with low vision.Ours
Some links have no text, so a screen reader cannot say where they go.Ours
Fixed this month
Product gallery reachable by keyboard
-
For you
Know where your store stands, and hear when something changes.
-
For your developer
Each problem, its fix in your code, and proof it holds.
-
For anyone who asks
A dated record, plus what your lawyer or tax preparer needs.
For you
A few minutes a month. Most of it asks nothing of you.
-
Our test store
Monthly report, September 2026
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.
Every month
The monthly report
One page on what we fixed, what's still to fix and whose move each problem is.
You: Read it.
-
Accessibility statuslast checked October 14, 2026
Where the store stands, out of 55 requirements at WCAG 2.2 level AA
What is open
What changed
October 13 Some buttons and links are too small or too close together to tap reliably. (the start of checkout)
After every check
Your status page
Where your store stands, in plain words, on a page you can open any time.
You: Nothing. Look whenever you like.
-
Alert
Sep 28, 2026, 12:55 UTC
New since the last check: 1
A new icon-only link at the foot of the home page has no name, so a screen reader announces it only as "link".
- Where
- The home page, in 6 places
- Likely cause
- The theme published that day
Read by our team, sent to you
Within 24 hours of the check that finds a problem
Alerts
A note when a theme change or an app gets in your customers' way. A person reads each alert before it reaches you.
You: Nothing to chase.
-
Even Entry Lab wants everyone to be able to use this store, including people with disabilities, and works to make it so.
The standard we use
The Web Content Accessibility Guidelines (WCAG) 2.2, at level AA.
What we are doing
- A page of every kind was last checked on 2026-10-16.
- 4 changes the checks found were read by a person before anything was said about them.
In your first month, then after each full check
Your accessibility statement
A page on your store that tells shoppers what works, what we're fixing and how to reach you.
You: Read it and tell us how shoppers can reach you. On Engage, your developer puts it on your store; on Resolve and Defend, we do once you approve it.
-
From the start, then each new one
Picture descriptions
We draft a short description of every product picture, so people using a screen reader know what each one shows.
You: Approve or change each one, and nothing goes on your store until you do. On Engage, your developer puts them on your store; on Resolve and Defend, we do.
For your developer
Enough on every problem that they won't need to ask us what we meant.
-
Phone, 375 pixels The problem
The Product heading over the cart is too pale to read
The evidence
Heading text #6d736d on #f6f3ec, 10 pixels, measures 4.38:1. WCAG 2.2 asks for at least 4.5:1 for text this size.
Problems we found
After every check, each new problem comes with a screenshot, its cause and the rule it breaks.
-
The change assets/component-cart-items.css
11 .cart-items th {
12 text-align: left;
13 padding-bottom: 1.8rem;
14 - opacity: 0.85;
15 font-weight: normal;
16 }
Make the cart table headings dark enough to read
Fixes in your own code
Each fix comes in your theme's own code, drafted by our software and checked by a person. On Shopify, it waits on an unpublished copy of your theme until you say yes. We don't add anything to your store. On Engage, your developer publishes it. On Resolve and Defend, we do.
-
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 to-do list
Every fix and how far along it is, with a spreadsheet for your developer's own tools.
-
Fix: the cart's small headings
- October 10, 11:52, A check first saw the store serving the copy
- October 10, 11:53, Same check: no longer found
- 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
Proof each fix stays fixed
Once a fix is live, the next check confirms the problem's gone, and every check after keeps looking.
-
Apps from other companies
Which app is getting in your customers' way, and how. On Engage, we write a note you send to the company that makes it. On Resolve and Defend, we take it to them and follow up.
-
Shopping with only a keyboard
On every plan, we test every page using only a keyboard, as some shoppers do. We test when you join, then every month, and again after each new theme.
-
Listening with a screen reader
Engage has no screen reader test, but Resolve tests every page with Orca and NVDA on the same schedule, and Defend adds JAWS. Resolve can add JAWS for $300 a month up to 1,000 pages, and $60 more per 1,000 after that.
-
Answers to their questions
Your developer can write to us with any question. A person replies within 1 business day, with a full answer within 3 business days on Engage, 2 on Resolve and 1 on Defend.
For anyone who asks
When someone wants to know what you've done about accessibility, this is what you hand them.
| Entry | When | What happened |
|---|---|---|
| 1765 | October 9, 05:51 | Found |
| 1799 | October 9, 13:07 | Fix written |
| 1812 | October 9, 15:24 | Fix checked by a person |
| 1879 | October 10, 11:45 | Earlier steps signed off |
| 1880 | October 10, 11:46 | Fix on an unpublished copy of the theme |
| 1913 | October 10, 11:52 | Copy seen as the live theme |
| 1917 | October 10, 11:53 | No longer found (6 findings) |
| 1924 | October 10, 11:53 | Dated by an outside service |
-
The record
Every problem, fix and check, dated by an outside service so nobody, us included, can change a date. It's yours, and we send a copy within 10 business days of asking.
-
The evidence pack
If a demand letter or a lawsuit arrives, we put the record together for your lawyer. They'll have it within 10 business days, or 5 with Defend.
-
A summary every three months
Where your store stands against each rule of the standard, including what we haven't tested yet. It comes with Resolve and Defend.
-
The accessibility report for buyers
The formal report a large customer may ask for before buying from you, often called a VPAT. Defend includes it, updated every six months. On Engage and Resolve, you can add it any time.
-
What people with disabilities found
Twice a year on Defend, people with disabilities shop your store, from a product page to checkout. You can hand over what they found, and what we did about it.
-
The file for your tax preparer
Each January, we lay out what you paid us last year and what it bought, for the disabled access credit on IRS Form 8826. It comes on every plan, and we send it straight to your tax preparer.
Your first month
We check every page once, and that's the starting point every later check is measured against. We write your accessibility statement and get your first fixes ready to publish.
Where our part ends
- We don't give legal advice. Your lawyer does, and we get them what they need from us.
- We don't decide if you qualify for the tax credit, or fill in the form. That's your tax preparer's call.
- We never write that your store meets every rule. Your statement says what works and what we're fixing.
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.