Our goals
We aim to follow the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA as our design target. This is a goal, not a claim: KEYXE has not been audited for WCAG conformance by an independent assessor.
What we have done
- Semantic structure: one main heading per page, ordered headings, landmarks, breadcrumbs and a “Skip to content” link.
- Keyboard operation: menus, “Learn more” panels, FAQ items, demo tabs, tables, dialogs and forms work with the keyboard, with a visible focus indicator. Charts can be explored with the arrow keys.
- Meaningful labels: form fields have visible labels, errors are announced and linked to their fields, and status messages use live regions.
- Text alternatives: meaningful images have descriptive alt text; decorative images are hidden from assistive technology. Charts include text summaries, and every number in a chart is also available in a table or tooltip.
- Responsive text and layout: content reflows on small screens and at 200% zoom without horizontal page scrolling.
- Motion: animation is minimal and respects the “reduce motion” setting.
- Color: text colors are chosen for contrast, and status is never communicated by color alone.
How we check
Automated accessibility checks (axe) run against key pages in our test suite, alongside keyboard-navigation tests. We also spot-check pages manually with the keyboard and at 200% zoom. Results are recorded in our internal test report.
Known limitations
- Some dense demo tables scroll horizontally inside their container on narrow screens.
- The bot-protection widget on forms is provided by Cloudflare; its accessibility depends on that provider.
- Charts are visual summaries; screen-reader users may find the accompanying tables and tooltips more efficient.
Report a barrier
If something on KEYXE is hard to use, please tell us through the contact form (choose any topic and mention “accessibility”). Include the page address and what happened. We read every report and use it to prioritize fixes.