Accessibility

Standards and regulatory framework

Koji for Education targets conformance with the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA. This aligns with EN 301 549 v3.2.1, the harmonised European standard for ICT accessibility, as required by the EU Web Accessibility Directive (2016/2102) and the European Accessibility Act (effective June 28, 2025).

Dutch public institutions, including universities, are required to meet these standards under the Tijdelijk besluit digitale toegankelijkheid overheid. Koji for Education is designed with these obligations in mind, so that institutions can adopt the platform without introducing accessibility gaps in their digital learning environment.

Current conformance status

Accessibility conformance is in progress. Koji has not yet completed a formal third-party WCAG audit. A comprehensive audit against WCAG 2.1 Level AA is planned for Q3 2026.

Current measures in place include:

• Semantic HTML throughout the application
• Full keyboard navigability for all core workflows
• Sufficient colour contrast ratios meeting WCAG AA thresholds
• Screen reader compatibility testing with VoiceOver and NVDA
• ARIA labels and roles applied throughout the interface
• Focus management and visible focus indicators
• Resizable text without loss of content or functionality

These measures reflect our current best efforts. We acknowledge that until a formal audit is completed, there may be conformance gaps we have not yet identified.

Conversation interface

The AI conversation interface, which is the primary student-facing component, is accessible via keyboard and screen reader. Text-based participation is the primary interaction mode. Students can complete their entire evaluation through text input alone.

Voice input is available as an optional input method but is never required. No workflow in Koji for Education depends on voice input as the sole means of participation.

Alternative participation methods

For students who cannot use the web interface due to disability, assistive technology incompatibility, or other access barriers, the university can provide alternative evaluation methods. Koji supports data import for evaluations collected through other channels, allowing institutions to include responses gathered via alternative means in their analysis.

We encourage institutions to establish alternative participation procedures as part of their accessibility policies. Our team can advise on integration approaches for common alternative evaluation workflows.

Voice interface accessibility

Voice input and output are designed to support students with visual impairments or motor disabilities that make typing difficult. The voice interface provides an additional channel of interaction alongside the text-based interface.

Transcripts of voice conversations are generated automatically and are available to both students and educators. This ensures that all interactions, regardless of input method, produce a text-based record that can be reviewed, searched, and processed by assistive technologies.

Captions for voice output are planned for a future release. This is a recognised gap, and development is on our roadmap.

Reporting and dashboards

Reports and dashboards are built with semantic HTML, including data tables with proper header associations and sufficient colour contrast. Charts and data visualisations include text alternatives so that the underlying data is accessible to screen reader users.

PDF exports follow PDF/UA accessibility standards where possible, including tagged content, reading order, and alternative text for non-text elements. We recognise that full PDF/UA conformance is not yet achieved across all export types; improvements are in progress (see roadmap below).

Known limitations

We are transparent about areas where accessibility work is ongoing. The following are known gaps that we are actively working to address:

• Complex data visualisations: Some interactive charts and multi-dimensional visualisations may not be fully accessible to screen reader users. We are working on enhanced text alternatives and data table fallbacks.
• PDF export accessibility: Not all PDF exports currently meet PDF/UA standards. Tagged PDF support is being expanded across report types.
• Mobile voice interface with screen readers: The combination of voice input and screen reader software on mobile devices has not been fully tested. There may be interaction conflicts that we have not yet resolved.
• Third-party embedded content: Some third-party components used in the platform may not meet the same accessibility standards we apply to our own code. We are working with vendors to address these gaps.
• Voice output captions: Live captions for AI-generated voice responses are not yet available. Transcripts are available as an alternative.

Accessibility statement

Koji publishes an accessibility statement on the platform that is kept up to date as conformance status evolves. The statement includes:

• Current conformance status and the standards being targeted
• Known limitations and the timeline for addressing them
• A feedback mechanism for reporting accessibility barriers
• Contact information for accessibility issues

This statement is reviewed and updated at least quarterly, and whenever significant accessibility improvements are deployed.

Feedback and reporting

Users can report accessibility barriers via accessibility@koji.so. We welcome reports from students, educators, administrators, and accessibility specialists.

We commit to the following response timelines:

• Acknowledgement: Within 5 business days of receiving a report
• Remediation timeline: Provided within 15 business days, including a description of planned changes and expected delivery dates

For barriers that prevent a student from completing an evaluation, we will work with the institution to provide an interim accommodation while a permanent fix is developed.

VPAT (Voluntary Product Accessibility Template)

A Voluntary Product Accessibility Template (VPAT) based on EN 301 549 is in development. The VPAT documents conformance status for each relevant accessibility criterion and is a standard procurement document for institutions evaluating software accessibility.

The VPAT is expected to be available on request by Q3 2026, following completion of the formal WCAG audit. To request a copy or to be notified when it is available, contact accessibility@koji.so.

Accessibility roadmap

The following milestones reflect our planned accessibility work. Dates are targets and may be adjusted based on audit findings and development priorities.

• Q3 2026: Formal WCAG 2.1 Level AA audit by an independent third party
• Q3 2026: VPAT (EN 301 549) completion and availability on request
• Q4 2026: PDF/UA export improvements across all report types
• 2027: WCAG 2.2 gap analysis and remediation planning

We will update this page as milestones are completed. For questions about our accessibility roadmap or to discuss your institution's accessibility requirements, contact accessibility@koji.so.