Accessibility Statement

Actualizado por última vez el 30 de mayo de 2026 · Versión 1.3

Astravera is committed to making our products usable by everyone, regardless of disability, assistive technology, or context. This statement covers the Astravera marketing site (astravera.app) and the Astravera product suite (Hermes, Kairos, Nomia, Athena). It describes our current conformance status, the gaps we know about, and how to request help or report an issue.

Target standard

We are targeting Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA, which is the standard referenced by:

The European Accessibility Act (Directive (EU) 2019/882), enforceable from 28 June 2025.
The UK Equality Act 2010 and associated public-body regulations.
The US Americans with Disabilities Act (ADA) Title III as interpreted by US case law.

What we have done

Marketing site (astravera.app)

The marketing site is built with accessibility as a first-class constraint:

Semantic HTML — landmarks (<header>, <nav>, <main>, <footer>), heading hierarchy, lists, articles, and sections with aria-labelledby.
Skip-to-main-content link as the first focusable element on every page.
Keyboard navigation — every interactive element reachable by Tab, with a visible focus ring (focus-visible); menus dismissable by Escape.
Form labels — every input has a <label for> (not just placeholder); errors announced via aria-invalid and aria-describedby.
Alternative text on every meaningful image; decorative images marked alt="".
prefers-reduced-motion respected throughout — every animation and transition is suppressed when the user prefers reduced motion.
prefers-color-scheme respected, with a manual light/dark toggle that persists.
Colour contrast verified against WCAG AA thresholds for body text (≥ 4.5:1) and UI components (≥ 3:1).
Live-region announcements for asynchronous status changes (toasts, form submission outcomes) via the Nuxt <NuxtAnnouncer> primitive.
Per-locale <html lang> and <html dir>, including correct right-to-left rendering for Arabic and Urdu.

Product apps (Hermes, Kairos, Nomia)

As of May 2026, the product apps have completed their Phase 3 accessibility rollout:

Linting — eslint-plugin-vuejs-accessibility is installed and enforced in CI for all three apps, with zero violations.
Skip links — every app layout opens with a "Skip to main content" link as the first focusable element.
Form labels — every input across Hermes, Kairos, and Nomia has either a <label for> association or an aria-label. Inputs paired with custom dropdown components use visible <span> labels.
Reduced motion — a @media (prefers-reduced-motion: reduce) block disables all CSS animations and transitions suite-wide.
Focus management in modals — a shared useFocusTrap composable traps Tab/Shift-Tab within open modals, restores focus to the trigger on close, and supports Escape to dismiss.
ARIA on dialogs and menus — all modal dialogs carry role="dialog", aria-modal="true", and aria-labelledby. Navigation menus carry aria-haspopup and aria-expanded.
Interactive non-button elements — clickable list rows, plan bars, and kanban card items that are not native <button> elements carry role="button", tabindex="0", and keyboard (Enter) handlers.
Decorative element suppression — modal backdrops and decorative SVGs carry aria-hidden="true" so screen readers do not announce them.

Known gaps

The following items are not yet fully conformant. We are actively working on them:

Colour contrast audit — a systematic check of all design-system tokens (light mode, dark mode, and each per-board theme in Kairos) against WCAG AA thresholds has not been completed. Some muted secondary and tertiary text colours may fall below 4.5:1.
Automated accessibility CI — @axe-core/playwright regression tests covering the top user journeys (login, board view, card edit, plan view, sign document, profile) are not yet wired into CI.
Screen-reader passes — a full manual QA pass with NVDA (Windows) and VoiceOver (macOS and iOS) across the top journeys has not been completed. Specific areas of concern: the kanban drag-and-drop interaction, the date-picker in card due-dates, and the avatar image cropper.
Drag-and-drop keyboard alternative — the kanban column drag-and-drop in Kairos does not yet have a keyboard-accessible "Move card to…" secondary action for users who cannot use a pointing device.
Video captions — any onboarding or tutorial video content added in future will require a WebVTT caption track. No video content currently exists in the product.

These items are tracked under our internal compliance plan and are expected to land in the next iteration.

Current conformance status

Surface	Status
astravera.app (marketing site)	Fully conformant with WCAG 2.2 AA
Hermes (account and admin)	Partial conformance — known gaps listed above
Kairos (project management)	Partial conformance — known gaps listed above
Nomia (e-signatures)	Partial conformance — known gaps listed above
Athena (AI assistant)	Partial conformance — shares Hermes shell

The known gaps listed above apply to the product apps (Hermes, Kairos, Nomia, Athena). We will update each app to "full conformance" as those items are resolved.

How to report an issue

If you encounter an accessibility barrier on any Astravera product or page:

Email: [email protected]
Subject: "Accessibility issue: page or feature"
Include: the URL, your browser and assistive technology (if any), and a short description of what happened and what you expected to happen.

We aim to acknowledge reports within 5 business days and to provide a remediation plan within 20 business days for issues we can confirm.

If you are unsatisfied with our response:

EU users may contact their national accessibility enforcement body.
UK users may contact the Equality Advisory and Support Service (EASS).
US users may file a complaint with the Department of Justice under the ADA.

Technical specifications

Accessibility relies on the following technologies working correctly with assistive technology:

HTML5
WAI-ARIA
CSS (including prefers-reduced-motion and prefers-color-scheme media queries)
JavaScript (interactive components require JavaScript; the marketing site degrades gracefully)

We test on current versions of:

Screen readers: NVDA (Windows), VoiceOver (macOS, iOS), TalkBack (Android).
Browsers: Chrome, Firefox, Safari, Edge.
Keyboard-only navigation in all of the above.

Assessment methodology

Conformance of the marketing site (astravera.app) was assessed using:

Automated tools: Lighthouse CI (accessibility score 100/100 on all 13 public pages) and @axe-core/playwright regression tests (16 tests, all passing).
Manual review: semantic HTML structure, keyboard navigation, focus management, and colour-contrast verification against WCAG AA thresholds.
Screen-reader pass: a full manual screen-reader evaluation of all public pages was completed using NVDA (Windows) and VoiceOver (macOS and iOS) on physical devices, covering reading order, announcement phrasing, focus order, and form-error flows. No blocking issues were found.

Document history

This statement was last reviewed on the "Last updated" date shown above. We review it at minimum annually and after any major release that affects the user interface.