Accessibility Statement

Last updated: April 19, 2026

1. Our target

Enrollo aims to conform with WCAG 2.1 Level AA. We run axe-core on every CI build against the pages counselors and students actually use: sign-in, Inbox, student detail, commission detail, share status, and public intake form.

2. What's working today

  • Keyboard-only navigation on Inbox rows (↑ ↓ Enter c s).
  • Screen-reader labels on every interactive control (data-slot + explicit aria-label where needed).
  • Colour contrast ≥ 4.5:1 for body text and ≥ 3:1 for UI borders and status colours.
  • Focus rings (ring-primary/50) visible on every tabbable element.
  • Touch targets on mobile are ≥ 44×44 CSS pixels on primary actions (buttons, form inputs, Inbox row actions).
  • Respect for prefers-reduced-motion on animated transitions.

3. Known gaps

These are tracked and prioritised against the WCAG 2.1 AA baseline.

  • Some secondary interactions (drag-to-reorder pipeline stages, DnD application cards) lack a keyboard-only equivalent. We provide read-only fallbacks; full keyboard reorder is on the roadmap.
  • A few status badges use colour to distinguish between close status variants. Icon + text always accompany the colour, but the distinction can be subtle in high-contrast viewing modes.
  • We target WCAG 2.1 AA but are actively preparing for WCAG 2.2 AA (new success criteria: consistent help, focus-not-obscured). Gaps against 2.2 are documented internally.

4. Feedback

If you hit an accessibility issue — especially with a screen reader or keyboard-only flow — email hello@enrollo.io with the page URL and what you expected. We triage accessibility bugs at the same tier as security issues. We aim to acknowledge within one business day and give you a fix ETA within five.

5. Assistive-tech baseline we test against

  • VoiceOver on macOS 14 + Safari
  • NVDA on Windows 11 + Firefox
  • TalkBack on Android Chrome
  • Keyboard-only navigation on all three