L·ALiving AI AtlasA Coding As Creating project

ACCESSIBILITY

What we’ve tested,
and what we haven’t.

Our target is WCAG 2.2 Level AA. We are not claiming conformance yet — no full audit has been done. This page states what has actually been checked, so you can judge the gap yourself.

What is in place

  • A “Skip to content” link as the first focusable element on every page.
  • Every page is reachable and operable by keyboard; navigation uses real links, so browser shortcuts and open-in-new-tab work.
  • A visible focus outline on every interactive element, at a 3px width that does not rely on colour alone.
  • The current page is marked with aria-current; the lens menu and mobile navigation close on Escape and return focus to the control that opened them.
  • One h1 per page and a single main landmark.
  • prefers-reduced-motion is respected — transitions and smooth scrolling are disabled when you ask your system for reduced motion.
  • Body text, muted text, and the moss/iris accents meet the 4.5:1 contrast minimum. The clay and gold accents were darkened specifically for small text and icons, which previously sat at 3.7:1 and 2.2:1.
  • Every interactive control has an accessible name, and no image is missing alternative text.

Known gaps

We would rather list these than let you discover them.

  • No screen-reader testing. The markup and ARIA have been inspected programmatically, but the site has not been driven with VoiceOver, NVDA, or JAWS. Until it has, we cannot honestly claim it reads well.
  • No independent audit. Checks so far are our own, partly automated. WCAG 2.2 AA remains a target, not a verified result.
  • The lens menu and depth dial are toggle buttons, not composite widgets. They are keyboard-operable with Tab and Enter, but do not support arrow-key navigation. We describe them to assistive technology as what they are rather than promising behaviour they lack.
  • The decorative ring diagram on the home page conveys structure visually. The same information is available as text on the roadmap, but the diagram itself is not an equivalent experience.
  • Zoom and reflow beyond 200% and touch-target sizing have not been systematically verified.

Reporting a barrier

If something here blocks you, please tell us — a specific description of what you were trying to do, and what your browser and assistive technology were, helps most. Accessibility problems are treated as bugs, not enhancement requests.

or email support@codingascreating.com — whichever is easier for you.

Last reviewed: 14 August 2026. Basis: manual keyboard checks, programmatic DOM and ARIA inspection, and calculated contrast ratios against the WCAG 2.x formula.