Accessibility
Accessibility statement
Last updated: 3 June 2026
comxbot is committed to making the platform usable by everyone, including people who use assistive technology, who rely on keyboard navigation, or who need plain English. This statement describes the current accessibility status of three surfaces: the public marketing site at comxbot.com, the authenticated dashboard at app.comxbot.com, and the chat widget embedded on customer websites.
Conformance status
We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.2 Level AA. The marketing site and chat widget currently meet AA. The authenticated dashboard meets most of AA, with known gaps listed below.
What works
- All interactive elements are reachable by keyboard with visible focus rings.
- Icon-only buttons have accessible labels announced by screen readers.
- Status colours are always paired with an icon (✓ / ⚠ / 🔴), so meaning isn't conveyed by colour alone.
- Form inputs have associated labels and inline error messages with aria-invalid.
- Modals trap focus and close on Escape.
- The chat widget renders fullscreen on mobile, supports markdown-rendered links, and persists conversation history.
- The dashboard offers Plain English, Step-by-step (chunked) and Guided learning modes for learners with different access needs.
- We use semantic HTML throughout, proper headings, landmarks, lists.
- Skip-to-content links on every dashboard page.
- ARIA live regions on chat logs, status badges and form errors.
Known gaps we're working on
- Some legacy data tables (Analytics, Sessions) lack column-sort announcements for screen readers.
- A few icon-only buttons on less-trafficked admin pages still need aria-label sweeps.
- The Clearing & Admissions setup wizard relies on visual progress; we're adding announced step changes.
- Tooltip dismissal-on-blur in citation chips needs improvement for keyboard users.
Assistive technology we've tested with
- NVDA on Windows + Firefox
- VoiceOver on macOS + Safari
- VoiceOver on iOS + Safari
- TalkBack on Android + Chrome
- Keyboard-only navigation
Reporting an issue
If you find an accessibility problem we haven't listed, please email accessibility@comxbot.com with the page URL, what you were trying to do, and the assistive technology you were using. We aim to acknowledge within 2 working days and fix or schedule a fix within 10.
Enforcement
For UK public-sector bodies (FE colleges, universities, schools): if you're unsatisfied with our response under the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018, you can contact the Equality Advisory and Support Service (EASS).
Preparation
This statement was prepared in May 2026. The platform was last tested in May 2026 against WCAG 2.2 AA using automated checks (axe-core) plus manual keyboard and screen-reader walkthroughs of the most-trafficked flows: sign-up, dashboard navigation, assistant creation, knowledge source upload, conversation inbox.