Adobe Accessibility Conformance Report International Edition
(Based on VPAT® Version 2.5)
Product Information
- Name of Product/Version: Adobe Frame.io / Version 4
- Report Dated: October 2025
- Product Description: Frame.io is a creative management tool that lets you share media, track feedback, and streamline your workflow so your team can work closely together from anywhere in the world.
- 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 Adobe Frame.io involved extensive use of leading assistive technology, such as screen readers, as well as exclusive use of the keyboard. 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 standards/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: The product provides sufficient text alternatives for most instances of non-text content.
An image does not have a text alternative, so people who are blind and/or use a screen reader will not be able to access the information available in the image, and if it is an active image, will not understand its function. This occurs on the following pages: Landing page; Workspace Settings; Configuration Panel; All Shares Page.
An image does not have a text alternative, so people who are blind and/or use a screen reader will not be able to access the information available in the image, and if it is an active image, will not understand its function. This occurs on the following pages: Account – Workspaces; Project Switcher; Views / Filter / Sort; Main Asset Grid; Personal – Profile; Purchase flow.
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)
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)
The product contains audio content in media and closed captions are provided for most instances. Exceptions include:
The captions provided for media that include audio and video do not identify all the speakers, so people who are deaf or hard of hearing will lose some of the context when reading the dialogue. This occurs on the following page: Video Asset.
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: The product provides audio description | transcripts for most video. Exceptions include:
The text transcript provided for a video is incorrect or inadequate, so the visual content presented by the video will be misrepresented to people who are blind or have low vision. This occurs on the following page: Video Asset.
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: Some structure and relationship information, is provided through element semantics | object information or in text. However, most structure and relationship information are not provided programmatically or in text, such as:
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. This occurs on the following pages: Configuration Panel; Views / Filter / Sort.
A group of form controls is not programmatically associated with their group label, so the purpose of individual controls in the group cannot be understood by people who are blind and/or use a screen reader. This occurs on the following pages: Video Asset; Filtered By.
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: Personal – Profile.
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: Account; Account – Users; Account - Content Security; Account – Workspaces; Manage Metadata; Panels; Profile Settings – Left Nav; Project Search; Project Settings; Purchase flow; Reel Share; Uploads; Video Asset – Transcriptions; Workspace Settings; Configuration Panel; Create New Project; Customize Metadata; Landing Page; Manage Members - Inherit Access; Manage Members - Invite New Members; Notifications; Personal – Profile; Project Switcher.
One or more data cells is incorrectly marked up as a header cell in a table, so the table structure and the header/data relationship between the cell(s) and other cells in the table will be incorrectly conveyed to people who are blind and/or use a screen reader. This occurs on the following pages: All Shares Page; Account – Users; Account - Workspaces.
A set of radio buttons is not programmatically grouped, so the group label for the 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 page: Project Switcher.
An element's 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: Views / Filter / Sort; User Profile Settings; Image Viewer; Main Asset Grid; Configuration Panel; Appearance.
A set of checkboxes is not programmatically grouped, so the group label for the set of checkboxes 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 checkboxes. This occurs on the following page: Panels.
Data is arranged visually like a data table, but the programmatic table header markup is missing or incomplete. People who are blind and/or use a screen reader will not be aware of the association between the table headers and their related data. This occurs on the following pages: All Shares Page.
Content that is visually presented as a list is not marked up as a list, so the presence and structure of the list are not conveyed to assistive technologies and people who are blind and/or use a screen reader. This occurs on the following pages: Purchase flow; Profile Settings - Left Nav
An element's 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: Views / Filter / Sort; Configuration Panel; Appearance; Main Asset Grid; Image Viewer.
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: The product presents most content in a meaningful sequence. Exceptions include:
Some visually hidden content is announced by a screen reader, so people who are blind and/or use a screen reader may be misled or confused when hearing content that is not intended to be part of the reading order on the page. This occurs on the following pages: Purchase flow; Login.
The screen reader skips and does not announce informative static content (text or images), so the intended meaning of that content will be lost or changed for people who are blind and/or use a screen reader. This occurs on the following pages: Project Switcher; Customize Metadata; Manage Members - Invite New Members
The screen reader announcement of static text does not match the visual text displayed, so the intended meaning of the text will be lost or changed for people who are blind and/or use a screen reader. This occurs on the following page: Project Search.
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)
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: Most functions of the product do not convey information through color alone. Exceptions 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: Account; Workspace Settings; Purchase flow; Account - Content Security.
Color is used as the only method to identify errors on a form field, so the error 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 page: Purchase flow.
Color is used as the only method to convey the state (such as "checked," "pressed," or "selected") of a control, 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: Project Search; Panels; Video Asset; Configuration Panel; Account - Users; Viewer – Header; Personal – Profile; Account - Workspaces.
Color is used as the only method to convey information 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 page: Panels.
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)
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: Most product functionality cannot be operated through a keyboard interface. Examples 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. This occurs on the following pages: Document Viewer; Panels; Views / Filter / Sort; Video Asset; Create New Project; Configuration Panel; Manage Metadata; Main Asset Grid; Personal - Profile; Manage Members - Inherit Access; Purchase flow; Account - Users; Filtered By; Image Viewer; All Shares Page.
The content in a scrollable region cannot be accessed using a keyboard, so people who use a keyboard to navigate will not be able to view this content. This occurs on the following pages: Document Viewer; Reel Share.
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)
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
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)
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)
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)
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
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)
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: Most components receive focus in a meaningful order. Exceptions include:
Keyboard focus or touch screen swiping goes to an element that is hidden or empty, so people who use the keyboard to navigate content (including screen reader users) may become disoriented or confused. This occurs on the following pages: Login; Main Asset Grid - Left Nav; Video Asset; Manage Members - Inherit Access; Purchase flow.
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. This occurs on the following pages: Landing page; Context Menu; Panels; Project Switcher.
The focus order is not logical and presents content in an order that misrepresents its meaning or operability, so people who use a keyboard, switch control, or other assistive technology to navigate content may become disoriented or confused. This occurs on the following pages: Panels; Video Asset; Create New Project; Configuration Panel; Filtered By; Customize Sort; Image Viewer; Creating Share from Project; Manage Metadata.
When a modal closes, keyboard focus is not returned to the control that opened the modal or to another logical location, 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: Delete Asset; Workspace Settings; Project Settings.
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)
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: The product does not rely on multipoint or path-based gestures except where essential. Exceptions include:
Functionality (excluding operating system, user agents [like a browser], or assistive technology functions) relies on path-based gestures that require the user to move the finger or pointer in a specific path or sequence, so people with motor disabilities or limited dexterity and people who use certain assistive technology to interact with the page will not be able to operate this functionality. This occurs on the following pages: All Shares Page; Account – Users; Account - Workspaces.
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
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: In most product functions, accessible names of controls do not contain the text of their visible labels. Examples include:
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. This occurs on the following pages: Main Asset Grid - Left Nav; Document Viewer; Views / Filter / Sort; Reel Share; Video Asset; All Shares Page; Personal - Profile; Manage Members - Inherit Access; Create New Project; Configuration Panel; Account - Workspaces; Account - Users; Landing page; Customize Metadata; Customize Sort; Workspace Settings; Manage Metadata; Account - Content Security; Project Settings.
An interactive element (such as a link, button, or form input) does not have an accessible name because its visible label is not programmatically associated with the element, so people who use speech input to navigate and operate content will not be able to access the element. This occurs on the following pages: Document Viewer; Panels; Video Asset; Workspace Settings.
The accessible name of an interactive element (such as a link, button, or form input) includes the visible label but has other words interspersed, so people who use speech input to navigate and operate content will not be able to access the element. This occurs on the following pages: Purchase flow.
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
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)
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: In most product functions, components do not initiate a change of context when focused. Exceptions include:
When an element receives keyboard focus, it results in a substantial, unanticipated context change (such as a change in the page content that changes the meaning of the page), so people who use a keyboard to navigate content (including screen reader users) may become confused or disoriented. This occurs on the following page: Landing page.
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: In most cases, when a user inputs information or interacts with a control, it does not result in a substantial change to the page that could disorient the user, or the user is informed about the change ahead of time. Exceptions include:
When a user changes the setting of a user interface control (such as entering text in an input field or selecting a checkbox or radio button), it results in an unanticipated context change (such as opening a new window, moving focus to another element, or submitting a form), so people who have cognitive disabilities and others may be confused or disoriented. This occurs on the following page: Customize Metadata.
3.2.6 Consistent Help (Level A 2.2 only)
EN 301 549 Criteria – Does not apply
Revised Section 508 – Does not apply
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: Most input errors are identified and described to the users in text. Exceptions include:
- An error for a form input (such as a text input field, radio button, select dropdown, or checkbox) is not identified with a text error message or a text alternative for an image, so people who are blind and/or use a screen reader will not be made aware that an error has occurred. This occurs on the following page: Purchase flow.
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: Labels are provided for most input fields. Exceptions include:
The label of an element is not persistent (always visible on the page), so the element's purpose may be difficult to discover. This occurs on the following pages: Configuration Panel; Manage Members - Invite New Members; Account - Content Security; Document Viewer; Panels.
The label for a form field is missing, so the field's purpose is not clear. This occurs on the following pages: Purchase flow; Document Viewer; Configuration Panel.
Select or dropdown control missing a visible label so the Select or dropdown control purpose is not clear. This occurs on the following pages: Document Viewer; Panels; Manage Members - Inherit Access; Video Asset - Transcriptions; Configuration Panel; Account - Workspaces; Account - Users; Filtered By; Customize Metadata; Manage Members - Invite New Members.
3.3.7 Redundant Entry (Level A 2.2 only)
EN 301 549 Criteria – Does not apply
Revised Section 508 – Does not apply
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)
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: User interface components in most product functions do not provide programmatic [name, role, state, or value] information. Examples include:
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 pages: Manage Metadata; All Shares Page; Configuration Panel; Project Switcher; Project Search; Customize Metadata; Account – Users; Account –Workspaces; Metadata - Set the status; Set Source; Video Asset; Document Viewer; Panels; Video Asset; Image Viewer; Landing page - Left Nav; Video Asset – Transcriptions; Notifications; User Profile Settings; Main Asset Grid - Left Nav; Viewer – Header; Manage Members – Inherit Access.
An element's 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 page: Landing 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 pages: Configuration Panel; All Shares Page; Landing page; Document Viewer; Main Asset Grid - Left Nav; Metadata - Set the status; Reel Share.
The total number of slides in the carousel is indicated visually but not programmatically, so people who are blind and/or use a screen reader or other assistive technology may not be able to understand how many slides the carousel contains. This occurs on the following page: Reel Share.
An element that appears and functions like a combo box 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: Video Asset.
An element is missing or has an incorrect 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 content or how to interact with it. This occurs on the following pages: Profile Settings - Left Nav; Video Asset.
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. This occurs on the following pages: Set Source; Filtered By.
An element that appears and functions like a slider control 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 element's name, purpose, or current value or how to interact with it. This occurs on the following pages: Video Asset; Landing Page; Panels; All Shares page; Main Asset Grid-Left Nav; Configuration Panel; Video Asset; Account – Workspaces; Document Viewer; Video Asset - Transcriptions
An element does not have an attribute in its 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: Main Asset Grid; Account – Users; All Shares Page; Project Switcher; Document Viewer; Panels.
An element that appears and functions like a switch control 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 element's name, purpose, or current state (such as "On" or "Off") or how to interact with it. This occurs on the following pages: Purchase flow; Manage Metadata.
A tooltip 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 the information it conveys. This occurs on the following page: Video Asset.
An element functions as if it has two programmatic roles, so one or both roles may be incorrectly conveyed to people who are blind and/or use a screen reader or other assistive technology, since assistive technology can convey only one role for any single element. This occurs on the following page: Main Asset Grid - Left Nav.
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 pages: Purchase flow; Video Asset – Transcriptions; Configuration Panel; Filtered By; Main Asset Grid; Manage Members - Inherit Access.
The HTML code for a link or button is nested inside the code of another link or button, so assistive technologies may not be able to determine the function of the element. This occurs on the following pages: Main Asset Grid - Left Nav; All Shares Page; Account; Account – Users; Account – Workspaces; Notifications; Manage Members - Inherit Access; Manage Members - Invite New Members; Project Search; Metadata - Set the status.
A button does not have a programmatic name, so its 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: Account – Users; Filtered By; Configuration Panel; Panels; Views / Filter / Sort; Customize Metadata.
An element that is focusable or contains one or more focusable elements is programmatically hidden, so people who use the keyboard to navigate, as well as people who are blind and/or use a screen reader or other assistive technology, will not be able to perceive or interact with the element. This occurs on the following pages: Login; Purchase flow
An element with a "link," "button," or "menu item" role is missing or has an incorrect 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 content or how to interact with it. This occurs on the following page: Image Viewer.
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 pages: Panels; Project Settings; Create New Project; Configuration Panel; All Shares Page; Main Asset Grid; Purchase flow.
A button does not have a programmatic role, so its role (usually button, but sometimes link or something else) 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: Metadata - Set the status; Purchase flow; Viewer – Header; Document Viewer; Video Asset; Configuration Panel; Create New Project; Customize Metadata; Landing page; Open Viewer; Project Search; Project Switcher; Reel Share; Filtered By; Main Asset Grid; Panels.
A button does not have a programmatic role and name, so its 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: Metadata - Set the status; Purchase flow; Configuration Panel; Main Asset Grid; Manage Members - Inherit Access; Personal – Profile.
When a button is pressed, its pressed 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 pressed. This occurs on the following pages: Viewer – Header; Video Asset;
Main Asset Grid; Document Viewer; Panels.
A custom checkbox element does not have a programmatic role and/or its current state (checked or not checked) is not conveyed programmatically, so people who are blind and/or use a screen reader or other assistive technology will not be aware that the element is a checkbox or if the checkbox is checked. This occurs on the following page: Configuration Panel.
When a button is selected, its selected 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 selected. This occurs on the following pages: Document Viewer; Set Source; Purchase flow; Video Asset; Main Asset Grid - Left Nav; User Profile Settings; Viewer – Header; Notifications; Project Search.
The programmatic state of an element that reveals or hides 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 the element or the state will be misrepresented. This occurs on the following pages: Creating Share from Project; Metadata - Set the status; Panels; Main Asset Grid - Left Nav; Image Viewer; Main Asset Grid; Manage Members - Inherit Access; Configuration Panel; Delete Asset.
A form field 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 understand the purpose of the form field or what input it requires. This occurs on the following pages: Document Viewer; Panels; Delete Asset; Workspace Settings.
An iframe does not have a programmatic title that is 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 or content of the iframe without browsing its content. This occurs on the following page: Purchase flow.
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 pages: Main Asset Grid; Uploads; Views / Filter / Sort.
A custom select does not have a role and/or a state (such as which options are available and/or which option is currently selected) that are 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 the element, the available options, and which option is selected. This occurs on the following page: Customize Metadata.
In a table that can be sorted by column, the sorted state (ascending or descending) of the table's columns is not conveyed to assistive technology or the state conveyed is incorrect, so people who are blind and/or use a screen reader or other assistive technology may not be able to understand the order in which the table's content is presented and whether that order is meaningful when interpreting the data. This occurs on the following page: Configuration Panel.
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)
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)
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
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: Most input fields in the product do not collect information about the user. However, some input fields collect information about the user and do not programmatically convey their purpose. Exceptions include:
The programmatic purpose provided for an input element (like a text input field) is not accurate, so information automatically suggested by the browser or assistive technology to fill in the input will be incorrect. This occurs on the following pages: Login; Personal - Profile.
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: Most text meets minimum contrast requirements. Exceptions include:
The color contrast ratio between placeholder text in an input and the input's background is less than 4.5:1, so people who are colorblind or have low vision may have difficulty reading the placeholder text. This occurs on the following pages: Purchase flow; Panels.
The color contrast ratio between text and its background 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 pages: Project Search; Document Viewer; Panels; Video Asset; Landing page - Left Nav; All Shares Page; Manage Members - Inherit Access; Purchase flow; Video Asset - Transcriptions; Configuration Panel; Account - Users; Filtered By; Delete Asset; Account - Content Security; Main Asset Grid - Left Nav; Project Settings; User Profile Settings; Context Menu.
The color contrast ratio on hover or focus between a control's text label and its background is less than 4.5:1, so people who are colorblind or have low vision may have difficulty reading the text label of the control. This occurs on the following pages: Main Asset Grid - Left Nav; Panels; All Shares Page; Video Asset - Transcriptions; Configuration Panel; Account - Users; Context Menu; Landing page; User Profile settings; Project Search; Filtered By; Metadata - Set the status; Delete Asset; Video Asset; Manage Members - Inherit Access.
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: Most content is readable and functional when browser zoom is set to 200% of its initial size. 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: Project Settings; Reel Share.
Functionality is lost 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 this functionality. This occurs on the following pages: Panels; Set Source; Configuration Panel; Manage Metadata; Profile Settings - Left Nav; Project Switcher; Document Viewer; Video Asset.
The ability to zoom or scale the screen has been disabled, so people who have low vision and need to enlarge text to read it cannot do so. This occurs on the following page: Login.
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)
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: 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: Configuration Panel; Manage Metadata; Project Settings; Profile Settings - Left Nav; Reel Share; Video Asset; Set Source; Manage Members - Invite New Members; Panels; Document Viewer; Filtered By; Project Switcher; Video Asset - Transcriptions.
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 pages: All Shares Page; Video Asset - Transcriptions; Create New Project; Project Search; Reel Share; Account - Workspaces; Customize Metadata; Main Asset Grid; Viewer – Header; Personal - Profile; Manage Members - Invite New Members; Customize Metadata.
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: Most of the boundaries and indicators of the visual states of each active user component and any graphics required to understand content have a 3:1 color contrast ratio with adjacent colors or their background. Exceptions include:
The visual boundary of an interactive element (like a radio button or input field) does 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: Project Switcher; Document Viewer; Panels; Video Asset; All Shares Page; Personal - Profile; Manage Members - Inherit Access; Purchase flow; Video Asset - Transcriptions; Create New Project; Configuration Panel; Landing page; Workspace Settings; Main Asset Grid; Account - Content Security; Appearance; Project Settings; Context Menu; Manage Metadata; Delete Asset; Customize Metadata.
An icon (or part of the icon required to understand its content) does 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 the icon. This occurs on the following pages: Login; Views / Filter / Sort; Landing page – Left Nav; Filtered By; Workspace Settings; Landing Page; Main Asset Grid-Left Nav; Manage Metadata; Manage Fields; Panels; Project Switcher; Customize metadata; Manage Members - Invite New Members; Manage Members - Inherit Access; Project Search; Delete Asset; Main Asset Grid; Reel Share; Document Viewer; Image Viewer; Video Asset; Configuration Panel; Purchase flow; Personal – Profile; Account – Users; Account - Content Security; Video Asset – Transcriptions; Set Source; Create New Project; All Shares page
The indicator for the state of an interactive element (like a checkbox or radio button) does 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 element. This occurs on the following pages: Project Search; Project Switcher; Panels; All Shares Page; Video Asset - Transcriptions; Configuration Panel; Customize Metadata; Manage Metadata; Context Menu; Document Viewer; Landing page; Main Asset Grid - Left Nav; Panels; Main Asset Grid; Appearance.
The focus indicator of an interactive element (like a button or input field) does 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 the interactive element is receiving focus. This occurs on the following pages: Login; Project Search; Panels; Views / Filter / Sort; Reel Share; Video Asset; All Shares Page; Personal - Profile; Manage Members - Inherit Access; Purchase flow; Set Source; Create New Project; Configuration Panel; Account - Workspaces; Account - Users; Filtered By; Delete Asset; Manage Metadata; Manage Members - Invite New Members; Main Asset Grid; Account - Content Security; Appearance; Project Settings; Context Menu; Metadata - Set the status; Account; Customize Metadata; Customize Sort.
An image or graphic (like a chart) or part of the image/graphic required to understand its content does 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 the image/graphic. This occurs on the following pages: Project Search; Project Switcher.
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: 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: Account - Workspaces; Account – Users; Configuration Panel.
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: In most product functions, content does not become visible and then hidden in response to pointer hover or keyboard focus. Exceptions include:
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 pages: Main Asset Grid - Left Nav; Video Asset; All Shares Page; Video Asset - Transcriptions; Configuration Panel; Account - Users; Delete Asset; Manage Members - Invite New Members; Main Asset Grid; User Profile Settings; Context Menu; Document Viewer; Panels; Landing page - Left Nav; Manage Members - Inherit Access; Purchase flow; Filtered By; Customize Metadata; Main Asset Grid.
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 page: Video Asset.
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
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: Most headings and labels for form and interactive controls are informative. Exceptions include:
A programmatic label for a control or form input field does not convey the purpose of the control or input, so people who are blind and/or use a screen reader may not understand what the control does or what data to enter. This occurs on the following pages: Project Search; Document Viewer; Panels; Views / Filter / Sort; Video Asset; Personal - Profile; Video Asset - Transcriptions; Configuration Panel; Account - Workspaces; Account - Users; Landing page; Delete Asset; Workspace Settings; Main Asset Grid; Account - Content Security; Filtered By; Customize Sort; Manage Members - Invite New Members.
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: Main Asset Grid - Left Nav; Panels; Reel Share; Personal - Profile; Configuration Panel; Account - Workspaces; Account - Users; Landing page; Main Asset Grid; Project Search; Document Viewer; All Shares Page.
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: Most focusable elements have a visible keyboard focus indicator. Exceptions include:
An interactive element (such as a link, button, or form input) does not have a visual focus indicator, so sighted people who use a keyboard to navigate content will not know when that element is receiving focus. This occurs on the following pages: Notifications; Project Search; Document Viewer; Panels; Manage Members - Inherit Access; Video Asset - Transcriptions; Create New Project; Filtered By; Manage Members - Invite New Members; Main Asset Grid; Image Viewer; Open Viewer; Metadata - Set the status; Main Asset Grid - Left Nav; Panels; Configuration Panel; Delete Asset.
The visual focus indicator for an interactive element (such as a link, button, or form input) is not visible, so sighted people who use a keyboard to navigate content will not know when that element is receiving focus. This occurs on the following pages: Reel Share; Configuration Panel.
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: When most user interface components receive keyboard focus, each component is not entirely hidden due to author-created content. Exceptions include:
A focused element is completely covered by other author-created content, which may cause people who use the keyboard to navigate content to become disoriented. This occurs on the following pages: Project Switcher; Filtered By; Customize Sort; Uploads; Account; Panels; Video Asset; Configuration Panel; Manage Metadata.
2.5.7 Dragging Movements (Level AA 2.2 only)
EN 301 549 Criteria – Does not apply
Revised Section 508 – Does not apply
Web: Most 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. Exceptions include:
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 on the following pages: Video Asset; Configuration Panel; Customize Metadata; Manage Metadata; Views / Filter / Sort; Landing page; Panels; All Shares page; Document Viewer; Account – Workspace; Main Asset Grid-Left Nav; Video Asset – Transcriptions.
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: 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 pages: Panels; Video Asset; All Shares Page; Video Asset - Transcriptions; Configuration Panel; Delete Asset; Main Asset Grid; Personal – Profile; Main Asset Grid - Left Nav; Set Source; Customize Metadata.
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: On most pages, the language of each section of content that is different from the default language of the page is correctly identified and can be determined programmatically. Exceptions include:
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: Video Asset - Transcriptions.
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
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
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)
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)
3.3.8 Accessible Authentication (Minimum) (Level AA 2.2 only)
EN 301 549 Criteria – Does not apply
Revised Section 508 – Does not apply
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: In most cases, status messages can be programmatically determined and presented by assistive technologies without receiving focus. Exceptions include:
A status message is 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 message, or they may not hear it in a timely fashion. This occurs on the following pages: Login; Project Switcher; Panels; Views / Filter / Sort; Purchase flow; Video Asset - Transcriptions; Configuration Panel; Account - Users; Filtered By; Customize Sort; Main Asset Grid; Account - Content Security; Context Menu; Uploading; Project Search; Document Viewer; Panels; Purchase flow; Manage Metadata.
Table 3: Success Criteria, Level AAA
Notes: Not Applicable
Revised Section 508 Report
Notes:
Chapter 3: Functional Performance Criteria (FPC)
Notes:
Web: Most functions of the product are usable without vision. Exceptions include:
1.1.1 Non-Text Content
1.2.3 Audio Description or Media Alternative (prerecorded)
1.3.1 Info and Relationships
1.3.2 Meaningful Sequence
1.4.1 Use of Color
2.1.1 Keyboard Navigation
2.4.3 Focus Order
2.4.6 Headings and Labels
3.1.2 Language of Parts
3.2.1 On Focus
3.2.2 On Input
3.3.1 Error Identification
4.1.2 Name, Role, Value
Web: Most functionality is usable with limited vision. Exceptions included
1.1.1 Non-Text Content
1.2.3 Audio Description or Media Alternative (prerecorded)
1.3.1 Info and Relationships
1.3.2 Meaningful Sequence
1.4.1 Use of Color
1.4.3 Contrast (minimum)
1.4.4 Resize Text
2.1.1 Keyboard Navigation
2.4.3 Focus Order
2.4.6 Headings and Labels
2.4.7 Focus Visible
3.1.2 Language of Parts
3.2.1 On Focus
3.2.2 On Input
3.3.1 Error Identification
3.3.2 Labels or Instructions
4.1.2 Name, Role, Value
Web: Most functions of the product are usable without perception of color. Exceptions include:
1.4.1 Use of Color
1.4.3 Contrast (minimum)
3.3.1 Error Identification
Web: Most functionality is usable without hearing. Exceptions include:
1.2.2 Captions (prerecorded)
Web: Most functionality is usable with limited hearing. Exceptions include:
1.2.2 Captions (prerecorded)
Web: Most functionality is usable with limited manipulation and does not require fine motor control or simultaneous manual operations. Exceptions include:
2.1.1 Keyboard Navigation
2.4.3 Focus Order
2.4.6 Headings and Labels
2.4.7 Focus Visible
3.2.1 On Focus
4.1.2 Name, Role, Value
Web: Most functions of the product are usable with limited language, cognitive, and learning abilities. Users with cognitive disabilities have varying needs for features that allow them to adapt content and work with assistive technology or accessibility features of the platform. The product provides descriptive labels, instructions, and error identification and suggestions for most user input. Exceptions include:
1.1.1 Non-Text Content
1.2.2 Captions (prerecorded)
1.2.3 Audio Description or Media Alternative (prerecorded)
1.3.1 Info and Relationships
1.3.2 Meaningful Sequence
1.4.1 Use of Color
2.1.1 Keyboard
2.4.3 Focus Order
2.4.6 Headings and Labels
2.4.7 Focus Visible
3.1.2 Language of Parts
3.2.1 On Focus
3.2.2 On Input
3.3.1 Error Identification
3.3.2 Labels or Instructions
4.1.2 Name, Role, Value
The product allows assistive technology to perform most actions on objects. Exceptions include:
Zoom In/Out button, Voiceover only announces a percentage (e.g., “27%”) without indicating that the button controls zoom functionality. Users are not informed that pressing the button will zoom in or out.
Add Pin Button, The action required after pressing the “Add Pin” button is not conveyed to the voiceover users, leading to confusion and inability to complete the task.
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:
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:
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. Exceptions include:
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 value(s) are available programmatically, so they can be perceived and conveyed by assistive technology. Exceptions include:
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:
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:
1.3.1 Info and Relationships
4.1.2 Name, Role, Value
For most elements that have a parent-child relationship, those relationships are programmatically determinable, so they can be perceived by assistive technology. Exceptions include:
1.3.1 Info and Relationships
For most of the elements on which one or more actions may be performed, all of those actions are programmatically determinable, so that each action can be perceived and conveyed by assistive technology. Exceptions include:
4.1.2 Name, Role, Value
For most of the 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. Exceptions include:
2.1.1 Keyboard Navigation
On most pages, the position and content of the focus indicator, text insertion point, and/or text selector are programmatically determinable, so that focus position and content can be perceived and conveyed by assistive technology. Exceptions include:
2.4.7 Focus Visible
In most cases, status messages relevant to user interactions are available to, and presented by, assistive technology. Exceptions include:
4.1.3 Status Messages
Chapter 6: Support Documentation and 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.
EN 301 549 Report
Notes:
Chapter 4: Functional Performance Statements (FPS)
Notes:
Web: Most functions of the product are usable without vision. Exceptions include:
1.1.1 Non-Text Content
1.2.3 Audio Description or Media Alternative (prerecorded)
1.3.1 Info and Relationships
1.3.2 Meaningful Sequence
1.4.1 Use of Color
2.1.1 Keyboard Navigation
2.4.3 Focus Order
2.4.6 Headings and Labels
3.1.2 Language of Parts
3.2.1 On Focus
3.2.2 On Input
3.3.1 Error Identification
4.1.2 Name, Role, Value
4.1.3 Status Messages
Web: Most functions of the product are usable With Limited Vision. Exceptions include:
1.1.1 Non-Text Content
1.2.3 Audio Description or Media Alternative (prerecorded)
1.3.1 Info and Relationships
1.3.2 Meaningful Sequence
1.4.1 Use of Color
1.4.3 Contrast (minimum)
1.4.4 Resize Text
1.4.10 Reflow
1.4.11 Non-Text Contrast
1.4.12 Text Spacing
1.4.13 Content on Hover or Focus
2.1.1 Keyboard Navigation
2.4.3 Focus Order
2.4.6 Headings and Labels
2.4.7 Focus Visible
3.1.2 Language of Parts
3.2.1 On Focus
3.2.2 On Input
3.3.1 Error Identification
3.3.2 Labels or Instructions
4.1.2 Name, Role, Value
Web: Most functions of the product are usable without perception of color. Exceptions include:
1.4.1 Use of Color
1.4.3 Contrast (minimum)
1.4.11 Non-Text Contrast
3.3.1 Error Identification
Web: Most functions of the product are usable without hearing. Exceptions include:
1.2.2 Captions (prerecorded)
Web: Most functions of the product are usable with limited hearing. Exceptions include:
1.2.2 Captions (prerecorded)
Most functions of the product are usable by people with limited manipulation and does not require manipulation, simultaneous action, or hand strength. Exceptions include:
1.3.5 Identify Input Purpose
1.4.13 Content on Hover or Focus
2.1.1 Keyboard Navigation
2.4.3 Focus Order
2.4.6 Headings and Labels
2.4.7 Focus Visible
2.5.1 Pointer Gestures
2.5.3 Label in Name
3.2.1 On Focus
4.1.2 Name, Role, Value
Most functions of the product are usable with limited reach. Exceptions include:
1.3.5 Identify Input Purpose
1.4.13 Content on Hover or Focus
2.5.1 Pointer Gestures
2.5.3 Label in Name
Most functions of the product are usable with limited language, cognitive, and learning abilities. Users with cognitive disabilities have varying needs for features that allow them to adapt content and work with assistive technology or accessibility features of the platform. The product provides. Exceptions include:
1.1.1 Non-Text Content
1.2.2 Captions (prerecorded)
1.2.3 Audio Description or Media
Alternative (prerecorded)
1.3.1 Info and Relationships
1.3.2 Meaningful Sequence
1.3.5 Identify Input Purpose
1.4.1 Use of Color
1.4.10 Reflow
1.4.12 Text Spacing
1.4.13 Content on Hover or Focus
2.1.1 Keyboard Navigation
2.4.3 Focus Order
2.4.6 Headings and Labels
2.4.7 Focus Visible
2.5.1 Pointer Gestures
2.5.3 Label in Name
3.1.2 Language of Parts
3.2.1 On Focus
3.2.2 On Input
3.3.1 Error Identification
3.3.2 Labels or Instructions
4.1.2 Name, Role, Value
4.1.3 Status Messages
Chapter 5: Generic Requirements
Notes:
Chapter 6: ICT with Two-Way Voice Communication
Notes: Not Applicable
Chapter 7: ICT with Video Capabilities
Notes:
The product has the ability to show closed captions however the appearance of those closed captions cannot be modified by the user.
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. This occurs on the following page: Video Asset.
The product supports language subtitles however it does not have a function to speak those subtitles out loud.
A multimedia player that provides access to subtitles does not provide an option for the subtitles to be read aloud, so people who are blind or low vision may not be able to hear the dialogue in a language they can understand. This occurs on the following page: Video Asset.
The product does not provide a mechanism to select and play closed audio description.
A multimedia player cannot play an audio description track, so people who are blind or have low vision are not able to access the information in the video portion of the multimedia described in the audio track. This occurs on the following page: Video Asset.
The product provides user controls for captions, but not for audio descriptions.
A multimedia player provides a closed caption control but does not also provide a control to activate the audio description track, so people who are blind, low vision, and others who need audio description will not be able to access information provided by the video alone. This occurs on the following page: Video Asset.
Chapter 8: Hardware
Notes: Not Applicable
Chapter 9: Web (see WCAG 2.2 section)
Notes :
Chapter 10: Non-Web Documents
Notes : Not Applicable
Chapter 11: Software
Notes: Not Applicable
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