Accessibility statement

Target

We aim at WCAG 2.2 level AA. This statement describes the current state honestly rather than claiming conformance we have not audited independently.

What is in place

• Content never depends on an animation running. Every reveal on this site is a CSS animation whose resting state is fully visible, so the page reads correctly with animations disabled, scripting disabled, or a crawler that never scrolls.
• Reduced motion is respected. With prefers-reduced-motion: reduce, decorative motion stops, the interactive rig on the home page holds a static frame, and smooth scrolling is switched off.
• The interactive rig is decoration. Everything the canvas draws also exists as real HTML beneath it, reachable with a keyboard and readable by a screen reader. Nothing on this site exists only inside a bitmap.
• Keyboard access. A skip link is the first focusable element, focus is visible everywhere against the dark background, the mobile menu and the cookie dialog close with Escape, and closing the cookie dialog with Escape is treated as a rejection rather than as consent.
• Forms. Every field has a real label, errors are tied to their field with aria-describedby, the first field with an error takes focus on a failed submission, and error text explains what to do rather than only what is wrong.
• Contrast. Body and heading colours on the dark ground are measured against WCAG AA. Buttons use dark ink on bright accents rather than the reverse.
• Layout. No page scrolls horizontally at 320 px and up; wide tables scroll inside their own container instead of moving the page.

Known limitations

• The site has not been audited by an independent accessibility assessor, and no automated tool substitutes for that.
• The rig on the home page can be rotated by pointer or touch but not by keyboard; the same content is fully available through the stage buttons underneath it, which are keyboard operable.
• We have tested with browser zoom and reduced-motion settings, but not with every assistive technology combination in use.

Tell us

If something here is hard to use, write to help@cuizgamedesigndk.com with the page and what happened. We will reply, and we would rather hear about it than not.