Honest status: Solus is designed and tested against WCAG 2.1 AA aspirationally. A formal independent VPAT (Voluntary Product Accessibility Template) audit is on our roadmap but has not yet been completed. We are transparent about this because institutional customers should know the state of the art rather than take a marketing claim at face value.
What we're doing today
- Semantic HTML across every surface — form labels, headings, landmark regions, native buttons.
- Keyboard navigation across the editor, dashboards, and verifier. Interactive elements are reachable via Tab, activated with Enter/Space, and dismissible with Escape.
- Sufficient color contrast — foreground/background pairs are checked against WCAG AA (4.5:1 for normal text, 3:1 for large text) in the primary flows.
- Focus indicators visible on all interactive elements.
- Responsive layouts from ~320px viewport up.
- Text alternatives for graphical elements where the graphic conveys information.
- No autoplay audio or video, no flashing content.
- Dark mode respected in the web editor.
Known gaps
- Formal VPAT audit not yet completed. Independent third-party audit is on the roadmap for enterprise readiness.
- Screen-reader compatibility with the rich-text editor (TipTap-based) has known limitations shared by most modern web editors. We continue to track upstream improvements.
- The Cloudflare Turnstile challenge used on signup and password recovery is more accessible than image-based CAPTCHAs but is not fully accessible for all assistive-tech users. Users encountering issues can email us for an alternative signup path.
- Complex data tables in the teacher and admin dashboards would benefit from row/column headers and ARIA relationships.
- Automated accessibility test coverage in CI is not yet in place.
How to report a barrier
If you encounter an accessibility barrier while using Solus, please email soluseditor@gmail.com with:
- The URL or page where you encountered the barrier
- The assistive technology you use (screen reader, magnifier, voice control, keyboard only, etc.)
- A description of what happened and what you expected
We aim to acknowledge within 3 business days and, when the barrier can be reasonably remedied, provide a fix or workaround within 10 business days.
Formal accommodation requests
Institutional customers with users requiring specific accommodations (extended time on assignments, alternative submission methods, exemption from behavioral-analytics scoring for individuals with motor-control differences) should contact us. Solus supports policy-level accommodations at the class and per-user level, and we will document how these apply under any executed Data Processing Agreement.