Accessibility

Effective Date: September 26, 2026

Raileon is committed to making our marketing site and dashboard usable by everyone, including people who use assistive technology such as screen readers, screen magnifiers, voice control, or keyboard-only navigation. We target WCAG 2.2, Level AA, as our standard.

This statement reflects a good-faith self-assessment based on our own testing, not an independent third-party audit. We list what we believe conforms today, what we know does not yet, and how to tell us about a barrier we have missed.

What conforms today

Verified against the code that is live on this domain:

• Every page declares a language (<html lang>) so screen readers pick the right pronunciation rules.
• A working skip link on the marketing site, the dashboard, and the admin console lets keyboard users jump past repeated navigation straight to the main content.
• Animations and auto-scrolling content (including the marketing use-case marquee) respect your device's reduced-motion preference, and the marquee also has an explicit pause control independent of that preference.
• Chat replies in the dashboard are announced to screen readers as they arrive, instead of relying on the user noticing new text on the screen.
• Our accent color, emerald #00D47E on a black dashboard background, measures 10.72:1 — well above the AA text minimum and into AAA territory.
• In the default dark and light dashboard palettes, body text meets the 4.5:1 contrast minimum for text, and the resting border of every text field, text area and dropdown meets the 3:1 minimum for interface components.
• Automated accessibility checks run on every code change: eslint-plugin-jsx-a11y lints the source of every page and component, and axe-core checks the dashboard navigation, overview, chat and customization components.

What does not conform yet

We would rather list a real gap than claim a false positive:

• This statement is based on automated testing and our own review, not an independent audit by a person who uses assistive technology day to day. Some issues that only surface in real-world use may not be caught yet.
• Automated coverage is strongest on our primary flows — the public marketing pages and the core dashboard screens. Less-visited screens have not each been individually reviewed.
• Browser-level axe-core checks of our public pages are written but do not yet run automatically on every change, so a regression on a public page could ship before we catch it.

VPAT / Accessibility Conformance Report

We have not completed a formal Voluntary Product Accessibility Template (VPAT) or Accessibility Conformance Report (ACR), and we would rather say so than hand over a document we cannot stand behind. If your organization's procurement process requires one, contact us and we will work through your accessibility questionnaire directly with you.

Report a barrier

If you run into an accessibility barrier anywhere on Raileon, or a claim on this page does not match what you experienced, please tell us. Reports go to a real, monitored mailbox — not a form that disappears into a queue.