Last updated November 2, 2026

Accessibility Statement

We want everyone to be able to use Butterchop, including people who use a keyboard, screen magnification, a screen reader or other assistive technology. This statement says what we have checked, what we have not, and how to tell us about a barrier. It describes our evidence as ofOctober 30, 2026.

Products this statement covers

• This website, butterchop.com, including plan selection and these legal pages.
• The Butterchop Support site, support.butterchop.com, including its contact form.
• The Account portal, account.butterchop.com, used to sign up, manage billing and manage organizations.
• The Butterchop restaurant app: point of sale, kitchen display, back office, and guest pages that restaurants publish, such as booking, ordering and surveys.

Printed receipts and kitchen tickets, hardware such as printers, card readers and cash drawers, and pages run by other companies (for example payment checkout pages and the Cloudflare Turnstile security check on the support contact form) are not covered by our testing.

Our target standard

We use theWeb Content Accessibility Guidelines (WCAG) 2.2, Level AAas our design and testing target. It is a target, not a claim: we have not measured every page against every success criterion, and parts of our products may not meet it yet.

How we have checked

On October 30, 2026 our engineering team reviewed the accessibility checks that exist in our source code, and onNovember 2, 2026 it added the browser checks of restaurant app screens made since then. They are automated browser tests (Playwright) that check only the behavior listed here. They are not a full evaluation, and this page does not report their pass rate.

• butterchop.com home page: no horizontal scrolling at 320, 375 and 768 pixel widths; footer links stack at narrow widths; after an invalid plan quantity, the message is announced as a polite status and focus returns to the field; text in the product previews keeps a contrast ratio of at least 4.5:1 in light and dark themes.Evidence: services/landing-ui/tests/e2e/landing.spec.ts, services/landing-ui/tests/e2e/preview-contrast.spec.ts
• This statement and our India privacy and tax information page:one main heading, no horizontal scrolling at 320 pixels or at 200% zoom, links reachable with the Tab key with a visible focus indicator, and no motion with reduced motion requested.Evidence: services/landing-ui/tests/e2e/legal-statements.spec.ts, services/landing-ui/test/legal-statements.test.ts, services/landing-ui/test/india-information.test.ts
• Support contact form: keyboard order through every field at 320 and 1280 pixel widths, focus moves to the error message when a request fails, and the page without the online form fits a 320 pixel width.Evidence: services/support-ui/tests/e2e/contact.spec.ts, services/support-ui/tests/e2e/publication.spec.ts
• Restaurant app sign-in: the back office sign-in and the station unlock screen fit a 320 pixel width and can be completed with the keyboard.Evidence: tests/e2e/specs/api/backoffice-session.spec.mjs, tests/e2e/specs/api/station-session.spec.mjs
• Selected restaurant app tasks: the guest survey page is tested at a 320 pixel width; the catering guest-count screen is captured at 320 pixels and at emulated 200% zoom for review.Evidence: tests/e2e/specs/ui/ui-guest-survey.spec.mjs, tests/e2e/specs/ui/ui-catering-journeys-guest-counts.spec.mjs
• Account portal support request: focus moves to the error message when a request cannot be sent.Evidence: tests/e2e/specs/ui/ui-account-support-public.spec.mjs
• Restaurant app screens, checked in a real browser against the live service:in English and Spanish, light and dark themes, at 1280 and 320 pixel widths and at emulated 200% zoom (640 pixels at twice the pixel density), each check confirms that the page does not scroll sideways. These checks run by hand, not on every change. Screens and dates:
  • AI proposals waiting for approval, November 1, 2026.Evidence: services/isolation-unit-api/tests/third-round-gap-724-browser.integration.test.ts
  • Backups list, backup detail and restore request, with dialogs that stay inside the window and close with the Escape key, November 1, 2026.Evidence: services/isolation-unit-api/test-runner/backup-ui-browser/matrix.mjs
  • Waste allocation on a production batch, November 1, 2026.Evidence: services/isolation-unit-api/tests/helpers/waste-allocation-browser/harness.mjs
  • Changing a line quantity on the point of sale and the handheld (768, 640 and 320 pixel widths), November 1, 2026.Evidence: services/isolation-unit-api/tests/helpers/qty-change-browser/harness.mjs
  • Delivery history, delivery timeline and delivery report, November 2, 2026.Evidence: services/isolation-unit-api/tests/third-round-gap-575-browser.integration.test.ts
  • Reports page with report names and columns in the selected language, November 2, 2026.Evidence: services/isolation-unit-api/tests/third-round-gap-607-615-browser.integration.test.ts
  • Tax by rate detail, menu margin coverage and budget comparison, November 2, 2026.Evidence: services/isolation-unit-api/tests/third-round-gap-627-629-556-browser.integration.test.ts
  • Back office navigation pages, the fixed point of sale and handheld routes and check dialogs, and the kiosk, guest, host and dispatch screens. The checks run in English and Spanish, in light and dark themes, at 1280 pixels, 320 pixels and 200% zoom. They record missing control names, sideways scrolling, focus that is hidden or covered by a fixed bar, and axe-core rule results. They press Tab six times and make trial clicks on up to 25 controls on each page. They do not complete every task. Open findings are listed under limitations. November 2, 2026.Evidence: services/isolation-unit-api/tests/third-round-gap-746-browser.integration.test.ts, services/isolation-unit-api/tests/third-round-gap-746-pos-browser.integration.test.ts, services/isolation-unit-api/tests/third-round-gap-746-surfaces-browser.integration.test.ts
  • Accepting restored data after a backup restore, with a confirmation dialog that stays inside the window, no clipped text and focus back on a button after Escape, November 2, 2026.Evidence: services/isolation-unit-api/tests/third-round-gap-706-browser.integration.test.ts

