Adobe Learning Manager Accessibility Conformance Report International Edition.
(Based on VPAT® Version 2.5)
Product Information
- Name of Product/Version: Adobe Learning Manager – Web Learner
- Product Description: Learning Management System (LMS) which delivers personalized learning experiences across multiple devices for enterprise-wide learning initiatives.
- Date: December 2025
- Contact information: Access@adobe.com
- Notes: The information contained in this report applies to the product itself. Information about product help and support documentation is located at: http://www.adobe.com/accessibility/compliance.html.
- Evaluation Methods Used: Testing ALM Web Learner involved extensive use of leading assistive technology such as screen readers, screen magnifiers, and speech recognition software, as well exclusive use of the keyboard. Native platform accessibility features were also used to assist with testing. These were supplemented with techniques such as manual inspection of Accessibility API output.
Applicable Standards/Guidelines
This report covers the degree of conformance for the following accessibility standard/guidelines:
Standard/Guideline
Included In Report
Level A (Yes)
Level AA (Yes)
Level AAA (No)
Level A (Yes)
Level AA (Yes)
Level AAA (No)
Level A (Yes)
Level AA (Yes)
Level AAA (No)
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: The product has not been evaluated against the criterion. This can only be used in WCAG Level AAA criteria.
WCAG 2.2 Report
Tables 1 and 2 also document conformance with:
- EN 301 549: Chapter 9 - Web, Sections 10.1-10.4 of Chapter 10 - Non-Web documents, and Sections 11.1-11.4 and 11.8.2 of Chapter 11 - Non-Web Software (open and closed functionality), and Sections 12.1.2 and 12.2.4 of Chapter 12 – Documentation
- Revised Section 508: Chapter 5 – 501.1 Scope, 504.2 Content Creation or Editing, and Chapter 6 – 602.3 Electronic Support Documentation.
Note: When reporting on conformance with the WCAG 2.2 Success Criteria, they are scoped for full pages, complete processes, and accessibility-supported ways of using technology as documented in the WCAG 2.2 Conformance Requirements.
Table 1: Success Criteria, Level A
Notes:
Guideline 1.1 Text Alternatives:
Provide text alternatives for any non-text content so that it can be changed into other forms people need, such as large print, braille, speech, symbols or simpler language.
1.1.1 Non-text Content (Level A)
Also applies to:
EN 301 549 Criteria
- 9.1.1.1 (Web)
- 10.1.1.1 (Non-web document)
- 11.1.1.1.1 (Open Functionality Software)
- 11.1.1.1.2 (Closed Functionality Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
Web: Partially Supports
Authored Content (PDF): Supports (Not Applicable)
Authored Content (SCORM): Supports (Not Applicable)
Authored Content (Video): Supports (Not Applicable)
Web: The product provides sufficient text alternatives for most instances of the application. Exceptions include: Some informative images do not have a text alternative, so people who are blind and/or use a screen reader will not be able to access the information conveyed by the image. This occurs on the following pages: Learner - Course Completed; Learner - Course Not Completed; Learner - Course Overview; Learner - Catalog; Learner - My Learning.
Authored Content (PDF): Authored content does not contain non-text content that would require a text alternative.
Authored Content (SCORM): Authored content does not contain non-text content that would require a text alternative.
Authored Content (Video): Authored content does not contain non-text content that would require a text alternative.
Guideline 1.2 Time-based Media:
Provide alternatives for time-based media.
1.2.1 Audio-only and Video-only (Prerecorded) (Level A)
Also applies to:
EN 301 549 Criteria
- 9.1.2.1 (Web)
- 10.1.2.1 (Non-web document)
- 11.1.2.1.1 (Open Functionality Software)
- 11.1.2.1.2.1 and 11.1.2.1.2.2 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
Web: Supports (Not Applicable)
Authored Content (PDF): Supports
Authored Content (SCORM): Supports
Authored Content (Video): Supports
Web: The product does not contain prerecorded audio-only or video-only media.
Authored Content (PDF): Authored content does not contain prerecorded audio-only or video-only media.
Authored Content (SCORM): Authored content does not contain prerecorded audio-only or video-only media.
Authored Content (Video): Authored content does not contain prerecorded audio-only or video-only media.
1.2.2 Captions (Prerecorded) (Level A)
Also applies to:
EN 301 549 Criteria
- 9.1.2.2 (Web)
- 10.1.2.2 (Non-web document)
- 11.1.2.2 (Open Functionality Software)
- 11.1.2.2 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
Web: Supports (Not Applicable)
Authored Content (PDF): Supports (Not Applicable)
Authored Content (SCORM): Supports (Not Applicable)
Authored Content (Video): Supports
Web: The product does not contain prerecorded synchronized media.
Authored Content (PDF): Authored content does not contain prerecorded synchronized media.
Authored Content (SCORM): Authored content does not contain prerecorded synchronized media.
Authored Content (Video): Authors can preserve closed captions for audio content in video
1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A)
Also applies to:
EN 301 549 Criteria
- 9.1.2.3 (Web)
- 10.1.2.3 (Non-web document)
- 11.1.2.3.1 (Open Functionality Software)
- 11.1.2.3.2 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
Web: Supports (Not Applicable)
Authored Content (PDF): Supports (Not Applicable)
Authored Content (SCORM): Supports (Not Applicable)
Authored Content (Video): Supports
Web: The product does not contain prerecorded video content that would require audio description or a media alternative.
Authored Content (PDF): Authored content does not contain video content that would require audio description or a media alternative.
Authored Content (SCORM): Authored content does not contain video content that would require audio description or a media alternative.
Authored Content (Video): Authors can provide [closed audio description | open audio description | transcripts] for video.
Guideline 1.3 Adaptable:
Create content that can be presented in different ways (for example simpler layout) without losing information or structure.
1.3.1 Info and Relationships (Level A)
Also applies to:
EN 301 549 Criteria
- 9.1.3.1 (Web)
- 10.1.3.1 (Non-web document)
- 11.1.3.1.1 (Open Functionality Software)
- 11.1.3.1.2 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
Web: Partially Supports
Authored Content (PDF): Partially Supports
Authored Content (SCORM): Partially Supports
Authored Content (Video): Partially Supports
Web: Most visual structure and relationship information is provided through element semantics, object information or in text. Exceptions include:
Some sets of radio buttons are not programmatically grouped, so the group label for each set of radio buttons will not be conveyed to people who are blind and/or use a screen reader and they will not understand the purpose of the individual radio buttons. This occurs on the following pages: Learner - Course Completed; Learner - Course Overview.
Some heading levels are out of order, so the structure of the content is not properly conveyed to assistive technologies and people who are blind and/or use a screen reader. This occurs on the following pages: Learner - My Learning; Learner - Catalog.
Some text that visually functions as a heading is not marked up as a heading, so the structure of the content is not properly conveyed to assistive technologies and people who are blind and/or use a screen reader. This occurs on the following pages: Learner - Course Overview; Learner - Leaderboard; Learner – Skills.
Some HTML lists contain elements in the code that are not allowed in a programmatic list, so the structure and/or content of each list is not correctly conveyed to people who are blind and/or use a screen reader or other assistive technology. This occurs on the following pages: Global Header; Learner - Course Not Completed.
Content that is visually presented as a list is not properly marked up as a list, so the structure of the list is not correctly conveyed to assistive technologies and people who are blind and/or use a screen reader. This occurs on the following page: Learner - Course Not Completed.
Content that is visually presented as a list is not properly marked up as a list, so the structure of the list is not correctly conveyed to assistive technologies and people who are blind and/or use a screen reader. This occurs on the following page: Learner - Home Page.
Some elements' programmatic role requires that the element have a parent element, but the parent element is missing, so people who are blind and/or use a screen reader or other assistive technology may not be able to understand the purpose or content of the element without the context provided by the parent. This occurs on the following pages: Global Header; Learner - Leaderboard.
Multiple elements' programmatic role requires one or more child element(s) but the child element(s) is/are missing, so people who are blind and/or use a screen reader or other assistive technology may not be able to understand the purpose or content of the element or its related content. This occurs on the following pages: Global Header; Learner - Home Page.
Authored Content (PDF): The product does not allow authors to provide appropriate programmatic or textual equivalents for most visual structure and relationship information, such as:
Visual heading text is not marked as heading.
Some elements' programmatic role requires that the element have a parent element, but the parent element is missing, so people who are blind and/or use a screen reader or other assistive technology may not be able to understand the purpose or content of the element without the context provided by the parent.
Multiple elements' programmatic role requires one or more child element(s) but the child element(s) is/are missing, so people who are blind and/or use a screen reader or other assistive technology may not be able to understand the purpose or content of the element or its related content.
Authored Content (SCORM): The product does not allow authors to provide appropriate programmatic or textual equivalents for most visual structure and relationship information, such as:
Visual heading text is not marked as heading.
Content is arranged visually like a data table, but it is not programmatically marked up as a table, so the table's structure and relationships are not conveyed to people who are blind and/or use a screen reader.
Some elements' programmatic role requires that the element have a parent element, but the parent element is missing, so people who are blind and/or use a screen reader or other assistive technology may not be able to understand the purpose or content of the element without the context provided by the parent.
Multiple elements' programmatic role requires one or more child element(s) but the child element(s) is/are missing, so people who are blind and/or use a screen reader or other assistive technology may not be able to understand the purpose or content of the element or its related content.
Authored Content (Video): Authors can provide only visible text equivalents, not programmatic equivalents, for most visual structure and relationship information, such as:
Visual heading text is not marked as heading.
Some elements' programmatic role requires that the element have a parent element, but the parent element is missing, so people who are blind and/or use a screen reader or other assistive technology may not be able to understand the purpose or content of the element without the context provided by the parent.
Multiple elements' programmatic role requires one or more child element(s) but the child element(s) is/are missing, so people who are blind and/or use a screen reader or other assistive technology may not be able to understand the purpose or content of the element or its related content.
1.3.2 Meaningful Sequence (Level A)
Also applies to:
EN 301 549 Criteria
- 9.1.3.2 (Web)
- 10.1.3.2 (Non-web document)
- 11.1.3.2.1 (Open Functionality Software)
- 11.1.3.2.2 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
Web: Partially Supports
Authored Content (PDF): Does Not Support
Authored Content (SCORM): Supports
Authored Content (Video): Supports
Web: The product presents most content in a meaningful sequence. Exceptions include:
The correct reading order of dynamically changing content is not programmatically determinable by screen readers, so people who are blind and/or use a screen reader may not be made aware of new or changed content that is dynamically added to a page. This occurs on the following page: Learner – Leaderboard.
Screen reader focus does not follow the visual focus order or does not move to the intended target, so the reading order for people who are blind and/or use a screen reader may not follow the visual organization of the page. This occurs on the following pages: Learner - My Learning; Learner - Catalog.
Authored Content (PDF): The product does not create PDF documents with tags for accessibility which results in documents that may not have the appropriate meaningful sequence.
Authored Content (SCORM): The product allows authors to present content in a meaningful sequence.
Authored Content (Video): The product allows authors to present content in a meaningful sequence.
1.3.3 Sensory Characteristics (Level A)
Also applies to:
EN 301 549 Criteria
- 9.1.3.3 (Web)
- 10.1.3.3 (Non-web document)
- 11.1.3.3 (Open Functionality Software)
- 11.1.3.3 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
Web: Supports
Authored Content (PDF): Supports
Authored Content (SCORM): Supports
Authored Content (Video): Supports
Web: Instructions do not rely solely on sensory characteristics.
Authored Content (PDF): Authors can ensure that content meets this criterion.
Authored Content (SCORM): Authors can ensure that content meets this criterion.
Authored Content (Video): Authors can ensure that content meets this criterion.
Guideline 1.4 Distinguishable:
Make it easier for users to see and hear content including separating foreground from background.
1.4.1 Use of Color (Level A)
Also applies to:
EN 301 549 Criteria
- 9.1.4.1 (Web)
- 10.1.4.1 (Non-web document)
- 11.1.4.1 (Open Functionality Software)
- 11.1.4.1 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
Web: Does Not Support
Authored Content (PDF): Supports
Authored Content (SCORM): Supports
Authored Content (Video): Supports
Web: Most functions of the product convey information through color alone. Examples include:
Color is the only visual method used to identify a link, and a link text's contrast ratio with the color of the surrounding text is less than 3:1, so people who are colorblind or have low vision may not be able to identify the link. This occurs on the following pages: Learner - Badges; Global Header.
Color is used as the only method to convey the state (such as "checked," "pressed," or "selected") of some controls, so that information will not be available to people who are colorblind and people who are blind and/or use a screen reader. This occurs on the following pages: Learner - Course Completed; Learner - Course Not Completed; Learner - Course Overview; Learner - Skills; Learner - Catalog; Learner - My Learning.
Authored Content (PDF): Authors can ensure that content meets this criterion.
Authored Content (SCORM): Authors can ensure that content meets this criterion.
Authored Content (Video): Authors can ensure that content meets this criterion.
1.4.2 Audio Control (Level A)
Also applies to:
EN 301 549 Criteria
- 9.1.4.2 (Web)
- 10.1.4.2 (Non-web document)
- 11.1.4.2 (Open Functionality Software)
- 11.1.4.2 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
Web: Supports (Not Applicable)
Authored Content (PDF): Supports (Not Applicable)
Authored Content (SCORM): Supports (Not Applicable)
Authored Content (Video): Supports (Not Applicable)
Web: The product does not contain audio that plays automatically.
Authored Content (PDF): Authored content does not contain audio that plays automatically.
Authored Content (SCORM): Authored content does not contain audio that plays automatically.
Authored Content (Video): Authored content does not contain audio that plays automatically.
Guideline 2.1 Keyboard Accessible:
Make all functionality available from a keyboard.
2.1.1 Keyboard (Level A)
Also applies to:
EN 301 549 Criteria
- 9.2.1.1 (Web)
- 10.2.1.1 (Non-web document)
- 11.2.1.1.1 (Open Functionality Software)
- 11.2.1.1.2 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
Web: Partially Supports
Authored Content (PDF): Supports
Authored Content (SCORM): Does Not Support
Authored Content (Video): Supports
Web: Most product functionality can be operated through a keyboard interface. Exceptions include:
Multiple functions cannot be performed using only the keyboard, so people who use the keyboard alone to navigate and operate content cannot use these functions. This occurs on the following pages: Learner - Course Overview; Learner - Catalog; Learner - Course Completed; Learner - My Learning; Learner - Home Page.
Authored Content (PDF): Authored content does not contain audio that plays automatically.
Authored Content (SCORM): Some product functionality can be operated through a keyboard interface. Exceptions include:
A function cannot be performed using only the keyboard, so people who use the keyboard alone to navigate and operate content cannot use this function. Drag and drop functionality of the control.
Authored Content (Video): Authored content does not contain audio that plays automatically.
2.1.2 No Keyboard Trap (Level A)
Also applies to:
EN 301 549 Criteria
- 9.2.1.2 (Web)
- 10.2.1.2 (Non-web document)
- 11.2.1.2 (Open Functionality Software)
- 11.2.1.2 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
Web: Supports
Authored Content (PDF): Supports
Authored Content (SCORM): Supports
Authored Content (Video): Supports
Web: The product does not include keyboard traps.
Authored Content (PDF): Authored content does not include keyboard traps.
Authored Content (SCORM): Authored content does not include keyboard traps.
Authored Content (Video): Authored content does not include keyboard traps.
2.1.4 Character Key Shortcuts (Level A 2.1 and 2.2)
Also applies to:
EN 301 549 Criteria
- 9.2.1.4 (Web)
- 10.2.1.4 (Non-web document)
- 11.2.1.4.1 (Open Functionality Software)
- 11.2.1.4.2 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508 – Does not apply
Web: Supports (Not Applicable)
Authored Content (PDF): Supports (Not Applicable)
Authored Content (SCORM): Supports (Not Applicable)
Authored Content (Video): Supports (Not Applicable)
Web: The product does not provide character key shortcuts.
Authored Content (PDF): Authored content does not provide character key shortcuts.
Authored Content (SCORM): Authored content does not provide character key shortcuts.
Authored Content (Video): Authored content does not provide character key shortcuts.
Guideline 2.2 Enough Time:
Provide users enough time to read and use content.
2.2.1 Timing Adjustable (Level A)
Also applies to:
EN 301 549 Criteria
- 9.2.2.1 (Web)
- 10.2.2.1 (Non-web document)
- 11.2.2.1 (Open Functionality Software)
- 11.2.2.1 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
Web: Supports (Not Applicable)
Authored Content (PDF): Supports (Not Applicable)
Authored Content (SCORM): Supports (Not Applicable)
Authored Content (Video): Supports (Not Applicable)
Web: The product does not include time limits.
Authored Content (PDF): Authored content does not include time limits.
Authored Content (SCORM): Authored content does not include time limits.
Authored Content (Video): Authored content does not include time limits.
2.2.2 Pause, Stop, Hide (Level A)
Also applies to:
EN 301 549 Criteria
- 9.2.2.2 (Web)
- 10.2.2.2 (Non-web document)
- 11.2.2.2 (Open Functionality Software)
- 11.2.2.2 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
Web: Supports (Not Applicable)
Authored Content (PDF): Supports (Not Applicable)
Authored Content (SCORM): Supports (Not Applicable)
Authored Content (Video): Supports
Web: The product does not include elements which move, blink, scroll, or auto-update.
Authored Content (PDF): Authored content does not include elements which move, blink, scroll, or auto-update.
Authored Content (SCORM): Authored content does not include elements which move, blink, scroll, or auto-update.
Authored Content (Video): Authors can ensure that content meets this criterion.
Guideline 2.3 Seizures:
Do not design content in a way that is known to cause seizures.
2.3.1 Three Flashes or Below Threshold (Level A)
Also applies to:
EN 301 549 Criteria
- 9.2.3.1 (Web)
- 10.2.3.1 (Non-web document)
- 11.2.3.1 (Open Functionality Software)
- 11.2.3.1 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
Web: Supports (Not Applicable)
Authored Content (PDF): Supports
Authored Content (SCORM): Supports
Authored Content (Video): Supports
Web: The product does not contain flashing content.
Authored Content (PDF): Authors can ensure that content does not flash.
Authored Content (SCORM): Authors can ensure that content does not flash.
Authored Content (Video): Authors can ensure that content does not flash.
Guideline 2.4 Navigable:
Provide ways to help users navigate, find content, and determine where they are.
2.4.1 Bypass Blocks (Level A)
Also applies to:
EN 301 549 Criteria
- 9.2.4.1 (Web)
- 10.2.4.1 (Non-web document) – Does not apply
- 11.2.4.1 (Open Functionality Software) – Does not apply
- 11.2.4.1 (Closed Software) – Does not apply
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software) – Does not apply to non-web software
- 504.2 (Authoring Tool)
- 602.3 (Support Docs) – Does not apply to non-web docs
Web: Supports
Authored Content (PDF): Supports (Not Applicable)
Authored Content (SCORM): Supports (Not Applicable)
Authored Content (Video): Supports (Not Applicable)
Web: The product provides a mechanism to bypass repeated blocks.
Authored Content (PDF): This criterion does not apply to non-web documents.
Authored Content (SCORM): Authored content does not contain repeated blocks that would require a skip mechanism.
Authored Content (Video): Authored content does not contain repeated blocks that would require a skip mechanism.
2.4.2 Page Titled (Level A)
Also applies to:
EN 301 549 Criteria
- 9.2.4.2 (Web)
- 10.2.4.2 (Non-web document)
- 11.2.4.2 (Open Functionality Software) - Does not apply
- 11.2.4.2 (Closed Software) – Does not apply
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
Web: Supports
Authored Content (PDF): Does Not Support
Authored Content (SCORM): Does Not Support
Authored Content (Video): Supports
Web: The titles of pages describe their purpose.
Authored Content (PDF): The product does not allow authors to customize the document title or display it in the window title.
Authored Content (SCORM): The containing modal dialog does not include a descriptive title.
Authored Content (Video): Authored video content is embedded in a web application iframe container. The title is a function of the container, not the authored content.
2.4.3 Focus Order (Level A)
Also applies to:
EN 301 549 Criteria
- 9.2.4.3 (Web)
- 10.2.4.3 (Non-web document)
- 11.2.4.3 (Open Functionality Software)
- 11.2.4.3 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
Web: Partially Supports
Authored Content (PDF): Supports
Authored Content (SCORM): Does Not Support
Authored Content (Video): Supports
Web: Most components receive focus in a meaningful order. Exceptions include:
Keyboard focus does not follow the visual focus order, or it does not move to the intended target, so people who use the keyboard to navigate content (including screen reader users) may become disoriented on the page. This occurs on the following pages: Learner - Catalog; Learner - My Learning.
Authored Content (PDF): Authors can ensure that content meets this criterion.
Authored Content (SCORM): Authored content does not meet this criterion.
Keyboard focus is lost or misplaced as a result of user interaction or content update, or refresh, so people who use the keyboard to navigate content (including screen reader users) will become disoriented.
Authored Content (Video): Authors can ensure that content meets this criterion.
2.4.4 Link Purpose (In Context) (Level A)
Also applies to:
EN 301 549 Criteria
- 9.2.4.4 (Web)
- 10.2.4.4 (Non-web document)
- 11.2.4.4 (Open Functionality Software)
- 11.2.4.4 (Closed Software
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
Web: Supports
Authored Content (PDF): Supports (Not Applicable)
Authored Content (SCORM): Supports (Not Applicable)
Authored Content (Video): Supports (Not Applicable)
Web: The purpose of links in the product can be determined from the link text alone or from the programmatic context of the link.
Authored Content (PDF): Authored content does not contain links.
Authored Content (SCORM): Authored content does not contain links.
Authored Content (Video): Authored content does not contain links.
Guideline 2.5 Input Modalities:
Make it easier for users to operate functionality through various inputs beyond keyboard
2.5.1 Pointer Gestures (Level A 2.1 and 2.2)
Also applies to:
EN 301 549 Criteria
- 9.2.5.1 (Web)
- 10.2.5.1 (Non-web document)
- 11.2.5.1 (Open Functionality Software)
- 11.2.5.1 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508 – Does not apply
Web: Supports (Not Applicable)
Authored Content (PDF): Supports (Not Applicable)
Authored Content (SCORM): Supports (Not Applicable)
Authored Content (Video): Supports (Not Applicable)
Web: The product does not rely on multipoint or path-based gestures.
Authored Content (PDF): Authored content does not rely on multipoint or path-based gestures.
Authored Content (SCORM): Authored content does not rely on multipoint or path-based gestures.
Authored Content (Video): Authored content does not rely on multipoint or path-based gestures.
2.5.2 Pointer Cancellation (Level A 2.1 and 2.2)
Also applies to:
EN 301 549 Criteria
- 9.2.5.2 (Web)
- 10.2.5.2 (Non-web document)
- 11.2.5.2 (Open Functionality Software)
- 11.2.5.2 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508 – Does not apply
Web: Supports
Authored Content (PDF): Supports
Authored Content (SCORM): Supports
Authored Content (Video): Supports
Web: Product functions that use a single pointer are completed when the user releases the pointer and allow the user to cancel the pointer action before completing the pointer click.
Authored Content (PDF): Authors can ensure that content meets this criterion.
Authored Content (SCORM): Authors can ensure that content meets this criterion.
Authored Content (Video): Authors can ensure that content meets this criterion.
2.5.3 Label in Name (Level A 2.1 and 2.2)
Also applies to:
EN 301 549 Criteria
- 9.2.5.3 (Web)
- 10.2.5.3 (Non-web document)
- 11.2.5.3.1 (Open Functionality Software)
- 11.2.5.3.2 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508 – Does not apply
Web: Supports
Authored Content (PDF): Does Not Support
Authored Content (SCORM): Does Not Support
Authored Content (Video): Does Not Support
Web: The accessible names of controls contain the text of their visible labels.
Authored Content (PDF): Authors provided accessible text does not contain the visual names for the user interface controls.
The accessible name of an interactive element (such as a link, button, or form input) does not contain the visible label, so people who use speech input to navigate and operate content will not be able to access the element.
Authored Content (SCORM): Authors provided accessible text does not contain the visual names for the user interface controls.
The accessible name of an interactive element (such as a link, button, or form input) does not contain the visible label, so people who use speech input to navigate and operate content will not be able to access the element.
Authored Content (Video): Authors provided accessible text does not contain the visual names for the user interface controls.
The accessible name of an interactive element (such as a link, button, or form input) does not contain the visible label, so people who use speech input to navigate and operate content will not be able to access the element.
2.5.4 Motion Actuation (Level A 2.1 and 2.2)
Also applies to:
EN 301 549 Criteria
- 9.2.5.4 (Web)
- 10.2.5.4 (Non-web document)
- 11.2.5.4 (Open Functionality Software)
- 11.2.5.4 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508 – Does not apply
Web: Supports (Not Applicable)
Authored Content (PDF): Supports (Not Applicable)
Authored Content (SCORM): Supports (Not Applicable)
Authored Content (Video): Supports (Not Applicable)
Web: The product does not have functionality operated by device motion or user motion.
Authored Content (PDF): Authored content does not have functionality operated by device motion or user motion.
Authored Content (SCORM): Authored content does not have functionality operated by device motion or user motion.
Authored Content (Video): Authored content does not have functionality operated by device motion or user motion.
Guideline 3.1 Readable:
Make text content readable and understandable.
3.1.1 Language of Page (Level A)
Also applies to:
EN 301 549 Criteria
- 9.3.1.1 (Web)
- 10.3.1.1 (Non-web document)
- 11.3.1.1.1 (Open Functionality Software)
- 11.3.1.1.2 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
Web: Supports
Authored Content (PDF): Supports
Authored Content (SCORM): Supports (Not Applicable)
Authored Content (Video): Supports (Not Applicable)
Web: The language is programmatically determinable within the product.
Authored Content (PDF): Authors can set the language of the document.
Authored Content (SCORM): Authored content is embedded in a web application iframe container. The language is a function of the container, not the authored content.
Authored Content (Video): Video file formats are not capable of containing a programmatically determined language.
Guideline 3.2 Predictable:
Make Web pages appear and operate in predictable ways.
3.2.1 On Focus (Level A)
Also applies to:
EN 301 549 Criteria
- 9.3.2.1 (Web)
- 10.3.2.1 (Non-web document)
- 11.3.2.1 (Open Functionality Software)
- 11.3.2.1 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
Web: Supports
Authored Content (PDF): Supports
Authored Content (SCORM): Supports
Authored Content (Video): Supports
Web: Components do not initiate a change of context when focused.
Authored Content (PDF): Authors can ensure that content meets this criterion.
Authored Content (SCORM): Authors can ensure that content meets this criterion.
Authored Content (Video): Authors can ensure that content meets this criterion.
3.2.2 On Input (Level A)
Also applies to:
EN 301 549 Criteria
- 9.3.2.2 (Web)
- 10.3.2.2 (Non-web document)
- 11.3.2.2 (Open Functionality Software)
- 11.3.2.2 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
Web: Supports
Authored Content (PDF): Supports
Authored Content (SCORM): Supports
Authored Content (Video): Supports
Web: Changes of context do not occur automatically on user input.
Authored Content (PDF): Authors can ensure that content meets this criterion.
Authored Content (SCORM): Authors can ensure that content meets this criterion.
Authored Content (Video): Authors can ensure that content meets this criterion.
3.2.6 Consistent Help (Level A 2.2 only)
EN 301 549 Criteria – Does not apply
Revised Section 508 – Does not apply
Web: Supports
Authored Content (PDF): Supports
Authored Content (SCORM): Supports
Authored Content (Video): Supports
Web: On application that contain help features (including human or automated contact options or self-help options), those features occur in the same order throughout the application.
Authored Content (PDF): Authors can ensure that content meets this criterion.
Authored Content (SCORM): Authors can ensure that content meets this criterion.
Authored Content (Video): Authors can ensure that content meets this criterion.
Guideline 3.3 Input Assistance:
Help users avoid and correct mistakes
3.3.1 Error Identification (Level A)
Also applies to:
EN 301 549 Criteria
- 9.3.3.1 (Web)
- 10.3.3.1 (Non-web document)
- 11.3.3.1.1 (Open Functionality Software)
- 11.3.3.1.2 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
Web: Partially Supports
Authored Content (PDF): Supports
Authored Content (SCORM): Supports
Authored Content (Video): Supports
Web: Most input errors are identified and described to the users in text. Exception includes:
A form field with an error is not identified in the text error message or a text alternative for an image, and the error message with the field name is not programmatically associated with the form field (so it is announced when a screen reader user navigates to the field), so people who are blind and/or use a screen reader will not be able to identify in which form field the error occurred. This occurs on the following page: Learner - Profile Settings.
Authored Content (PDF): Authored content does not contain user input controls which would require error identification.
Authored Content (SCORM): Authored content does not detect input errors that are displayed to users.
Authored Content (Video): Authored content does not contain user input controls which would require error identification.
3.3.2 Labels or Instructions (Level A)
Also applies to:
EN 301 549 Criteria
- 9.3.3.2 (Web)
- 10.3.3.2 (Non-web document)
- 11.3.3.2 (Open Functionality Software)
- 11.3.3.2 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
Web: Partially Supports
Authored Content (PDF): Partially Supports
Authored Content (SCORM): Partially Supports
Authored Content (Video): Partially Supports
Web: Labels are provided for most input fields. Exceptions include:
Some labels of elements are not persistent (always visible on the page), so each element's purpose may be difficult to discover. This occurs on the following page: Learner - Leaderboard.
The label for a select or dropdown control is missing, so the field's purpose is not clear. This occurs on the following page: Global Header.
Authored Content (PDF): Authored content contain user input controls that would require labels or instructions.
The label for a form field is missing, so the field's purpose is not clear.
Some labels of elements are not persistent (always visible on the page), so each element's purpose may be difficult to discover.
Authored Content (SCORM): Authored content contain user input controls that would require labels or instructions.
Some labels of elements are not persistent (always visible on the page), so each element's purpose may be difficult to discover.
Authored Content (Video): Authored content contain user input controls that would require labels or instructions.
Some labels of elements are not persistent (always visible on the page), so each element's purpose may be difficult to discover.
3.3.7 Redundant Entry (Level A 2.2 only)
EN 301 549 Criteria – Does not apply
Revised Section 508 – Does not apply
Web: Supports
Authored Content (PDF): Supports
Authored Content (SCORM): Supports
Authored Content (Video): Not Applicable
Web: If information previously entered by, or provided to, the user is required to be entered again in the same process, that information is either automatically populated or available for the user to select unless the previously entered information is no longer valid or re-entering the information is essential or required to ensure security.
Authored Content (PDF): Authors can ensure that content meets this criterion.
Authored Content (SCORM): Authors can ensure that content meets this criterion.
Authored Content (Video): Authors can ensure that no authored video content is included or required for this submission.
Guideline 4.1 Compatible:
Maximize compatibility with current and future user agents, including assistive technologies.
4.1.1 Parsing (Level A)
Applies to:
WCAG 2.0 and 2.1 – Always answer ‘Supports’
WCAG 2.2 (obsolete and removed) - Does not apply
EN 301 549 Criteria
- 9.4.1.1 (Web)
- 10.4.1.1 (Non-web document)
- 11.4.1.1.1 (Open Functionality Software)
- 11.4.1.1.2 (Closed Software) – Does not apply
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
Web: Supports
Authored Content (PDF): Supports (Not Applicable)
Authored Content (SCORM): Supports
Authored Content (Video): Supports (Not Applicable)
Web: Elements have complete start and end tags, elements are nested according to their specifications, elements do not contain duplicate attributes, and any IDs are unique.
Authored Content (PDF): The authored content is not implemented using markup languages.
Authored Content (SCORM): Elements have complete start and end tags, elements are nested according to their specifications, elements do not contain duplicate attributes, and any IDs are unique.
Authored Content (Video): The authored content is not implemented using markup languages.
4.1.2 Name, Role, Value (Level A)
Also applies to:
EN 301 549 Criteria
- 9.4.1.2 (Web)
- 10.4.1.2 (Non-web document)
- 11.4.1.2.1 (Open Functionality Software)
- 11.4.1.2.2 (Closed Software) – Does not apply
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
Web: Does Not Support
Authored Content (PDF): Partially Supports
Authored Content (SCORM): Partially Supports
Authored Content (Video): Partially Supports
Web: User interface components in some product functions do not provide programmatic ‘name, role, state, or value’ information. Examples include:
Multiple buttons do not have a programmatic name, so each button's name (such as "Submit" or "Cancel") is not conveyed to screen readers and other assistive technologies and will not be available to people who use those technologies. This occurs on the following pages: Learner - Catalog; Learner - My Learning; Learner - Course Not Completed.
Multiple buttons do not have a programmatic role and name, so each button's role (usually button, but sometimes link or something else) and its name (such as "Submit" or "Cancel") are not conveyed to screen readers and other assistive technologies and will not be available to people who use those technologies. This occurs on the following pages: Learner - Course Completed; Learner - Leaderboard.
A form control (such as a text input field or checkbox) is not programmatically associated with its visible label, so people who are blind and/or use a screen reader or other assistive technology may not be able to understand the purpose of the form control or what input it requires. This occurs on the following page: Learner – Leaderboard.
The HTML code for some links or buttons is nested inside the code of another link or button, so assistive technologies may not be able to determine the function of these elements. This occurs on the following page: Global Header.
A link does not have a programmatic role, so people who are blind and/or use a screen reader or other assistive technology may not be able to understand the purpose and function of the link or how to interact with it. This occurs on the following page: Learner - Home Page.
The programmatic state of some elements that reveal or hide content ("expanded" or "collapsed") is missing or is used incorrectly, so people who are blind and/or use a screen reader or other assistive technology will not be informed of the current state of each element or the state will be misrepresented. This occurs on the following pages: Learner - Course Not Completed; Learner - Leaderboard; Learner - Catalog; Learner - Course Completed; Learner - Course Overview.
For some elements that allow a user either to select or not select a single option (like a checkbox or radio buttons) or to select from among 2 or more options (like a select dropdown), the state (such as checked/unchecked or selected/not selected) is not conveyed to assistive technology, so people who are blind and/or use a screen reader or other assistive technology may not be able to understand the purpose of each element, the options available, and whether the element or an option is currently checked. This occurs on the following pages: Learner - Home Page; Learner - Profile Settings; Global Header; Learner - Course Not Completed.
A form input element does not have a programmatic name, so people who are blind and/or use a screen reader or other assistive technology may not be able to determine the name of the element and may not understand its purpose or how to interact with it. This occurs on the following page: Global Header.
An element that appears and functions like a combobox does not have the required attributes in its HTML code needed to provide its programmatic role, name, state, and other properties to assistive technology, so people who are blind and/or use a screen reader or other assistive technology may not be able to understand the name, purpose, or content of the element or how to interact with it. This occurs on the following page: Global Header.
An element that appears and functions like a listbox (which allows the user to select 1 or more options from a list of options) does not have the required attributes in its HTML code needed to provide the programmatic role, name, state, and other properties for the listbox and/or its options to assistive technology, so people who are blind and/or use a screen reader or other assistive technology may not be able to understand the name, purpose, or content of the listbox and its options or how to interact with them. This occurs on the following page: Learner - Leaderboard.
An element has an invalid attribute in its HTML code that is intended to provide its programmatic role, name, state, or another property to assistive technology, so people who are blind and/or use a screen reader or other assistive technology may not be able to understand the name, purpose, or content of the element or how to interact with it. This occurs on the following page: Learner - Home Page.
An element is missing one or more required attributes in its HTML code that would provide its programmatic role, name, state, or another property to assistive technology, so people who are blind and/or use a screen reader or other assistive technology may not be able to understand the name, purpose, or content of the element or how to interact with it. This occurs on the following page: Learner - Home Page.
Multiple elements do not have an attribute in their HTML code that will provide its programmatic state (such as "checked"/"not checked") to assistive technology or the state assigned is not correct, so people who are blind and/or use a screen reader or other assistive technology may not be able to understand the current state of the element or how to interact with it. This occurs on the following pages: Global Header; Learner - Course Completed; Learner - Course Overview.
The content of a tooltip cannot be accessed using a screen reader, so people who are blind and others who use a screen reader will not be able to read this content. This occurs on the following page: Learner - Course Completed.
Authored Content (PDF): Authored content does not provide programmatic name, role, state or value information.
For some elements that allow a user either to select or not select a single option (like a checkbox or radio buttons) or to select from among 2 or more options (like a select dropdown), the state (such as checked/unchecked or selected/not selected) is not conveyed to assistive technology, so people who are blind and/or use a screen reader or other assistive technology may not be able to understand the purpose of each element, the options available, and whether the element or an option is currently checked.
Multiple elements have an invalid attribute in its HTML code that is intended to provide its programmatic role, name, state, or another property to assistive technology, so people who are blind and/or use a screen reader or other assistive technology may not be able to understand the name, purpose, or content of each element or how to interact with it.
An element has an invalid attribute in its HTML code that is intended to provide its programmatic role, name, state, or another property to assistive technology, so people who are blind and/or use a screen reader or other assistive technology may not be able to understand the name, purpose, or content of the element or how to interact with it.
An element that appears and functions like a tree view widget that presents a hierarchical list does not have the required attributes in its HTML code needed to provide its programmatic role, name, state, and other properties to assistive technology, so people who are blind and/or use a screen reader or other assistive technology may not be able to understand name, purpose, structure, or content of the list or how to interact with it.
Authored Content (SCORM): Authored content does not provide programmatic name, role, state or value information.
For some elements that allow a user either to select or not select a single option (like a checkbox or radio buttons) or to select from among 2 or more options (like a select dropdown), the state (such as checked/unchecked or selected/not selected) is not conveyed to assistive technology, so people who are blind and/or use a screen reader or other assistive technology may not be able to understand the purpose of each element, the options available, and whether the element or an option is currently checked.
When a button is disabled, its disabled state is not conveyed programmatically, so people who are blind and/or use a screen reader or other assistive technology will not be informed that the button is disabled.
Multiple elements have an invalid attribute in its HTML code that is intended to provide its programmatic role, name, state, or another property to assistive technology, so people who are blind and/or use a screen reader or other assistive technology may not be able to understand the name, purpose, or content of each element or how to interact with it.
An element has an invalid attribute in its HTML code that is intended to provide its programmatic role, name, state, or another property to assistive technology, so people who are blind and/or use a screen reader or other assistive technology may not be able to understand the name, purpose, or content of the element or how to interact with it.
An element that appears and functions like a tree view widget that presents a hierarchical list does not have the required attributes in its HTML code needed to provide its programmatic role, name, state, and other properties to assistive technology, so people who are blind and/or use a screen reader or other assistive technology may not be able to understand name, purpose, structure, or content of the list or how to interact with it.
Authored Content (Video): Authored content contain controls that would require programmatically determined name, role, state, property, and value information.
For some elements that allow a user either to select or not select a single option (like a checkbox or radio buttons) or to select from among 2 or more options (like a select dropdown), the state (such as checked/unchecked or selected/not selected) is not conveyed to assistive technology, so people who are blind and/or use a screen reader or other assistive technology may not be able to understand the purpose of each element, the options available, and whether the element or an option is currently checked.
Multiple elements have an invalid attribute in its HTML code that is intended to provide its programmatic role, name, state, or another property to assistive technology, so people who are blind and/or use a screen reader or other assistive technology may not be able to understand the name, purpose, or content of each element or how to interact with it.
An element does not have an attribute in its HTML code that will provide its programmatic role to assistive technology or the role assigned is not correct (like assigning a button the role of "checkbox"), so people who are blind and/or use a screen reader or other assistive technology may not be able to understand the name, purpose, or content of the element or how to interact with it.
An element has an invalid attribute in its HTML code that is intended to provide its programmatic role, name, state, or another property to assistive technology, so people who are blind and/or use a screen reader or other assistive technology may not be able to understand the name, purpose, or content of the element or how to interact with it.
An element that appears and functions like a tree view widget that presents a hierarchical list does not have the required attributes in its HTML code needed to provide its programmatic role, name, state, and other properties to assistive technology, so people who are blind and/or use a screen reader or other assistive technology may not be able to understand name, purpose, structure, or content of the list or how to interact with it.
Table 2: Success Criteria, Level AA
Notes:
1.2.4 Captions (Live) (Level AA)
Also applies to:
EN 301 549 Criteria
- 9.1.2.4 (Web)
- 10.1.2.4 (Non-web document)
- 11.1.2.4 (Open Functionality Software)
- 11.1.2.4 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
Web: Supports (Not Applicable)
Authored Content (PDF): Supports (Not Applicable)
Authored Content (SCORM): Supports (Not Applicable)
Authored Content (Video): Supports (Not Applicable)
Web: The product does not contain live synchronized media.
Authored Content (PDF): Authored content does not contain live synchronized media.
Authored Content (SCORM): Authored content does not contain live synchronized media.
Authored Content (Video): Authored content does not contain live synchronized media.
1.2.5 Audio Description (Prerecorded) (Level AA)
Also applies to:
EN 301 549 Criteria
- 9.1.2.5 (Web)
- 10.1.2.5 (Non-web document)
- 11.1.2.5 (Open Functionality Software)
- 11.1.2.5 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
Web: Supports (Not Applicable)
Authored Content (PDF): Supports (Not Applicable)
Authored Content (SCORM): Supports (Not Applicable)
Authored Content (Video): Supports (Not Applicable)
Web: The product does not contain prerecorded video content that would require audio description.
Authored Content (PDF): Authored content does not contain video content that would require audio description.
Authored Content (SCORM): Authored content does not contain video content that would require audio description.
Authored Content (Video): Authors can create content which conforms to this criterion by providing open audio description or a link to an alternative that includes the required information.
1.3.4 Orientation (Level AA 2.1 and 2.2)
Also applies to:
EN 301 549 Criteria
- 9.1.3.4 (Web)
- 10.1.3.4 (Non-web document)
- 11.1.3.4 (Open Functionality Software)
- 11.1.3.4 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508 – Does not apply
Web: Supports
Authored Content (PDF): Supports
Authored Content (SCORM): Supports
Authored Content (Video): Supports
Web: Content does not restrict its view and operation to a single display orientation.
Authored Content (PDF): Responding to the display orientation is a function of the user’s viewer application, not the authored content.
Authored Content (SCORM): Content does not restrict its view and operation to a single display orientation
Authored Content (Video): Authored video content is embedded in a web application iframe container. Responding to the display orientation is a function of the container, not the authored content.
1.3.5 Identify Input Purpose (Level AA 2.1 and 2.2)
Also applies to:
EN 301 549 Criteria
- 9.1.3.5 (Web)
- 10.1.3.5 (Non-web document)
- 11.1.3.5.1 (Open Functionality Software)
- 11.1.3.5.2 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508 – Does not apply
Web: Supports (Not Applicable)
Authored Content (PDF): Supports (Not Applicable)
Authored Content (SCORM): Supports (Not Applicable)
Authored Content (Video): Supports (Not Applicable)
Web: The product does not contain input fields that collect information about the user.
Authored Content (PDF): Authored content does not contain input fields that collect information about the user.
Authored Content (SCORM): Authored content does not contain input fields that collect information about the user.
Authored Content (Video): Authored content does not contain input fields that collect information about the user.
1.4.3 Contrast (Minimum) (Level AA)
Also applies to:
EN 301 549 Criteria
- 9.1.4.3 (Web)
- 10.1.4.3 (Non-web document)
- 11.1.4.3 (Open Functionality Software)
- 11.1.4.3 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
Web: Does Not Support
Authored Content (PDF): Does Not Support
Authored Content (SCORM): Supports (Not Applicable)
Authored Content (Video): Supports (Not Applicable)
Web: Most text and images of regular meet minimum contrast requirements. Examples include:
The color contrast ratio between text and its background is less than 4.5:1 (or less than 3:1 for large text), so people who are colorblind or have low vision may have difficulty reading the text. This occurs on the following pages: Learner - Profile Settings; Learner - Badges; Global Header; Learner - Course Not Completed; Learner – Leaderboard.
The color contrast ratios on hover or focus between the text labels of some controls and their background are less than 4.5:1, so people who are colorblind or have low vision may have difficulty reading the text label of each control. This occurs on the following pages: Global Header; Learner - Course Completed; Learner - Course Not Completed; Learner - Course Overview; Learner - Leaderboard; Learner - Profile Settings.
The color contrast ratio between text placed over an image and that image is less than 4.5:1, so people who are colorblind or have low vision may have difficulty reading the text. This occurs on the following page: Learner - Profile Settings.
Authored Content (PDF): Authored content does not meet the text contrast requirements.
The color contrast ratio between text and its background is less than 4.5:1 (or less than 3:1 for large text), so people who are colorblind or have low vision may have difficulty reading the text.
Authored Content (SCORM): Authors can ensure that text meets contrast requirements.
Authored Content (Video): Authors can ensure that text meets contrast requirements.
1.4.4 Resize text (Level AA)
Also applies to:
EN 301 549 Criteria
- 9.1.4.4 (Web)
- 10.1.4.4 (Non-web document)
- 11.1.4.4.1 (Open Functionality Software)
- 11.1.4.4.2 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
Web: Partially Supports
Authored Content (PDF): Supports
Authored Content (SCORM): Supports
Authored Content (Video): Supports (Not Applicable)
Web: Using browser zoom, text can be resized up to 200 percent without loss of content or functionality for most content. Exceptions include:
Content is lost, clipped, or obscured when the page is zoomed to 200%, so people who have low vision and need to enlarge text to read it may not have access to that content. This occurs on the following pages: Global Header; Learner - Course Not Completed.
Authored Content (PDF): Using the zoom function of a PDF reader application, text can be resized up to 200 percent without loss of content or functionality.
Authored Content (SCORM): Using browser zoom, text can be resized up to 200 percent without loss of content or functionality.
Authored Content (Video): This criterion does not apply to captions or images of text in video.
1.4.5 Images of Text (Level AA)
Also applies to:
EN 301 549 Criteria
- 9.1.4.5 (Web)
- 10.1.4.5 (Non-web document)
- 11.1.4.5.1 (Open Functionality Software)
- 11.1.4.5.2 (Closed Software) – Does not apply
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
Web: Supports
Authored Content (PDF): Does Not Support
Authored Content (SCORM): Supports
Authored Content (Video): Supports (Not Applicable)
Web: The product uses text instead of images of text, except for branding elements that are considered essential.
Authored Content (PDF): Authors can ensure that content meets this criterion.
Authored Content (SCORM): Authors can ensure that content meets this criterion.
Authored Content (Video): A particular presentation is essential for images of text in video.
1.4.10 Reflow (Level AA 2.1 and 2.2)
Also applies to:
EN 301 549 Criteria
- 9.1.4.10 (Web)
- 10.1.4.10 (Non-web document)
- 11.1.4.10 (Open Functionality Software)
- 11.1.4.10 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508 – Does not apply
Web: Partially Supports
Authored Content (PDF): Does Not Support
Authored Content (SCORM): Does Not Support
Authored Content (Video): Does Not Support
Web: At the required width of 320 CSS pixels, most content is presented without loss of information or functionality, and without requiring scrolling in two dimensions. Exceptions include:
When the page is adjusted to an equivalent width of 320 pixels and content reflows to fit within the viewport, some content or functionality becomes unavailable, so people with low vision who increase the size of text and other content using the browser zoom will not be able to access all of the page's content and/or functionality. This occurs on the following pages: Global Header; Learner - Catalog; Learner - My Learning.
When the page is adjusted to an equivalent width of 320 pixels and content reflows to fit within the viewport, some content overlaps and cannot be seen or understood, so the overlapping content is not available to people with low vision who increase the size of text and other content using the browser zoom. This occurs on the following page: Learner - Course Not Completed.
When the page is adjusted to an equivalent width of 320 pixels and content reflows to fit within the viewport, some content does not fit horizontally, so it cannot be viewed without scrolling. People with low vision who increase the size of text and other content using the browser zoom may have difficulty accessing the content that can only be seen by horizontal scrolling. This occurs on the following pages: Learner - Home Page; Learner - Profile Settings.
Authored Content (PDF): At the required width of 320 CSS pixels, authored content is presented with loss of information or functionality.
When the page is adjusted to an equivalent width of 320 pixels and content reflows to fit within the viewport, some content overlaps and cannot be seen or understood, so the overlapping content is not available to people with low vision who increase the size of text and other content using the browser zoom.
Authored Content (SCORM): At the required width of 320 CSS pixels, content is presented with loss of information or functionality, and requiring scrolling in two dimensions.
When the page is adjusted to an equivalent width of 320 pixels and content reflows to fit within the viewport, some content overlaps and cannot be seen or understood, so the overlapping content is not available to people with low vision who increase the size of text and other content using the browser zoom.
Authored Content (Video): Authored content requires two-dimensional layout for meaning.
When the page is adjusted to an equivalent width of 320 pixels and content reflows to fit within the viewport, some content overlaps and cannot be seen or understood, so the overlapping content is not available to people with low vision who increase the size of text and other content using the browser zoom.
1.4.11 Non-text Contrast (Level AA 2.1 and 2.2)
Also applies to:
EN 301 549 Criteria
- 9.1.4.11 (Web)
- 10.1.4.11 (Non-web document)
- 11.1.4.11 (Open Functionality Software)
- 11.1.4.11 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508 – Does not apply
Web: Does Not Support
Authored Content (PDF): Does Not Support
Authored Content (SCORM): Does Not Support
Authored Content (Video): Does Not Support
Web: Most meaningful non-text content elements have sufficient contrast. Examples include:
Some icons (or parts of an icon required to understand its content) do not have a 3:1 color contrast ratio with the background or adjacent colors, so people who are colorblind or have low vision may not be able to understand the information presented by each icon. This occurs on the following pages: Learner - Catalog; Learner - Leaderboard; Learner - My Learning; Global Header.
The focus indicators of some interactive elements (like buttons or input fields) do not have a 3:1 color contrast ratio with the background, so people who are colorblind or have low vision may have difficulty perceiving when each interactive element is receiving focus. This occurs on the following pages: Learner - Leaderboard; Learner - Profile Settings; Global Header.
The indicators for the state of some interactive elements (like checkboxes or radio buttons) do not have a 3:1 color contrast ratio with the background, so people who are colorblind or have low vision may have difficulty in perceiving the state of the interactive elements. This occurs on the following pages: Learner - Course Overview; Learner - Course Completed; Left Navigation.
The visual boundaries of some interactive elements (like a radio button or input fields) do not have a 3:1 color contrast ratio with the background, so people who are colorblind or have low vision may have difficulty in perceiving the boundaries of the interactive element. This occurs on the following pages: Learner - Course Completed; Learner - Course Overview.
Authored Content (PDF): Authored content does not meet this criterion.
Some icons (or parts of an icon required to understand its content) do not have a 3:1 color contrast ratio with the background or adjacent colors, so people who are colorblind or have low vision may not be able to understand the information presented by each icon.
The indicators for the state of some interactive elements (like checkboxes or radio buttons) do not have a 3:1 color contrast ratio with the background, so people who are colorblind or have low vision may have difficulty in perceiving the state of the interactive elements
Authored Content (SCORM): Authored content does not meet this criterion.
Some icons (or parts of an icon required to understand its content) do not have a 3:1 color contrast ratio with the background or adjacent colors, so people who are colorblind or have low vision may not be able to understand the information presented by each icon.
The indicators for the state of some interactive elements (like checkboxes or radio buttons) do not have a 3:1 color contrast ratio with the background, so people who are colorblind or have low vision may have difficulty in perceiving the state of the interactive elements
Authored Content (Video): Authored content does not meet this criterion.
Some icons (or parts of an icon required to understand its content) do not have a 3:1 color contrast ratio with the background or adjacent colors, so people who are colorblind or have low vision may not be able to understand the information presented by each icon.
The indicators for the state of some interactive elements (like checkboxes or radio buttons) do not have a 3:1 color contrast ratio with the background, so people who are colorblind or have low vision may have difficulty in perceiving the state of the interactive elements.
The visual boundaries of some interactive elements (like a radio button or input fields) do not have a 3:1 color contrast ratio with the background, so people who are colorblind or have low vision may have difficulty in perceiving the boundaries of the interactive element.
1.4.12 Text Spacing (Level AA 2.1 and 2.2)
Also applies to:
EN 301 549 Criteria
- 9.1.4.12 (Web)
- 10.1.4.12 (Non-web document)
- 11.1.4.12 (Open Functionality Software)
- 11.1.4.12 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508 – Does not apply
Web: Partially Supports
Authored Content (PDF): Supports
Authored Content (SCORM): Supports
Authored Content (Video): Supports
Web: Most functions of the product support the required text style properties without loss of content or functionality. Exceptions include:
When text spacing is adjusted to help people with vision, reading, and/or cognitive disabilities, some content cannot be seen because it is cut off. This occurs on the following pages: Learner - Course Overview; Learner - My Learning; Learner - Catalog; Learner - Leaderboard.
Authored Content (PDF): Authors can ensure that content meets this criterion.
Authored Content (SCORM): Authors can ensure that content meets this criterion.
Authored Content (Video): Authors can ensure that content meets this criterion.
1.4.13 Content on Hover or Focus (Level AA 2.1 and 2.2)
Also applies to:
EN 301 549 Criteria
- 9.1.4.13 (Web)
- 10.1.4.13 (Non-web document)
- 11.1.4.13 (Open Functionality Software)
- 11.1.4.13 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508 – Does not apply
Web: Partially Supports
Authored Content (PDF): Supports
Authored Content (SCORM): Supports
Authored Content (Video): Supports
Web: In most cases when additional content is triggered by pointer hover or keyboard focus, that additional content can be dismissed and hovered over, and the content persists until the user dismisses it. Exceptions include:
Content that appears on mouse hover (such as tooltips, drop-down menus, or popups) disappears when the mouse pointer is moved over that content, meaning people with disabilities, especially people with low vision who need to magnify text, may not be able to read the additional content. This occurs on the following pages: Learner - Leaderboard; Learner - Skills.
Content that appears on mouse hover or keyboard focus (such as tooltips, drop-down menus, or popups) is not dismissible, so it obscures all or part of the original content on the page. This occurs on the following page: Learner – Skills.
Authored Content (PDF): Authored content does not contain elements triggered by hover or focus.
Authored Content (SCORM): Authored content does not contain elements triggered by hover or focus.
Authored Content (Video): Authored content does not contain elements triggered by hover or focus.
2.4.5 Multiple Ways (Level AA)
Also applies to:
EN 301 549 Criteria
- 9.2.4.5 (Web)
- 10.2.4.5 (Non-web document) – Does not apply
- 11.2.4.5 (Open Functionality Software) – Does not apply
- 11.2.4.5 (Closed Software) – Does not apply
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software) – Does not apply to non-web software
- 504.2 (Authoring Tool)
- 602.3 (Support Docs) – Does not apply to non-web docs
Web: Supports
Authored Content (PDF): Supports (Not Applicable)
Authored Content (SCORM): Supports
Authored Content (Video): Supports
Web: Users can locate web pages in the product.
Authored Content (PDF): This criterion does not apply to non-web documents.
Authored Content (SCORM): Authors can provide more than one way to locate a page in a set of pages.
Authored Content (Video): Authors can provide more than one way to locate a page in a set of pages.
2.4.6 Headings and Labels (Level AA)
Also applies to:
EN 301 549 Criteria
- 9.2.4.6 (Web)
- 10.2.4.6 (Non-web document)
- 11.2.4.6 (Open Functionality Software)
- 11.2.4.6 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
Web: Partially Supports
Authored Content (PDF): Supports
Authored Content (SCORM): Supports
Authored Content (Video): Supports
Web: Most of the headings and labels are descriptive. Exceptions include:
Multiple buttons have identical programmatic labels but different functionality, and there is no programmatic context, so people who are blind and/or use a screen reader will not know or may be confused or misled about what each button does. This occurs on the following pages: Learner - Skills; Learner - Catalog; Learner - Home Page; Learner - Profile Settings.
Multiple programmatic labels for controls or form input fields do not convey the purpose of the control or input, so people who are blind and/or use a screen reader may not understand what a control does or what data to enter. This occurs on the following pages: Learner - Catalog; Learner - Home Page; Learner - My Learning; Learner - Course Not Completed.
Authored Content (PDF): Authors can ensure that content meets this criterion.
Authored Content (SCORM): Authors can ensure that content meets this criterion.
Authored Content (Video): Authors can ensure that content meets this criterion.
2.4.7 Focus Visible (Level AA)
Also applies to:
EN 301 549 Criteria
- 9.2.4.7 (Web)
- 10.2.4.7 (Non-web document)
- 11.2.4.7 (Open Functionality Software)
- 11.2.4.7 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
Web: Partially Supports
Authored Content (PDF): Partially Supports
Authored Content (SCORM): Partially Supports
Authored Content (Video): Partially Supports
Web: Most focusable elements have a visible keyboard focus indicator. Exceptions include:
Multiple interactive elements (such as links, buttons, or form inputs) do not have a visual focus indicator, so sighted people who use a keyboard to navigate content will not know when those elements are receiving focus. This occurs on the following pages: Learner - Catalog; Learner - Course Overview; Learner - Skills; Learner - Profile Settings; Learner - Course Completed.
Authored Content (PDF): Control elements within the authored content lack visible indication of keyboard focus.
Multiple interactive elements (such as links, buttons, or form inputs) do not have a visual focus indicator, so sighted people who use a keyboard to navigate content will not know when those elements are receiving focus.
Authored Content (SCORM): Control elements within the authored content lack visible indication of keyboard focus.
Multiple interactive elements (such as links, buttons, or form inputs) do not have a visual focus indicator, so sighted people who use a keyboard to navigate content will not know when those elements are receiving focus.
Authored Content (Video): Control elements within the authored content lack visible indication of keyboard focus.
Multiple interactive elements (such as links, buttons, or form inputs) do not have a visual focus indicator, so sighted people who use a keyboard to navigate content will not know when those elements are receiving focus.
2.4.11 Focus Not Obscured (Minimum) (Level AA 2.2 only)
EN 301 549 Criteria – Does not apply
Revised Section 508 – Does not apply
Web: Supports
Authored Content (PDF): Supports
Authored Content (SCORM): Supports
Authored Content (Video): Supports
Web: When a user interface component receives keyboard focus, the component is not entirely hidden due to author-created content.
Authored Content (PDF): Authors can ensure that content meets this criterion.
Authored Content (SCORM): Authors can ensure that content meets this criterion.
Authored Content (Video): Authors can ensure that content meets this criterion.
2.5.7 Dragging Movements (Level AA 2.2 only)
EN 301 549 Criteria – Does not apply
Revised Section 508 – Does not apply
Web: Supports
Authored Content (PDF): Supports
Authored Content (SCORM): Partially Supports
Authored Content (Video): Supports
Web: All functionality that uses a dragging movement can be achieved by a single pointer without dragging, unless dragging is essential or the functionality is determined by the user agent and not modified by the author.
Authored Content (PDF): Authors can ensure that content meets this criterion.
Authored Content (SCORM): Authors can ensure that most content meets this criterion.
Some functionality relies on a dragging movement with no single-pointer, single-touch alternative, making it difficult or impossible for persons with motor difficulties and users of assistive technology to perform the gesture.
Authored Content (Video): Authors can ensure that content meets this criterion.
2.5.8 Target Size (Minimum) (Level AA 2.2 only)
EN 301 549 Criteria – Does not apply
Revised Section 508 – Does not apply
Web: Partially Supports
Authored Content (PDF): Supports
Authored Content (SCORM): Supports
Authored Content (Video): Partially Supports
Web: The size of the target for most clickable controls is at least 24 by 24 CSS pixels, except where the target size is determined by the user agent; there is a different control with equivalent functionality; the target is in line with text; the presentation of the target is essential to the function or otherwise exempted under the rule; or each control is spaced such that a 24-pixel circle placed around the bounding box of the control will not intersect any similar circle for another control. Exceptions include:
A target's hit area does not meet a minimum 24x24 pixel size or spacing. making it difficult for users with hand tremors and those who have difficulty with fine motor movement to activate them accurately. This occurs on the following page: Learner - Profile Settings.
Authored Content (PDF): Authors can ensure that controls meet this criterion.
Authored Content (SCORM): Authors can ensure that controls meet this criterion.
Authored Content (Video): Authors can ensure that most controls meet this criterion.
A target's hit area does not meet a minimum 24x24 pixel size or spacing. making it difficult for users with hand tremors and those who have difficulty with fine motor movement to activate them accurately.
3.1.2 Language of Parts (Level AA)
Also applies to:
EN 301 549 Criteria
- 9.3.1.2 (Web)
- 10.3.1.2 (Non-web document)
- 11.3.1.2 (Open Functionality Software) – Does not apply
- 11.3.1.2 (Closed Software) – Does not apply
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
Web: Partially Supports
Authored Content (PDF): Supports
Authored Content (SCORM): Supports
Authored Content (Video): Supports (Not Applicable)
Web: Changes of language for passages or phrases can be programmatically determined. Exception includes:
A portion of content on a page that is in a different language from the rest of the content on the page is not programmatically assigned the language for that portion of content, so screen readers may mispronounce that part of the content. This occurs on the following page: Learner - Profile Settings.
Authored Content (PDF): Authors can set the language for individual phrases within content.
Authored Content (SCORM): Authors can set the language for individual phrases within content.
Authored Content (Video): Video file formats are not capable of containing programmatic determination of the language of phrases.
3.2.3 Consistent Navigation (Level AA)
Also applies to:
EN 301 549 Criteria
- 9.3.2.3 (Web)
- 10.3.2.3 (Non-web document) – Does not apply
- 11.3.2.3 (Open Functionality Software) – Does not apply
- 11.3.2.3 (Closed Software) – Does not apply
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software) – Does not apply to non-web software
- 504.2 (Authoring Tool)
- 602.3 (Support Docs) – Does not apply to non-web docs
Web: Supports
Authored Content (PDF): Supports
Authored Content (SCORM): Supports
Authored Content (Video): Supports
Web: When navigational mechanisms are repeated in the product, they occur in a consistent relative order.
Authored Content (PDF): This criterion does not apply to non-web documents.
Authored Content (SCORM): Authored content does not contain a navigational mechanism that is repeated on multiple web pages.
Authored Content (Video): The product does not contain a navigational mechanism that is repeated on multiple web pages.
3.2.4 Consistent Identification (Level AA)
Also applies to:
EN 301 549 Criteria
- 9.3.2.4 (Web)
- 10.3.2.4 (Non-web document) – Does not apply
- 11.3.2.4 (Open Functionality Software) – Does not apply
- 11.3.2.4 (Closed Software) – Does not apply
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software) – Does not apply to non-web software
- 504.2 (Authoring Tool)
- 602.3 (Support Docs) – Does not apply to non-web docs
Web: Supports
Authored Content (PDF): Supports
Authored Content (SCORM): Supports
Authored Content (Video): Supports
Web: Components with the same functionality are identified consistently.
Authored Content (PDF): This criterion does not apply to non-web documents.
Authored Content (SCORM): Authors can ensure that components with the same functionality are identified consistently in a set of pages.
Authored Content (Video): Authors can ensure that components with the same functionality are identified consistently in a set of pages.
3.3.3 Error Suggestion (Level AA)
Also applies to:
EN 301 549 Criteria
- 9.3.3.3 (Web)
- 10.3.3.3 (Non-web document)
- 11.3.3.3 (Open Functionality Software)
- 11.3.3.3 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
Web: Supports
Authored Content (PDF): Supports (Not Applicable)
Authored Content (SCORM): Supports (Not Applicable)
Authored Content (Video): Supports (Not Applicable)
Web: Where input errors are automatically detected, suggestions for correction are provided to the user.
Authored Content (PDF): Authored content does not contain user input controls which would require error identification.
Authored Content (SCORM): Authored content does not detect input errors that are displayed to users.
Authored Content (Video): Authored content does not contain user input controls that would require suggestions for correction.
3.3.4 Error Prevention (Legal, Financial, Data) (Level AA)
Also applies to:
EN 301 549 Criteria
- 9.3.3.4 (Web)
- 10.3.3.4 (Non-web document)
- 11.3.3.4 (Open Functionality Software)
- 11.3.3.4 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
Web: Supports
Authored Content (PDF): Supports (Not Applicable)
Authored Content (SCORM): Supports (Not Applicable)
Authored Content (Video): Supports (Not Applicable)
Web: The product does not process legal commitments or financial transactions and does not modify user-controllable data.
Authored Content (PDF): Authored content does not contain legal or financial data and does not modify user-controllable data.
Authored Content (SCORM): Authored content does not contain legal or financial data and does not modify user-controllable data.
Authored Content (Video): Authored content does not contain legal or financial data and does not modify user-controllable data.
3.3.8 Accessible Authentication (Minimum) (Level AA 2.2 only)
EN 301 549 Criteria – Does not apply
Revised Section 508 – Does not apply
Web: Supports
Authored Content (PDF): Supports
Authored Content (SCORM): Supports
Authored Content (Video): Not Applicable
Web: A cognitive function test (such as remembering a password or solving a puzzle) is not required for any step in an authentication process unless either another method is available that does not rely on a cognitive function test; help is available to assist the user in completing the test; or the test is to recognize objects or identify non-text content the user provided to the Web site.
Authored Content (PDF): The authored content does not require cognitive function tests—including memory, recall, pattern recognition, or puzzle-style challenges—to open, access, or use the document.
Authored Content (SCORM): The authored content does not require cognitive function tests—such as memorizing information, solving puzzles, or performing recognition-based tasks—to access or complete learning interactions.
Authored Content (Video): The authored video content does not include any authentication mechanism. Users are not required to enter credentials, remember information, or perform any cognitive function tests to view or interact with the video.
4.1.3 Status Messages (Level AA 2.1 and 2.2)
Also applies to:
EN 301 549 Criteria
- 9.4.1.3 (Web)
- 10.4.1.3 (Non-web document)
- 11.4.1.3 (Open Functionality Software)
- 11.4.1.3 (Closed Software) – Does not apply
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508 – Does not apply
Web: Partially Supports
Authored Content (PDF): Supports
Authored Content (SCORM): Supports
Authored Content (Video): Supports (Not Applicable)
Web: Most status messages can be programmatically determined and presented by assistive technologies without receiving focus. Exceptions include:
Some status messages are not automatically announced by the screen reader, so people who are blind and/or use a screen reader or other assistive technology may completely miss the status messages or they may not hear them in a timely fashion. This occurs on the following pages: Learner - Catalog; Learner - Leaderboard; Learner - My Learning; Learner - Course Overview; Learner - Home Page; Learner - Course Completed.
Authored Content (PDF): The authored content presents information in a static, non-interactive format and does not rely on dynamic status messages.
Authored Content (SCORM): The authored content conveys status updates in ways that are programmatically determinable and accessible to assistive technologies.
Authored Content (Video): The authored video content does not generate status messages, dynamic updates, or interactive elements requiring announcements for assistive technologies.
Table 3: Success Criteria, Level AAA
Notes: Not Applicable. The website was not assessed for WCAG 2.2 AAA conformance.
Revised Section 508 Report
Chapter 3: Functional Performance Criteria (FPC)
Web: Partially Supports
Authored Content (PDF): Partially Supports
Authored Content (SCORM): Partially Supports
Authored Content (Video): Partially Supports
Web: Most functionality is usable without vision. Exceptions include:
As noted in 1.1.1 Non-Text Content
As noted in 1.3.1 Info and Relationships
As noted in 1.3.2 Meaningful Sequence
As noted in 1.4.1 Use of Color
As noted in 2.1.1 Keyboard
As noted in 2.4.3 Focus Order
As noted in 2.4.6 Headings and Labels
As noted in 3.3.1 Error Identification
As noted in 4.1.2 Name, Role, Value
Authored Content (PDF): Authors can create content in which most functions can be used without vision. Exceptions include:
As noted in 1.3.1 Info and Relationships
As noted in 4.1.2 Name, Role, Value
Authored Content (SCORM): Authors can create content in which most functions can be used without vision. Exceptions include:
As noted in 1.3.1 Info and Relationships
As noted in 2.1.1 Keyboard
As noted in 2.4.3 Focus Order
As noted in 4.1.2 Name, Role, Value
Authored Content (Video): Authors can create content in which most functions can be used without vision. Exceptions include:
As noted in 1.3.1 Info and Relationships
As noted in 4.1.2 Name, Role, Value
Web: Partially Supports
Authored Content (PDF): Partially Supports
Authored Content (SCORM): Partially Supports
Authored Content (Video): Partially Supports
Web: Most functionality is usable with limited vision. Exceptions include:
As noted in 1.1.1 Non-Text Content
As noted in 1.3.1 Info and Relationships
As noted in 1.3.2 Meaningful Sequence
As noted in 1.4.1 Use of Color
As noted in 1.4.3 Contrast (minimum)
As noted in 1.4.4 Resize Text
As noted in 2.1.1 Keyboard
As noted in 2.4.3 Focus Order
As noted in 2.4.6 Headings and Labels
As noted in 2.4.7 Focus Visible
As noted in 3.1.2 Language of Parts
As noted in 3.3.1 Error Identification
As noted in 3.3.2 Labels or Instructions
As noted in 4.1.2 Name, Role, Value
Authored Content (PDF): Authors can create content in which most functions can be used with limited vision. Exceptions include:
As noted in 1.3.1 Info and Relationships
As noted in 1.4.3 Contrast (minimum)
As noted in 2.4.7 Focus Visible
As noted in 3.3.2 Labels or Instructions
As noted in 4.1.2 Name, Role, Value
Authored Content (SCORM): Authors can create content in which most functions can be used with limited vision. Exceptions include:
As noted in 1.3.1 Info and Relationships
As noted in 2.1.1 Keyboard
As noted in 2.4.3 Focus Order
As noted in 2.4.7 Focus Visible
As noted in 3.3.2 Labels or Instructions
As noted in 4.1.2 Name, Role, Value
Authored Content (Video): Authors can create content in which most functions can be used with limited vision. Exceptions include:
As noted in 1.3.1 Info and Relationships
As noted in 2.4.7 Focus Visible
As noted in 3.3.2 Labels or Instructions
As noted in 4.1.2 Name, Role, Value
Web: Partially Supports
Authored Content (PDF): Partially Supports
Authored Content (SCORM): Supports
Authored Content (Video): Supports
Web: Most functionality is usable without perception of color. Exceptions include:
As noted in 1.4.1 Use of Color
As noted in 1.4.3 Contrast (minimum)
Authored Content (PDF): Authors can create content which is functional for users without perception of color. Exceptions include:
As noted in 1.4.3 Contrast (minimum)
Authored Content (SCORM): Authors can create content which is functional for users without perception of color.
Authored Content (Video): Authors can create content which is functional for users without perception of color.
Web: Partially Supports
Authored Content (PDF): Supports
Authored Content (SCORM): Supports
Authored Content (Video): Partially Supports
Web: Most functionality is usable without hearing. Exceptions include:
As noted in 1.2.2 Captions (prerecorded)
As noted in 3.1.2 Language of Parts
Authored Content (PDF): The product does not require the use of hearing.
Authored Content (SCORM): The product does not require the use of hearing.
Authored Content (Video): Most product does not require the use of hearing. Exceptions include:
As noted in 1.2.2 Captions (prerecorded)
Web: Partially Supports
Authored Content (PDF): Supports
Authored Content (SCORM): Supports
Authored Content (Video): Partially Supports
Web: Most functionality is usable with limited hearing. Exceptions include:
As noted in 1.2.2 Captions (prerecorded)
As noted in 3.1.2 Language of Parts
Authored Content (PDF): The product does not require the use of hearing.
Authored Content (SCORM): The product does not require the use of hearing.
Authored Content (Video): Most product does not require the use of hearing. Exceptions include:
As noted in 1.2.2 Captions (prerecorded)
Web: Supports (Not Applicable)
Authored Content (PDF): Supports (Not Applicable)
Authored Content (SCORM): Supports (Not Applicable)
Authored Content (Video): Supports (Not Applicable)
Web: The product does not require the use of speech.
Authored Content (PDF): Authors can create content which is functional for users without speech.
Authored Content (SCORM): Authors can create content which is functional for users without speech.
Authored Content (Video): Authors can create content which is functional for users without speech.
Web: Partially Supports
Authored Content (PDF): Partially Supports
Authored Content (SCORM): Partially Supports
Authored Content (Video): Partially Supports
Web: Most functionality is usable with limited manipulation and does not require fine motor control or simultaneous manual operations. Exceptions include:
As noted in 2.1.1 Keyboard
As noted in 2.4.3 Focus Order
As noted in 2.4.6 Headings and Labels
As noted in 2.4.7 Focus Visible
As noted in 4.1.2 Name, Role, Value
Authored Content (PDF): In most instances, authors can create content which is functional with limited manipulation. Exceptions include:
As noted in 2.1.1 Keyboard
As noted in 2.4.3 Focus Order
As noted in 2.4.7 Focus Visible
As noted in 4.1.2 Name, Role, Value
Authored Content (SCORM): In most instances, authors can create content which is functional with limited manipulation. Exceptions include:
As noted in 2.1.1 Keyboard
As noted in 2.4.3 Focus Order
As noted in 4.1.2 Name, Role, Value
Authored Content (Video): In most instances, authors can create content which is functional with limited manipulation. Exceptions include:
As noted in 2.4.7 Focus Visible
As noted in 4.1.2 Name, Role, Value
Web: Supports
Authored Content (PDF): Supports
Authored Content (SCORM): Supports
Authored Content (Video): Supports
Web: The product is functional with limited reach and strength.
Authored Content (PDF): Authors can create content which is functional with limited reach and strength.
Authored Content (SCORM): Authors can create content which is functional with limited reach and strength.
Authored Content (Video): Authors can create content which is functional with limited reach and strength.
Web: Partially Supports
Authored Content (PDF): Partially Supports
Authored Content (SCORM): Partially Supports
Authored Content (Video): Partially Supports
Web: Most functionality is usable by people with limited language, cognitive, and learning abilities. People with cognitive disabilities have varying needs for features that allow them to adapt content and work with assistive technology. Exceptions include:
As noted in 1.1.1 Non-Text Content
As noted in 1.2.2 Captions (prerecorded)
As noted in 1.3.1 Info and Relationships
As noted in 1.3.2 Meaningful Sequence
As noted in 1.4.1 Use of Color
As noted in 2.1.1 Keyboard
As noted in 2.4.3 Focus Order
As noted in 2.4.6 Headings and Labels
As noted in 2.4.7 Focus Visible
As noted in 3.1.2 Language of Parts
As noted in 3.3.1 Error Identification
As noted in 3.3.2 Labels or Instructions
As noted in 4.1.2 Name, Role, Value
Authored Content (PDF): In most instances, authors can create content which is functional for users with limited language, cognitive, and learning abilities. Exceptions include:
As noted in 1.3.1 Info and Relationships
As noted in 1.4.1 Use of Color
As noted in 2.4.7 Focus Visible
As noted in 3.3.2 Labels or Instructions
As noted in 4.1.2 Name, Role, Value
Authored Content (SCORM): In most instances, authors can create content which is functional for users with limited language, cognitive, and learning abilities. Exceptions include:
As noted in 1.3.1 Info and Relationships
As noted in 2.1.1 Keyboard
As noted in 2.4.3 Focus Order
As noted in 2.4.7 Focus Visible
As noted in 3.3.2 Labels or Instructions
As noted in 4.1.2 Name, Role, Value
Authored Content (Video): In most instances, authors can create content which is functional for users with limited language, cognitive, and learning abilities. Exceptions include:
As noted in 1.2.2 Captions (prerecorded)
As noted in 1.3.1 Info and Relationships
As noted in 2.4.7 Focus Visible
As noted in 4.1.2 Name, Role, Value
The role, state(s), properties, boundary, name, and description of most objects can be programmatically determined, so those attributes can be perceived and conveyed by assistive technology. Exceptions include:
As noted in 4.1.2 Name, Role, Value
For most objects that allow the user to set their respective properties and/or state, the act of setting a property or state is available programmatically, so that it can be perceived and performed using assistive technology. Exceptions include:
As noted in 4.1.2 Name, Role, Value
In most instances, when a data table is present, all information in the data cells and the row and/or column headers associated with each data cell are available programmatically, so they can be perceived and conveyed by assistive technology. Exception includes:
As noted in 1.3.1 Info and Relationships
For most objects that have a current value or have a set or range of values associated with the object, the values are available programmatically, so they can be perceived and conveyed by assistive technology. Exceptions include:
As noted in 4.1.2 Name, Role, Value
For most objects that allow the user to set or modify their value, the act of setting a value is available programmatically, so that it can be perceived and performed using assistive technology. Exceptions include:
As noted in 4.1.2 Name, Role, Value
For most elements that act as a label for another element and elements that are labeled by another element, the labeling relationship is programmatically determinable, so it can be perceived and conveyed by assistive technology. Exceptions include:
As noted in 1.3.1 Info and Relationships
As noted in 4.1.2 Name, Role, Value
Most of the product’s text objects, text attributes, and on-screen text boundaries are exposed to assistive technology. Exceptions include:
As noted in 1.3.2 Meaningful Sequence
As noted in 1.3.1 Info and Relationships
Most controls in the product expose programmatic role information and actions which can be taken on objects to assistive technology. Exception includes:
As noted in 4.1.2 Name, Role, Value
Most elements on which one or more actions may be performed, all of those actions are available programmatically, so that each action can be performed using assistive technology. Exception includes:
As noted in 2.1.1.a Keyboard Navigation
In most cases, status messages relevant to user interactions are available to, and presented by, assistive technology. Exception includes:
As noted in 4.1.3 Status Messages
Chapter 6: Support Documentation and Services
Notes: Notes: Information regarding Support Documentation and Services is available in the Accessibility Conformance Report for the Adobe Help Center on the Adobe Accessibility Compliance website.
EN 301 549 Report
Notes:
Chapter 4: Functional Performance Statements (FPS)
Web: Partially Supports
Authored Content (PDF): Partially Supports
Authored Content (SCORM): Partially Supports
Authored Content (Video): Partially Supports
Web: Most functionality is usable without vision. Exceptions include:
As noted in 1.1.1 Non-Text Content
As noted in 1.3.1 Info and Relationships
As noted in 1.3.2 Meaningful Sequence
As noted in 1.4.1 Use of Color
As noted in 2.1.1 Keyboard
As noted in 2.4.3 Focus Order
As noted in 2.4.6 Headings and Labels
As noted in 3.1.2 Language of Parts
As noted in 3.3.1 Error Identification
As noted in 4.1.2 Name, Role, Value
As noted in 4.1.3 Status Messages
Authored Content (PDF): Authors can create content in which most functions can be used without vision. Exceptions include:
As noted in 1.3.1 Info and Relationships
As noted in 4.1.2 Name, Role, Value
Authored Content (SCORM): Authors can create content in which most functions can be used without vision. Exceptions include:
As noted in 1.3.1 Info and Relationships
As noted in 2.1.1 Keyboard
As noted in 2.4.3 Focus Order
As noted in 4.1.2 Name, Role, Value
Authored Content (Video): Authors can create content in which most functions can be used without vision. Exceptions include:
As noted in 1.3.1 Info and Relationships
As noted in 4.1.2 Name, Role, Value
Web: Partially Supports
Authored Content (PDF): Partially Supports
Authored Content (SCORM): Partially Supports
Authored Content (Video): Partially Supports
Web: Most functionality is usable with limited vision. Exceptions include:
As noted in 1.1.1 Non-Text Content
As noted in 1.3.1 Info and Relationships
As noted in 1.3.2 Meaningful Sequence
As noted in 1.4.1 Use of Color
As noted in 1.4.3 Contrast (minimum)
As noted in 1.4.4 Resize Text
As noted in 1.4.10 Reflow
As noted in 1.4.11 Non-Text Contrast
As noted in 1.4.12 Text Spacing
As noted in 1.4.13 Content on Hover or Focus
As noted in 2.1.1 Keyboard
As noted in 2.4.3 Focus Order
As noted in 2.4.6 Headings and Labels
As noted in 2.4.7 Focus Visible
As noted in 3.1.2 Language of Parts
As noted in 3.3.1 Error Identification
As noted in 3.3.2 Labels or Instructions
As noted in 4.1.2 Name, Role, Value
Authored Content (PDF): Authors can create content in which most functions can be used with limited vision. Exceptions include:
As noted in 1.3.1 Info and Relationships
As noted in 1.4.3 Contrast (minimum)
As noted in 1.4.10 Reflow
As noted in 1.4.11 Non-Text Contrast
As noted in 2.4.7 Focus Visible
As noted in 3.3.2 Labels or Instructions
As noted in 4.1.2 Name, Role, Value
Authored Content (SCORM): Authors can create content in which most functions can be used with limited vision. Exceptions include:
As noted in 1.3.1 Info and Relationships
As noted in 1.4.11 Non-Text Contrast
As noted in 2.1.1 Keyboard
As noted in 2.4.3 Focus Order
As noted in 4.1.2 Name, Role, Value
Authored Content (Video): Authors can create content in which most functions can be used with limited vision. Exceptions include:
As noted in 1.3.1 Info and Relationships
As noted in 1.4.11 Non-Text Contrast
As noted in 2.4.7 Focus Visible
As noted in 4.1.2 Name, Role, Value
Web: Partially Supports
Authored Content (PDF): Partially Supports
Authored Content (SCORM): Partially Supports
Authored Content (Video): Partially Supports
Web: Most functionality is usable without perception of color. Exceptions include:
As noted in 1.4.1 Use of Color
As noted in 1.4.3 Contrast (minimum)
As noted in 1.4.11 Non-Text Contrast
Authored Content (PDF): Authors can create content in which most functions can be used with limited vision. Exceptions include:
As noted in 1.4.3 Contrast (minimum)
As noted in 1.4.11 Non-Text Contrast
Authored Content (SCORM): Authors can create content in which most functions can be used with limited vision. Exceptions include:
As noted in 1.4.11 Non-Text Contrast
Authored Content (Video): Authors can create content in which most functions can be used with limited vision. Exceptions include:
As noted in 1.4.11 Non-Text Contrast
Web: Partially Supports
Authored Content (PDF): Supports
Authored Content (SCORM): Supports
Authored Content (Video): Partially Supports
Web: Most functionality is usable without hearing. Exceptions include:
As noted in 1.2.2 Captions (prerecorded)
As noted in 3.1.2 Language of Parts
Authored Content (PDF): The product does not require the use of hearing.
Authored Content (SCORM): The product does not require the use of hearing.
Authored Content (Video): Most product does not require the use of hearing. Exceptions include:
- As noted in 1.2.2 Captions (prerecorded)
Web: Partially Supports
Authored Content (PDF): Supports
Authored Content (SCORM): Supports
Authored Content (Video): Partially Supports
Web: Most functionality is usable with limited hearing. Exceptions include:
As noted in 1.2.2 Captions (prerecorded)
As noted in 3.1.2 Language of Parts
Authored Content (PDF): The product does not require the use of hearing.
Authored Content (SCORM): The product does not require the use of hearing.
Authored Content (Video): Most product does not require the use of hearing. Exceptions include:
As noted in 1.2.2 Captions (prerecorded)
Web: Supports (Not Applicable)
Authored Content (PDF): Supports (Not Applicable)
Authored Content (SCORM): Supports (Not Applicable)
Authored Content (Video): Supports (Not Applicable)
Web: The product does not require the use of speech.
Authored Content (PDF): Authors can create content which is functional for users without speech.
Authored Content (SCORM): Authors can create content which is functional for users without speech.
Authored Content (Video): Authors can create content which is functional for users without speech.
Web: Partially Supports
Authored Content (PDF): Partially Supports
Authored Content (SCORM): Partially Supports
Authored Content (Video): Partially Supports
Web: Most functionality is usable by people with limited manipulation and does not require manipulation, simultaneous action, or hand strength. Exceptions include:
As noted in 1.4.13 Content on Hover or Focus
As noted in 2.1.1 Keyboard
As noted in 2.4.3 Focus Order
As noted in 2.4.6 Headings and Labels
As noted in 2.4.7 Focus Visible
As noted in 2.5.3 Label in Name
As noted in 4.1.2 Name, Role, Value
Authored Content (PDF): In most instances, authors can create content which is functional with limited manipulation or strength. Exceptions include:
As noted in 2.4.7 Focus Visible
As noted in 2.5.3 Label in Name
As noted in 4.1.2 Name, Role, Value
Authored Content (SCORM): In most instances, authors can create content which is functional with limited manipulation or strength. Exceptions include:
As noted in 2.1.1 Keyboard
As noted in 2.4.3 Focus Order
As noted in 4.1.2 Name, Role, Value
Authored Content (Video): In most instances, authors can create content which is functional with limited manipulation or strength. Exceptions include:
As noted in 2.4.7 Focus Visible
As noted in 4.1.2 Name, Role, Value
Web: Supports
Authored Content (PDF): Partially Supports
Authored Content (SCORM): Supports
Authored Content (Video): Supports
Web: The product is functional with limited reach.
Authored Content (PDF): In most instances, authors can create content which is functional with limited reach. Exceptions include:
As noted in 2.5.3 Label in Name
Authored Content (SCORM): Authors can create content which is functional with limited reach.
Authored Content (Video): Authors can create content which is functional with limited reach.
Web: Supports (Not Applicable)
Authored Content (PDF): Supports (Not Applicable)
Authored Content (SCORM): Supports (Not Applicable)
Authored Content (Video): Supports (Not Applicable)
Web: The product does not contain flashing content.
Authored Content (PDF): Authors can create content which does not flash, or flashes within an acceptable threshold, in order to minimize the potential for triggering photosensitive seizures.
Authored Content (SCORM): Authors can create content which does not flash, or flashes within an acceptable threshold, in order to minimize the potential for triggering photosensitive seizures.
Authored Content (Video): Authors can create content which does not flash, or flashes within an acceptable threshold, in order to minimize the potential for triggering photosensitive seizures.
Web: Partially Supports
Authored Content (PDF): Partially Supports
Authored Content (SCORM): Partially Supports
Authored Content (Video): Partially Supports
Web: Most functionality is usable by people with limited language, cognitive, and learning abilities. People with cognitive disabilities have varying needs for features that allow them to adapt content and work with assistive technology. Exceptions include:
As noted in 1.1.1 Non-Text Content
As noted in 1.2.2 Captions (prerecorded)
As noted in 1.3.1 Info and Relationships
As noted in 1.3.2 Meaningful Sequence
As noted in 1.4.1 Use of Color
As noted in 1.4.10 Reflow
As noted in 1.4.12 Text Spacing
As noted in 1.4.13 Content on Hover or Focus
As noted in 2.1.1 Keyboard
As noted in 2.4.3 Focus Order
As noted in 2.4.6 Headings and Labels
As noted in 2.4.7 Focus Visible
As noted in 2.5.3 Label in Name
As noted in 3.1.2 Language of Parts
As noted in 3.3.1 Error Identification
As noted in 3.3.2 Labels or Instructions
As noted in 4.1.2 Name, Role, Value
As noted in 4.1.3 Status Messages
Authored Content (PDF): In most instances, authors can create content which is functional for users with limited language, cognitive, and learning abilities. Exceptions include:
As noted in 1.3.1 Info and Relationships
As noted in 1.4.10 Reflow
As noted in 2.4.7 Focus Visible
As noted in 2.5.3 Label in Name
As noted in 3.3.2 Labels or Instructions
As noted in 4.1.2 Name, Role, Value
Authored Content (SCORM): In most instances, authors can create content which is functional for users with limited language, cognitive, and learning abilities. Exceptions include:
As noted in 1.3.1 Info and Relationships
As noted in 2.1.1 Keyboard
As noted in 2.4.3 Focus Order
As noted in 4.1.2 Name, Role, Value
Authored Content (Video): In most instances, authors can create content which is functional for users with limited language, cognitive, and learning abilities. Exceptions include:
As noted in 1.2.2 Captions (prerecorded)
As noted in 1.3.1 Info and Relationships
As noted in 2.4.7 Focus Visible
As noted in 4.1.2 Name, Role, Value
Web: Supports (Not Applicable)
Authored Content (PDF): Supports (Not Applicable)
Authored Content (SCORM): Supports (Not Applicable)
Authored Content (Video): Supports (Not Applicable)
Web: The product does not ask for or display legal, financial, or personal data.
Authored Content (PDF): Authors can create content which maintains user privacy when accessibility features are used.
Authored Content (SCORM): Authors can create content which maintains user privacy when accessibility features are used.
Authored Content (Video): Authors can create content which maintains user privacy when accessibility features are used.
Chapter 5: Generic Requirements
Notes: Not Applicable
Chapter 6: ICT with Two-Way Voice Communication
Notes: Not Applicable.
Chapter 7: ICT with Video Capabilities
Notes:
A multimedia player does not provide a way for the user to modify the appearance of captions to their individual needs, so people who are deaf, have limited hearing, and others who rely on captions to understand the content may not have access to the information. Examples include:
Course - Authored Content - Video
The product does not provide access to subtitles with an option for the subtitles to be read aloud. Examples include:
Course - Authored Content - Video
The product does not provide a mechanism to select and play closed audio description. Examples include:
Course - Authored Content - Video
The product does not provide user controls for captions but not for audio descriptions. Examples include:
Course - Authored Content - Video
Chapter 8: Hardware
Notes: Not Applicable
Chapter 9: Web
Notes: (see WCAG 2.2 section)
Chapter 10: Non-Web Documents
Notes: Not Applicable
Chapter 11: Software
Notes: The ICT covered by this report is a web application, and it is not an authoring tool. As such, its accessibility requirements are covered in Clause 9 and by reference to the WCAG 2.2 section. Thus, the requirements of this clause do not apply.
Chapter 12: Documentation and Support Services
Notes: Information regarding Support Documentation and Services is available in the Accessibility Conformance Report for the Adobe Help Center on the Adobe Accessibility Compliance website.
Chapter 13: ICT Providing Relay or Emergency Service Access
Notes: Not Applicable