Skip to main content
Accessibilitynot lawyer-reviewedLast updated: 2026-09-06

Keyboard-first,
not screenshot-first.

CodeParty treats accessibility as a first-class requirement. This site is built with the checklist below in mind and is intended to meet WCAG 2.2 AA for its content.

§ 01

What this site commits to

  • Text and interactive contrast at or above WCAG 2.2 AA on the site's dark theme.
  • All interactive elements reachable and operable by keyboard. Visible :focus-visible ring on every focusable element.
  • A skip-to-main-content link at the top of every page.
  • Semantic landmarks (header, nav, main, footer) and one h1 per page.
  • Motion respects prefers-reduced-motion. Reveal, decrypt, and pulse effects are neutralised for anyone who opts out.
  • Descriptive alt text on decorative graphics uses aria-hidden; meaningful graphics carry alternative text.
  • Colour is never the sole carrier of meaning; icons and text always accompany a status colour.
  • Fonts are self-hosted on this origin (no remote font load, no font CDN), so text renders even under aggressive privacy conditions. Every face declares font-display: swap, so copy is readable before the webfont arrives.
  • Forms will be keyboard-friendly and labelled — although the app ships with no forms on the marketing site.
§ 02

What the desktop app commits to

The app reuses the assistant-first workspace's warm-neutral surfaces and keyboard-first layout. Monaco carries its own accessibility features; teammate spectator mode is read-only and cannot steal focus.

The desktop app has not had a full manual accessibility audit of every window. If something gets in your way, please tell us.

§ 03

Reporting a barrier

Report accessibility issues to codepartysupport@gmail.com. A response-time target has not been set.

Note

This statement describes the current state. It is not a claim of legal compliance in any specific jurisdiction.