ADAPT for Students Accessibility Conformance Report

The purpose of this Accessibility Conformance Report (ACR) is to assist LibreTexts ADAPT users in making preliminary assessments regarding the accessibility support provided by the LibreTexts ADAPT product.

Name of Product and Version

LibreTexts ADAPT

Report Date

February 2022

Product Description

LibreTexts ADAPT is an adaptive learning assessment system.

Contact Information

Information About LibreTexts

Notes

This report is based on a sample course that, as of the date of this report, students would use to:

• Register for an ADAPT account
• Login to ADAPT
• Contact ADAPT to ask questions
• Enroll in a course through ADAPT
• Take Assessments, including homework and exams
• Review summary information of assessment results.

The Campus Registration Single Sign On (SSO) page through the Central Authentication Service (CAS) is not part of the scope of this accessibility conformance report.

Additionally, assessment question content and functionality from outside sources that is added to ADAPT assessments is not part of the scope of this accessibility conformance report. For example, ADAPT assessments may include H5P, MyOpenMath, and WeBWork questions which were created outside of the ADAPT product.

Evaluation Methods Used

ADAPT web content and user pages were evaluated using automated and manual testing procedures by a certified Trusted Tester Version 5 with the Chrome browser on Windows.

Additionally, testing with screen reading software was conducted by an expert user of screen reading software. The evaluator worked through the sample exam process using JAWS for Windows (version 2022) screen reading software with Chrome Version 97.

Applicable Standards and Guidelines

This report covers the degree of conformance for the following accessibility standard or guidelines:

• Web Content Accessibility Guidelines 2.1
  • Level A (Yes)
  • Level AA (Yes)
  • Level AAA (No)
• Revised 508 Standards
  • (Yes)

Terms

The terms used in the Conformance Level information are defined as follows:

• Supports: The functionality of the product has at least one method that meets the criterion without known defects or meets with equivalent facilitation.
• Partially Supports: Some functionality of the product does not meet the criterion.
• Does Not Support: The majority of product functionality does not meet the criterion.
• Not Applicable: The criterion is not relevant to the product.
• Not Evaluated: Evaluation of this product against the criterion is pending.

A response may use “Supports” instead of using “Not Applicable” to mean that if there is no content to which a success criterion applies, the success criterion is satisfied. Additionally, some success criteria may be supported by providing alternative solutions available in the Student Accessibility Guide (under development) while the product is being updated to fully meet all success criteria without the use of alternative solutions.

WCAG 2.1 Report

Note: When reporting on conformance with the WCAG 2.1 Success Criteria, they are scoped for full pages, complete processes, and accessibility-supported ways of using technology as documented in the WCAG 2.1 ­Conformance Requirements.

WCAG 2.1 Accessibility Conformance

Conformance Level	Number of Criteria	Percent
Supports (labeled in green)	56	100%
Partially Supports (labeled in yellow)	0	0%
Does Not Support (labeled in red)	0	0%
Not Evaluated (labeled in blue)	0	0%

Table Information for ACR Readers

For each of the standards or guidelines, the criteria are listed in a table. The structures of the tables are as follows:

• the first column contains the criteria being evaluated,
• the second column describes the level of conformance of the product regarding the criteria,
• and the third column contains additional remarks and explanations regarding the product, including whether known workarounds are available in the Student Accessibility Guide (under development).

Table 1: WCAG 2.1 Level A

