Trust & information

Accessibility

The project uses semantic controls and automated checks, but it does not claim conformance with an accessibility standard.

Current provisions

  • The reading app uses headings, landmarks, labelled native form controls, buttons, status regions, and a dialog for enlarged card artwork.
  • Reading-stage headings receive focus as the interface changes, and status messages announce selection and save results.
  • Light and dark themes are available. Motion-based scrolling is disabled when the browser reports a reduced-motion preference.
  • These static information pages use a skip link, visible keyboard focus, semantic headings, and no JavaScript.

Checks in the repository

Browser tests run axe-core against the landing and setup view, a completed journal journey, and the dark theme. Separate journeys cover compact phone, phone, medium, and desktop viewports and check that long German content does not overflow the viewport.

Static-output tests check that every trust page has a language, unique metadata, a visible main heading, working internal links, and a path back to the reading app.

Known limits

Automated checks cannot establish that the whole experience works well for every person or assistive technology. The project has not published an independent manual audit or an accessibility conformance report. Revealed card illustrations carry card-name alternative text, and the enlarged-image dialog plus each English card page provide an editorial description of common Rider–Waite–Smith imagery. Those descriptions remain English and may not match every detail of a production rendering.

The project does not yet provide a public accessibility contact address. This reporting gap is recorded on the corrections page and should not be mistaken for a complete feedback process.

Page record

Last reviewed
Evidence reviewed
  • Current application markup and focus behavior
  • Current Playwright and axe-core browser journeys
  • Static-output test suite