Accessibility
Accessibility
A quiet place should be open to everyone who wants to rest in it.
The standard I hold this to
Mythic Dream aims to meet WCAG 2.2 at Level AA. Every public page is checked with axe-core, and the things no tool can judge — keyboard travel, where focus lands, motion, sound, and how the layout folds on a small screen — are walked through by hand. This page says what that found, including the parts that are still imperfect.
It can be walked with a keyboard
Every link, button and control can be reached and used with the keyboard alone, in the order the page reads. A clear violet ring follows wherever you are — it appears for keyboard and assistive input and stays out of the way of the mouse. The first press of Tab on any page offers a link that skips the navigation and drops you straight into the content.
Text holds its contrast
Body text and interface labels meet or exceed the 4.5:1 contrast that Level AA asks for against the deep indigo behind them, and the focus ring clears the 3:1 asked of controls. The palette is deliberately hushed, so the few places that fell just short — the small step numbers in the navigation, two lines in the footer — were lifted until they passed rather than left as an artistic exception.
Motion can be stilled
If your system asks for reduced motion, the dream listens: the worlds slow and soften, drifting symbols settle, and page transitions fall silent. Nothing on the site flashes, strobes, or moves fast enough to provoke a seizure, and nothing important is told through motion alone.
Sound is always yours to silence
The dream may begin its ambience as you walk in, so a Sound control sits in the header and again in the dream's own dock — either one silences everything at once, and a volume slider sits beside it. Nothing plays on the reading pages at all.
Its structure makes sense unseen
Pages are built from real landmarks — a header, a single main region, a footer — with headings in a sensible order and lists that are genuinely lists. Images that carry meaning describe themselves; the purely decorative ones are hidden from screen readers rather than read aloud as noise. Each page declares the language it is written in, so a screen reader pronounces it correctly.
It survives magnification
At 400% zoom, or on a 320-pixel-wide screen, every page reflows into a single column with no sideways scrolling and nothing clipped. Text can be spaced more loosely without content colliding.
It speaks eight languages
The codex, the dream dictionary and these pages are written in English, Spanish, German, French, Portuguese, Italian, Polish and Japanese. A language picker sits in the header and the footer of every page, and each version has its own address, so a search engine or a screen reader always knows which language it is holding.
Where it still falls short
An honest list is more useful than a confident one.
The dreamscape is a visual experience
The dream itself is a moving picture you stir with a cursor. Its worlds are described in words on the Worlds page, and every god it can show you is written out in full in the Codex — but the experience of drifting through it is not something I have found a way to convey without sight. If you have an idea for how it could be, I would genuinely like to hear it.
A few corners are still English
The navigation, footer, controls, page titles, the codex, the dream dictionary and the nightly guide all follow the language you are reading in. Three things do not: the page you land on when a link is broken, and the Worlds and Your Sky pages, which are written and kept in English only.
It has not been audited by anyone but me
The testing described above is my own, with automated tools and manual keyboard and screen-reader passes. It has not been reviewed by an independent auditor or by a panel of disabled users, which is the only way to find everything. Treat this statement as a careful, honest self-assessment rather than a certificate.
If something blocks you
Please tell me — a barrier I do not know about is one I cannot remove. Describe the page and what happened, and I will answer. Accessibility problems go to the front of the queue, ahead of new worlds and new gods.
Last reviewed and tested: · WCAG 2.2 AA