§ LEGALAccessibility
Accessibility statement
Effective·2026-06-12CodeTitan aims to be usable by everyone. We target WCAG 2.1 Level AA as the baseline. No formal third-party accessibility audit has been performed yet — what follows is what we build for and where the gaps are.
What we build for
- Keyboard navigation across interactive elements
- Colour contrast (4.5:1 for text, 3:1 for UI elements) in the design tokens
- Respect for
prefers-reduced-motion— non-essential animation stops - Focus-visible indicators on focusable elements
- Alt text on non-decorative images; decorative elements marked
aria-hidden
Known gaps
- No automated accessibility checks (e.g. axe-core) run in CI yet — adding them is on the roadmap.
- Screen-reader checks so far are informal; a systematic pass with NVDA and VoiceOver has not been done.
- Decorative animations (such as the ASCII render on the landing page) honour
prefers-reduced-motionand are markedaria-hidden, but the site is animation-heavy and we treat that as an ongoing risk to verify.
Reporting an issue
Found something that doesn't work for you? Email accessibility@codetitan.dev. Every report gets read; pre-launch, there is no response-time guarantee, but accessibility reports go to the top of the queue.
Continuous improvement
Accessibility is not a checkbox — it's ongoing. Automated checks in CI and a systematic screen-reader pass are the next two steps on the roadmap.
Questions?·legal@codetitan.dev