Accessibility Statement

Modified on Thu, 16 Apr at 1:35 PM

Commitment

At Learnvia, we believe that education should be accessible to all learners, regardless of their abilities or circumstances. We are dedicated to fostering a digital learning environment that is usable, equitable, and inclusive. This commitment informs every stage of our product design and development process. We aim to remove barriers that may impede learning and to ensure that all users can fully engage with our content and tools.


Standards Applied

Learnvia measures accessibility conformance against the Web Content Accessibility Guidelines (WCAG) 2.1 at Level A and Level AA. These guidelines, developed by the World Wide Web Consortium (W3C), outline best practices for making web content more accessible to a wider range of people with disabilities, including users with blindness and low vision, limited mobility, hearing loss, cognitive limitations, and others.


Conformance Status

A thorough internal evaluation has determined that the Learnvia platform is in a state of partial conformance with WCAG 2.1 Level A and AA. This means that while most essential features and functions are accessible using assistive technologies—such as screen readers, screen magnifiers, and keyboard-only input—there are still some areas that do not yet fully meet accessibility criteria. These gaps are documented in our Accessibility Conformance Report (VPAT) and are actively being addressed.


Known Limitations

The following accessibility issues are known and documented:

  • Non-text alternatives: A number of decorative and functional images do not yet include descriptive alt attributes or meaningful labels.

  • Keyboard operation: Certain interactive features, such as drag-and-drop modules and complex scrolling areas, are not consistently operable via keyboard alone.

  • Color contrast: Some text and interface elements do not meet minimum contrast requirements, which may hinder readability for users with low vision or color blindness.

  • Focus visibility: Visual indicators of focus are occasionally missing or poorly defined, which can disrupt navigation for users relying on keyboard traversal.

  • Status messages: Live region updates and dynamic content—such as real-time tutor responses—are not reliably announced by screen readers, which may cause confusion or missed context.



Assessment Method

Accessibility was evaluated using a hybrid approach. Automated scans were conducted using the aXe-core accessibility engine to identify baseline issues. In addition, a manual audit was performed using native screen readers (VoiceOver on macOS), keyboard-only navigation, and browser developer tools. This approach ensures that both machine-detectable and experiential barriers are identified.


Planned Improvements

We have developed a remediation roadmap to address the outstanding conformance issues. Fixes are being implemented in a phased manner, focusing first on high-impact barriers that affect core learning functionality. In parallel, our engineering and design teams are undergoing accessibility training to embed inclusive design principles into future releases. Updated accessibility conformance documentation will be published regularly to reflect ongoing improvements.


Feedback Channel

We welcome feedback from all users. If you encounter an accessibility barrier while using Learnvia, please reach out to us:


Email: support@learnvia.freshdesk.com


Your input is vital to helping us build a more accessible learning experience for everyone.


Requesting a VPAT

For institutions, procurement officers, or accessibility reviewers who require a copy of our latest Accessibility Conformance Report (VPAT), please contact us at:


Email: support@learnvia.freshdesk.com


We are happy to provide the most recent version of the report and answer any questions related to our product’s accessibility features or compliance status.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article