Skip to main content
← Back to Home

Accessibility Statement

Last updated: May 4, 2026

Our Commitment

Ludwitt is committed to digital accessibility for people with disabilities. This statement reflects the platform's current state — not a finished product. We publish known limitations and remediation timelines so institutional reviewers can evaluate fit honestly.

Conformance Status

Target: Web Content Accessibility Guidelines (WCAG) 2.1 Level AA.

Current state: Partially conformant. The platform meets many WCAG 2.1 AA criteria but has known gaps documented below. A third-party accessibility audit is scheduled for Q3 2026; the resulting VPAT will replace any prior self-assessment.

What's in place today

  • Skip-navigation links on top-level pages
  • Semantic HTML landmarks (header, nav, main, footer) on most pages
  • Form inputs associated with labels and error descriptions
  • Sufficient color contrast in the primary "Kinematic Minimalism" theme (4.5:1+ for normal text)
  • Focus management in primary modals and dialogs
  • ARIA live regions for in-app notifications
  • Text alternatives for icon-only controls in primary navigation

Known limitations

Areas where conformance is incomplete. We document these openly so institutional reviewers can assess procurement fit and prioritize remediation:

  • Clickable non-button elements: Some interactive surfaces are stilldivelements with click handlers rather than semanticbuttonelements. Affects keyboard activation and screen-reader announcement on those surfaces. Migration in progress.
  • Reduced-motion preference: A platform-wideprefers-reduced-motionguard is being added; some animation-heavy components do not yet honor the user's OS-level preference.
  • Math notation rendering: Math is rendered with KaTeX. Most expressions include MathML for screen-reader access, but legacy problem sets may lack alternative descriptions for purely visual diagrams.
  • AI-generated explanations: Content produced by AI grading and tutoring may include plain-text math notation that screen readers verbalize less cleanly than authored content.
  • Third-party embeds: Stripe Checkout, Daily.co video rooms, and other vendor surfaces are subject to those vendors' accessibility postures, which we do not control.
  • Mobile screen-reader gaps: Coverage is strongest on desktop. We are tracking mobile-specific issues separately.

Remediation timeline

  • Q2 2026: Migrate clickable divs to semantic buttons; add theprefers-reduced-motionguard at the global stylesheet level; expand authenticated-routeaxe-coretest coverage.
  • Q3 2026: Engage a third-party accessibility firm for an independent audit; publish the resulting VPAT and remediate any new findings on a pre-disclosed schedule.
  • Ongoing: Treat axe-core E2E violations as build-blocking on the primary user journeys (basics math, basics reading, dashboard, institution admin).

Compatibility

We test against the following assistive technologies on the platform's primary user journeys:

  • VoiceOver on macOS/iOS (Safari)
  • NVDA on Windows (Firefox, Chrome)
  • Keyboard-only navigation across all browsers

JAWS (Windows) and TalkBack (Android) are not part of our regular test matrix yet but are planned additions during the Q3 2026 audit.

Technical specifications

The platform relies on HTML, WAI-ARIA, CSS, and JavaScript (with progressive enhancement where feasible). Server-side rendering is used on most non-interactive routes so basic content is reachable without JavaScript.

Standards we work toward

Ludwitt aims to support institutions in meeting their obligations under Section 508 of the Rehabilitation Act, the Americans with Disabilities Act (ADA), and applicable state accessibility mandates. We do not claim certification under these statutes; the responsibility for institutional compliance rests with the deploying organization, and we provide the underlying platform behavior they need to assess.

Feedback

If you encounter an accessibility barrier or have suggestions, please contact us:

We aim to acknowledge accessibility reports within 5 business days and to share a remediation plan or timeline within 15 business days.

This statement is reviewed quarterly and after every third-party audit.