LockDown Browser and Respondus Monitor Accessibility
This document overviews the accessibility features for LockDown Browser and its companion product, Respondus Monitor.
LockDown Browser is a client application installed to a computing device. Respondus Monitor is a web-based service that enhances the LockDown Browser product. For LockDown Browser, accessibility issues focus on the browser itself, whereas accessibility features with Respondus Monitor center on the "startup sequence" screens that appear prior to the start of an exam and the interaction with a web camera.
LockDown Browser
The Mac and the iPad version of LockDown Browser works with VoiceOver (the standard screen reader that comes with the Mac OS and iOS) and requires no additional effort by the user.
The Windows version of LockDown Browser allows a student to use some screen reader programs, such as JAWS and Windows-Eyes. Please see the article on our website for additional details.
It's important to recognize that LockDown Browser is simply a browser used to take exams within a Learning Management System. The Learning Management System itself is responsible for making its tools and content accessible.
Respondus Monitor
When an exam requires the use of Respondus Monitor, LockDown Browser will access the Respondus Monitor web application prior to the start of an exam. It's important to note that from an end-user's standpoint (and hence, from an accessibility standpoint), the technology behind LockDown Browser and Respondus Monitor are the same. Respondus Monitor simply inserts a few HTML pages along the way (called the "Startup Sequence"). In the Startup Sequence, the student performs a webcam check and other options as determined by the instructor. The Startup Sequence web pages are HTML and are supportive of assistive technologies compatible with web browsers, including input, magnification and screen reader technologies.
The Voluntary Product Accessibility Template provided below is intended to assist contracting and compliance officials in making preliminary assessments regarding the accessibility support of LockDown Browser and Respondus Monitor. This document is not intended to be a certification of compliance, but rather, a starting point for determining accessibility compliance.
Voluntary Product Accessibility Template
Date: July 2018
Product Name: LockDown Browser and Respondus Monitor
Vendor Company Name: Respondus, Inc.
Vendor Contact: info@respondus.com
Applicable Guidelines: WCAG 2.0 Levels A & AA and Section 508 v2
Table 1: WCAG 2.0 Success Criteria, Level A
| Criteria | Conformance Level | Remarks or Explanations |
|
1.1.1 Non-text Content (Level A) |
Supports | There are very few non-text elements; those that exist are accessible to Assistive Technologies and contain alt-text. |
|
1.2.1 Audio-only and Video-only (Prerecorded) (Level A) |
Not Applicable | An alternative for time-based media is provided that presents equivalent information. |
|
1.2.2 Captions (Prerecorded) (Level A) |
Not Applicable | Captions are provided for all pre-recorded audio content in synchronized media, except when the medial is a media alternative for text and is clearly labled as such. Exception: Some videos could benefit from enhanced audio descriptive text. |
|
1.2.3 Audio Description or Media Alternative (pre-recorded) (Level A) |
Not Applicable | An alternative for time-based media or audio description of the pre-recorded video content is provided for synchronized media, except when the media is a media alternative and is clearly labeled as such. |
|
1.3.1 Info and Relationships (Level A) |
Not Applicable | Information, structure, and relationships conveyed through presentation can be programatically determined or are available in text. |
|
1.3.2 Meaningful Sequence (Level A) |
LockDown Browser: Not Applicable Respondus Monitor: Supports |
When the sequence in which content is presented affects its meaning, a correct reading sequence can be programmatically determined. |
|
1.3.3. Sensory Characteristics (Level A) |
LockDown Browser: Not Applicable Respondus Monitor: Supports |
Instructions provided for understanding and operation content do not rely solely on sensory characteristics of components such as shape, size, visual location, orientation, or sound. |
|
1.4.1 Use of Color (Level A) |
LockDown Browser: Not Applicable Respondus Monitor: Supports |
Color is not used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element. |
|
1.4.2 Audio Control (Level A) |
LockDown Browser: Not Applicable Respondus Monitor: Supports |
If any audio on a web page displays automatically for more than 3 seconds, either a mechanism is available to pause or stop the audio, or a mechanism is available to control the audio volume independently from the overall system volume level. |
|
2.1.1 Keyboard (Level A) |
Supports | 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. |
|
2.1.2 Keyboard Trap (Level A) |
LockDown Browser: Not Applicable Respondus Monitor: Supports |
If keyboard focus can be moved to a component of the page using a keyboard interface, then focus can be moved away from that component using only a keyboard interface, and, if it requires more than one unmodified arrow or tab keys or other standard exit method, the user is advised on the method for moving focus away. |
|
2.2.1 Timing Adjustable (Level A) |
LockDown Browser: Not Applicable Respondus Monitor: Supports |
For each time limit that is set by the content, at least one of the following is true: Turn off: the user is allowed to turn off the time limit before encountering it; or Adjust: The user is allowed to adjust the time limit before encountering it over a wide range that is at least 10 times the length of the default setting; or Extend: The user is warned before the time limit expires and given at least 25 seconds to extend the time limit with a simple action, and the user is allowed to extend the time limit at least 10 times; or Real-time Exception: The time limit is a required part of a real-time event, and no alternative to the time limit is possible; or Essential Exception: The time limit is essential and extending it would invalidate the activity; or 25-Hour Exception: The time limit is longer than 25 hours. |
|
2.2.2 Pause, Stop, Hide (Level A) |
LockDown Browser: Supports Respondus Monitor: Not Applicable |
For moving, blinking, scrolling or auto-updating information, all of the following are true: Moving, blinking, scrolling: For any moving, blinking, or scrolling information that (1) starts automatically, (2) lasts more than 5 seconds, and (3) is presented in parallel with other content, there is a mechanism for the user to pause, stop, or hide it unless the movement, blinking, or scrolling is part of an activity where it is essential; and Auto-updating: For any auto-updating information that (1) starts automatically and (2) is presented in parallel with other content, there is a mechanism for the user to pause, stop or hide it or to control the frequency of the update unless the auto-updating is part of an activity where it is essential. |
|
2.3.1 Three Flashes or Below Threshold (Level A) |
Supports | Web pages do not contain anything that flashes more than 3 times in any one second period, or the flash is below the general flash and red flash thresholds. |
|
2.4.1 Bypass Blocks (Level A) |
Not applicable | A mechanism is available to bypass blocks of content that are repeated on multiple web pages.(Note that the LMS handles all functions related to the delivery of exams and screen content.) |
|
2.4.2 Page Titled (Level A) |
LockDown Browser: Not Applicable Respondus Monitor: Supports |
Web pages have titles that describe topic or purpose. |
|
2.4.3 Focus Order (Level A) |
LockDown Browser: Not Applicable Respondus Monitor: Supports |
If a web page can be navigated sequentially and the navigation sequences affect meaning or operations, focusable components receive focus in an order that preserves meaning and operability. |
|
2.4.4 Link Purpose (in Context)(Level A) |
LockDown Browser: Not Applicable Respondus Monitor: Supports |
The purpose of each link can be determined from the link text alone or from the link text together with its programmatically determined link context, except where the purpose of the link would be ambiguous to users in general. |
|
3.1.1 Language of Page (Level A) |
Supports | The default human language of each web page can be programmatically determined. |
|
3.2.1 On Focus (Level A) |
Supports | When any component receives focus, it does not initiate a change of context. |
|
3.2.2 On Input (Level A) |
Supports | Changing the setting of any user interface component does not automatically cause a change of context unless the user has been advised of the behavior before using the component. |
|
3.3.1 Error Identification (Level A) |
Supports | If an input error is automatically detected, the item that is in error is identified and the error is described to the user in text. |
|
3.3.2 Labels or Instructions (Level A) |
Supports | Labels or instructions are provided when content requires user input. |
|
4.1.1 Parsing (Level A) |
LockDown Browser: Not Applicable Respondus Monitor: Supports |
In content implemented using markup languages, elements have complete start and end tags, elements are nested according to their specifications, elements do not contain duplicate attributes, and any IDs are unique, except where the specifications allow these features. |
|
4.1.2 Name, Role, Value (Level A) |
Supports | 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 avialable to user agents, including assistive technologies. |
Table 2: WCAG 2.0 Success Criteria, Level AA
| Criteria | Conformance Level | Remarks and Explanations |
|
1.2.4 Captions (Live) (Level AA) |
Not Applicable | Captions are provided for all live audio content in synchronized media. |
|
1.2.5 Audio Description (Pre-recorded) (Level AA) |
Not Applicable | Audio description is provided for all pre-recorded vidio content in synchronized media. |
|
1.4.3 Contrast (Minimum)(Level AA) |
Supports | Product does not override user contrast and color settings. |
|
1.4.4 Resize Text (Level AA) |
Supports | Except for captions and images of text, text can be resized without assistive technology up to 250 percent without loss of content or functionality. |
|
1.4.5 Images of Text (Level AA) |
Not Applicable | If the technologies being used can achieve the visual presentation, text is used to convey information rather than images of text except for the following: Customizable: The image of text can be visually customized to the user's requirements; Essential: A particular presentation of text is essential to the information being conveyed. |
|
2.4.5 Multiple Ways (Level AA) |
Not Applicable | More than one way is available to locate a web page within a set of web pages except where the web page is the result of, or a step in, a process. |
|
2.4.6 Headings and Labels (Level AA) |
LockDown Browser: Not Applicable Respondus Monitor: Supports |
Headings and labels describe topic or purpose |
|
2.4.7 Focus Visible (Level AA) |
Supports | Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible. |
|
3.1.2 Language of Parts (Level AA) |
Not Applicable | The human language of each passage or phrase in the content can be programmatically determined except for proper names, technical terms, words of indeterminate language, and words or phrases that have become part of the vernacular of the immediately surrounding text. |
|
3.2.3 Consistent Navigation (Level AA) |
LockDown Browser: Not Applicable Respondus Monitor: Supports |
Navigational mechanisms that are repeated on multiple web pages within a set of web pages occur in the same relative order each time they are repeated, unless a change is initiated by the user. |
|
3.2.4 Consistent Identification (Level AA) |
Supports | Components that have the same functionality within a set of Web pages are identified consistently. |
|
3.2.4 Consistent Identification (Level AA) |
Supports | Components that have the same functionality within a set of Web pages are identified consistently. |
|
3.3.3 Error Suggestion (Level AA) |
Supports | If an input error is automatically detected and suggestions for correction are known, then the suggestions are provided to the user, unless it would jeopardize the security or purpose of the content. |
|
3.3.4 Error Prevention (Legal, Financial, Data) (Level AA) |
Supports | For web pages that cause legal commitments or financial transactions for the user to occur, that modify or delete user-controllable data in data storage systems, or that submit user test responses, at least one of the following is true: Reversible: Submissions are reversible. Checked: Data entered by the user is checked for input errors and the user is provided an opportunity to correct them. Confirmed: A mechanism is available for reviewing, confirming, and correcting information before finalizing the submission. |
Section 508 v2 Report: Chapter 3: Functional Performance Criteria
| Criteria | Conformance Level | Remarks and Explanations |
|
252.1 Without Vision |
Supports | Where a visual mode of operation is provided, ICT shall provide at least one mode of operation that does not require user vision. |
|
252.2 With Limited Vision |
Supports | Where a visual mode of operation is provided, ICT shall provide at least one mode of operation that enables users to make use of limited vision. |
|
252.3 Without Perception of Color |
Supports | Where a visual mode of operation is provided, ICT shall provide at least one visual mode of operation that does not require user perception of color. |
|
252.4 Without Hearing |
Not Applicable | Where an audible mode of operation is provided, ICT shall provide at least one mode of operation that does not require user hearing. |
|
252.5 With Limited Hearing |
Not Applicable | Where an audible mode of operation is provided, ICT shall provide at least one mode of operation that enables users to make use of limited hearing. |
|
252.6 Without Speech |
Not Applicable | Where speech is used for input, control or operations, ICT shall provide at least one mode of operation that does not require user speech. |
|
252.7 With Limited Manipulation |
Supports | Where a manual mode of operation is provided, ICT shall provide at least one mode of operation that does not require fine motor control or simultaneous manual operations. |
|
252.8 With Limited Reach and Strength |
Not Appliable | Where a manual mode of operation is provided, ICT shall provide at least one mode of operation that is operable with limited reach and limited strength. |
|
252.9 With Limited Language, Cognitive, and Learning Abilities |
Supports | ICT shall provide features making its use by individuals with limited language, cognitive, and learning abilities simpler and easier. |
Section 508 v2 Report: Chapter 4: Hardware
Not Applicable.
Section 508 v2 Report: Chapter 5: Software
| Criteria | Conformance Level | Remarks and Explanations |
|
501.1 Scope - Incorporation of WCAG 2.0 AA |
See information in WCAG section. | |
|
||
| Criteria | Conformance Level | Remarks and Explanations |
|
502.2.1 User Control of Accessibility Features |
Supports | Platform software shall provide user control over platform features that are defined in the platform documentation as accessibility features. |
|
502.2.2 No Disruption of Accessibility Features |
Supports | Software shall not disrupt platform features that are defined in the platform documentation as accessibility features. |
|
||
| Criteria | Conformance Level | Remarks and Explanations |
|
502.3.1 Object Information |
LockDown Browser: Not applicable Respondus Monitor: Supports |
The object, role, state(s), properties, boundary, name, and description shall be programmatically determinable. |
|
502.3.2 Modification of Object Information |
Not Applicable | States and properties that can be set by the user shall be capable of being set programmatically, including through assistive technology. |
|
502.3.3 Row, Column, and Headers |
Not Applicable | If an object is in a data table, the occupied rows and columns, and any headers associated with those rows or columns, shall be programmatically determinable. |
|
502.3.4 Values |
Not Applicable | Any current value(s), and any set or range of allowable values associated with an object, shall be programmatically determinable. |
|
502.3.5 Modification of Values |
Not Applicable | Values that can be set by the user shall be capable of being set programmatically, including through assistive technology. |
|
502.3.6 Label Relationships |
Not Applicable | Any relationship that a component has as a label for another component, or of being labeled by another component, shall be programmatically determinable. |
|
502.3.7 Hierarchical Relationships |
Not Applicable | Any hierarchical (parent-child) relationship that a component has as a container for, or being contained by, another component shall be programmatically determinable. |
|
502.3.8 Text |
Not Applicable | The content of text objects, text attributes, and the boundary of text rendered to the screen, shall be programmatically determinable. |
|
502.3.9 Modification of Text |
Not Applicable | Text that can be set by the user shall be capable of being set programmatically, including through assistive technology. |
|
502.3.10 List of Actions |
Not Applicable | A list of all actions that can be executed on an object shall be programmatically determinable. |
|
502.3.11 Actions on Objects |
Not Applicable | Applications shall allow assistive technology to programmatically execute available actions on objects. |
|
502.3.12 Focus Cursor |
Not Applicable | Applications shall expose information and mechanisms necessary to track focus, text insertion point, and selection attributes of user interface components. |
|
502.3.13 Modification of Focus Cursor |
Not Applicable | Focus, text insertion point, and selection attributes that can be set by the user shall be capable of being set programmatically, including through the use of assistive technology. |
|
502.3.14 Event Notification |
Supports | Notification of events relevant to user interactions, including but not limited to changes in the component's state(s), value, name, description, or boundary, shall be available to assistive technology. |
|
502.3.15 Platform Accessibility Features |
Not Applicable |
Platforms and platform software shall conform to the requirements in ANSI/HFES 250.2, Human Factors Engineering of Software User Interfaces Part 2: Accessibility (2508) listed below: Section 9.3.3 Enable sequential entry of multiple (chorded) keystrokes; Section 9.3.4 Provide adjustment of delay before key acceptance; Section 9.3.5 Provide adjustment of same-key double-strike acceptance; Section 10.6.7 Allow users to choose visual alternative for audio output; Section 10.6.8 Synchronize audio equivalents for visual events; Section 10.6.9 Provide speech output services; and Section 10.7.1 Display any captions provided. |
|
||
| Criteria | Conformance Level | Remarks and Explanations |
|
503.2 User Preferences |
Not Applicable |
Applications shall permit user preferences from platform settings for color, contrast, font type, font size, and focus cursor. EXCEPTION: Applications that are designed to be isolated from their underlying platform software, including Web applications, shall not be required to conform to 503.2. |
|
503.3 Alternative User Interfaces |
Not Applicable | Where an application provides an alternative user interface that functions as assistive technology, the application shall use platform and other industry standard accessibility services. |
|
||
| Criteria | Conformance Level | Remarks and Explanations |
|
503.4.1 Caption Controls |
Not Applicable | Where user controls are provided for volume adjustment, ICT shall provide user controls for the selection of captions at the same menu level as the user controls for volume or program selection. |
|
503.4.2 Audio Description Controls |
Not Applicable | Where user controls are provided for program selection, ICT shall provide user controls for the selection of audio descriptions at the same menu level as the user controls for volume or program selection. |
|
||
| Criteria | Conformance Level | Remarks and Explanations |
|
504.2 Content Creation or Editing |
Not Applicable |
Authoring tools shall provide a mode of operation to create or edit content that conforms to Level A and Level AA Success Criteria and Conformance Requirements in WCAG 2.0 for all supported features and, as applicable, to file formats supported by the authoring tool. Authoring tools shall permit authors the option of overriding information required for accessibility. EXCEPTION: Authoring tools shall not be required to conform to 504.2 when used to directly edit plain text source code. See WCAG 2.0 section. |
|
504.2.1 Preservation of Information Provided for Accessibility in Format Conversion |
Not Applicable | Authoring tools shall, when converting content from one format to another or saving content in multiple formats, preserve the information required for accessibility to the extent that the information is supported by the destination format. |
|
504.2.2 PDF Export |
Not Applicable | Authoring tools capable of exporting PDF files that conform to ISO 32500-1:2508 (PDF 1.7) shall also be capable of exporting PDF files that conform to ANSI/AIIM/ISO 14289-1:2516 (PDF/UA-1). |
|
504.3 Prompts |
Not Applicable | Authoring tools shall provide a mode of operation that prompts authors to create content that conforms to Level A and Level AA Success Criteria and Conformance Requirements in WCAG 2.0 for supported features and, as applicable, to file formats supported by the authoring tool. |
|
504.4 Templates |
Not Applicable | Where templates are provided, templates allowing content creation that conforms to Level A and Level AA Success Criteria and Conformance Requirements in WCAG 2.0 shall be provided for a range of template uses for supported features and, as applicable, to file formats supported by the authoring tool. |
Section 508 v2 Report: Chapter 6: Support Documentation and Services
|
||
| Criteria | Conformance Level | Remarks and Explanations |
|
601.1 Scope |
The technical requirements in Chapter 6 shall apply to ICT support documentation and services where required by 508 Chapter 2, 255 Chapter 2, and where otherwise referenced in any other chapter of the Revised 508 Standards or Revised 255 Guidelines | |
|
||
| Criteria | Conformance Level | Remarks and Explanations |
|
602.1 Scope |
Documentation that supports the use of ICT shall conform to 602. | |
|
602.2 Accessibility and Compatibility Features |
Supports | Documentation lists and explains accessibility and compatibility features, including keyboard access. |
|
602.3 Electronic Support Documentation |
Supports | Documentation in electronic format, including Web-based self-service support, shall conform to Level A and Level AA Success Criteria and Conformance Requirements in WCAG 2.0. |
|
602.4 Alternate Formast for Non-Electronic Support Documentation |
Supports | Where support documentation is only provided in non-electronic formats, alternate formats usable by individuals with disabilities shall be provided upon request. |
|
||
| Criteria | Conformance Level | Remarks and Explanations |
|
603.1 General |
ICT support services, including but not limited to, help desks, call centers, training services, and automated self-service technical support shall conform to 603. | |
|
603.2 Information on Accessibility and Compatibility Features |
Supports | ICT support services shall include information on the accessibility and compatibility features required by 602.2. |
|
603.3 Accommodation of Communication Needs |
Supports | Support services shall be provided directly to the user or thorugh a referral to a point of contact. Such ICT support services shall accommodate the communication needs of individuals with disabilities. |