Accessibility Statement
Last updated: March 2026
Support software should be usable by everyone. We're building cStar to meet WCAG 2.1 AA standards because accessibility isn't a feature — it's a responsibility.
Our Commitment
- We aim to conform to WCAG 2.1 Level AA across the entire platform.
- We test with keyboard navigation, screen readers, and automated tools.
- We treat accessibility bugs with the same urgency as any other bug.
- We continuously audit and improve — this is an ongoing effort, not a checkbox.
What We've Built
Keyboard Navigation
Every interactive element in cStar is reachable and operable via keyboard. We provide a skip navigation link, focus trapping in modals, and logical tab order throughout the application.
Screen Reader Support
We use semantic HTML, ARIA landmarks, live regions for dynamic content, and descriptive
labels. Form fields have proper label associations, error messages are announced via role="alert", and decorative elements are hidden from assistive technology.
Color & Contrast
All text meets WCAG AA minimum contrast ratios (4.5:1 for normal text, 3:1 for large text) across all four themes (light, dark, retro, and minimal). We use CSS custom properties to ensure consistency and testability.
Focus Management
Modals trap focus within their boundaries and restore focus to the triggering element on close. Focus indicators are visible and meet contrast requirements.
Responsive Design
cStar works across screen sizes and respects user preferences for reduced motion. Content reflows properly at 200% zoom without loss of information or functionality.
Known Limitations
We're actively working on the following areas and welcome feedback on any accessibility issues you encounter:
- Gamification visuals: Some animated game elements (boss battles, XP effects) rely on visual presentation. We're adding text alternatives and ensuring all game mechanics are also conveyed through non-visual means.
- Third-party content: Embedded content from external sources (e.g., customer-uploaded images) may not have alt text. We encourage users to add descriptions where possible.
- Complex data tables: Some analytics and metrics views are being improved for screen reader navigation with proper table headers and summaries.
Standards & Testing
We test accessibility using:
- Automated testing with axe-core and Lighthouse CI
- Manual keyboard-only navigation testing
- Screen reader testing (VoiceOver on macOS)
- ESLint a11y rules enforced in CI pipeline
- Color contrast validation across all themes
Feedback & Contact
If you encounter any accessibility barriers while using cStar, we want to hear about it. Your feedback helps us improve.
Email us at support@cstar.app with "Accessibility" in the subject line. We aim to respond within 2 business days and resolve issues as quickly as possible.
When reporting an issue, it helps to include what page you were on, what you were trying to do, and what assistive technology you're using (if any).
Accessibility is a journey, not a destination. We're committed to making cStar better for everyone, and we take that responsibility seriously. If something isn't working for you, tell us — we'll fix it.