The vault is for everyone.
A vault that protects the things only a person owns must be openable by every person who has a right to it. The page below records AION’s accessibility commitments, the standard AION targets, and the honest gaps to close before launch. Accessibility is treated as part of the broader vulnerable-user doctrine at /safety: a User who cannot interact with the Gate has not given informed consent.
WCAG 2.2 AA, with active intent toward AAA
AION targets WCAG 2.2 Level AA across the public website and the application. Where a stricter Level AAA criterion can be met without harming the ceremony of the experience, AION holds it: ample color contrast, generous tap targets, slow-motion defaults, and a reduced-motion preference that turns off breathing animations and the constellation parallax.
What is verified now
- Keyboard navigation through the seal, the begin and unseal links, and the prototype flows. Every interactive element is reachable by Tab.
prefers-reduced-motionrespected: animations shorten to a single millisecond and stop iterating when the user opts out.- Color contrast: AION’s palette (bone over ink, gold over ink) is checked against the AA contrast threshold for body text. The pure-gold accent is reserved for non-essential emphasis and chapter marks.
- Semantic landmarks (
main,nav,footer,header) on every page so a screen reader can skip directly to content. - The Wheel of Aion seal carries SVG
titleelements naming each sovereign, so a hover or screen-reader pass surfaces the meaning of every dot.
Honest gaps
- A formal third-party accessibility audit. Phase 1 schedules this alongside the cryptographic audit.
- Full screen-reader review of the unseal ceremony. The current ceremony layout was designed visually first; a separate pass with a screen-reader user is required to confirm the witness rail and oracle panel narrate in the right order.
- Mobile-specific keyboard interaction (external keyboards on tablets) is not yet exhaustively tested.
- Localization. AION ships in English today. Translation into the languages of the sovereign holdings is a Phase 3 commitment, with right-to-left layout support included from that release forward.
Things AION will not do
- AION will not gate any operation behind motion, sound, or color alone. Every state has a textual narration.
- AION will not require a mouse for any cryptographic flow. Sealing and unsealing must be completable by keyboard or screen reader.
- AION will not depend on a CAPTCHA that defeats users with disabilities. Where rate limits are needed, AION uses privacy-respecting heuristics first and human review for exceptions.
- AION will not minimize touch targets below the platform accessibility recommendation. The ceremony is slow; the buttons are large.
If something is not accessible
Write to accessibility@sealedaion.com with the page, the assistive technology you are using, and what AION should have done differently. Email forwarding may still propagate after MX setup on sealedaion.com; mail sent before routing is verified may not be received. AION will acknowledge accessibility reports within five working days and treat them at the same priority as security reports. Where an issue blocks core function for a class of users, AION will remediate before any non-blocking feature work.