Success Criterion	Conformance Level	Remarks and Explanations
1.1.1 Non-text Content	Supports	Meaningful images have appropriate alternative text descriptions. Decorative images do not have alternative text descriptions. Background images are not used to provide meaningful information that is not communicated in another way. CAPTCHA images are not used on the pages.
1.2.1 Audio-only and Video-only (Prerecorded)	Supports	There is no audio-only or video-only content in the sample reviewed. This success criterion is not applicable. The LibreTexts platform provides tools for content authors to include transcripts for audio-only content and text descriptions for video-only content.
1.2.2 Captions (Prerecorded)	Supports	The LibreTexts platform allows content authors to include accurate synchronized captions for prerecorded synchronized content. There is no prerecorded synchronized media in the sample reviewed.
1.2.3 Audio Description or Media Alternative (Prerecorded)	Supports	The LibreTexts platform allows content authors to include prerecorded synchronized media with audio descriptions. There is no prerecorded synchronized media in the sample reviewed.
1.3.1 Info and Relationships	Supports	Form fields are described with accessible names, descriptions, or other programmatic associations that include all relevant instructions and cues (textual and graphical), including form fields in the Contact Us pop-up and other form fields throughout the pages. Each programmatically determinable heading is a visual heading, and each visual heading is programmatically determinable. Programmatic heading levels logically match the visual heading presentation withing the heading structure. The structure of lists matches the visual structure of lists. All caps are not used for text on the pages other than acronyms. Italics are not used to convey emphasis or meaning for text on the pages unless required by a formatting convention, such as the American Psychological Association (APA) style. Bold text is not used as the only means of conveying meaning. When data tables are used, the tables are programmatically identifiable. The headers for tables are programmatically identified. Layout tables are not used. Meaningful information is not provided by the CSS pseudo-elements ::before or ::after without providing the information in another way.
1.3.2 Meaningful Sequence	Supports	The reading and navigation order is logical on all pages. For example, when pop-ups are open, such as the Contact Us pop-up on the Homepage, the content behind the pop-up cannot be read by screen reading software.
1.3.3 Sensory Characteristics	Supports	Instructions for understanding and operating content do not use sensory information to convey information (references to shape, size, visual location, orientation, or sound).
1.4.1 Use of Color	Supports	Color is not used as the only means of conveying information, indicating an action, prompting a response, or distinguishing a visual element.
1.4.2 Audio Control	Supports	No audio on a pages plays automatically.
2.1.1 Keyboard	Supports	All functionality can be accessed and executed using only the keyboard. A keyboard method is provided for functionality to be activated without requiring users to perform specific timings for activation. Tooltips that can be triggerd on-hover (using the mouse pointer) can be triggered using only the keyboard.
2.1.2 No Keyboard Trap	Supports	There are no keyboard traps.
2.1.4 Character Key Shortcuts	Supports	Single-key character shortcuts are not used. This success criterion is not applicable.
2.2.1 Timing Adjustable	Supports	Content on the pages does not have time limits. This success criterion is not applicable.
2.2.2 Pause, Stop, Hide	Supports	There is no content that continues moving for more than 5 seconds. The user can pause, stop, hide, or control the frequency of automatically updating content. For example, on Assessment pages, the user may hide the automatically updating count-down to the assessment due date and time.
2.3.1 Three Flashes or Below Threshold	Supports	There is no flashing content. This success criterion is not applicable.
2.4.1 Bypass Blocks	Supports	A keyboard-accessible method to bypass repetitive content is provided on all pages.
2.4.2 Page Titled	Supports	A page title element is defined for each web page. The title element of pages identifies its contents or purpose. For example, the title element of the registration page for instructors is "Instructor Registration ∙ ADAPT" and the title element of the registration page for students is "Student Registration ∙ ADAPT."
2.4.3 Focus Order	Supports	The focus order preserves the meaning and operability of the page. When the keyboard is used to trigger controls that reveal hidden content, the focus is moved to the revealed content. When page content is hidden or dismissed, focus returns to a logical sequence on the page.
2.4.4 Link Purpose (In Context)	Supports	The purpose of links and buttons can be programmatically determined. For example, on The Commons ADAPT page, aria-label is used to include the course name, that is provided as a heading on the page, as part of the accessible name for each View Assignments and Enter Course button. Descriptive text, instead of URLs, is used for links, including email addresses.
2.5.1 Pointer Gestures	Supports	All functionality that can be operated with a pointer can be operated with single-pointer actions. Path-based or multi-point gestures are not required to operate any functionality.
2.5.2 Pointer Cancellation	Supports	For functionality that can be operated using a single-pointer the action is not triggered on the down event.
2.5.3 Label in Name	Supports	For each user interface component that includes a visible text label, the accessible names match (or include) the visible text in the label.
2.5.4 Motion Actuation	Supports	No functionality has been implemented that can be triggered by motion actuation. This success criterion is not applicable.
3.1.1 Language of Page	Supports	The default primary language is correctly specified as "en" (English) and matches the default human language of the page.
3.1.2 Language of Parts	Supports	The human language of each passage or phrase in the content can be programmatically determined. For example, on The Commons ADAPT page, the human language of the names of three courses (Entrada Libre, Naveguemos juntos, and Français 101) and the content in the associated Assignments pop-up for the three courses can be programmatically determined.
3.2.1 On Focus	Supports	When interface components receive focus, there are no unexpected changes of context that occur (for example, a new window is launched or focus is moved to another interface component).
3.2.2 On Input	Supports	Changing the value of a form element does not initiate an unexpected context change.
3.3.1 Error Identification	Supports	Form-related items that are in error are identified in text and sufficiently described to the user in text.
3.3.2 Labels or Instructions	Supports	Labels or instructions are provided for each form element. For all form elements, the label or instruction is visible when the form field has focus.
4.1.1 Parsing	Supports	The ADAPT pages were tested with the W3C Markup Validation Service. No errors were reported.
4.1.2 Name, Role, Value	Supports	Pages provide notification of changes in content that are the result of interaction with a link or button (either through the link or button text or programmatic label). Frames are not used on the pages. When iframes are used, such as on pages with assessments, the iframes have descriptive names.

Table 2: WCAG 2.1 Level AA

