Respondus is committed to ensuring that LockDown Browser meets the diverse accessibility needs of all learners. Our accessibility program includes regular testing (by internal and third-party teams) in order to achieve conformance to regulations and accessibility standards. Processes are in place to track defects and to work toward timely remediation.
Accessibility with LockDown Browser
LockDown Browser is a client application installed to a user’s computing device. It is based on the Chromium Embedded Framework (CEF) and renders content nearly identically to other browsers based on CEF (eg. Chrome, Edge).
Integrations with Learning Management Systems (LMS)
LockDown Browser displays exam content within the Learning Management System nearly identically to Google Chrome. The Learning Management System itself is responsible for making its tools and content accessible. Our compliance testing does not encompass tools or content within the learning system itself.
Voluntary Product Accessibility Template (VPAT)
Respondus partners with Online ADA, experts in user accessibility and compliance. Every six months, Online ADA will audit, produce and certify the Voluntary Product Accessibility Template (VPAT) for LockDown Browser. This ensures our accessibility documentation is kept up to date, and can alert us to issues missed with internal accessibility testing.
LockDown Browser – VPAT
Certification of WCAG 2.1 Level A and AA Conformance
Compatibility with Other Accessibility Technologies
The VPAT demonstrates that LockDown Browser meets the basic standards for web accessibility. But that’s only part of our story. Some assistive technologies have toolbars or features that compromise a locked browser environment. That’s why Respondus works with third-party accessibility vendors to ensure seamless compatibility and exam security. Some of these partnerships include:
Respondus maintains a knowledge base article that provides the latest details on how LockDown Browser works with various assistive technologies. If you have a question not addressed by this article, please email [email protected].
Accessibility Knowledge Base Article