- On the “main” page:
- The site template contains the “AccessiBe” accessibility widget, which is fully accessible using the widget interface controls for page color contrasting, font sizing and other accessibility related options. All widget controls are fully operational.
- The main page and subsequent pages contain detectable landmark regions such as <banner>, <nav>, <main> and <footer> regions, which enhances page navigation and accessibility. Example: https://www.w3.org/WAI/GL/wiki/Using_ARIA_landmarks_to_identify_regions_of_a_page
- All regions have detectable region roles defined using ARIA role attributes, such as: <header role=”banner”>, <nav role=”navigation”>, <main role=”main”> and <footer role=”contentinfo”>, which improves screen reader compatibility.
- The page templates have proper skip links such as: “skip to content,” “skip to menu” and “skip to footer” for increased accessibility. Example: https://webaim.org/techniques/skipnav/
- The navigation skip links such as: “Our story,” “Menu,” “Catering,” “Press” and “Contact” do not move screen focus to the appropriate anchored section of the page when activated using the keyboard. Ensure that all anchor links move screen focus to the appropriate area of the page when activated. Example: https://webaim.org/techniques/skipnav/
- In the “Contact” page:
- In the contact form, choosing a required date from the date drop-down boxes is difficult to accomplish using the keyboard. The user has to manually input the date in year/month/day format. Ensure that the date drop-down boxes are coded for month/day/year input and that the drop-down boxes are coded as native drop-down boxes. Example: https://www.w3.org/WAI/ARIA/apg/patterns/dialog-modal/examples/datepicker-dialog/ and https://www.w3.org/WAI/ARIA/apg/patterns/combobox/examples/combobox-datepicker/
- The “submit” control needs to be coded as a native submit button control in order for screen reading software to detect the control for keyboard activation. Example: https://www.w3.org/WAI/WCAG21/Techniques/html/H32
- In the “Pickup online” module:
Note: The user is redirected to a third party ordering website: “toasttab.com.” A statement should be placed on the page indicating that the link with redirect the user to an external third-party site and that accessibility cannot be guaranteed on third-party sites.
- Able to view the online menu items and options.
- Able to customize an order.
- Able to place an item in the shopping cart and remove/cancel order.
The online pickup process is accessible
- In the “Delivery online” mobule:
Note: The user is redirected to a third party ordering website: “UberEats.com.” A statement should be placed on the page indicating that the link with redirect the user to an external third-party site and that accessibility cannot be guaranteed on third-party sites.
- Able to view the online menu items and options.
- Able to customize an order.
- Able to place an item in the shopping cart.
The online delivery process is accessible with some difficulties due to using the third party UberEats website