Success Criterion	Conformance Level	Remarks and Explanations
1.2.4 Captions (Live)	Supports	There is no live synchronized media. This success criterion is not applicable.
1.2.5 Audio Description (Prerecorded)	Supports	The LibreTexts platform allows content authors to include prerecorded synchronized media with audio descriptions. There is no prerecorded synchronized media in the sample reviewed.
1.3.4 Orientation	Supports	Orientation of the content is not locked to either landscape or portrait, unless a specific orientation is essential for the functionality.
1.3.5 Identify Input Purpose	Supports	Form elements that accept an individual's personal data used on the page have accurate autocomplete attributes.
1.4.10 Reflow	Supports	Content reflows to fit horizontally within the viewpoint when the page width is adjusted to 320 pixels.
1.4.11 Non-text Contrast	Supports	The visual boundaries used as the only means of indicating active user components’ hit areas have color contrast of at least 3 to 1 with the adjacent background, including, in the Contact Us pop-up, the Name, Email, and Subject form fields and the form fields on other pages. The visual state of some active user interface components have sufficient contrast of 3 to 1 with the adjacent background. Parts of graphics required to understand the content have a contrast ratio of 3 to 1 against adjacent colors.
1.4.12 Text Spacing	Supports	The spacing between letters, words, lines of text and/or paragraphs on pages can be adjusted.
1.4.13 Content on Hover or Focus	Supports	Tooltips can be dismissed without moving the mouse pointer (the tooltip associated with the item is dismissible). Tooltips that become available on hover allow the user to move the pointer over that same additional content without the additional content disappearing (the tooltip associated with the item is hoverable). Tooltips remain visible until the hover or focus trigger is removed, the user dismisses it, or its information is no longer valid (the tooltip associated with the item is persistent).
1.4.3 Contrast (Minimum)	Supports	Text and images of text on pages has sufficient color contrast. Regular text and images of regular text have a contrast ratio of at least 4.5 to 1 with the background. Large text and images of large text have a contrast ratio of at least 3 to 1 with the background.
1.4.4 Resize text	Supports	When page content is resized to at least 200% using the browser magnification, there is no loss of content or functionality.
1.4.5 Images of Text	Supports	Images of text are not used on the pages and if images of text are used, the meaningful information is provided in another way.
2.4.5 Multiple Ways	Supports	There are at least two ways to locate the ADAPT Home page and other pages within the set of ADAPT pages, excluding pages that are the result of, or a step in, a process (for example, taking an exam). In addition to breadcrumb navigation links, ADAPT includes a site map for each user.
2.4.6 Headings and Labels	Supports	Headings on the pages describe the topic or purpose of its content. Labels for form elements sufficiently describe the purpose and applicable data requirements.
2.4.7 Focus Visible	Supports	A visible indication of focus is provided so that it is visually apparent which screen element has the current keyboard focus.
3.2.3 Consistent Navigation	Supports	Navigational elements that occur across multiple pages are presented in the same relative order.
3.2.4 Consistent Identification	Supports	Components with identical functionality are identified consistently.
3.3.3 Error Suggestion	Supports	The description contains adequate information for the user to know what is required to correct errors in form fields.
3.3.4 Error Prevention (Legal, Financial, Data)	Supports	When users are required to submit user form entries that modify or delete user-controllable data in a data storage system or to submit test responses, the changes or deletions are reversible, verified, or confirmed.
4.1.3 Status Messages	Supports	When status messages are used, the status messages can be programmatically determined through role or properties such that they can be presented to the user by assistive technologies without receiving focus.

Table 3: Revised 508 Standards

Success Criterion	Conformance Level	Remarks and Explanations
503.4 User Controls for Captions and Audio Description	Supports	The LibreTexts platform allows content authors to include media players that provide user controls for closed captions and audio descriptions. There is no media player in the sample reviewed.
503.4.1 Caption Controls	Supports	The LibreTexts platform allows content authors to include media players that provide user controls for captions at the same menu level as the user controls for volume or program selection. There is no media player in the sample reviewed.
503.4.2 Audio Description Controls	Supports	The LibreTexts platform allows content authors to include media players that provide user controls for audio descriptions at the same menu level as the user controls for program selection or volume. There is no media player in the sample reviewed.
504.2.1 Preservation of Information Provided for Accessibility in Format Conversion	Supports	There is no format conversion tool. This success criterion is not applicable.
504.2.2 PDF Export	Supports	There is no format conversion tool. This success criterion is not applicable.
Conforming Alternate Version	Supports	There is only one version of the content. This success criterion is not applicable.

Legal Disclaimer LibreTexts

This document is for informational purposes only. LibreTexts makes no warranties, expressed or implied, in this document. The information contained in this document represents the current view of LibreTexts on the issues discussed as of the date of publication. Because LibreTexts must respond to changing market conditions, it should not be interpreted to be a commitment on the part of LibreTexts, and LibreTexts cannot guarantee the accuracy of any information presented after the date of publication.