Accessibility statement

This website is partially conformant with WCAG 2.2 level AA.

"Partially conformant" means some parts of the site do not fully conform to the standard. The known exceptions are listed below, each with the date we expect to fix it.

Prepared on 7 October 2026. Last reviewed 7 October 2026. Next review due 7 April 2027.

This statement applies to the following pages, which anyone can reach without an account:

• / — The J'Toye home page
• /shop — The list of vendors
• /shop/[slug] — An individual vendor's shop page
• /shop/[slug] — The dish detail panel that opens on a vendor's shop page
• /shop/[slug]/cart — Your basket at a vendor
• /shop/[slug]/checkout — Checkout
• /shop/[slug]/orders/[orderNumber] — The order confirmation shown on an order's page straight after you place it, when you pay on collection or delivery
• /shop/[slug]/orders/[orderNumber] — The page for one order, where you follow its progress
• /track — Order tracking by order number and email address
• /shop/signin — Customer sign-in
• /auth/signin — Vendor sign-in
• /legal — Legal and company information
• /legal/accessibility — This statement

What is not covered

• The vendor dashboard, and everything behind a vendor sign-in. The dashboard is the tool vendors use to run their shop. It has not been comprehensively assessed against WCAG 2.2 level AA, so no conformance claim is made about it — but it is no longer unmonitored: key dashboard pages are scanned automatically with axe on every pull request (a blocking check), and every dashboard route is scanned nightly in a report-only pass that surfaces new problems without gating a release. It is named here rather than left unmentioned, because a scope that quietly stops at the sign-in page reads as a claim about everything.

These are the accessibility problems we know about. Each one says what you would experience, why it is still outstanding, and the date by which we expect it to be addressed. Some sit inside pages this statement does cover but are built by another company, so they are listed here rather than left to look like part of our own claim.

• The vendor dashboard has not been comprehensively assessed

  Not covered by this statement

  Everything behind a vendor sign-in — the dashboard, the kitchen display and the vendor settings pages — is now scanned automatically for accessibility problems: an axe scan of key dashboard pages runs on every pull request and blocks it on a violation, and every dashboard route is scanned again nightly in a report-only pass. That is real, ongoing coverage, but it is not the same as a person comprehensively testing the standard against every page, so we do not yet make a conformance claim about it.

  This round of work deliberately covered the pages a member of the public can reach without an account, because that is where an inaccessible page stops somebody buying food. Automated dashboard scanning closes part of that gap; a full assessment is next, not forgotten.

  Affects: /dashboard

  We expect to address this by 16 February 2027.

• Creating an account happens on our identity provider's site

  Provided by someone else

  Choosing "Create an account" from the customer sign-in page sends you to our identity provider, which is a different website on a different address. The pages you see there are built and controlled by that provider, not by us, so we cannot fix their markup and do not claim conformance for them.

  Sign-in and registration are handled by a dedicated identity system so that we never handle your password. The trade-off is that those particular screens are outside what we author.

  Affects: /shop/signin

  We expect to address this by 16 February 2027.

• The card payment form is supplied by our payment provider

  Provided by someone else

  The fields where you type your card details sit inside our checkout page, but they are rendered by our payment provider rather than by us. We cannot change how those particular fields are labelled or announced.

  Card details are deliberately never handled by J'Toye's own code, which is what keeps them out of our systems entirely. The part of the checkout page around the payment fields is ours and is covered by this statement.

  Affects: /shop/[slug]/checkout

  We expect to address this by 16 February 2027.

• Some checkout fields are marked required only by a visible asterisk

  Known problem, not yet fixed

  On the delivery address part of checkout, the address, town and postcode labels end in an asterisk to show they are required, but that requirement is not carried in the page's code. A screen reader will not announce those three fields as required, so the asterisk is meaningless to anyone who cannot see it.

  The name, email and phone fields do carry the requirement correctly; the three delivery address fields were missed when delivery was added.

  Affects: /shop/[slug]/checkout

  We expect to address this by 16 November 2026.

• Some text does not have enough contrast against its background

  Known problem, not yet fixed

  A number of smaller pieces of text — prices, secondary notes, muted helper lines and some error text — are lighter than the standard's minimum contrast against the page behind them. They are readable for most people but harder to read in bright light or with low vision.

  These are enumerated with their measured contrast ratios in the codebase and are checked automatically so the set cannot grow, but the existing entries have not yet been corrected. Changing them touches the visual design of several pages and is being done deliberately rather than in a rush.

  Affects: /, /shop, /shop/[slug], /shop/[slug]/cart, /shop/[slug]/checkout, /shop/[slug]/orders/[orderNumber], /track, /auth/signin

  We expect to address this by 16 February 2027.

This statement was prepared on 7 October 2026. That is the date the accessibility testing behind it was carried out against the running site, not the date this page was written — a statement is only as current as the measurement underneath it.

It was last reviewed on 7 October 2026, when every problem listed above was checked again against the live code rather than copied forward.

The next review is due by 7 April 2027. If that date passes without this statement being updated, our build fails — so a stale statement stops being something a reader has to notice.

If you find an accessibility problem that is not listed here, or you need something on this site in a different format, please tell us. We want to know — the list above only contains what we have found ourselves.

How to reach us

• Write to us at Crispins Manor Farm Lane, Michelmersh, Romsey, England, SO51 0NT.

Please tell us which page you were on and what happened. If you were using a screen reader, magnifier or voice control, telling us which one helps us reproduce the problem.

The Equality and Human Rights Commission (EHRC) is responsible for enforcing the accessibility requirements that apply in the UK.

If you contact us about an accessibility problem and you are not happy with how we respond, you can contact the Equality Advisory and Support Service (EASS), which gives free advice to people who think they have been treated unfairly. You can find them at equalityadvisoryservice.com, and the EHRC at equalityhumanrights.com.

Raising a problem with us first is usually faster, but you do not have to, and nothing on this page limits your rights under the Equality Act 2010.