LibreTexts Libraries Accessibility Conformance Report Nov 2021

Name of Product and Version

LibreTexts Libraries

Report Date

November 2021

Product Description

The LibreTexts Libraries are an online textbook platform.

Contact Information

Send Email to Information About LibreTexts

Notes

This report is based on sample online textbook platform content, as of the date of this report, that students would use to:

Navigate an online textbook in a LibreTexts Library
Generate a page citation
Download a PDF version of a LibreTexts online textbook
Use tools and resources in the LibreTexts Sidebar
Donate to LibreTexts.

About Math Content

LibreTexts uses MathJax and MathML to display math content, including expressions and equations. MathJax works with screen reading software and provides tools to magnify math content and interactively explore math content. Visit MathJax Accessibility Features for more information.

Evaluation Methods Used

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

Additionally, testing with screen reading software was conducted by an expert user of screen reading software. The evaluator worked through the sample of online textbook platform content using JAWS for Windows (version 2021) screen reading software with the Chrome browser version 95.

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)	27	48%
Partially Supports (labeled in yellow)	17	30%
Does Not Support (labeled in red)	11	20%
Not Evaluated (labeled in blue)	1	2%

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	Partially Supports	Meaningful images do not have alt-text descriptions. Examples: the alt-text for the image of the LibreTexts chemistry logo contains a file name; the Single Sign-On icon is not recognizable with assistive technology; the alt-text for the PDF image is not descriptive (picture_as_pdf); the Readability and Cite this page icons are not recognizable with assistive technology; the general overview of the LibreVerse image does not have descriptive alt-text and the alt-text for the image contains a file name; and except for the Merlot logo, the alt-text for the LibreTexts supporters' logos are acronyms without including the text in the images. Sidebar examples: The alt-text descriptions for the periodic table does not include the information associated with the options from the Property to Display dropdown box, such as electron configuration. Meaningful images on the Sidebar References Organic Chemistry Glossary pages do not have alt-text or have file names as alt-text. Decorative images do not have alt-text descriptions. When background images that represent meaningful information are used, the information is presented as an accessible alternative. CAPTCHA images are not used on the pages.
1.2.1 Audio-only and Video-only (Prerecorded)	Supports	There is no audio-only content in the sample reviewed. There is no video-only content in the sample reviewed.
1.2.2 Captions (Prerecorded)	Partially Supports	Auto-generated captions are provided that are not accurate.
1.2.3 Audio Description or Media Alternative (Prerecorded)	Partially Supports	No audio description is provided for meaningful visual information that is part of the synchronized media. Examples: URLs for resources; LibreTexts Mission Statement; What is OER? 5R definitions; Content Development flowchart.
1.3.1 Info and Relationships	Partially Supports	Most form fields are described with accessible names, descriptions, or other programmatic associations that include all relevant instructions and cues (textual and graphical). In the citation pop-up, the citation dropdown box does not have an accessible name. In the page attribution pop-up, the page attribution dropdown box does not have an accessible name. Each programmatically determinable heading is a visual headings and most visual headings are programmatically determinable. Donate Pop-up examples: The visual headings Choose amount, Information, and Payment are not programmatic headings. Programmatic headings logically match the visual heading presentation within the page heading structure. Not all visually apparent lists are correctly structured programmatic lists. There is an empty <li> (list item) before the list of links including the PDF link. The structure of the list with the PDF, Downloads, Readability, Cite this page, and Donate links does not match the visual structure of the list because the links are grouped as one list item instead of multiple list items. The structure of the list with the items Back, Previous, and Next links does not match the visual structure of the list because it is an ordered list instead of an unordered list. On 1.1: Project Overview, after the No button, there is an empty <li> (list item). Sidebar examples: The structure of the lists in the Sidebar Contents and Libraries does not match the visual structure of the lists. All caps are used for text that is not acronyms on the Readability tab. Italics is used for text on the page when not required by a formatting convention, such as APA. On 1.1: Project Overview, the caption in Figure 1.1.1 is in italics. Bold text is not used as the only means of conveying meaning. Data tables are identified as tables. Data tables do not have row headers. Sidebar examples: The Physical Constants data table does not have row headers. Layout tables are not used. Meaningful information is provided by the CSS pseudo-elements ::before or ::after without providing the information in another way. Examples: the Single Sign On link; the Sign In link (to open the menu with the Forgot password link); the Creative Commons link; and when magnified 200% with the browser settings, the Contents menu icon and the Sign In menu icon. Donate Pop-up examples: the question mark for the tooltips are provided by the CSS pseudo-elements ::before or ::after without providing the information in another way.
1.3.2 Meaningful Sequence	Partially Supports	The reading order of the content is not correct. Examples: when the cite this page and get attribution pop-ups are open, the focus is not restricted to the pop-ups until they are dismissed by the user. Donate Pop-up examples: When the Donate pop-up is open, the focus is not restricted to the pop-up until it is dismissed by the user.
1.3.3 Sensory Characteristics	Supports	Instructions for understanding and operating content do not use sensory information to convey information (for example, 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	There is no audio content that plays automatically for more than 3 seconds. This success criterion is not applicable.
2.1.1 Keyboard	Does Not Support	Several links and buttons are not accessible with the keyboard: the SSO link (the SSO link can be accessed with JAWS); the Readability, and Cite This Page menu and menu items; the PDF menu options; the links in the Get Page Citation pop-up; the links in the Get Page Attribution pop-up; and the Yes and No buttons may not be keyboard accessible (the Yes and No buttons may not be functioning). The tooltips for the Previous and Next buttons and the tooltips for the links and buttons on the page do not appear when the buttons receive keyboard focus. Sidebar examples: When not using assistive technology, such as JAWS screen reading software, links in the sidebar Contents, Resources, and Libraries require Shift+Enter to activate using the keyboard but the non-standard method is not described for users. (This issue appears to affect links that are in expandable lists.) The Scientific Calculator is not keyboard accessible but equivalent functionality is provided through support for typing math content. (The sidebar Content menu is not keyboard accessible with NVDA.) Donate Pop-up examples: Several items are not accessible with the keyboard, including the time options, amount options, and information tips. A keyboard method is provided for functionality to be activated without requiring users to perform specific timings for activation. The timing of the keystrokes is not required to activate the element, (the speed at which a button that is part of viewing a session is activated, and there is no timing dependent functionality).
2.1.2 No Keyboard Trap	Does Not Support	In the Donate Pop-up, navigating the credit card edit fields with the keyboard triggers an error message that freezes the form.
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	Partially Supports	The image for 5. Interactive Elements on the page continues moving for more than 5 seconds without a mechanism to pause, stop, or hide the image. There is no automatically updating content.
2.3.1 Three Flashes or Below Threshold	Supports	There is no flashing content.
2.4.1 Bypass Blocks	Does Not Support	No keyboard-accessible method to bypass repetitive content is provided and the skip navigation link does not function as expected. The skip navigation link at the top of the page does not move the keyboard focus past the repetitive content at the top of the page (it only moves past the Remixer link). No keyboard-accessible method is provided to move past the second set of repetitive content, from the Creative Commons link through the Donate link.
2.4.2 Page Titled	Supports	A page title element is defined for each web page. The title element of the web page identifies its contents or purpose.
2.4.3 Focus Order	Partially Supports	In image captions, the numbering is math content making it keyboard accessible when it does not need to be. (The numbering in headings in H5P query boxes may also be math content.) When the keyboard is used to trigger controls that reveal hidden content, the focus is not moved to the revealed content. The focus is not moved to the links in Contents when the links are revealed. Sidebar examples: The focus is not moved to the revealed content when a Libraries options are expanded (there is a link to the library in the page tab order before the revealed content). When the keyboard is used to trigger controls that hide or dismiss content, the focus is not returned to a logical sequence. Sidebar examples: In Contents and Libraries, when content is hidden or dismissed by navigating with the arrow keys (instead of with Tab or Shift+Tab), focus does not return to a logical sequence (the focus returns to the end of the list content). Keyboard-only users should navigate the Contents and Libraries menus using the arrow keys and not using Tab or Shift+Tab so that when content is hidden, the focus will return to a logical sequence.
2.4.4 Link Purpose (In Context)	Does Not Support	The purpose of several links or buttons cannot be programmatically determined. Examples: the LibreTexts Chemistry logo link; the Single Sign-On link; the Sign in link (forgot password link); the Creative Commons link; the Readability link; the Cite this page link; the links in the citation and attribution pop-ups; the Yes and No buttons; the Previous and Next buttons; and the accessible names for links to the LibreTexts supporters include the URLs. Also, the link text for several links is unclear because the link text is the URL: Construction Forums URL; in 1.1 Project Overview, the URL in the image caption; contact email address; and the status page URL. Sidebar examples: in Resources, the close button in the periodic table properties dropdown box; and the expand and collapse buttons in the Sidebar Contents, Resources, and Libraries. Donate Pop-up examples: Previous and Next buttons.
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	Partially Supports	When the sidebar is expanded, the Content menu triggers on the down event. In Readability, the Text Size and Margin Size options trigger on the down event. Donate Pop-up examples: The Custom Amount edit field triggers on the down event. The edit fields trigger on the down event (Your comment, First name, etc.).
2.5.3 Label in Name	Partially Supports	Most user interface components that include a visible text label also have accessible names that match (or include) the visible text in the label. In the citation pop-up, the citation dropdown box does not have an accessible name. In the page attribution pop-up, the page attribution dropdown box does not have an accessible name.
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	Partially Supports	The default primary language is correctly specified as "en" and matches the default human language of the page. However, content authors do not have the option to change the primary language to match the default human language on the page.
3.1.2 Language of Parts	Supports	The human language for content matches the default human language of the page.
3.2.1 On Focus	Partially Supports	When some interface components receive focus, there are unexpected changes of context that occur (for example, a new window is launched or focus is moved to another interface component). In the Donate pop-up, when the Custom Amount edit field receives keyboard focus, the amount selected is unselected. Navigating the credit card edit fields with the keyboard triggers an error message that freezes the form.
3.2.2 On Input	Supports	Changing the value of form elements does not initiate an unexpected change of context.
3.3.1 Error Identification	Supports	The item in error is identified in text and sufficiently described to the user in text.
3.3.2 Labels or Instructions	Partially Supports	Labels or instructions are not provided for each form element or the label or instruction is not visible when the form field has focus. Examples: in the Donate pop-up, the Custom Amount field.
4.1.1 Parsing	Partially Supports	There are markup validation errors on the page. The potential impact of the errors for users is reported as part of the results in the respective success criteria. For example, incorrectly structured lists are reported in 1.3.1 Info and Relationships.
4.1.2 Name, Role, Value	Partially Supports	The page content does not update or change automatically. The page does not provide notification of each form-related change in content. In the citation pop-up, the citation dropdown box does not have an accessible name to notify users of the changes in content. In the page attribution pop-up, the page attribution dropdown box does not have an accessible name to notify users of the changes in content. Donate Pop-up examples: when the Custom Amount edit field receives keyboard focus, the amount selected is unselected. The page does not 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. Examples: the Sign in link; the PDF link; the Readability link; the Cite this page link. Sidebar examples: In Readability, the Reset to Default Settings button does not provide notification that the sidebar will close. Donate Pop-up examples: The page does not provide notification that the selected amount is removed when the keyboard focus enters the Custom amount edit field. Frames are not used. iframes to not have titles that describe the contents or purpose. On 1.1: Project Overview, the iframe with the video does not have a title attribute. Also, the video content has a <title> tag "YouTube" that is not descriptive.

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)	Partially Supports	No audio description is provided for meaningful visual information that is part of the synchronized media. Examples: URLs for resources; LibreTexts Mission Statement; What is OER? 5R definitions; Content Development flowchart.
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	Partially Supports	Some form elements that accept an individual's personal data used on the page have inaccurate or missing autocomplete attributes. Examples: First Name, Last Name, and Email address edit fields.
1.4.10 Reflow	Does Not Support	Some page content is not viewable at a width of 320px. Examples: the Cite this page menu is obscured; the annotation sidebar obscures part of the page; the sidebar panel obscures part of the page; the search field, Remixer, Downloads, Single Sign On and sign in options are not available. Sidebar examples: in the Sidebar, parts of the scientific calculator are obscured. Donate Pop-up examples: label for Custom Amount is obscured; information about making a donation is obscured, button and text; month and day of credit card is obscured; postal code text is obscured.
1.4.11 Non-text Contrast	Does Not Support	The visual boundaries used as the only means of indicating some active user component's hit area do not have color contrast of at least 3 to 1 with the adjacent background. Examples: In the Sidebar, in Resources, the visual boundary of the edit field for the scientific calculator does not have sufficient color contrast. The visual state of some active user interface components do not have sufficient contrast of 3 to 1 with the adjacent background: the focused states of links that use a light blue dotted line; the focused and hovered states of the edit fields (Search, username, and password); the hover states of the Remixer, Downloads, SSO, and Sign in links; the focused and hovered state of the Sign in button; the hovered states of links in Contents and the focused states of the links in Contents (with the light blue dotted lines); the focused and hovered state of the Forgot password link; and the focused and hovered states of the chapter links. Sidebar examples: The visual state of some active user interface components do not have sufficient contrast of 3 to 1 with the adjacent background: in Contents, the grey on white text of the hovered state of links and the focused state of the links; the hovered and selected state of the expanded and collapsed icons; the black on dark blue text of a hovered link in the Sidebar when collapsed and the focused state (white on light grey); in Tools, the focused and hovered states of the links; the focused and hovered state of the collapse Sidebar button; the focused state of the Contents dropdown and the focused and hovered states of the Contents dropdown menu items; the focused and hovered states of most of the elements in the Readability tab; in Resources, the focused and hovered states of the properties dropdown menu for the periodic table and the focused states of the elements; in the properties pop-up, the focused states of the links and close button; and in the Libraries, the focused and hovered states of the menus and links. In the scientific calculator, the hovered states of the buttons do not have sufficient color contrast. Donate Pop-up examples: Active user interface components with states that do not have sufficient contrast of 3 to 1 with the adjacent background: in the Donate pop-up, the focused state of the Previous and Next buttons; the focused state of the check boxes (Write us a comment, etc.); and the focused state of the Custom Amount edit field. Parts of graphics required to understand the content do not have a contrast ratio of 3 to 1 against adjacent colors. Examples: in the Sidebar, the hovered and selected state of the expanded and collapsed icons.
1.4.12 Text Spacing	Supports	The spacing between letters, words, lines of text and/or paragraphs can be adjusted.
1.4.13 Content on Hover or Focus	Does Not Support	The tooltips on the page do not allow the user to move the pointer over that same additional content without the additional content disappearing (the tooltips associated with the links are not hoverable). The tooltips for the Previous and Next page buttons are not hoverable, dismissible, or focusable. The tooltips for the links and buttons on the page are not focusable. Donate Pop-up examples: The information tooltips are not dismissible or hoverable.
1.4.3 Contrast (Minimum)	Does Not Support	Some text does not have sufficient color contrast. Examples: white text on blue background, "Check out our new LibreCommons search portal", "Downloads", and Downloads menu items; blue text on light blue background, "Contents"; and grey text on white background, "Last Updated"; the Remixer and Downloads links text when hovered with the mouse; the text in the Contents when hovered with the mouse.; the Forgot password text. The white on blue text in the General overview of the LibreVerse image does not have sufficient color contrast. Sidebar examples: in the Contents, the green on white text (indicating that current page) does not have sufficient color contrast; in the Readability, the light blue on white link text. Donate Pop-up examples: The Donate button text does not have sufficient color contrast.
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	Partially Supports	Images of text are used on the pages without ensuring the meaningful information is provided in another way. On 1.1: Project Overview, the text in the overview of the LibreVerse image is not provided in another way (as text in the caption or on the page).
2.4.5 Multiple Ways	Supports	At least two ways are provided to locate a web page within a set of web pages, excluding web pages that are the result of, or a step in, a process (for example, taking an exam).
2.4.6 Headings and Labels	Supports	Labels for form elements sufficiently describe the purpose and applicable data requirements. Headings on the page describe the topic or purpose of its content.
2.4.7 Focus Visible	Does Not Support	A visible indication of focus is not provided when focus is on some interface components. Examples of interface components without a visible indication of focus: in the Contents, the expand and collapse buttons; the PDF menu items; the Download menu items; the Readability link; the Cite This page menu items; the previous page and next page links at the end of the page content (after Hypothesis). Donate Pop-up examples: Components without a visible indication of focus include the Next button, the Powered by link, and the Donate button.
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)	Not Evaluated	This success criterion will be evaluated and the ACR updated.
4.1.3 Status Messages	Supports	Status messages are not used. This success criterion is not applicable.

Table 3: Revised 508 Standards

Success Criterion	Conformance Level	Remarks and Explanations
503.4 User Controls for Captions and Audio Description	Does Not Support	The media player does not provide audio description controls. Controls for captions on the media player are provided at the same menu level as the user controls for volume.
503.4.1 Caption Controls	Supports	Controls for captions on the media player are provided at the same menu level as the user controls for volume.
503.4.2 Audio Description Controls	Supports	The media player does not have user controls for program selection. The success criterion is not applicable.
504.2.1 Preservation of Information Provided for Accessibility in Format Conversion	Does Not Support	When converting content to PDF, the LibreTexts PDF export function does not preserve the information required for accessibility to the extent that the information is supported by the PDF format. LibreTexts will be implementing the EPUB3 format to improve the accessibility conformance of exported content.
504.2.2 PDF Export	Supports	The LibreTexts PDF export function is not capable of exporting PDF files that conform to PDF 1.7. This success criterion is not applicable.
Conforming Alternate Version	Supports	There is only one version of the page 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.

Search

Text Color

Text Size

Margin Size

Font Type