Accessibility Testing
Use this alongside docs/ACCESSIBILITY_BASELINE.md when changing learner-facing content or interfaces.
Web frontend checks
- Verify Tab / Shift+Tab / Enter / Space flow in
dojo_web.html
- Check contrast in the default theme
- Check small-screen readability
- Confirm mission prompts remain understandable at browser zoom
Terminal checks
- Keep prompts short and plain-language
- Avoid relying on color alone for meaning
- Keep menu choices predictable and easy to re-enter
- Confirm important progress cues still make sense without journal use
Content checks
- define jargon on first use
- use inclusive examples
- keep hints helpful without giving away the answer immediately
Pilot checks
- ask what made learners feel included or excluded
- note where extra facilitator intervention was needed
- turn recurring confusion into documentation or mission updates