Skip to main content

Accessibility Statement

Last updated: March 4, 2026

1. Our Commitment

Interakly is committed to ensuring that our interactive video platform is accessible to all users, including people with disabilities. We strive to conform to the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA, and to meet the requirements of:

  • Section 508 of the Rehabilitation Act (U.S.)
  • Americans with Disabilities Act (ADA) (U.S.)
  • EN 301 549 (European accessibility standard for ICT)

We view accessibility as an ongoing effort, not a one-time achievement. We continuously evaluate and improve the accessibility of our platform as we develop new features.

2. Accessibility Features

Video Player

  • Closed captions support (VTT format) for all uploaded videos, with configurable caption display
  • Keyboard-accessible playback controls (play/pause, seek, volume, fullscreen)
  • Screen reader announcements for player state changes
  • Visible focus indicators on all interactive controls

Interactive Overlays

  • Full keyboard navigation for multiple choice, true/false, poll, rating scale, numeric input, and fill-in-the-blank interactions
  • Focus management — focus is moved to the interaction overlay when it appears and returned to the video when it is dismissed
  • Sufficient color contrast ratios for text and interactive elements (minimum 4.5:1 for normal text, 3:1 for large text)
  • ARIA labels and roles on interactive elements for screen reader compatibility
  • Screen reader announcements for score feedback and interaction results

Editor

  • Properly labeled form controls for all interaction configuration fields
  • Logical heading hierarchy throughout the editor interface
  • Keyboard-accessible timeline and interaction management

Dashboard and Analytics

  • Data tables with proper header associations for screen readers
  • Keyboard-navigable video cards, lists, and collection sidebar
  • Focus-visible outlines on all interactive elements

Workspace

  • Code editor (CodeMirror 6) with built-in accessibility support including screen reader mode, keyboard navigation, and ARIA announcements
  • Notes, worksheet, and flashcard widgets with full keyboard support
  • Equation editor with keyboard input for LaTeX expressions

General

  • Responsive design that supports zoom up to 200% without loss of content or functionality
  • No content that flashes more than 3 times per second
  • Semantic HTML throughout the application (headings, lists, landmarks, buttons vs. links)
  • Skip-to-content navigation links on page load

3. Known Limitations

We are aware of the following accessibility limitations and are actively working to address them:

  • Hotspot interactions: clicking on image regions is inherently visual. We are exploring alternative input methods (tabbed regions, text descriptions) for keyboard and screen reader users
  • Whiteboard / drawing widget: the freeform canvas drawing widget is not accessible to keyboard-only or screen reader users. We recommend providing alternative submission methods when this widget is used in educational contexts
  • Drawing submit interaction: similar to the whiteboard, annotation and drawing submissions require pointer input
  • Map widget (Leaflet): while Leaflet provides basic keyboard navigation, interactive map features such as marker placement have limited screen reader support
  • Graph widget: function graphing visualizations are currently not accessible to screen reader users. The function input itself is keyboard-accessible
  • Drag-and-drop ordering: the ordering interaction type uses drag-and-drop which has limited keyboard support. We are implementing keyboard-based reordering as an alternative
  • Live streaming controls: some live streaming setup controls (camera preview, WHIP connection status) have limited screen reader feedback

4. VPAT / Accessibility Conformance Report

We are currently developing a Voluntary Product Accessibility Template (VPAT) based on the ITI VPAT 2.5 format, which will document our conformance against WCAG 2.1 AA, Section 508, and EN 301 549 criteria.

Educational institutions and procurement teams may request our current accessibility documentation by contacting accessibility@interakly.com.

5. Testing and Evaluation

We evaluate our platform using a combination of automated tools and manual testing:

  • Automated testing: axe-core, Lighthouse accessibility audits, and ESLint jsx-a11y plugin
  • Manual testing: keyboard-only navigation, high-contrast mode, and zoom/magnification testing
  • Screen readers: VoiceOver (macOS/iOS), NVDA (Windows), and JAWS (Windows)

Accessibility testing is integrated into our development process and performed before significant feature releases.

6. Browser and Assistive Technology Compatibility

The Service is designed to be compatible with:

  • Browsers: latest versions of Chrome, Firefox, Safari, and Edge
  • Screen readers: VoiceOver (macOS/iOS), NVDA (Windows), JAWS (Windows), TalkBack (Android)
  • Input methods: mouse, keyboard, touch, and voice control (where supported by the operating system)
  • Display: standard and high-contrast modes, zoom up to 200%, reduced motion preferences (respects prefers-reduced-motion)

7. Feedback and Reporting Issues

We welcome feedback on the accessibility of the Service. If you encounter an accessibility barrier or have suggestions for improvement, please contact us:

When reporting an accessibility issue, please include:

  • A description of the issue and the page or feature where it occurs
  • The browser and assistive technology you are using
  • Steps to reproduce the issue, if possible

We aim to respond to accessibility inquiries within 5 business days and to resolve reported issues on a priority basis.

8. Enforcement and Complaint Procedures

If you are not satisfied with our response to an accessibility concern, you may pursue the following:

  • United States: file a complaint with the U.S. Department of Education Office for Civil Rights (OCR) or the U.S. Department of Justice, Civil Rights Division
  • European Union: contact your national enforcement body under the Web Accessibility Directive (Directive (EU) 2016/2102)
  • United Kingdom: contact the Equality and Human Rights Commission (EHRC) or the Equality Advisory and Support Service (EASS)