Accessibility Statement
We want every person who runs a business on ERPS X, and every guest who scans a menu, to be able to use it. Here is where we stand and how to tell us when we fall short.
1. Scope
This statement covers the public website erpsx.com, the ERPS X panel, the hosted workspaces at {company}.erpsx.com and on custom domains, the guest-facing RMS QR menu, and our documentation site. Third-party services we link to, such as Stripe checkout, are covered by their own statements.
2. Conformance status
We are working towards WCAG 2.1 Level AA. Parts of the Service already meet the standard; others are being improved release by release. We describe the current status honestly below rather than claiming full conformance.
3. What we do
- Keyboard access: navigation, forms, menus and dialogs are designed to be operable with a keyboard alone, with a visible focus indicator.
- Structure: pages use semantic HTML with a logical heading order, landmarks and labelled form controls so screen readers can navigate them.
- Colour and contrast: our brand palette (purple on black in light mode, purple on white in dark mode) is applied so body text and controls meet a minimum 4.5:1 contrast ratio. Status is never conveyed by colour alone.
- Text and zoom: layouts are responsive and remain usable at 200% zoom and on small screens, including the QR menu on phones.
- Images and icons: meaningful images carry alternative text; decorative icons are hidden from assistive technology.
- Forms: fields have visible labels, required fields are marked, and errors are described in text next to the field.
- Motion: animations are short and respect the operating system's reduced-motion preference where supported.
- Dark mode: users can switch the panel to dark mode from their settings.
4. Known limitations
We are aware of the following and are working on them:
- Some data-dense screens in ERPS and POS (large tables and reports) are difficult to navigate with a screen reader and may not reflow well on very narrow screens.
- Some icon-only buttons in older screens lack a text label for assistive technology.
- Printable receipts and PDF reports generated by the products may not be fully tagged for accessibility.
- Third-party embedded components, including live chat and payment checkout, may not fully meet our target.
5. Compatibility
ERPS X is designed to work with current versions of Chrome, Edge, Firefox and Safari on desktop and mobile, and with common screen readers such as NVDA, JAWS, VoiceOver and TalkBack. Very old browsers are not supported.
6. How we assess
We review new and restyled screens against WCAG 2.1 AA as part of our release checklist, using automated checks and manual keyboard and screen-reader testing. We have not yet commissioned an independent third-party audit.
7. Feedback and assistance
If you encounter a barrier, or need content in an alternative format, please tell us. Include the page or screen, what you were trying to do, and the browser and assistive technology you use.
We aim to acknowledge accessibility feedback within 2 business days and to tell you what we will do about it.
8. Escalation
If you are not satisfied with our response, you may refer the matter to the body responsible for accessibility or equal-access complaints in your jurisdiction. We will co-operate fully.
ERPS X LLC, St. Petersburg, Florida, USA.