The prototype should be usable without guesswork.

What we support

Current commitments

• Keyboard access, visible focus, labeled forms, and meaningful page landmarks.
• Reduced-motion and increased-contrast preferences on public pages.
• Plain-language test instructions and text alternatives for meaningful images.
• No accessibility claim based only on automated testing. Manual tester feedback remains required.

Honest limitations

Known gaps

• The Windows game prototype is keyboard-and-mouse first and has not completed controller or screen-reader testing.
• Combat, camera motion, visual effects, subtitles, remapping, and color-independent cues still need blind external validation.
• The launcher and game do not yet expose a complete text API for every action.
• Experimental builds can regress. Accessibility blockers are treated as release blockers for the affected test cohort.

Report a barrier

Tell us what stopped you.

Use the playtest request form and put accessibility in the testing-focus field, or reply through the invitation channel for an active test. Include the page or build, the action you attempted, your input or assistive technology, and the result you expected.

We will acknowledge reports for active test cohorts within two business days and prioritize any barrier that prevents access, account use, download, combat, death recovery, or feedback submission.