Accessibility Statement

AxioTab is built by Axiosware LLC. We want anyone to be able to order food from a restaurant that runs on AxioTab, whatever they use to browse the web.

What this covers

The ordering pages we build for restaurants: the restaurant’s menu page, the item options screen, the cart, checkout, the order status page, and the rewards page. These are served both at axiotab.com and on each restaurant’s own web address. It also covers axiotab.com itself.

It does not cover the restaurant staff portal, the in-store point of sale, or the payment page, which is hosted and controlled by Stripe.

The standard we aim for

Web Content Accessibility Guidelines (WCAG) 2.1, Level AA.

Where we actually stand

Partially conformant. Most of WCAG 2.1 Level AA is met on the ordering pages, and we have fixed the specific problems listed below. We have not commissioned an independent audit, so we do not claim full conformance.

What we have done

• Colour contrast, including each restaurant’s own colours. Restaurants pick their own brand colours. We calculate the contrast of every colour a restaurant chooses. Their colour is used exactly as picked wherever it fills an area, such as buttons and banners. Where the same colour would be used for small text and would be too faint to read, we use a deeper shade of that same colour for the text only, and we tell the restaurant owner in their settings that we did. Text sitting on top of a brand colour is set to black or white automatically, whichever reads.
• Keyboard.Every control can be reached and operated with a keyboard, and the focused control is outlined clearly. There is a “skip to content” link at the top of each page. The item options window traps focus while it is open, closes with the Escape key, and returns you to the item you opened it from.
• Things that change without reloading the page. The order status page updates itself while you wait for your food, and it now announces the change out loud to a screen reader, including when your order is ready and your pickup code. Adding to the cart, searching the menu, applying a promo code and checkout errors are announced the same way.
• Forms.Every field has a name that a screen reader reads, including the delivery address fields. Errors are described in words rather than signalled by a red outline, and pressing “Continue to payment” with something missing moves you to the explanation.
• Information carried by colour. Which step your order is on, which day is today, whether a reward is selected and whether points were earned or spent are all stated in words as well as shown in colour.
• Images. Menu photos, restaurant logos and cover photos are marked as decorative, because the item name, restaurant name and page heading next to them already carry the same information. Photos are never the only way to learn what a dish is.
• Motion. If your device is set to reduce motion, the fade-ins, the smooth scrolling and the card hover effects all turn off.

Known gaps

• We have not tested with a real screen reader end to end. Our work so far is based on the WCAG success criteria and on inspecting the markup, not on a session with JAWS, NVDA or VoiceOver. Some of what we have fixed may still read awkwardly in practice.
• Restaurants upload their own menu photos and cover photos. If a restaurant uploads a picture of text, such as a photographed paper menu, that text is not available to a screen reader. We do not currently stop them.
• Restaurants write their own item names, descriptions and page text. We cannot guarantee the reading level or clarity of that writing.
• Some controls, such as the quantity plus and minus buttons, are smaller than the 44 by 44 pixel target size recommended by WCAG at Level AAA. They meet the Level AA minimum.
• The payment step happens on Stripe’s own checkout page. Its accessibility is Stripe’s responsibility, not ours.
• Where a restaurant uses a cover photo behind its name, we darken the photo enough that white text over it stays readable. Because the photo is chosen by the restaurant, we verify this by how the darkening is built rather than per photo.

Tell us about a problem

If something on an ordering page blocks you, please email hello@axiosware.com and tell us the restaurant, the page and what happened. We aim to reply within five business days. If we cannot fix it quickly, we will tell you how to place the order another way.