Skip to content
Swiffit Coach is live for macOS — real-time coaching for interviews, sales, meetings & security
Swiffit

LEGAL

Accessibility Statement

Last updated: April 22, 2026

Our commitment

Swiffit is committed to making our product usable by everyone, including people with disabilities. We design and build to meet the Web Content Accessibility Guidelines (WCAG) 2.2 Level AA where reasonably achievable, and we treat accessibility as a first-class requirement, not an afterthought.

Conformance target

We target WCAG 2.2 Level AA across the marketing site and the authenticated product. This includes the requirements in EN 301 549, the harmonised European standard referenced by the European Accessibility Act (EAA).

Scope

This statement covers:

  • The public marketing site at swiff.it and its subpages.
  • The authenticated Swiffit product (dashboard, enhancement flow, cover letter editor, application tracker, settings).
  • Transactional emails sent to users (welcome, subscription, cancellation, account deletion).

Measures we take

  • Automated accessibility testing (axe-core) runs in our CI on every pull request.
  • Semantic HTML, landmark regions, and skip-to-content links on every layout.
  • Forms use programmatically associated labels. Errors are announced to assistive technology.
  • Colour contrast meets WCAG 2 ratios in light and dark modes.
  • All animations respect the operating-system prefers-reduced-motion preference.
  • Interactive controls meet a minimum target size of 24 x 24 CSS pixels (WCAG 2.5.8).
  • Drag-and-drop interactions include a keyboard-only alternative (WCAG 2.5.7).

Known limitations

We are transparent about where we fall short. Current known issues being actively worked on:

  • The application-tracker Kanban board is being refactored so the keyboard shortcut for card reorder is discoverable and announced, not only implemented.
  • Passkey and Sign In with Apple are being added as alternatives to password authentication to satisfy WCAG 3.3.8 Accessible Authentication without relying on cognitive function tests.

We track accessibility issues the same way we track any other bug and aim to resolve Level AA issues within two release cycles.

Feedback and contact

If you encounter an accessibility barrier in Swiffit, please let us know. We take accessibility feedback seriously and aim to respond within five business days.

Enforcement

If you are in the European Union and you believe Swiffit has failed to meet the requirements of the European Accessibility Act or EN 301 549, and we have not resolved your concern, you may contact the market-surveillance authority in your EU member state. A directory is maintained by the European Commission.

In the United States, the Americans with Disabilities Act (ADA) Title III may apply. If you believe Swiffit has failed to meet its obligations, you may contact the U.S. Department of Justice.

Technical information

Swiffit is built with Next.js and deployed on Vercel. Our automated accessibility suite uses axe-core via Playwright and is run on every pull request against the pages covered above.