Kaamio

Accessibility statement

Last updated: 2026-05-24

Kaamio is built to be usable by everyone, including candidates and recruiters who rely on assistive technology. We target conformance with Web Content Accessibility Guidelines 2.2, Level AA (the current W3C Recommendation, published December 2023), and we apply the same intent to the Indian Rights of Persons with Disabilities Act, 2016 requirement that digital services be accessible.

The on-page accessibility menu

Every page on Kaamio shows a floating accessibility button in the bottom-right corner. Open it to:

  • Increase text size up to 125% without breaking the layout.
  • Switch on a high-contrast yellow-on-black theme.
  • Pause animations and motion (useful for vestibular conditions).
  • Force underlines on every link.
  • Use a larger, higher-contrast cursor.

Your choices are saved on this device and applied on every subsequent visit. You can reset them from the same menu.

Built-in screen-reader and keyboard support

  • Skip-to-content link appears as the first focusable element on every page.
  • Semantic structure: pages use one <main> landmark, a single <h1>, and ARIA labels on icon-only controls so screen readers announce them clearly.
  • Visible focus indicators: every interactive element has a 2-pixel focus ring with high contrast against its background.
  • Forms: every input has an associated <label>. Error messages are announced through aria-live regions.
  • Modal dialogs trap focus while open and restore focus to the trigger element on close. Press Esc to dismiss.
  • Toast notifications appear in a polite live region so they don't interrupt the reader's flow.
  • Keyboard navigation: every action — including drag-to-reorder kanban columns and dropdown menus — has a keyboard alternative.
  • Reduced motion: we honour both your operating-system preference and the per-device toggle above.

Standards we test against

We target WCAG 2.2 Level A and AA. The six new success criteria added in 2.2 are addressed as follows:

  • 2.4.11 Focus Not Obscured (Minimum) — the document sets scroll-padding-top and scroll-padding-bottom so a focused element is never fully hidden by the sticky top nav, cookie banner, or save bars.
  • 2.5.7 Dragging Movements — no flow in Kaamio requires a drag gesture. The application kanban moves cards via a status dropdown, not drag-and-drop.
  • 2.5.8 Target Size (Minimum) — every <button> and role=button has a base min-height: 24px; min-width: 24px floor; icon-only buttons are 36×36 by default via the shadcn size="icon" variant.
  • 3.2.6 Consistent Help — the accessibility widget (bottom-right), the legal footer links, and the in-app support / contact links appear in the same relative position on every page.
  • 3.3.7 Redundant Entry — multi-step flows (registration, profile setup, job application) carry already-entered values forward; we never ask the same fact twice in a single session.
  • 3.3.8 Accessible Authentication (Minimum) — every auth input has the right autoComplete attribute (so password managers and OS auto-fill work). Paste is allowed everywhere — no onPaste blocking. The one-time code field accepts paste and pulls from SMS auto-fill on supported browsers.

Other standing commitments:

  • Keyboard-only navigation: every flow can be completed without a mouse.
  • NVDA and VoiceOver: we test major flows (sign-up, resume builder, job search, application tracking) with both screen readers.
  • Colour contrast: body text ≥ 4.5:1, large text ≥ 3:1, against its background.

Known limitations

We are honest about where we still have work to do. As of today these are the gaps we are actively addressing:

  • Some third-party embeds (for example certain employer career-page previews) inherit their source site's accessibility, which we don't control.
  • The AI mock interview microphone capture relies on Web Speech APIs that vary by browser; we offer a typed alternative for every prompt.
  • Charts on the analytics dashboards convey information primarily through colour. We render a tabular alternative under each chart but the pattern is not yet uniform.

Tell us about a barrier

If you hit anything on Kaamio that doesn't work with your assistive technology, Contact support with the page URL and a short description. We aim to acknowledge within 2 working days and ship a fix — or a workaround plus a target date — within 10.

Formal complaints

For unresolved complaints in India, you may also contact the Chief Commissioner for Persons with Disabilities under the Ministry of Social Justice and Empowerment. For EU users, your national accessibility-monitoring body has equivalent powers under the European Accessibility Act.

    Accessibility statement · Kaamio