Our Commitment
Accessibility is not a feature we layer on at the end — it's the floor we start from. We follow WCAG 2.2 Level AA as our published target standard, and we measure ourselves against the European Accessibility Act (EAA / EN 301 549), Canada's Accessibility for Ontarians with Disabilities Act (AODA), the Accessible Canada Act (ACA), and the US Americans with Disabilities Act (ADA).
15% of the world has a permanent disability. Many more of us are temporarily disabled at some point: a broken arm, a migraine, glasses left at home, a noisy kitchen, a moving train. Good design accommodates all of us. We treat accessibility as a quality signal — when the dashboard works for a blind GM, it works better for everyone.
Target Standards
WCAG 2.2 Level AA
Web Content Accessibility Guidelines 2.2. Covers perceivable, operable, understandable, and robust criteria — including the new SC 2.5.8 (24×24 px minimum touch targets), SC 2.4.11 (focus not obscured), and SC 3.3.8 (accessible authentication).
EAA / EN 301 549
European Accessibility Act + harmonised standard EN 301 549. Incorporates WCAG 2.1/2.2 AA and extends to mobile apps. Mandatory for any provider serving EU consumers.
AODA
Accessibility for Ontarians with Disabilities Act, 2005. We target full conformance with Information & Communications Standards including WCAG 2.0 Level AA (and exceed it with 2.2).
ACA (Federal Canada)
Federal goal of a barrier-free Canada by 2040. We participate as a federally regulated digital service across all Canadian provinces and territories.
ADA Title III
Americans with Disabilities Act. Restaurants account for ~10% of all private ADA web-accessibility lawsuits. We aim to keep TableFlow on the right side of that line for every venue we serve.
Beyond compliance
Reduced-motion users get a different valuable experience, not a degraded one. Dark-mode is offered everywhere — operators work in dim restaurants. Touch targets are 44 px (not the WCAG floor of 24 px) because hands get greasy on iPads.
Most Recent Self-Audit
We run automated and manual accessibility checks on every release. This is the most recent published result — verified with axe DevTools, WAVE, Lighthouse, and keyboard-only navigation.
2026-05-14
Admin dashboard, booking widget, public marketplace, operator marketing site
axe DevTools + WAVE + Lighthouse + manual keyboard + screen reader (VoiceOver, NVDA)
Substantial — known issues listed below Improving each release
External certified audit: we plan to engage a CPACC, WAS, or CPWA-certified third-party auditor for an independent conformance report. When that audit is complete we will publish the auditor's name, certification, and findings on this page.
Features We Provide
- Full keyboard navigation — every interactive control reachable with Tab/Shift+Tab/Enter/Space/Escape. No keyboard traps.
- Screen-reader optimised — semantic HTML, proper landmarks, ARIA live regions for live data, descriptive labels on all icons.
- Colour + icon + label — status is never communicated by colour alone. Green/red dots are always paired with text and icons for colour-blind operators.
- Reduced-motion respected — when
prefers-reduced-motion: reduceis set, we replace animations with steady states. Information density is unchanged. - High-contrast mode — when
prefers-contrast: highis set, borders sharpen automatically. - 44×44 touch targets — comfortably tappable on iPads, even with greasy hands or in motion. (WCAG 2.2 minimum is 24×24; we exceed it.)
- Dark mode in service — operator dashboard ships dark by default. Light mode available via system preference.
- Visible focus indicators — 2 px outline on every focusable element, with offset, never relying on subtle colour cues.
- Skip-to-content links — on every public and operator page, visible on focus.
- 200% zoom without breakage — content reflows; nothing is cut off.
- Multi-language support — English, French, Spanish, Portuguese ship today, with Italian, German, Dutch, and Nordic locales in active development.
- Restaurant-timezone honesty — every time on the system is shown in the venue's local timezone. Never UTC. Canada spans six timezones; getting this wrong is a real accessibility failure.
Known Issues
We publish what we know. The list below reflects open accessibility issues we've identified in our own audit. Each one has an owner and a target release.
| Issue | Severity | Status | Target |
|---|---|---|---|
| Auto-playing hero videos on the public homepage and business page lack visible pause controls (WCAG 2.2.2). | Major | Planned | 2026-Q3 |
| Some date-picker components don't yet have a fully accessible keyboard alternative for screen reader users — manual text input is always available as a fallback. | Minor | Planned | 2026-Q3 |
| Older legal pages (Privacy Policy, Terms of Service) still ship with inline CSS — being refactored to the same accessible chrome this page uses. | Minor | Planned | 2026-Q3 |
| Third-party content embedded in some venue pages (Cloudinary media library, Stripe payment iframes) inherits its host's accessibility posture, which we do not control end-to-end. | Minor | Monitoring | Ongoing |
How to Report a Barrier
If you encounter anything on TableFlow that doesn't work for you, please tell us. Specific feedback ("the date picker on the booking widget can't be reached with a screen reader on Safari") is more valuable than a star rating — it lets us fix the exact thing that broke for you.
Email our accessibility team
[email protected]Standards References
- Web Content Accessibility Guidelines (WCAG) 2.2 — W3C
- WAI-ARIA Authoring Practices — W3C
- EN 301 549 — ETSI (EU harmonised standard)
- European Accessibility Act — European Commission
- Accessibility for Ontarians with Disabilities Act (AODA), 2005
- Accessible Canada Act (ACA), 2019
- Americans with Disabilities Act — ADA.gov