Accessibility Statement
Connect2Code aims to provide a usable keyboard, screen-reader, zoom, contrast, and reduced-motion experience across learning and account features.
Last reviewed 17 November 2026
Measures in the current interface
- Semantic headings, landmarks, labels, status regions, and keyboard-accessible controls are used across shared components.
- Shared dialogs manage focus and Escape dismissal; custom selects support keyboard navigation.
- Light and dark themes use project design tokens, and motion is reduced when the operating system requests it.
- The coding editor enables Monaco accessibility auto-detection, while splitters and major workspace views include keyboard alternatives.
- Responsive layouts support mobile widths and browser zoom without requiring a separate mobile site.
Known limitations
- The codebase has not been independently certified against WCAG 2.2 AA.
- Some legacy icon usage and complex coding, chart, and assessment interfaces may require further assistive-technology testing.
- Assessment-integrity controls restrict selection, clipboard, printing, and some shortcuts on protected learner routes; the admin interface is excluded. These controls may affect some assistive workflows and require product/legal review.
- Third-party pages and services have their own accessibility practices.
Accessibility feedback
A verified accessibility-support contact is not configured in this repository. The owner must publish one before launch. When reporting a barrier, include the page, the task you were trying to complete, browser/device, and assistive technology, but do not include passwords, tokens, or unnecessary personal data.
Target and review
The recommended production target is WCAG 2.2 Level AA, supplemented by applicable Indian accessibility requirements. Conformance must be established through automated checks and manual keyboard, screen-reader, zoom, contrast, and mobile testing—not by this statement alone.
