Accessibility

The first thing the Tab key reaches on any page is a “Skip to content” link that jumps past the whole top navigation and moves focus into the page body. It is hidden visually until it takes focus, so it costs sighted mouse users nothing.

The app shell renders a single main landmark and no page adds a second one, so “jump to main content” in a screen reader is unambiguous. This is not a convention we hope holds: an automated test walks every file under src/app and src/components and fails the build if a second one appears.

Ambient page animation (drifting gradients, shimmer, pulse glows) is written so its static first frame is the default, and the keyframes are enabled only inside a prefers-reduced-motion: no-preference query. The animated canvases obey the same preference: the homepage hero paints one composed frame and stops, and every engine preview loads paused with a play control instead of starting itself. Setting the preference in your operating system stops all of it.

The control further down this page sets motion for this site: follow your system (the default), full motion, reduced motion, or no animation at all. Your choice overrides the operating system in both directions and is applied before the first frame, so there is no flash of the motion you asked not to see. “Reduced” and “off” are deliberately different: reduced keeps the short fades that tell you a control responded and keeps phone haptics, because reducing motion is a request about motion sickness, not a request to lose feedback.

Every live engine preview carries its own play/pause button, so motion can be stopped whether or not you have set a system preference, and previews already stop on their own when scrolled out of view or when the tab is hidden.

Your saved theme is applied by an inline script in the document head, so there is no flash of the wrong theme on load, which matters most to people who chose dark mode for light sensitivity.

Icon-only buttons carry accessible names, decorative marks are hidden from assistive technology, navigation exposes the current page, and modal dialogs declare their role and expanded state so focus and announcement behave correctly.

A browser test drives the axe-core rule set over a representative set of pages of a real production build and fails on the WCAG 2.0/2.1 A and AA rules, colour contrast included. It is a ratchet: the outstanding findings are recorded per page and the test fails both when a new one appears and when a recorded one is fixed without being removed from the list, so the debt below cannot quietly grow and cannot be quietly forgotten.

A service worker caches visited pages and falls back to a dedicated offline page, so a dropped connection does not leave you on a browser error screen mid-task.