← Back to homepage

Accessibility

Last updated 2026-08-22. How TELUVANE is built to work for keyboard users, screen reader users, and people who need reduced motion.

Conformance statement

TELUVANE targets WCAG 2.1 Level AA across the marketing site and the dashboard. We haven't had a third-party audit yet, so treat this as a good-faith statement of intent and current practice, not a certification. If you hit a barrier, tell us (see Contact below) and we'll fix it.

Keyboard navigation

Every interactive element (links, buttons, form fields, the session table, the sidebar nav) is reachable and operable with Tab, Shift+Tab, and Enter/Space alone. Focus order follows visual order, and focus is never trapped except in modal dialogs, where Escape closes the dialog and returns focus to the element that opened it. Focus outlines are never removed with CSS.

Color contrast

Body text and links on this page are checked against WCAG AA (4.5:1 for normal text, 3:1 for large text) using the same contrast utility (lib/contrast.ts) the app uses internally. Live result for the colors on this page:

  • Body text on background: 15.58:1 — passes AA
  • Accent links on background: 7.28:1 — passes AA

Reduced motion

Pages check the prefers-reduced-motion media query (via lib/useReducedMotion.ts) and skip decorative transitions and animations when it's set. Your browser is currently reporting:

Reduced motion: off. Your system isn't requesting reduced motion.

Screen readers

Pages use semantic HTML (headings, lists, landmarks) instead of div soup, form fields have associated labels, and icon-only buttons carry an accessible name. We test regularly with VoiceOver on macOS.

Known gaps

The insights charts don't yet have a text-table fallback for screen reader users. We're working on it.

Contact

Found an accessibility barrier? Open an issue at github.com/iWeslax83/teluvane and we'll prioritize it.