VPAT — Accessibility Conformance Report
Last updated: May 4, 2026
Status: Self-assessment under remediation
This report is an internal self-assessment, not a third-party audit. An independent accessibility audit by a qualified firm is scheduled for Q3 2026, after which this report will be re-issued. Several criteria below are marked “Partially Supports” pending in-progress remediation; see Section 6 for the active limitations list and Section 8 for the remediation timeline.
1. Report Information
| Product Name | Ludwitt Adaptive Learning Platform |
| Product Version | Web Application (SaaS) |
| Report Date | March 2026 |
| WCAG Version | WCAG 2.1 Level AA |
| Evaluation Methods | Internal review: automated testing (axe-core in CI), code-level audit of ARIA/keyboard patterns, manual keyboard-only navigation. Independent third-party audit scheduled for Q3 2026. |
| Contact | accessibility@ludwitt.com |
2. Applicable Standards
The following accessibility standards have been evaluated for this product.
| Standard | Included in Report |
|---|---|
| WCAG 2.1 Level A | Yes |
| WCAG 2.1 Level AA | Yes |
| Section 508 | Yes |
3. Conformance Level Definitions
The following terms are used throughout this report to describe the level of conformance.
| Term | Definition |
|---|---|
| Supports | The functionality of the product has at least one method that meets the criterion without known defects or meets with equivalent facilitation. |
| Partially Supports | Some functionality of the product does not meet the criterion. |
| Does Not Support | The majority of product functionality does not meet the criterion. |
| Not Applicable | The criterion is not relevant to the product. |
4. WCAG 2.1 Level A Criteria
Detailed conformance results for all WCAG 2.1 Level A success criteria.
| Criteria | Conformance Level | Remarks |
|---|---|---|
| 1.1.1 Non-text Content | Partially Supports | Most icons and interactive elements have aria-labels. Image alt-text coverage is incomplete on some marketing pages and is being remediated. |
| 1.2.1 Audio-only and Video-only (Prerecorded) | Not Applicable | No prerecorded audio-only or video-only media is used. |
| 1.2.2 Captions (Prerecorded) | Not Applicable | No prerecorded multimedia content is present. Note: live video study rooms are provided via Daily.co; see “1.2.4 Captions (Live)” in Section 6 limitations. |
| 1.2.3 Audio Description or Media Alternative (Prerecorded) | Not Applicable | No prerecorded video content is used. |
| 1.3.1 Info and Relationships | Supports | Semantic HTML is used throughout. Forms use proper labels and fieldsets. Headings follow a logical hierarchy. |
| 1.3.2 Meaningful Sequence | Supports | Content reading order matches the visual presentation order. |
| 1.3.3 Sensory Characteristics | Supports | Instructions do not rely solely on shape, size, visual location, orientation, or sound. |
| 1.4.1 Use of Color | Supports | Color is not used as the sole means of conveying information. All status indicators include text labels. |
| 1.4.2 Audio Control | Not Applicable | No audio plays automatically on any page. |
| 2.1.1 Keyboard | Partially Supports | Primary navigation, forms, and most controls are keyboard-operable. An internal audit identified ~60 clickable container elements (table rows, cards) that lack keyboard activation; these are being converted to native buttons. Target: complete by end of Phase 1 (~week 6). |
| 2.1.2 No Keyboard Trap | Supports | Focus can be moved away from any component using standard keyboard mechanisms. Modals support Escape to close. |
| 2.1.4 Character Key Shortcuts | Not Applicable | No single-character key shortcuts are implemented. |
| 2.2.1 Timing Adjustable | Supports | Session timeouts display a warning and allow users to extend the session before expiration. |
| 2.2.2 Pause, Stop, Hide | Partially Supports | No auto-updating content is present. prefers-reduced-motion support is being added globally; until that ships, animations play regardless of OS-level preference. Target: complete by end of Phase 1 (~week 6). |
| 2.3.1 Three Flashes or Below Threshold | Supports | No content flashes more than three times per second. |
| 2.4.1 Bypass Blocks | Supports | Skip-to-content links are provided to bypass repeated navigation blocks. |
| 2.4.2 Page Titled | Supports | All pages have descriptive, unique titles. |
| 2.4.3 Focus Order | Supports | Focus order follows a logical, meaningful sequence throughout the interface. |
| 2.4.4 Link Purpose (In Context) | Supports | Link text is descriptive and can be determined from the link text alone or its surrounding context. |
| 2.5.1 Pointer Gestures | Supports | No multipoint or path-based gestures are required. All actions use simple clicks or taps. |
| 2.5.2 Pointer Cancellation | Supports | Actions are triggered on the up-event. Users can abort or undo pointer actions. |
| 2.5.3 Label in Name | Supports | Accessible names for UI components contain the visible text labels. |
| 2.5.4 Motion Actuation | Not Applicable | No functionality is triggered by device motion or user motion. |
| 3.1.1 Language of Page | Supports | The default human language is identified with lang=“en” on the HTML element. |
| 3.2.1 On Focus | Supports | No change of context occurs when a component receives focus. |
| 3.2.2 On Input | Supports | Changing the setting of any user interface component does not automatically cause a change of context unless the user has been advised beforehand. |
| 3.3.1 Error Identification | Supports | Input errors are automatically detected and described to the user in text. Error messages are associated with form fields. |
| 3.3.2 Labels or Instructions | Supports | All form inputs have visible labels or instructions. Required fields are clearly indicated. |
| 4.1.1 Parsing | Supports | HTML output is well-formed with no duplicate IDs, proper nesting, and complete start/end tags. |
| 4.1.2 Name, Role, Value | Partially Supports | Most components have programmatic names, roles, and values via native HTML or ARIA. Same exception as 2.1.1: ~60 clickable container elements lack proper button roles; remediation underway. |
5. WCAG 2.1 Level AA Criteria
Detailed conformance results for all WCAG 2.1 Level AA success criteria.
| Criteria | Conformance Level | Remarks |
|---|---|---|
| 1.3.4 Orientation | Supports | Content is not restricted to a single display orientation. All pages function in both portrait and landscape modes. |
| 1.3.5 Identify Input Purpose | Supports | Input fields that collect personal information use appropriate autocomplete attributes. |
| 1.4.3 Contrast (Minimum) | Partially Supports | Primary text (gray-900 on white) meets 4.5:1. Some secondary/utility text combinations (e.g., gray-500 on gray-100) may fall below 4.5:1 and are being audited as part of the Q3 2026 third-party review. |
| 1.4.4 Resize Text | Supports | Text can be resized up to 200% without loss of content or functionality. |
| 1.4.5 Images of Text | Supports | No images of text are used. All text is rendered as real text using web fonts. |
| 1.4.10 Reflow | Supports | Content reflows at 320px viewport width without horizontal scrolling. Responsive design is implemented throughout. |
| 1.4.11 Non-text Contrast | Supports | All UI components and graphical objects meet the 3:1 contrast ratio requirement. |
| 1.4.12 Text Spacing | Supports | No loss of content or functionality occurs when text spacing is adjusted per the criterion requirements. |
| 1.4.13 Content on Hover or Focus | Supports | Hover and focus-triggered content is dismissible, hoverable, and persistent until dismissed by the user. |
| 2.4.5 Multiple Ways | Supports | Multiple navigation mechanisms are available: primary navigation, breadcrumbs, dashboard links, and direct URL access. |
| 2.4.6 Headings and Labels | Supports | Headings and labels describe the topic or purpose of the content they introduce. |
| 2.4.7 Focus Visible | Supports | A visible focus indicator is provided for all interactive elements using focus:ring styles via Tailwind CSS. |
| 3.1.2 Language of Parts | Supports | Content in Latin uses lang=“la” and content in Ancient Greek uses lang=“grc” to identify language changes. |
| 3.2.3 Consistent Navigation | Supports | Navigation mechanisms are consistent across all pages within the application. |
| 3.2.4 Consistent Identification | Supports | Components with the same functionality are identified consistently throughout the platform. |
| 3.3.3 Error Suggestion | Supports | When input errors are detected, suggestions for correction are provided in text. |
| 3.3.4 Error Prevention (Legal, Financial, Data) | Supports | Submissions that involve financial transactions or data deletion are reversible, verified, or confirmed before processing. |
| 4.1.3 Status Messages | Supports | Status messages (success notifications, error alerts, progress updates) use aria-live regions to announce changes to screen readers without receiving focus. |
6. Known Limitations
The following areas have known accessibility limitations that are being actively addressed. Each item lists the affected criterion, current status, and remediation target.
Clickable container elements (affects 2.1.1, 4.1.2)
Approximately 60 interactive container elements (table rows, dashboard cards) are implemented as clickable div elements rather than native buttons, meaning they cannot be reliably activated by keyboard or announced as buttons by screen readers. Migration to native button semantics is in progress and targeted for completion in Phase 1 (~week 6).
Reduced-motion preference (affects 2.2.2)
The platform's CSS does not yet honor the prefers-reduced-motionmedia query. Users with motion sensitivities cannot disable animations via OS settings. A global guard is being added in Phase 1 (~week 6).
Live captions for video study rooms (affects 1.2.4)
Live video study rooms are provided through Daily.co. Live captioning availability is being verified with the vendor; if not natively available, an integration with a real-time captioning service will be added before broad K-12 deployment.
Internationalization (affects 3.1.2)
The interface is currently English-only. Spanish localization is planned for Phase 2 (~week 10), with full-platform coverage including student, parent, teacher, and admin surfaces. This is a significant gap for English Language Learner populations.
Third-Party Components
Embedded third-party components — including video players (Daily.co) and payment forms (Stripe Elements) — may have limited accessibility that is outside Ludwitt's direct control. We work with these vendors to advocate for accessibility improvements and select alternatives when accessibility gaps are significant.
AI-Generated Content
AI-generated explanations and feedback may occasionally produce content that does not fully meet readability or structural accessibility standards. All AI output is wrapped in appropriate semantic HTML containers, and we continue to refine prompt engineering to improve output quality.
Mathematical Content (KaTeX)
KaTeX-rendered mathematical expressions have limited screen reader support. While MathML fallbacks are provided where possible, complex mathematical notation may not be fully accessible to all assistive technology users. We are evaluating MathJax as an alternative for improved screen reader compatibility.
7. Testing Methodology
Ludwitt employs a multi-layered approach to accessibility testing:
Automated Testing
- axe-core accessibility engine integrated into CI/CD pipeline via Playwright
- Automated checks run on every pull request and deployment
- Coverage includes all pages and interactive components
Manual Review
- Code-level audit of ARIA usage, focus management, and keyboard event handlers
- Spot-check keyboard-only navigation of primary user workflows
- Spot-check screen reader behavior with VoiceOver (macOS) on key flows
Audit Schedule
- Internal accessibility self-assessments performed in connection with major releases
- Independent third-party accessibility audit scheduled for Q3 2026; this report will be re-issued based on the firm's findings
- Continuous monitoring and remediation of reported issues
8. Remediation
Ludwitt is committed to continual improvement of platform accessibility. If you encounter any accessibility barriers, please refer to our Accessibility Statement for information on how to report issues and our remediation process. All reported accessibility issues are triaged within 5 business days and prioritized in our development backlog.
9. Overall Conformance
Based on the self-assessment documented in this report, the Ludwitt Adaptive Learning Platform partially conforms to WCAG 2.1 Level AA. “Partially conforms” means that some parts of the content do not fully conform to the accessibility standard.
The specific gaps are listed in Section 6 (Known Limitations) with active remediation timelines. An independent third-party audit is scheduled for Q3 2026, after which this report will be re-issued. Ludwitt is committed to reaching full Level AA conformance through the remediation work described above.
This VPAT was prepared in accordance with the ITI VPAT 2.5 template. For accessibility inquiries, contact accessibility@ludwitt.com.