Accessibility statement

Accessible by design

Akan Vault targets Web Content Accessibility Guidelines (WCAG) 2.2 Level AA across the public site and the authenticated application. Accessibility is part of how every feature is accepted, not a later fix.

What we build in

Semantic landmarks, a logical heading order, and a skip link on every page.
Full keyboard operation with visible focus indicators and no keyboard traps.
Form labels, descriptions, and error messages that assistive technology announces.
Status announcements for uploads and background processing.
Color contrast verified in every state; meaning is never conveyed by color alone.
Text that resizes and reflows, and touch targets of at least 24 by 24 CSS pixels.
Captions and transcripts for audio and video, with navigation by timestamp and speaker.
Reduced-motion support and no reliance on inaccessible cognitive tests for sign-in.

How we test

Automated checks with axe-core run in continuous integration on representative pages, and every design token pair is tested for contrast. Keyboard and screen-reader oriented review is part of manual quality assurance for upload, review, search, record, and Akan AI flows.

Current status

The site currently consists of the foundation pages you can reach from the navigation. Automated accessibility checks pass on these pages. A full WCAG 2.2 AA audit will be completed and its findings published here before public launch. Known limitations, when they exist, will be listed on this page with a planned remediation date rather than left unstated.

Report a barrier

If any part of Akan Vault is difficult to use with assistive technology, we want to know. A reporting form will be available here once account and messaging infrastructure is in place; until then, project contact details are published in the repository README.