Building more accessible restaurant technology.
We want dining technology everyone can use. Accessibility is part of how we design and build Vertex.
Statement metadata
- Version
- Current
- Last reviewed
- Reviewed periodically
- Conformance target
- WCAG 2.1 Level AA
Current status
Partially conformant
Some parts of the site don't yet fully meet the target standard — see known limitations below.
Our accessibility commitment
At Vertex, accessibility is a design principle, not a checklist item. Our engineers and designers consider inclusive workflows from the first wireframe.
Automated & manual testing
Automated scanning alongside regular manual testing.
Screen-reader workflows
New features are tested with common screen readers such as NVDA, JAWS and VoiceOver.
What this statement covers
- Marketing website
- Online storefront
- Help Center
- Admin dashboard
- Web POS
Accessibility features
Keyboard navigation
Operable with tab, arrow and enter keys — no mouse required.
Visible focus
High-contrast focus indicators on interactive elements and links.
Semantic structure
Proper heading hierarchy and ARIA labels for assistive tech.
Screen-reader support
Content structured for readers such as JAWS and VoiceOver.
Colour contrast
Aims for at least a 4.5:1 ratio on essential text.
Responsive reflow
Usable at up to 400% zoom without losing content or function.
Form accessibility
Clearly labelled inputs and descriptive error messages.
Reduced motion
Respects your OS reduced-motion setting for non-essential animation.
Known limitations
A legacy sales-report table currently has limited keyboard column sorting and screen-reader context for complex merged cells.
Workaround
You can export the data to an accessible spreadsheet (Excel or CSV) using the Export button above the table for full screen-reader compatibility.
Alternative access
Need information in another format — large print, braille or audio? We're happy to help.
Request an alternative formatReport an accessibility issue
Your feedback helps us build a more inclusive product. Tell us what you ran into and we'll get back to you — we aim to respond promptly.
Helpful to include
- the page or feature
- what happened
- the assistive tech or browser you used
Help us do better.
Tell us where we can improve, or talk to our team about your needs.
