Accessibility Statement

The intended target is WCAG 2.2 Level AA for the create shell, the reveal shell, error pages, and these legal documents. Automated axe checks run on the public shells. Keyboard use, a skip link, visible focus, a 44×44 CSS-pixel target on primary actions, live status regions, and `prefers-reduced-motion` are part of the interaction contract.

• First-party dark theme with documented contrast tokens; no third-party widget overlays.
• Semantic headings, labelled secret and capability fields, and a footer attribution that stays on every public page.
• Reveal never runs on load, so a screen-reader user is not surprised by a consume.
• Legal documents are HTML, not a scanned PDF, with a contents list and language attributes on the main landmark (`lang` on `<main>`).
• No captcha and no time-limited puzzle on create or reveal.

• The tool UI is English. Legal documents are English and Romanian; the create/reveal controls are not localised.
• A capability link is a long string. It is labelled, but it is inherently hard to read aloud.
• Success and failure copy is concise by design. It does not describe cryptography in the status region.
• axe on a page is not a full WCAG audit. Manual testing with every assistive-technology combination is not claimed.
• If you enlarge text significantly, the three-column legal tables may require horizontal scroll.

If you cannot use a part of the Service, write to alex.jungean@gmail.com with subject “Accessibility — One Time Secret”. Describe the page, the assistive technology, and what failed. Do not include plaintext or a capability link. We will answer in English or Romanian and, where we can, provide the legal document as ordinary HTML (already the case) or as a clarification.

Prepared 22 August 2026. This statement will be reviewed when the interface changes in a way that affects accessibility.