At Cadmus, we strive to conform to WCAG 2.0 AA standards of the World Wide Web Consortium (W3C). Delivering a great User Experience is core to everything we do. It’s a fundamental principle that underpins how we approach design, development and support. We are working hard to deliver a great user experience for all our users, regardless of disability or circumstance.
We are very close to achieving our accessibility goals, however, due to the agile nature with which we had previously developed the product — we currently fall short of full WCAG 2.0 compliance. The two areas where functionality needs to be extended are:
“All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes, except where the underlying function requires input that depends on the path of the user’s movement and not just the endpoints.”
— W3C (World Wide Web Consortium): WCAG 2.1: Keyboard Accessible
“For all user interface components (including but not limited to: form elements, links and components generated by scripts), the name and role can be programmatically determined; states, properties, and values that can be set by the user can be programmatically set; and notification of changes to these items is available to user agents, including assistive technologies.
— W3C (World Wide Web Consortium): WCAG 4.1: Compatible
If you’d like to learn more about which guidelines we’re building towards, please contact email@example.com.
We are currently in the process of re-factoring our teacher and student user interfaces. Accessibility is a key driver of this change. We are re-developing all current functionality, to include greater keyboard operability and screen reader support, with the goal of achieving full compliance in 2020.
We are also improving our current development practices, to incorporate greater accessibility testing for any new functionality we deliver moving forward. This will ensure that all new functionality preserves accessibility compliance.