Skip to main content
Chemistry LibreTexts

LibreTexts Libraries Accessibility Conformance Report

  • Page ID
    433033
  • \( \newcommand{\vecs}[1]{\overset { \scriptstyle \rightharpoonup} {\mathbf{#1}} } \) \( \newcommand{\vecd}[1]{\overset{-\!-\!\rightharpoonup}{\vphantom{a}\smash {#1}}} \)\(\newcommand{\id}{\mathrm{id}}\) \( \newcommand{\Span}{\mathrm{span}}\) \( \newcommand{\kernel}{\mathrm{null}\,}\) \( \newcommand{\range}{\mathrm{range}\,}\) \( \newcommand{\RealPart}{\mathrm{Re}}\) \( \newcommand{\ImaginaryPart}{\mathrm{Im}}\) \( \newcommand{\Argument}{\mathrm{Arg}}\) \( \newcommand{\norm}[1]{\| #1 \|}\) \( \newcommand{\inner}[2]{\langle #1, #2 \rangle}\) \( \newcommand{\Span}{\mathrm{span}}\) \(\newcommand{\id}{\mathrm{id}}\) \( \newcommand{\Span}{\mathrm{span}}\) \( \newcommand{\kernel}{\mathrm{null}\,}\) \( \newcommand{\range}{\mathrm{range}\,}\) \( \newcommand{\RealPart}{\mathrm{Re}}\) \( \newcommand{\ImaginaryPart}{\mathrm{Im}}\) \( \newcommand{\Argument}{\mathrm{Arg}}\) \( \newcommand{\norm}[1]{\| #1 \|}\) \( \newcommand{\inner}[2]{\langle #1, #2 \rangle}\) \( \newcommand{\Span}{\mathrm{span}}\)\(\newcommand{\AA}{\unicode[.8,0]{x212B}}\)

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

    Name of Product and Version

    LibreTexts Libraries

    Report Date

    March 2023

    Product Description

    The LibreTexts Libraries are an online textbook platform.

    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
    • Search a LibreTexts textbook by keywords
    • Use tools and resources in the LibreTexts Toolbar
    • Download a PDF version of a LibreTexts online textbook.

    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 110 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 2023) screen reading software with the Chrome browser version 110.

    Applicable Standards and Guidelines

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

    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) 46 92%
    Partially Supports (labeled in yellow) 3 6%
    Does Not Support (labeled in red) 1 2%
    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

    All meaningful images on the page had alt-text descriptions or accessible names that provided equivalent description for the meaningful image and/or referred to a description in the page content, and LibreTexts provides content authors with the tools to include alternative text descriptions for meaningful images.

    Decorative images on the page did not have alt-text descriptions or accessible names, and LibreTexts provides content authors with the tools to label images decorative.

    When background images were used on the page to provide meaningful information, the meaningful information is communicated in another accessible way.

    CAPTCHA images were not used on the pages.

    1.2.1 Audio-only and Video-only (Prerecorded) Supports

    LibreTexts supports the Able Player media player so that authors may provide transcripts with a complete and accurate representation of the audio-only content.

    LibreTexts supports the Able Player media player so that authors may provide text or audio alternatives with a complete and accurate representation of the video-only content.

    1.2.2 Captions (Prerecorded) Supports

    LibreTexts supports the Able Player media player so that authors may provide accurate closed captions for prerecorded synchronized media.

    1.2.3 Audio Description or Media Alternative (Prerecorded) Supports

    LibreTexts supports the Able Player media player so that authors may provide audio description for prerecorded synchronized media.

    1.3.1 Info and Relationships Supports

    The combination of the accessible name, accessible description, and other programmatic associations (for example, table column and/or row associations, or location in a hierarchical list structure) described each input field on the page and included all relevant instructions and cues (textual and graphical).  Radio buttons and checkboxes were programmatically associated with their question and response.

    Each programmatically determinable heading was a visual heading on the page, but a few visual headings were not programmatically determinable.  In the search section, the visually apparent headings "Searching in …" were not programmatically determinable.  The Search section is a feature from a third-party template that will either be updated by the supplier or replaced with an accessible  custom Search feature.

    Programmatic headings logically matched the visual heading presentation within the page heading structure.  Headings level 5 and level 6 were reserved for container boxes for content such as definitions and examples.

    Most content that had the visual appearance of a list was defined programmatically as a list, according to the type of list (<ul>, <ol>, or <dl>), and most programmatic list relationships, including nesting and hierarchies, were consistent with the list relationships presented visually.  In the Resources menu, the programmatic list was 3 items but there were only 2 items that were visible.  However, users of screen reading software could review the list to verify the number of items in the list.

    When all caps were used for text on the page, the text in all caps was an acronym (or other term requiring all caps).

    When an acronym was used on the page, the abbreviated term was spelled out the first time it was used, and when an acronym was used in a heading on the page, the abbreviated term was spelled out in the section that follows.

    When italics were used for text on the page, the use of italics was required by a style format used for text on the page.

    Bold (or <strong>) text was not used on the page as the only means of conveying meaning.

    LibreTexts provides content authors with tools to create programmatic data tables.

    LibreTexts provides content authors with tools to label column and row headers in data tables.

    Layout tabls were not used.

    When meaningful information was provided on the page by the use of the CSS pseudo-elements ::before or ::after, equivalent information was usually provided on the page in another way.  In the Reference and Cite and in the Help modal dialog boxes, the close button icon was added using the CSS pseudo-element ::before without providing equivalent information on the page in another way.

    1.3.2 Meaningful Sequence Supports

    The sequence and meaning of the content (in context) was understandable without CSS positioning.

    1.3.3 Sensory Characteristics Supports

    When instructions on the page use shape, size, location, orientation, or sound to convey meaning, another method that did not rely on sensory characteristics was provided.

    1.4.1 Use of Color Supports

    When color is used on the page to convey information, indicate an action, prompt a response or distinguish a visual element, another visual, onscreen method is used to convey the information which does not use color.

    When links on the page were only distinguished by color, the link text had a color contrast ratio of at least 3.0:1 with surrounding text.

    1.4.2 Audio Control Supports

    There was no audio content on the page that plays automatically.  This success criterion was not applicable. 

    2.1.1 Keyboard Supports

    Most functionality on the page could be accessed and executed using only the keyboard, and most essential information could be accessed via keyboard interaction, or the information was not available elsewhere on the page.

    Tooltips for the Skip to main content link, the Jump back to the top of this article link, and for the Previous and Next page navigation links using the title attribute were not accessible with the keyboard, but the tooltips matched the link text.  Tooltips for the Previous and Next page links (arrow icons) were not accessible with the keyboard, but there were alternative page navigation links in the page content that were accessible with the keyboard.

    A keyboard method was provided for functionality to be activated without requiring users to perform specific timings for activation.  The timing of the keystrokes was not required to activate the element (for example, the speed at which a button that is part of viewing a session was activated, and there was no timing dependent functionality).

    2.1.2 No Keyboard Trap Supports

    Keyboard focus could be moved away from an element on the page, and keyboard focus could be moved away from each section of the page containing elements (and was not trapped in a “loop”, preventing access to other elements on the page) by using either using standard navigation keys.

    2.1.4 Character Key Shortcuts Supports

    Single key character shortcuts were not used on the pages.  This success criterion was not applicable.  

    2.2.1 Timing Adjustable Supports

    Content on the pages did not have time limits.  This success criterion was not applicable.  

    2.2.2 Pause, Stop, Hide Supports

    Content on the pages did not continue moving for more than 5 seconds without a mechanism to pause, stop, or hide the content. This success criterion was not applicable.

    There was no automatically updating content on the page. This success criterion was not applicable.

    2.3.1 Three Flashes or Below Threshold Supports

    There was no flashing content on the pages.

    2.4.1 Bypass Blocks Supports

    Pages had a skip navigation link to bypass repetitive content that was keyboard-accessible, and when activated, the method worked and the block of content was bypassed.

    2.4.2 Page Titled Supports

    A page <title> element was defined for each web page.

    The <title> element of the web page identified its contents or purpose.

    2.4.3 Focus Order Supports

    The focus order preserved the meaning and operability of the pages (for example, focus order followed the logical order of operation, normally top to bottom, and left to right).

    When a modal dialog box was open, the visual focus remained within the modal dialog box until it was closed.

    When the keyboard was used to trigger controls that revealed hidden content, either: 1. Keyboard focus moved directly to revealed content; or 2. One additional keystroke moved the focus to revealed content.

    When page content was hidden or dismissed, either: 1. Keyboard focus automatically returned to the logical sequence of focus order before the content was revealed; or 2. One additional keystroke or keystroke combination returned focus to the logical sequence of focus order before the content was revealed.

    2.4.4 Link Purpose (In Context) Partially Supports

    For some links and buttons, the combination of the programmatically determined link or button context (text that is in the same paragraph, list, or table cell as the link or button or in a table header cell that is associated with the table cell that contains the link or button) and the accessible name or accessible description for the link or button on the page did not provide adequate description of the link or button’s purpose.

    In the Reference & Cite modal dialog box, the accessible names for the Copy to Clipboard buttons were not unique and did not include the associated headings, either Cite or License & Attribution.

    The accessible names for the page navigation links at the bottom of the page did not include Previous page and Next page.  The accessible names for the page navigation arrow links did not include Previous page and Next page.

    In the search section, the accessible names for the "more" buttons did not include the associated result.  The Search section is a feature from a third-party template that will either be updated by the supplier or replaced with an accessible custom Search feature.

    The links in the Periodic table to element summary information did not link to the specific sections (use the links to sections that open in new tabs, such as Carbon physical description).  The Periodic Table is content from a third-party.  LibreTexts will share the issue with the third-party and request that the Periodic table links be updated by the supplier.

    2.5.1 Pointer Gestures Supports

    All functionality on the page that could be operated with a pointer could be operated with single-pointer actions.  Path-based or multi-point gestures were not required to operate any functionality unless a multipoint or path-based gesture was essential.

    2.5.2 Pointer Cancellation Supports

    For functionality on the pages that could be operated using a single-pointer, the down-event of the pointer was not used to execute any part of the function.

    2.5.3 Label in Name Supports

    All user interface components on the pages, including form elements, that included a visible text label or an image of text as a label, had accessible names that matched (or included) the visible text in the label.

    All links and buttons on the pages that included a visible text label or an image of text as a label, had accessible names that matched (or included) the visible text in the label.

    2.5.4 Motion Actuation Supports

    No functionality on the pages was implemented that could be triggered by motion actuation.  This success criterion was not applicable.

    3.1.1 Language of Page Supports

    The default primary language was correctly specified and matched the default human language of each page.

    3.1.2 Language of Parts Supports

    LibreTexts provides content authors with the option to label parts of content with the correct human language tag.

    3.2.1 On Focus Supports    

    When an interface component received focus, there were no unexpected changes of context that occurred (for example, a new window was launched or focus was moved to another interface component).

    3.2.2 On Input Supports

    Changing the value of form elements on the page did not initiate an unexpected change in context.  (A change was not unexpected if either: 1. The user was notified that a change of context was about to occur; or 2. The control was clearly intended to initiate a change in context when activated.)

    3.3.1 Error Identification Supports

    There was no error detection on the pages.  This success criterion was not applicable.

    3.3.2 Labels or Instructions Supports

    Labels or instructions were provided for each form element (the label or instruction was visible when the form field had focus and at all times).

    4.1.1 Parsing Supports

    The pages had HTML and CSS passing concerns in these 4 specific criteria: 1. elements had complete start and end tags; 2. elements were nested according to their specifications; 3. elements did not contain duplicate attributes; 4. IDs were unique, except where the specifications allow these features.

    4.1.2 Name, Role, Value Supports

    When any content updates or changes automatically, then: 1. The page notifies the user about a change via a keyboard-accessible dialog; or 2. The page moves focus to the content that has changed, and the content that has changed provides sufficient description about the change; or 3.  The content that has changed is contained in an ARIA Live Region.

    The accessible name of most input fields on the pages described its state.  In the Table of Contents, the accessible names for the "Show submenu …" buttons did not identify the state (expanded or collapsed).  In the Resources menu, the Periodic Table button and the Physics Constants button did not announce the states correctly.  When they corresponding panels were closed, the buttons still announced "expanded".

    Each page provided notification of each form-related change in content on the page by either: 1. The user’s action directly resulted in the change in content, and the interface component that triggered the change provided sufficient description about the change event or the page moved focus to the content that had changed, and the content that had changed provided sufficient description about the change.

    LibreTexts provides content authors with tools to create descriptive links.

    Frames were not used on the page.

    LibreTexts provides content authors with the option to include a frame title using the title attribute.

    Table 2: WCAG 2.1 Level AA

    Success Criterion Conformance Level Remarks and Explanations
    1.2.4 Captions (Live) Supports

    Live synchronized media is not used in LibreTexts.  This success criterion was not applicable.

    1.2.5 Audio Description (Prerecorded) Supports

    LibreTexts supports the Able Player media player so that authors may provide audio description for prerecorded synchronized media.

    1.3.4 Orientation Supports

    Orientation of the content was not locked to either landscape or portrait, unless a specific orientation was essential for the functionality: 1. The visual display of the content in portrait display adjusted to the landscape orientation; and 2. All content and functionality that were available in portrait orientation were still available somewhere within the web site in landscape orientation (not necessarily on the same screen).

    1.3.5 Identify Input Purpose Supports

    Form elements that accept an individual's personal data were not used on the pages.  This success criterion was not applicable.

    1.4.10 Reflow Does Not Support

    When the viewport is set to 320 CSS pixels wide (or when page content at 1280 CSS pixels wide was magnified to 400% with browser settings), there was some loss of information or functionality, except for parts of the content which required two-dimensional layout for usage or meaning.

    The Search button and Toolbar button required horizontal scrolling to view.  The Toolbar menus required horizontal scrolling to view and some of the menu items were partially obscured.

    The tooltips for the Previous and Next page (arrow icons) were mostly obscured.  The text for the previous and next page links was partially obscured and the tooltips using the title attribute for the links did not magnify.

    1.4.11 Non-text Contrast Partially  Supports

    The color contrast of each possible visual state of an active user interface component on the page, including but not limited to focused, hovered, checked, selected, unselected, and pressed, and the contrast of images or icons used for the component that were required to understand the purpose of the component, did not maintain a color contrast ratio of at least 3.0:1 in all states, except if the contrast of the state was the default color set by the browser.

    In the Reference & Cite modal dialog box, the unfocused states of the Copy to Clipboard buttons had a color contrast ratio of 1.5:1 instead of at least 3.0:1.

    In the Table of Contents, the unfocused and hovered states of some links and buttons did not have a color contrast ratio of at least 3.0:1, but the link and button text and icons had sufficient color contrast in all states.

    In the Search section, the unfocused state of the Submit Search button had a color contrast ratio of 1.5:1 instead of at least 3.0:1.  In the Search section, the unfocused, focused, and hovered states of the search input field did not have color contrast ratios of at least 3.0:1.

    In the Periodic Table panel and in the Physics Constants panel, the unfocused states of the minimize, grow or shrink, and close panel buttons had a color contrast ratio of 1.5:1 instead of at least 3.0:1.  

    1.4.12 Text Spacing Supports

    With no loss of content or functionality, the spacing between letters, words, lines of text and/or paragraphs on the page could be adjusted to: 1. Line height (1.5 times the font size); and 2. Spacing following paragraph (at least 2 times the font size); and 3. Letter spacing (at least .12 times the font size); and 4. Word spacing (at least .16 times the font size).

    1.4.13 Content on Hover or Focus Supports

    Additional content triggered by the pointer hover or keyboard focus that became visible and then hidden was dismissible, hoverable, and persistent.

    Tooltips for the Skip to main content link, the Jump back to the top of this article link, and for the Previous and Next page links using the title attribute were not hoverable, but the tooltips matched the link text.  Tooltips for the Previous and Next page navigation links (arrow icons) were not hoverable or dismissible, but there were alternative page navigation links with dismissible tooltips that matched the link text.

    1.4.3 Contrast (Minimum) Supports

    All text and images of text on the page had sufficient color contrast, meaning a contrast ratio of: 4.5:1 for regular text; 3.0:1 for large text (18pt and larger, or 14pt and larger if it is bold); 3.0:1 for links and body text when color was used as the only way of distinguishing links from body text on the page.

    1.4.4 Resize text Partially Supports

    For each page, when the text on the page was resized using the browser settings to at least 200% of its original size, some text was clipped, truncated or obscured and or all functionality was not available.

    The link text for the Previous and Next page links was partially obscured.  Tooltips for the Skip to main content link, Jump to the top of the page link, and for the Previous and Next page links using the title attribute did not magnify.

    1.4.5 Images of Text Supports

    When images of text were used on the page, the image of text could not be replaced with text (such as, logos, type samples, branding, or images of specific fonts that are not widely supported).

    2.4.5 Multiple Ways Supports

    For each web page within a set of related web pages that was not a result of, or a step in, a process there were at least two ways to locate the web page within the site, a search option and table of contents.

    2.4.6 Headings and Labels Supports

    Each form label was sufficiently clear and descriptive so users knew the purpose of the form element and what input data was expected (the label included applicable data requirements).  The hamburger menu icon was a sufficiently clear label for the Table of Contents button and the button had an aria-label, Table of contents.  In addition, a version with a text label will be added as part of a future update.

    Each visually identified heading on the page described the topic or purpose of its content.

    2.4.7 Focus Visible Supports

    There was a visible indication of focus when each interface element received focus.

    3.2.3 Consistent Navigation Supports

    Each repeated component on the page occurred in the same relative order with regard to other repeated components on each web page where it appeared.

    3.2.4 Consistent Identification Supports

    The accessible name and description were consistent for components on the pages that performed the same function within a set of web pages.

    3.3.3 Error Suggestion Supports

    There was no automatic error detection on the pages.  This success criterion was not applicable.

    3.3.4 Error Prevention (Legal, Financial, Data) Supports

    Users were not required to submit user form entries on the pages that resulted in or caused legal commitments or financial transactions, submit entries that modified or deleted user-controllable data in a data storage system, or to submit test responses.  This success criterion was not applicable.

    4.1.3 Status Messages Supports

    When status messages were used on the pages, status messages could be programmatically determined through role or properties such that they could be presented to the user by assistive technologies without receiving focus.  When a status message advised on the success or results of an action, or the state of an application, role="status" was used.  When a status message conveyed a suggestion, or a warning on the existence of an error, role="alert" was used.

    In the search section, the status message "About 'x' results" did not have role="status".  The Search section is a feature from a third-party template that will either be updated by the supplier or replaced with an accessible custom Search feature.

    Table 3: Revised 508 Standards

    Success Criterion Conformance Level Remarks and Explanations
    503.4 User Controls for Captions and Audio Description Supports

    LibreTexts supports the Able Player media player so that authors may provide user controls for closed captions and audio descriptions.

    503.4.1 Caption Controls Supports

    LibreTexts supports the Able Player media player so that authors may provide the user controls for captions at the same menu level as the volume controls or program selection controls.

    503.4.2 Audio Description Controls Supports

    LibreTexts supports the Able Player media player so that authors may provide the user controls for audio descriptions at the same menu level as program selection controls or volume.

    504.2.1 Preservation of Information Provided for Accessibility in Format Conversion Does Not Support

    When converting content to PDF, LibreTexts' PDF export function did not preserve the information required for accessibility to the extent that the information is supported by the PDF format.  EPUB 3 is being implemented to improve accessibility of the converted format.

    504.2.2 PDF Export Supports

    The LibreTexts PDF export function was not capable of exporting PDF files that conform to PDF 1.7.  This success criterion was not applicable.

    Conforming Alternate Version Supports

    The Reader View provides a more accessible alternative for many users.

    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.


    LibreTexts Libraries Accessibility Conformance Report is shared under a CC BY-SA 4.0 license and was authored, remixed, and/or curated by LibreTexts.

    • Was this article helpful?