Many of our component tests find buttons, fields and messages by their accessible name and role. That confirms those names exist; it does not show how a screen reader presents them.

Known limitations and areas not yet tested

• No independent accessibility audit has been carried out.
• We have not formally tested any product with a screen reader (such as VoiceOver, NVDA, JAWS or TalkBack), with voice control, or with people with disabilities.
• Our automated scanner (axe-core rules) finds only some barriers. A scan does not show whether a task can be completed with a keyboard or a screen reader.
• Automated browser checks do not cover every restaurant app screen or state. They do not cover the gift card, house account and store credit panels with data, reorder, the item detail, 86 and reject sheets on the kitchen display, the nutrition and allergen panels on guest pages, or the back office dialogs and row actions. Forced-colors (high contrast) modes have not been tested.
• Some findings remain open. In dark theme, some danger and success text on the kitchen display, the host floor and the offline card panel is below a 4.5 to 1 contrast ratio. We have not decided how to change the dark theme colors.
• Printed receipts and kitchen tickets, and hardware such as printers, card readers, cash drawers and customer-facing displays, have not been evaluated.
• PDF, CSV and spreadsheet downloads, and emails and text messages sent by Butterchop, have not been evaluated for accessibility.
• The support contact form uses the Cloudflare Turnstile security check, which we do not control. If it blocks you, email us instead (see below).

Report a barrier

Email [email protected]or use the Butterchop Support contact pageand choose the category "Other". Tell us:

• the page address or the screen and task you were using;
• what happened and what you expected;
• if you are comfortable sharing it, your browser, device and any assistive technology.

You do not need to tell us about any disability or health condition. Do not include passwords, payment card details, guest personal data or other secrets. We do not offer a guaranteed response time.

Get help another way

If a barrier stops you from finishing a task, such as choosing a plan or managing your account, email[email protected]with the task you are trying to complete and how you would like us to reply. Our support team will work with you on another way to complete it. If you are a guest of a restaurant, you can also contact the restaurant directly to book or order.

Review of this statement

• Prepared: October 30, 2026, from an engineering review of the tests listed above.
• Owner: Butterchop product team, with the support team for the contact route.
• Accessibility, product and support owner sign-off: pending.
• We review this statement when a major interface release changes the products it covers, and update the date above when we do.