Accessibility Statement

Vernacia should work for everyone. We are committed to meeting the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA across our web app and marketing site.

Last reviewed: April 2026

Our commitments

Keyboard navigation

Every interactive element — buttons, links, form fields, file upload — is reachable with Tab and operable with Enter or Space. Focus rings are visible and high-contrast on every theme.

Screen reader support

We test against NVDA on Windows, VoiceOver on macOS/iOS, and TalkBack on Android. Landmarks, ARIA labels, and live regions are used on status updates, toasts, and progress indicators.

Visual & motor

Colour contrast meets WCAG 2.1 AA (4.5:1 for text, 3:1 for UI). Respecting prefers-reduced-motion disables non-essential animations. Click targets are at least 44×44 px on mobile.

Known limitations

We believe in being honest about where we still have work to do. These are the accessibility issues we are actively tracking.

  • PDF preview in job detail page

    The inline PDF viewer used on the completed job page has limited screen reader support. Until we replace it, screen reader users can download the PDF and open it in a dedicated reader.

  • Drag-and-drop upload

    File drag-and-drop is offered as a convenience, but the primary upload path is a keyboard-accessible file picker. Users who cannot drag files will not lose any functionality.

  • Language selector search

    The searchable language dropdown uses typeahead; it is operable with arrow keys, but very long result lists can be slow to navigate with VoiceOver. A flat alphabetical list is available as a fallback.

  • Colour-only quality indicators

    Quality scores on the dashboard use colour plus a numeric value. We are adding text labels (Good / Fair / Poor) alongside the colour in an upcoming release.

Standards we follow

Vernacia targets WCAG 2.1 Level AA. We run automated accessibility checks (axe-core) in CI and periodic manual audits with a mix of assistive technologies.

All new features must pass our accessibility review before release. If a feature ships with a known limitation, it is tracked publicly on this page until resolved.

Related documentsSecurityCompliance

Report an accessibility issue

Found a barrier? Email [email protected] with a description and, if possible, the page URL. We aim to acknowledge reports within two business days.