Your accessibility statement
A page for your shoppers: where your store stands, and how to reach you.
- Who reads it
- Your shoppers, after you've read it and told us how they can reach you
- When it comes
- In your first month, then after each full check
- Which plans
- Every plan
Accessibility statement, Our store, as of October 16, 2026
Accessibility statement for our store
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.
Where the store stands
The store does not yet meet every part of WCAG 2.2 at level AA. These are the limitations we know of:
- Some controls contain other controls, which screen readers and keyboards can skip or announce wrongly. (product pages, collection pages, information pages, policy pages, search results, the cart, blog pages, blog articles, the home page and the page shown for an address that does not exist; from the Shopify Forms app)
- Some buttons and links are too small or too close together to tap reliably. (product pages, collection pages, information pages, policy pages, the home page, the cart, search results, blog articles, the page shown for an address that does not exist and blog pages; from the Chatty AI Chatbot & Live Chat app)
- Some text has too little contrast with its background to be read easily, especially by people with low vision. (pop-ups, product pages and collection pages; some from the Shopify Forms and Judge.me Product Reviews apps)
- Some product images have no text description, so people using a screen reader do not know what they show. (product listings)
- Some form fields have no label, so people using a screen reader do not know what to enter. (product pages)
What we are doing
- The store's purchase path was last checked on 2026-10-16.
- 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.
- 1 fix written in the store's own theme code is live on the store, and the checks no longer find the problem it was written for.
How the store was checked
Automated checks on 51 pages, each rendered in full at a desktop width, a phone width and 320 pixels wide. Last checked 2026-10-16. Of the 55 requirements at level AA, 11 pass the automated checks and wait for a test a person signs off, and 32 have not been tested yet.
Feedback
If something on this store is hard to use, please tell us [TO CONFIRM: the store's contact for accessibility feedback]. Tell us the page and what got in the way.
Laws and policies
[FOR THE OWNER: the laws and policies that apply to the store, as your counsel advises, or remove this section.]
Prepared 2026-10-16.
Our software drafted this from our test store's record of October 16, 2026, before a person read it or filled its gaps. It has never been published. "Even Entry Lab" is the name our store is set up under.
What your shoppers will read
What doesn't work yet, what you're doing about it, and who to tell.
- Your commitment
-
You want everyone to be able to shop with you, and you're working on it.
- The standard we use
-
The standard we check your store against: the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA.
- Where the store stands
-
What doesn't work yet, in plain words, and where.
Your emails aren't part of this page, and you'll find their problems on your status page.
- What we are doing
-
When your store was last checked, and the fixes that are live and confirmed.
A fix counts only once it's live and our checks no longer find its problem.
- How the store was checked
-
What we checked, how, at which screen widths and when.
- Feedback
-
Who shoppers tell when something gets in their way.
That's the contact you give us. Until you do, the draft leaves a gap for it.
- Laws and policies
-
Left for you and your lawyer to fill in, or take out.
The draft never says which laws apply to your store.
It never says too much
Every line in it traces back to your record.
-
Only what the record shows
It lists what doesn't work yet, and we built it so it can't claim your store meets the standard.
How you can check it
Read the sample through: you'll find open problems named, and nowhere does it say you meet the standard.
-
The same as your status page
We draw it from the same record as your status page.
How you can check it
Put them side by side, and you'll see the same problems and the same dates.
-
Dated by a full check
We date it only from a check that ran all the way through.
How you can check it
Look at its date: it's the last check that ran all the way through.
-
The legal part is yours
Your contact and the legal section are yours to fill in.
How you can check it
Look for the gaps in brackets in the sample.
For your developer or lawyer: The parts follow W3C's guidance on accessibility statements. Each statement we send is kept in your record with its fingerprint, dated by an outside service.
Where it fits
This is the page your shoppers see, and each full check brings it up to date.
- We check your store
- We start near checkout
- We check every fix
- We confirm it works
- You keep the record , This comes from here
By plan
On Engage, your developer puts it on your store from what we send, each time we update it. On Resolve and Defend, we put it on your store once you approve it.
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.