AISparks is built so every child can learn — regardless of ability, disability, or learning difference.
WCAG 2.1 Level AA · Good-faith commitment · Last updated: April 17, 2026
AISparks is committed to ensuring that our platform is accessible to all children and families, including those with disabilities. We work to conform to the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA as our target standard.
This statement reflects our good-faith effort. We recognize that perfect accessibility is an ongoing process, not a one-time achievement. We actively audit our platform, address issues as they are found, and incorporate accessibility feedback from users and families.
If you encounter any barrier that prevents your child from fully using AISparks, please contact us at support@aisparks.us — we will work with you directly to find a solution.
Built-in features designed to support every learner.
Parents can enable extended-time mode for children with IEPs or 504 Plans. When active, timed exercises remove or extend their time limits so every child can work at their own pace.
AISparks is designed to work with native device screen readers (VoiceOver on iOS/macOS, TalkBack on Android, NVDA and JAWS on Windows). All interactive elements have descriptive labels for screen reader compatibility.
Parents can request simplified language for AI-generated explanations and hints, making content more accessible for children with reading challenges, dyslexia, or language processing differences.
Four font size options (Small, Medium, Large, X-Large) are available per child profile, set by the parent. Larger sizes help children with low vision or reading difficulties.
A color-blind friendly palette replaces color-dependent UI elements with shapes, patterns, and text labels, ensuring the interface is usable by children with deuteranopia, protanopia, or tritanopia.
Parents can record IEP and 504 Plan accommodations in their child's profile. AISparks uses this information to adjust content difficulty, pacing, and AI interaction style — all stored encrypted and never shared with teachers via the share link.
Our learning algorithm continuously adapts question difficulty to the child's demonstrated ability. This benefits all learners, and especially those who need gradual scaffolding or a slower progression through topics.
The parent dashboard and all key flows support full keyboard navigation. Focus states are clearly visible. We target WCAG 2.1 Success Criteria 2.1.1 (Keyboard) and 2.4.7 (Focus Visible).
All interactive elements (buttons, inputs, tab items) are sized to at least 44×44 CSS pixels, meeting WCAG 2.1 Success Criterion 2.5.5 (Target Size) for touch device accessibility.
Full dark mode support reduces eye strain for users sensitive to bright screens. The mode respects system preferences automatically and can be toggled manually via the nav bar.
Our current status against key WCAG 2.1 success criteria.
| Criterion | Title | Level | Status | Notes |
|---|---|---|---|---|
| 1.1.1 | Non-text Content | A | ✅ Implemented | All images, icons, and decorative elements have descriptive alt text or aria-hidden. |
| 1.4.3 | Contrast (Minimum) | AA | ✅ Implemented | Text elements meet 4.5:1 contrast ratio in both light and dark modes. |
| 1.4.4 | Resize Text | AA | ✅ Implemented | Font size controls built into per-child profile settings. |
| 1.4.11 | Non-text Contrast | AA | ✅ Implemented | UI components and focus indicators meet 3:1 contrast ratio. |
| 2.1.1 | Keyboard | A | ✅ Implemented | All functionality operable via keyboard. |
| 2.4.7 | Focus Visible | AA | ✅ Implemented | Focus indicators visible on all interactive elements. |
| 2.5.5 | Target Size | AAA | ✅ Implemented | Minimum 44×44px targets throughout the app. |
| 4.1.2 | Name, Role, Value | A | ✅ Implemented | All form inputs, buttons, and controls have accessible names and ARIA roles. |
| 1.4.12 | Text Spacing | AA | 🔄 In Progress | Content reflow with custom letter/word spacing; completion planned Q3 2026. |
| 2.4.6 | Headings and Labels | AA | ✅ Implemented | Consistent heading hierarchy (h1 → h2 → h3) throughout all pages. |
We are transparent about areas where we are still working to improve accessibility:
If your child needs an accommodation not currently available in the platform, or if you encounter an accessibility barrier, please reach out. We are committed to working with families directly to ensure every child can use AISparks effectively.