LibreStudio Accessibility Conformance Report

Name of Product and Version

LibreStudio

Report Date

February 2022

Product Description

The LibreTexts LibreStudio is an H5P activity content authoring tool and a catalog of H5P activities available in the LibreTexts Libraries.

Contact Information

Information About LibreTexts

Notes

This report is based on sample content, as of the date of this report, that students and instructors would use to:

Search the online catalog for H5P activities
Navigate to H5P activities by Subject and Collection
Review H5P activities
Register for a LibreStudio account
Login to use the H5P activity content authoring tool.

Evaluation Methods Used

LibreTexts LibreStudio 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 99 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 catalog content using JAWS for Windows (version 2022) screen reading software with the Chrome browser version 99.

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.

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)	34	61%
Partially Supports (labeled in yellow)	18	32%
Does Not Support (labeled in red)	4	7%
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	Partially Supports	Not all meaningful images have alt-text descriptions. On the Homepage, the LibreStudio logo has alt-text that is not recognized. The aria-label will be removed so that assistive technology may recognize the alt-text. In the pop-up for each resource, LibreText logo will be added as the alt-text to the image. On the Collections pages, the LibreStudio logo in the Shared by information will be converted into a background image. On the User Profile pages, alt-text will be used instead of title attributes to provide the description of meaningful images. Most decorative images do not have alt-text descriptions. On the Subject Library pages, alt-text description "card image cap" will be removed from decorative images. Most of the time, when background images that represent meaningful information are used, the information is presented as an accessible alternative. On the Collection Pages, a text label with the equivalent information that is provided by the resource type icons will be added. On the User Registration page, in the Organization / Institution field, a text label with the equivalent information that is provided by the search icon will be added. 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. This success criterion is not applicable.
1.2.2 Captions (Prerecorded)	Supports	There is no prerecorded synchronized media in the sample reviewed. This success criterion is not applicable.
1.2.3 Audio Description or Media Alternative (Prerecorded)	Supports	There is no prerecorded synchronized media in the sample reviewed. This success criterion is not applicable.
1.3.1 Info and Relationships	Partially Supports	Not all form fields are described with accessible names, descriptions, or other programmatic associations that include all relevant instructions and cues (textual and graphical). On the Homepage and other pages, under Subject and License, accessible names for the check boxes will be updated to include the label Subject or License, and accessible names will be added to the edit fields for Tags, Author, Keyword, and Type. Not all programmatically determinable headings are a visual heading. On the Homepage and other pages, the Pagination heading level 4 will be added as a visual heading. Not all visual headings are programmatically determinable. On the Homepage, Subject, Tags, Author, Keyword, Type, and License are visual headings that will be converted to programmatic headings. On the Homepage and other pages, in the pop-up for each resource, Shared by will be converted to a visual heading level 2. On the Collections Library page, Title, Subject, Created On, Last Updated, Shared in Library, and ID will be converted to headings level 2. On the Collections pages, Subject, License, H5P Type, Created On, Last Updated, Shared in Library, Accessibility, Bookmarked, and H5P ID will be converted to headings level 2. Programmatic headings do not match the visual heading structure of the page. On the Homepage, the heading level 1 LibreStudio H5P Library, the heading level 2 Resources, and the heading level 2 Search Filters will be added, and the toggle button text will be converted to headings level 3. On the Subject Library page, a heading level 1 LibreStudio H5P Library by Subjects will be added, and the subject titles will be converted to headings level 2. On the Collections page, a heading level 1 LibreStudio H5P Library and a heading level 2 Collections will be added, the collection titles will be converted to headings level 3, a heading level 2 Search Filters will be added, and the toggle button text will be converted to headings level 3. On the Subject pages, a heading level 2 Resources will be added before the list of resources. On the Collection pages, a heading level 1 with the title of the Collection will be added and the title of the Collection as a heading level 2 will be removed. On the Collection pages, the subtitles (for example, 1: Introduction to Science) will be converted to headings level 2 instead of headings level 3 and the text Collection will be removed from the list of resources. On the Resource Pages, a heading level 1 with the title of the resource will be added. On the User Profile pages, the organization name will be converted to normal text instead of a heading level 3. Not all visually apparent lists are correctly structured programmatic lists. On the Homepage and other pages, the details that are part of each resource will be converted to programmatic lists and the filters will be converted to programmatic lists. On the Collection Library page, the description of the number of resources will be added as a list item in the list of details, and the tags for each collection will be converted into programmatic lists. On the User Profile pages, the empty unordered lists will be removed from the bottom of the page content. All caps are not used for text that is not acronyms. Italics is not used for text on the page. Bold text is not used as the only means of conveying meaning. Data tables are not used. Layout tables are not used. Some meaningful information is provided by the CSS pseudo-elements ::before or ::after without providing the information an another way. On the Homepage, the collapse and expand icons will be updated to not use ::after or the information will also be provided in another way. On the Register page and other pages, the * will be included as text instead of using ::after.
1.3.2 Meaningful Sequence	Supports	The reading order of the content is correct and the meaning of the content is preserved without CSS positioning.
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	Partially Supports	Not all functionality can be accessed and executed using only the keyboard. On the Homepage and other pages, the pop-ups to preview resources, the tooltips for the resource type icons, and the tooltips for the pagination menu items will be updated to work with the keyboard or replaced with text labels or instructions. 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	Supports	There is no keyboard trap.
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	Content does not continue moving for more than 5 seconds without a mechanism to pause, stop, or hide the content. 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	A keyboard-accessible method to bypass repetitive content is provided but it is not working (the keyboard focus does not move to the main content on the page). On the Homepage and other pages, an anchor with id="main-content" will be added to ensure the keyboard-accessible method that is provided skips repetitive content.
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	The focus order preserves the meaning and operability of the page. When the keyboard is used to trigger controls that reveal hidden content, focus is moved to the revealed content. When some page content is hidden or dismissed, focus does not returns to a logical sequence. The Homepage and other pages will be updated so that when the pop-up with a resource is dismissed, the focus will return to the link that opened the pop-up. The Resource page will be updated so that when the pop-up with the accessibility information is dismissed, the focus will return to the link that opened the pop-up.
2.4.4 Link Purpose (In Context)	Partially Supports	The purpose of some links or buttons cannot be programmatically determined. On the Homepage and other pages, links labeled open_in_new will be updated to include the name of the resource. On the Homepage and other pages, under Subject and License, the accessible names of the Select All and Select None links will be updated to include Subject or License, and the accessible name for the LibreStudio link will be updated to include home. On the Homepage and other pages, the title attributes will be removed from pagination and other links. On the Homepage and other pages, the resource title will be added to the accessible name of the View Details button in the pop-up for each resource, and in the pop-up for each resource, the LibreStudio logo link will be removed. On the Subject Library page, links labeled View all resources will be updated to include the name of the Subject. On the Collection Library page, the View Collection link will be removed because they are duplicates. On the Subject pages, links labeled bookmark_add will be updated to include the name of the resource, and the Subject link will be removed. On the Resource pages, in the Shared by information, the LibreStudio logo link will be removed, and Subject Library will be added to the programmatic label for the subject link (for example, Language Subject Library). On the Resource pages, the question type (for example, Usable with Workarounds, accessibility information for H5P Type Question Set) will be added to the accessibility links.
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	Partially Supports	Not all user interface components that include a visible text label have accessible names that match (or include) the visible text in the label. On the Homepage and other pages, under Subject and License, the accessible names for the check boxes will be updated to include the label Subject or License, and the edit fields for Tags, Author, Keyword, and Type will be updated with accessible names that include the text labels.
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 and matches the default human language of the page.
3.1.2 Language of Parts	Partially Supports	The human language for content does not always match the default human language of the page. On the Homepage and other pages, when the default human language is correctly specified as English, resource titles in Spanish and French will be updated with the correct human language tag.
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 form elements does not initiate an unexpected change of context.
3.3.1 Error Identification	Partially Supports	Some items in error are identified in text but not sufficiently described to the user in text. On the Register page, when the Display Name is not completed by the user, the error message in text will be updated to indicate that the error is associated with the Display Name field, and the error message will be updated to describe all the errors detected with the form entries. On the Login page, when the Email or username field is not completed by the user, the error message in text will be updated to indicate that the error is associated with the Email or username field, and the error message will be updated to describe all the errors detected with the form entries. On the Password Reset page, when the Email field is not completed by the user, the error message in text will be updated to indicate that the error is associated with the Email field.
3.3.2 Labels or Instructions	Supports	Labels or instructions are provided for each form element and the label or instruction is visible when the form field has focus.
4.1.1 Parsing	Partially Supports	The pages were tested with the W3C Markup Validation Service. There are several errors and warnings than will be addressed.
4.1.2 Name, Role, Value	Partially Supports	The page content does not update or change automatically. The pages provide notification of each form-related change in content. The 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. The iframes in the pop-ups for each resource to not have titles that describe the purpose or contents of the iframe. On the Homepage and other pages, the resource title will be added to the iframe label.

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	There is no prerecorded synchronized media. This success criterion is not applicable.
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	The purpose for some common input fields that collect an individual's personal data is not programmatically defined based on the list of 53 Input Purposes for User Interface Components. On the Register page, the email autocomplete attribute will be added to the Email field. On the Login page, the email or username autocomplete attributes will be added to the email and username fields. On the Password Reset page, the email autocomplete attribute will be added to the Email field.
1.4.10 Reflow	Does Not Support	Some page content and functionality are not viewable at 320 pixels (400% magnification) without requiring horizontal scrolling. On the Homepage and other pages, the navigation menu items will be updated so that they will scroll with the keyboard and mouse. On the Subject pages, the page header with the LibreStudio logo and navigation menu blocks will be updated os that content on the pages is not obscured, and resource details will be updated so that horizontal scrolling is not required to view the information. On the Register page, the Organization or Institution list items will be updated so that they are are visible and the list will be updated so that it scrolls using the keyboard. On the Resource pages, in the accessibility pop-up, the accessibility status will be updated so that it si visible.
1.4.11 Non-text Contrast	Partially Supports	The visual boundaries used as the only means of indicating an active user component's hit area do not all have color contrast of at least 3 to 1 with the adjacent background. On the homepage, the Tags, Author, Keyword, and Type edit fields' visual boundaries will be updated to have at least 3 to 1 color contrast with the background color. On the Collections page, the Tags and Keyword edit fields' visual boundaries will be updated to have at least 3 to 1 color contrast with the background color. The visual state of some active user interface components do not have sufficient contrast of 3 to 1 with the adjacent background. On the Homepage and other pages, the focused and hovered states of the open_in_new links, the focused states of the pagination links, and the focused and hovered states of similar links will be updated to have at least a 3 to 1 color contrast with the background color. Parts of graphics required to understand the content have a contrast ratio of 3 to 1 against adjacent colors.
1.4.12 Text Spacing	Partially Supports	The spacing between some letters and words can be adjusted but the spacing between some lines of text and/or paragraphs cannot be adjusted. On the Homepage and other pages, paragraph spacing will be updated so that it can be adjusted.
1.4.13 Content on Hover or Focus	Partially Supports	Some tooltips on the pages 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). Some tooltips on the pages do not allow the user to dismiss the content without moving the pointer or keyboard focus (the tooltips are not dismissible). On the Homepage and other pages, the tooltips for resource type icons that are not hoverable or dismissible and the tooltips for the page menu that are not hoverable will be removed.
1.4.3 Contrast (Minimum)	Does Not Support	Not all text has sufficient contrast. On the Homepage and other pages, text colors will be updated to ensure sufficient contrast and the smallest font size used on the pages will be updated to a minimum of the equivalent of 12 point font size.
1.4.4 Resize Text	Does Not Support	When page content is resized to at least 200% using the browser magnification, there is some loss of content or functionality. On the Homepage and other pages, when the page content is resized to at least 200% using the browser magnification, the filters button will be updated to function with both the keyboard and mouse, the filters toggles will be updated so that they are visible, the tooltips for the pagination links will be removed, the unfocused and hovered states of the navigation menu will be updated to have color contrast of at least 3 to 1, and the resource type icons will be updated to magnify along with the page content. On the Subject Library page and other pages, when the page content is resized to at least 200% using the browser magnification, the content will be updated so that it is not obscured and so that it uses word wrapping. On the Subject pages and other pages, when the page content is resized to at least 200% using the browser magnification, the content will be updated so that the resource type icons magnify along with the page content or so that the information is provided using text that magnifies. On the Register page, when the page content is resized to at least 200% using the browser magnification, the content will be updated so that the Organization or Institution list items are visible and the list will be updated so that it scrolls using the keyboard.
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	Partially Supports	Only one way is 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). The site will be updated to include at least a second way to locate pages within the LibreStudio set of web pages (for example, by adding a site map), except when a page is a step in a process.
2.4.6 Headings and Labels	Partially Supports	Not all labels for form elements are sufficiently descriptive. On the Register page and other pages, the instructions for the form fields will be updated to provide more information, the instructions for each field will be placed before the field, and a description of the meaning of the * will be included. Not all headings on the pages describe the topic or purpose of its content. On the Collections Library, the headings that describe the number of resources will be converted to normal text or a list item in the list of details. On the Collection and Resource pages, the heading that is the name of the individual who shared the collection will be converted to normal text (as a link). On the User Profile page, the organization name will be converted into normal text instead of a heading level 3.
2.4.7 Focus Visible	Partially Supports	A visible indication of focus is not provided when focus is on some interface components. On the Register page and other pages, a visible indication of focus will be added to the skip to main content link.
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	Partially Supports	The description of errors does not contain adequate information for the user to know what is required to correct errors in form fields. On the Register page and other pages, the descriptions of errors will be updated to include the name of the field that has an error.
3.3.4 Error Prevention (Legal, Financial, Data)	Supports	Users are not required to submit user form entries that result in or cause legal commitments or financial transactions, submit entries that modify or delete user-controllable data in a data storage system, or to submit test responses. This support criterion is not applicable.
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	There is no media player. This success criterion is not applicable.
503.4.1 Caption Controls	Supports	There is no media player. This success criterion is not applicable.
503.4.2 Audio Description Controls	Supports	There is no media player. This success criterion is not applicable.
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 PDF export function. 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