Accessibility statement

Our target

We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.1 at level AA everywhere: this website and the app for families, children, school staff and caterers, in English and in French, in light and dark mode. The app is built to work with a keyboard, screen readers and zoom, on phones, tablets and computers.

Where we are today

Luncheezy partially meets WCAG 2.1 level AA: most of the website and app meet it, and our internal review lists the parts that don’t yet. We fix the ones that stop someone from ordering or signing in first. Once the open issues are fixed, we’ll say here that Luncheezy meets WCAG 2.1 level AA, with the date.

How we check

• An internal review against every WCAG 2.2 level AA success criterion, on the main tasks: signing in, adding a child, ordering and paying, children ordering for themselves, a school’s lunch day, and the staff tables and forms. It covers keyboard use and what a screen reader announces.
• Automated axe checks on every page of this website, in English and French, on desktop and phone, and in dark mode on key pages. The app’s end-to-end tests run the same checks on its main screens, in English and French, on desktop and phone, and in dark mode.
• A test checks that every colour pair in our design system meets WCAG AA contrast, in light and dark mode.
• Key pages of this website must score 100 on Lighthouse’s accessibility audit.
• Our design rules: text rather than icons, colour never used alone, visible keyboard focus, a skip link, targets at least 44 pixels on public, family and child screens, and no animation when your device asks for reduced motion.

Automated checks don’t catch everything, and our team isn’t a substitute for people who use assistive technology every day. If something doesn’t work for you, please tell us.

Known limits

• We haven’t had an independent accessibility audit yet. We’ll arrange one when school boards need it for their purchasing.
• Children sign in with a username and a PIN, which asks them to remember it. A parent can instead sign their child in on a family device, and a classroom can use a kiosk.
• Printable PDFs, such as lunch labels and some reports, are made for printing and may not work well with screen readers. Most of the same information is available on screen or as a CSV file.
• Card payment and payout screens are provided by Stripe inside our pages.

Report a problem or ask for another format

Email [email protected] to tell us about a barrier or to ask for information in another format. It helps to include the page’s address, what you were trying to do, and the device, browser and any assistive technology you use.

A person replies within one business day and tells you what we’ll do and when. If a barrier stops you from ordering lunch or reading your child’s information, say so: we’ll help you do it another way right away, for example with the school placing the order for you.

You can also write to us at 4648 Lakelse Avenue, Terrace, BC V8G 1R2, Canada.

About this statement

We review this statement at least once a year and whenever we change how the website or app works. Last reviewed: September 2026.