Accessibility Statement

Qreat aims to use WCAG 2.2 Level AA as the target for new and updated web experiences, including public marketing pages, guest QR ordering pages, and restaurant administration workflows.

Accessibility is treated as an ongoing product quality requirement, not a one-time certification.

• Keep page structure, headings, links, and language switching understandable.
• Maintain readable text, sufficient color contrast, and responsive layouts.
• Avoid relying on color alone to communicate important information.
• Keep forms, links, and buttons accessible by keyboard and screen reader where applicable.

Guest ordering pages are higher-risk because restaurant visitors may depend on them to view menus and place orders.

• Menu items, prices, availability, allergy notes, and order status should be available as text, not only images or color.
• Quantity controls, cart updates, language switching, order confirmation, and error states should be keyboard operable and screen-reader understandable.
• Touch targets should be large enough for mobile use, and ordering should not depend on gestures that lack alternatives.
• Restaurants should provide an alternative ordering method when a guest cannot use the QR ordering flow.

• Order tables, kitchen displays, alerts, print status, and analytics should not rely only on color, sound, or motion.
• Critical actions such as deleting menu items, changing availability, or cancelling orders should include clear labels and confirmation where appropriate.
• Charts and dashboard metrics should have text alternatives or tabular equivalents where practical.

If you experience an accessibility barrier in Qreat, contact hello@qreat.ai with the page or feature, device, browser, assistive technology if any, and a short description of the issue.

We review accessibility feedback and prioritize fixes based on severity, frequency, and impact on ordering or restaurant operations.