Skip to main content
Back to homeStart checking

Accessibility

Accessibility Statement

Yentl's accessibility target, audited-route evidence, known gaps, and reporting path.

Last updated: 2026-05-18

Conformance level

Target: WCAG 2.2 Level AA — required under the European Accessibility Act (EAA), enforcement date 28 June 2025.

Current status: Automated checks on / and /session as of 2026-05-18 support the implementation notes below. They are not a full-product or manual assistive-technology conformance audit.

  • 1.4.1 Use of Color — Verdict states use color stripe + icon + text label (triple-encoded). Color is not the sole means of conveying information.
  • 1.4.3 Contrast (Minimum) — Text contrast checks passed on the audited routes for primary content; large text checks use the 3:1 threshold.
  • 1.4.4 Resize Text — The audited routes did not show blocking layout breakage at 200% zoom.
  • 2.1.1 Keyboard — Interactive elements on the audited routes are intended to be keyboard-accessible, with tab order following visual order.
  • 2.4.3 Focus Order — Skip-to-content link is first in tab order, anchors to #main-content.
  • 2.4.7 Focus Visible — Focus ring token (--ring) has ≥3:1 contrast against page background and common element backgrounds.
  • 2.5.5 Target Size — Primary interactive targets are designed for at least 44×44 CSS px.
  • 3.2.3 Consistent Navigation — Navigation structure is intended to stay consistent across public pages.
  • 3.3.1 Error Identification — Form errors in the checked report flow are identified and described to users.

Motion & animation

Animated elements (recording beacon pulse, toast entrances) respect the prefers-reduced-motion media query via Tailwind's motion-reduce: variants. Enabling reduced motion in your OS settings disables or shortens the affected animations.

Known limitations

  • Audio playback controls — Not applicable in v1 (audio is not persisted). When audio playback is added in a future version, accessible controls will be required.
  • Complex data visualizations — Planned for v2. Will require accessible tables and chart alternatives.
  • Screen reader testing — Automated axe-core audits are clean as of 2026-05-18 for the audited routes. Manual screen reader testing (VoiceOver, NVDA) is planned before commercial launch.

Audit information

Date of last automated audit: 2026-05-18

Tools used: axe-core CLI, Lighthouse (accessibility category).

Audits documented here ran on: / (home) and /session.

Report an accessibility issue

If you encounter an accessibility barrier or have a specific accommodation request, email accessibility@yentl.it or use the contact page.