Accessibility

Our commitment

DraftRPG is built to be usable by people with a wide range of abilities. We target WCAG 2.1 AA as our baseline standard and treat accessibility as an ongoing practice — not a one-time audit.

The product is alpha-stage. Some surfaces are more polished than others, and we appreciate reports about anything that doesn't work the way you expect.

What works today

• Semantic HTML structure with proper heading hierarchy (h1 → h2 → h3).
• Keyboard navigation for all standard interactions — forms, buttons, links. We don't trap focus or hide focus indicators.
• Color contrast ratios target WCAG AA (4.5:1 for body text, 3:1 for large text and UI components). Our primary palette uses gold on a dark canvas, which clears AAA for the common cases.
• ARIA roles and live regions on interactive components (consent banner, form-status indicators, error messages).
• Dark-mode-only design. No light-mode flash on load.
• Reduced-motion friendly — we use short, simple transitions and avoid parallax or unnecessary autoplay animations.

Known limitations

• Boss-fight combat scene (rendered via PixiJS / canvas) is harder to make screen-reader-friendly than HTML. We'll ship a parallel text-summary view before the canvas surface ships to real users.
• Emoji-based class glyphs read out by screen readers using emoji descriptions (e.g., the Mage glyph reads as “crystal ball”). We pair these with text labels everywhere they appear, but the doubling can be noisy.
• Complex stat tables on the players index page use sortable column headers; sort state is announced but the data set itself is dense.

How to report an issue

Email accessibility@draftrpg.com with:

• The page URL where you ran into the issue.
• What you were trying to do, and what happened instead.
• What assistive technology you're using (screen reader + browser + OS, voice control, keyboard-only, etc.).
• Whether the issue blocks a critical task or is a quality-of-life problem.

We aim to acknowledge reports within 5 business days.

Standards we reference

• WCAG 2.1 (Web Content Accessibility Guidelines)
• Section 508 (U.S. federal accessibility law)
• ADA Title III as interpreted by recent web-accessibility caselaw.