Web Content Accessibility Guidelines (WCAG) 2.1
We build accessibility into the software as it is created. Over the years we have worked closely with our clients to further understand the individual needs of our institutions, instructors, and learners, to ensure that Regpack maintains this commitment to full accessibility.
Our QA team regularly reviews the Regpack product for compliance with accessibility standards and any aspect of non-compliance is reported as exceptions on our WCAG checklist.
Accessibility tests are integrated into the unit testing and are part of the testing protocols of the QA team. QA team members are trained and equipped with automated accessibility testing tools.
If any test fails or is not covered by the automated processes they are tested manually by our quality assurance testers, which include testing with assistive technologies. We also partner with third-party QA companies that test directly on screen readers.
The feedback and reports are integrated into the development process of all future updates and existing versions. Key test methods used are listed below, with acronym legends. These acronyms are referenced in the Remarks and Explanations column to indicate how we tested for each of the WCAG 2.1 success criteria.
Our processes follow the WCAG Guidelines and standards (2.1 Level AA) for accessibility. Accessibility has long been a priority at Regpack, as part of our commitment to ensure the needs of our clients and their users are met when using our software and to provide the optimal and equitable onboarding and payment experience for everyone utilizing our services.
You can view our complete Accessibility report here.
This version of our Accessibility Conformance Report (ACR) as of April 2022, reports our conformance with WCAG 2.1 at Levels A and AA based on the VPAT® Version 2.4 WCAG template published by the Information Technology Industry Council (ITIC) in April 2022.