Accessibility Commitment
Every participant deserves full access to the interactive experiences your facilitators build. We are committed to meeting WCAG 2.1 Level AA standards across the Kontaim platform and all AI-generated content.
Note: Kontaim is an early-stage platform actively working toward comprehensive accessibility compliance. This document transparently outlines what we do today, where we acknowledge gaps, and our roadmap for improvement.
What We Do Today
Color Contrast Standards
Our shared GameUI component library enforces minimum 4.5:1 contrast ratios for all text. The AI agent is trained to verify contrast on every generated element, including custom-colored containers and dynamic themes.
Keyboard Navigation
All interactive elements — buttons, modals, settings menus, and mobile controls (DPad) — are fully tab-navigable with visible focus indicators. Modals (StartScreen, CompletionScreen, GameNotification, Overlay) support Escape to dismiss. Settings menus close on Escape, and audio/restart/exit buttons have aria-labels.
Semantic HTML Enforcement
Our AI prompt engineering mandates semantic elements — <button> for actions, heading hierarchy for structure, <label> for inputs. The agent is explicitly prohibited from using <div onClick> anti-patterns. All shared components use proper ARIA roles (dialog, alertdialog, progressbar, timer, status).
Non-Color Indicators
Correct/incorrect feedback always pairs color with icons and text (✅/🔄). Information is never conveyed through color alone, ensuring usability for colorblind users.
Screen Reader Support
Score badges announce changes via aria-live regions. Timers announce urgently when time is low. Toasts and notifications are announced via role=status. A dedicated ScreenReaderAnnouncer component is available for game-state announcements. Decorative icons use aria-hidden.
Motion Preferences
A usePrefersReducedMotion hook is exported from GameUI, allowing all activities to detect and respect the user's reduced-motion preference. The AI agent is trained to wrap non-essential animations with this hook.
Multilingual Support
All UI chrome auto-translates to 20+ languages. Game content supports runtime translation via the ArgraideBridge, ensuring linguistic accessibility for diverse populations.
Touch Target Sizing
Interactive elements maintain a minimum 44×44px touch target with adequate spacing, meeting WCAG 2.5.5 guidelines. Mobile controls (joysticks, D-pads) use 48px+ targets for comfortable use.
AI-Generated Experience Standards
Since experiences on Kontaim are generated by AI, we enforce accessibility at two levels:
1. Shared Component Library (GameUI)
All generated activities use our shared GameUI component library, which includes built-in ARIA attributes, keyboard handlers, focus management, and semantic HTML. By fixing accessibility at the component level, improvements propagate automatically to every activity — past and future.
2. AI Prompt Engineering
Our AI agent's system prompt includes a mandatory WCAG 2.1 AA accessibility module. This instructs the agent to use semantic HTML, ensure keyboard operability, provide alt text for images, include aria-live regions for dynamic updates, and verify contrast ratios — with a pre-submit checklist that the agent must complete before outputting code.
Known Limitations & Roadmap
We believe transparency about gaps is as important as celebrating what works. Below are areas we are actively working to improve.
| Area | Current State | Planned Improvement | Timeline |
|---|---|---|---|
| Screen Reader Testing | ARIA attributes included in components; not yet audited with NVDA/JAWS/VoiceOver. | Formal screen reader audit and remediation pass across all GameUI components. | Q3 2026 |
| Drag-and-Drop | Touch and mouse input fully supported. Keyboard-only alternative exists but is limited. | Full keyboard-driven drag-and-drop with Space to grab, arrows to navigate, Enter to drop. | Q3 2026 |
| Motion Preferences | usePrefersReducedMotion hook exported from GameUI. AI agent trained to use it. Not yet applied to built-in component animations. | Apply reduced-motion check to all built-in Framer Motion animations in GameUI components. | Q2 2026 |
| Focus Trapping | Modals can be dismissed via keyboard; focus is not yet trapped within modal boundaries. | Implement focus-trap-react for all overlay components (StartScreen, CompletionScreen). | Q2 2026 |
| Automated Testing | Manual accessibility review. No automated a11y CI pipeline yet. | Integrate axe-core into the build pipeline for automated WCAG violation detection. | Q4 2026 |
WCAG 2.1 Level AA — Self-Assessment
| Principle | Guideline | Status |
|---|---|---|
| Perceivable | 1.1 Text Alternatives | 🔧AI-enforced alt text; teacher uploads need manual alt |
| Perceivable | 1.3 Adaptable | ✅Semantic HTML enforced via prompts and GameUI |
| Perceivable | 1.4 Distinguishable | ✅4.5:1 contrast enforced; non-color indicators required |
| Operable | 2.1 Keyboard Accessible | ✅All shared components: buttons, modals, menus, DPad, and controls are keyboard-operable with focus rings |
| Operable | 2.3 Seizures | ✅No flashing content; animations are subtle and smooth |
| Operable | 2.4 Navigable | 🔧Logical tab order; focus trapping in modals: planned |
| Understandable | 3.1 Readable | ✅20+ language support; growth-mindset feedback tone |
| Robust | 4.1 Compatible | ✅ARIA roles on 15+ components; valid semantic HTML enforced |
Report an Accessibility Issue
If you encounter an accessibility barrier on the Argraide platform or in any generated activity, we want to hear about it. Our team is committed to addressing reported issues promptly.
Contact Accessibility Team