Accessibility Statement
Last updated: August 10, 2025. We are committed to making our platform usable by everyone. This statement outlines our conformance target, known issues, and how to request accommodations.
Conformance Status
Our target and current standing against international standards.
Target Standard
WCAG 2.1 AA
Web Content Accessibility Guidelines 2.1 Level AA
Current Status
Partially Conformant
Most pages meet AA; some third-party embeds and legacy content have known gaps (see below)
What we do well
Areas where we meet or exceed WCAG 2.1 AA.
- Semantic HTML5 landmarks (header, main, footer, nav, section, article)
- Heading hierarchy (h1–h6) with no skipped levels
- Colour contrast ratios ≥ 4.5:1 for text, ≥ 3:1 for UI components
- Focus visible on all interactive elements (custom focus rings)
- Keyboard navigation: all functionality reachable and operable via keyboard
- ARIA labels and roles where native HTML is insufficient
- Alt text for all informative images; decorative images marked with alt=""
- Form labels associated with inputs; error messages linked via aria-describedby
- Skip-to-main-content link as first focusable element
- Responsive text sizing up to 200% without loss of content/function
- Reduced-motion support via prefers-reduced-motion media query
- Language of page and parts identified (lang attributes)
Known Limitations
Areas where we are actively working to improve.
- Third-party embeds: Some video players (YouTube, Vimeo), calendar widgets, and payment iframes may not fully meet AA. We provide accessible alternatives where possible.
- Data visualisations: Interactive charts (Recharts) rely on colour and hover states. We are adding tabular data fallbacks and pattern fills.
- Legacy PDFs: Older curriculum PDFs may lack tagging. Newer documents are created as tagged PDFs.
- Live captions: Live cohort sessions use auto-generated captions (accuracy ~85%). Human-edited captions are provided for recordings within 48 hours.
- Complex drag-and-drop: Some curriculum builder interfaces require mouse. Keyboard alternatives are being added.
Assistive Technology Compatibility
Tested combinations where we verify core flows.
- NVDA 2024.x + Firefox 128+ (Windows)
- JAWS 2024 + Chrome 128+ (Windows)
- VoiceOver + Safari 17+ (macOS/iOS)
- TalkBack + Chrome 128+ (Android)
- Dragon NaturallySpeaking 16 (voice control)
- Keyboard-only navigation (no screen reader)
Testing and Evaluation
How we measure and maintain accessibility.
- Automated: axe-core in CI on every pull request (zero critical/high violations required to merge)
- Manual: quarterly expert audits covering core user journeys (apply, learn, submit, certify)
- User testing: annual sessions with students who use assistive technology
- Regression: smoke tests on every release for focus order, landmarks, contrast
Reporting Issues and Requesting Accommodations
We want to know when something doesn't work for you.
If you encounter an accessibility barrier, need an alternative format, or require a reasonable accommodation, please contact us:
Email: [email protected]
Phone/WhatsApp: +234 905 862 8386
Form: Contact page (select "Accessibility")
We aim to acknowledge reports within 2 business days and provide a remediation timeline within 10 business days.
Ongoing Work (Roadmap)
Planned improvements for the next 12 months.
- Full keyboard equivalents for all drag-and-drop interfaces (Q3 2025)
- Human-edited captions for all live sessions (Q4 2025)
- Tagged PDF regeneration for all legacy curriculum (Q4 2025)
- High-contrast theme toggle (Q1 2026)
- Sign-language interpreter option for live sessions (pilot Q1 2026)
- Accessibility conformance audit by third-party specialist (annual, next Q2 2026)
Legal References
Standards and regulations that inform our approach.
- WCAG 2.1 Level AA (W3C Recommendation)
- Nigeria Discrimination Against Persons with Disabilities (Prohibition) Act, 2018
- EN 301 549 v3.2.1 (European accessibility standard for ICT)
- Section 508 (US Rehabilitation Act) — for international partners
Feedback makes us better.
If something isn't accessible, it's a bug. Please tell us.