We use cookies for analytics and to measure advertising effectiveness. Your data helps us improve VersiClass. See our Privacy Policy for details.

Skip to main content

Accessibility Statement

Last updated: March 7, 2026

Our Commitment

VersiClass is committed to ensuring digital accessibility for people of all abilities. We continually improve the user experience for everyone and apply relevant accessibility standards to make our platform as inclusive as possible.

Conformance Status

VersiClass strives to conform to the Web Content Accessibility Guidelines (WCAG) 2.1, Level A. These guidelines explain how to make web content more accessible to people with disabilities and more user-friendly for everyone.

We are actively working toward Level AA conformance and have implemented several AA criteria across the platform.

Measures We Have Taken

We have taken the following measures to ensure the accessibility of VersiClass:

  • Semantic HTML: Proper use of headings, landmarks (main, nav, header, footer), and semantic elements throughout the application
  • Keyboard navigation: All interactive elements are reachable and operable via keyboard, with visible focus indicators
  • Skip navigation: Skip-to-content links are provided on all pages to allow keyboard users to bypass repetitive navigation
  • Form accessibility: All form fields have associated labels, validation errors are clearly communicated, and required fields are indicated
  • ARIA attributes: Appropriate ARIA roles, labels, and states are used to enhance screen reader support for interactive components including dialogs, menus, and tables
  • Color and contrast: Dark mode is supported across the entire platform, and we use color schemes designed for adequate contrast
  • Decorative images: Decorative images and icons are marked with aria-hidden="true" to prevent screen reader clutter
  • Consistent link text: Links to the same destination use consistent, descriptive text to avoid confusion for assistive technology users

Known Limitations

While we strive for comprehensive accessibility, some areas may have limitations:

  • Some dynamic notifications (toasts) may not be fully announced by all screen readers
  • Third-party integrations (such as Stripe payment forms) follow their own accessibility standards
  • Complex data visualizations in analytics charts may not be fully accessible to screen reader users; underlying data is available in tabular format where possible

We are working to address these limitations and welcome feedback on how we can improve.

Feedback

We welcome your feedback on the accessibility of VersiClass. If you encounter any accessibility barriers or have suggestions for improvement, please contact us:

VersiClass

Email: hello@versiclass.com

We aim to respond to accessibility feedback within 5 business days.