Adobe Accessibility Conformance Report International Edition
Adobe Media Encoder Beta (Version: 25.4 Build 63)
Product Information
- Name of Product/Version: Adobe Media Encoder (Version: 25.4 Build 76)
- Product Description: Encode and export audio and video files with custom settings and presets from the Adobe Media queue in Adobe Media Encoder.
- Date: July 2025
- Platforms, OS and devices
- OS: Mac
- Platforms: Desktop
- Contact information: access@adobe.com
- Notes: This report was created by Deque Systems Inc. upon completion of an accessibility evaluation performed in July 2025.
- Evaluation Methods Used: Testing Adobe Media Encoder involved extensive use of leading assistive technology such as screen readers, screen magnifiers, and speech recognition software, as well exclusive use of the keyboard.
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.0 Report
Sections 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)
Software: Supports
Software: The product provides sufficient text alternatives for all the non-text content instances of the application.
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)
Software: Supports (Not Applicable)
Software: The product 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)
Software: Supports (Not Applicable)
Software: The product does not contain prerecorded synchronized media.
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)
Software: Supports (Not Applicable)
Software: The product does not contain prerecorded video content that would require audio description or a media alternative.
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)
Software: Partially Supports
Software: Most visual structure and relationship information is provided through [element semantics | object information or in text.
Exceptions include:
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 page: Create New Preset: Tabs.
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: Create New Preset: Tabs
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 pages: Video: Bitrate; Create New Preset: Tabs.
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)
Software: Does Not Support
Software: The product does not present most content in a meaningful sequence.
Exceptions include:
The order that the screen reader announces static content does not match the visual order of the content and changes the meaning of that content, so the intended meaning of the content will be lost or changed for people who are blind and/or use a screen reader. This occurs on the following page: Export Settings.
The screen reader skips and does not announce informative content (text), 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: Add Multiple Videos to Queue; Export Settings; Video: Bitrate; Create New Preset: Tabs; Create New Preset; Media Browser; Preset Browser Panel; Encoding.
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)
Software: Supports
Software: Instructions do not rely solely on sensory characteristics.
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)
Software: Supports
Software: The product does not convey information through color alone.
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)
Software: Supports (Not Applicable)
Software: The product 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)
Software: Does Not Support
Software: Most product functionality cannot 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. This issue occurs across most functionalities within the application example pages: This occurs across the application.
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)
Software: Supports
Software: The product does not include keyboard traps.
Guideline 2.2 Enough Time:
Provide users enough time to read and use content.
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
Software: Supports
Software: The product provides character key shortcuts; it is only active when the relevant user interface component is in focus.
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)
Software: Supports (Not Applicable)
Software: The product 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)
Software: Supports (Not Applicable)
Software: The product does not include elements which move, blink, scroll, or auto-update.
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)
Software: Supports (Not Applicable)
Software: The product does not contain flashing content.
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
Software: Supports (Not Applicable)
Software: This criterion does not apply to non-web software.
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)
Software: Supports
Software: The titles describe the software purpose.
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)
Software: Partially Supports
Software: Most components receive focus in a meaningful order.
Exceptions include:
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 page: Video: Bitrate.
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)
Software: Supports
Software: The purpose of links in the product can be determined from the link text alone or from the programmatic context of the link.
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)
Software: Supports
Software: The purpose of links in the product can be determined from the link text alone or from the programmatic context of the link.
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
Software: Supports
Software: The product 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
Software: Supports
Software: 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.
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
Software: Partially Supports
Software: In most product functions, accessible names of controls contain the text of their visible labels.
Exceptions 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: Export Settings; Video: Bitrate; Create New Preset: Tabs; Create New Preset.
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: Add Multiple Videos to Queue; Export Settings; Video: Bitrate; Create New Preset: Tabs; Create New Preset.
The accessible name of an interactive element (such as a link, button, or form input) contains its visible label, but the words are in a different order, so the accessible name does not contain the visible label, and people who use speech input to navigate and operate content will not be able to access the element. This occurs on the following page: Export 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 page: Create New Preset: Tabs.
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
Software: Supports (Not Applicable)
Software: The product does not have functionality operated by device motion or user motion.
Guideline 3.1 Readable:
Make text content readable and understandable.
Criteria
Conformance Level
Remarks and Explanations
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)
Software: Supports
Software: The language is programmatically determinable within the product.
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)
Software: Supports
Software: Components do not initiate a change of context when focused.
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)
Software: Partially Supports
Software: Changes of context do not occur automatically on most user input.
Exceptions include:
When navigating a dropdown with the arrow keys, moving to an option but not selecting it, results in an unexpected change of context (such as moving focus to another element or changing the content 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 pages: Add Multiple Videos to Queue; Video: Bitrate.
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 pages: Add Multiple Videos to Queue; Video: Bitrate; Preset Browser Panel.
3.2.6 Consistent Help (Level A 2.2 only)
EN 301 549 Criteria – Does not apply
Revised Section 508 – Does not apply
Software: Supports
Software: On application pages that contain help features (including human or automated contact options or self-help options), those features occur in the same order relative to other page content unless the user changes that order.
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)
Software: Supports (Not Applicable)
Software: The product does not detect input errors.
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)
Software: Partially Supports
Software: Labels are provided for most input fields.
Exceptions include:
The label for a form field is missing, so the field's purpose is not clear. This occurs on the following pages: Export Settings; Media Browser.
Select or dropdown control missing a visible label so the Select or dropdown control purpose is not clear. This occurs on the following page: Add Multiple Videos to Queue.
3.3.7 Redundant Entry (Level A 2.2 only)
EN 301 549 Criteria – Does not apply
Revised Section 508 – Does not apply
Software: Supports
Software: 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.
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)
Software: Supports (Not Applicable)
Software: The product 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)
Software: Does Not Support
Software: User interface components in most product functions do not provide programmatic name, role, state, or value information.
Exceptions include:
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: Create New Preset: Tabs.
A custom radio button does not have a role and/or a state (checked/unchecked) 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 radio button, how to use it, and whether it is checked. This occurs on the following page: Create New Preset: Tabs.
For an element that allows 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 the element, the options available, and whether the element or an option is currently checked. This occurs on the following page: Media Browser.
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: Create New Preset: Tabs.
A control has an incorrect programmatic role, so the role (like button or link) conveyed to screen readers and other assistive technologies is incorrect and misrepresents the control's function to people who use those technologies. This occurs on the following pages: This occurs across the application.
A control (such as a button or link) 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: Add Multiple Videos to Queue; Export Settings; Video: Bitrate; Create New Preset: Tabs; Create New Preset; Media Browser; Preset Browser Panel.
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 across the application.
The control 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: Add Multiple Videos to Queue; Create New Preset: Tabs; Media Browser.
Table 2: Success Criteria, Level AA
Notes:
Guideline 1.2 Time-based Media:
Provide alternatives for time-based media.
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)
Software: Supports (Not Applicable)
Software: The product 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)
Software: Supports (Not Applicable)
Software: The product does not contain prerecorded video content that would require audio description.
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
Software: Supports
Software: Content does not restrict its view and operation to a single display orientation.
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
Software: Supports (Not Applicable)
Software: The product’s technology does not have support for programmatic identification of input purpose.
Guideline 1.4 Distinguishable:
Make it easier for users to see and hear content including separating foreground from background.
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)
Software: Partially Supports
Software: Most text meets minimum contrast requirements.
Exceptions include:
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: Export Settings; Video: Bitrate; Create New Preset: Tabs; Create New Preset.
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)
Software: Supports
Software: The product allows operating system display scaling to resize text up to 200 percent without loss of content or functionality.
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)
Software: Supports
Software: The product uses text instead of images of text, except for branding elements that are considered essential.
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
Software: Supports
Software: At the required width of 320 CSS pixels, content is presented without loss of information or functionality, and without requiring scrolling in two dimensions.
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
Software: Does Not Support
Software: Most of the boundaries and indicators of the visual state(s) of each active user component and any graphics required to understand content have a 3:1 color contrast ratio with adjacent color 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 perceiving the boundaries of the interactive element. This occurs on the following pages: Video: Bitrate; Create New Preset: Tabs; Media Browser.
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 understand the information presented by the icon. This occurs on the following pages: This occurs across the application.
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 perceiving the state of the interactive element. This occurs on the following pages: Add Multiple Videos to Queue; Export Settings; Media Browser.
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 page: This occurs across the application.
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
Software: Supports (Not Applicable)
Software: The product is not implemented using markup languages.
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
Software: Does Not Support
Software: 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: This occurs across the application.
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: This occurs across the application.
Content that appears on mouse hover or keyboard focus (such as tooltips, drop-down menus, or popups) does not remain visible until dismissed or invalid, so people with some disabilities, especially motor or reading disabilities, may not be able to read this additional content. This occurs across the application.
Guideline 2.4 Navigable:
Provide ways to help users navigate, find content, and determine where they are.
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
Software: Supports (Not Applicable)
Software: This criterion does not apply to non-web software.
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)
Software: Partially Supports
Software: 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: Export Settings; App wide; Video: Bitrate; Create New Preset: Tabs; Create New Preset.
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: Create New Preset: Tabs; Video: Bitrate.
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)
Software: Partially Supports
Software: 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: Export Settings; Media Browser.
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
Software: Supports
Software: When a user interface component receives keyboard focus, the component is not entirely hidden due to author-created content.
2.5.7 Dragging Movements (Level AA 2.2 only)
EN 301 549 Criteria – Does not apply
Revised Section 508 – Does not apply
Software: Does Not Support
Software: 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 (Column width adjustment options within the table) 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 page: This occurs across the application.
2.5.8 Target Size (Minimum) (Level AA 2.2 only)
EN 301 549 Criteria – Does not apply
Revised Section 508 – Does not apply
Software: Supports
Software: The size of the target for each clickable control 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.
Guideline 3.1 Readable:
Make text content readable and understandable.
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)
Software: Supports (Not Applicable)
Software: Content is only presented in one language at a time.
Guideline 3.2 Predictable:
Make Web pages appear and operate in predictable ways.
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
Software: Supports (Not Applicable)
Software: This criterion does not apply to non-web software.
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
Software: Supports (Not Applicable)
Software: This criterion does not apply to non-web software.
Guideline 3.3 Input Assistance:
Help users avoid and correct mistakes.
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)
Software: Supports (Not Applicable)
Software: The product does not detect input errors that are displayed to users.
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)
Software: Supports
Software: The product does not process legal commitments or financial transactions. When editing files changes to user-controllable data are reversible or can be confirmed before finalizing.
3.3.8 Accessible Authentication (Minimum) (Level AA 2.2 only)
EN 301 549 Criteria – Does not apply
Revised Section 508 – Does not apply
Software: Supports
Software: 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 application.
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
Software: Partially Supports
Software: 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: Add Multiple Videos to Queue; Encoding; Preset Browser Panel.
Table 3: Success Criteria, Level AAA
Notes: Not Applicable
Revised Section 508 Report
Notes:
Chapter 3: Functional Performance Criteria (FPC)
Notes:
Software: Partially Supports
Software: Most functions of the product are usable without vision.
Exceptions include:
1.3.1 Info and Relationships
1.3.2 Meaningful Sequence
2.1.1 Keyboard
2.4.3 Focus Order
2.4.6 Headings and Labels
3.2.2 On Input
4.1.2 Name, Role, Value
Software: Partially Supports
Software: Most functions of the product are usable With Limited Vision.
Exceptions include:
1.3.1 Info and Relationships
1.3.2 Meaningful Sequence
1.4.3 Contrast (minimum)
2.1.1 Keyboard
2.4.3 Focus Order
2.4.6 Headings and Labels
2.4.7 Focus Visible
3.2.2 On Input
3.3.2 Labels or Instructions
4.1.2 Name, Role, Value
Software: Partially Supports
Software: Most functions of the product are usable without perception of color.
Exceptions include:
1.4.3 Contrast (minimum)
Software: Supports (Not Applicable)
Software: The product does not require the use of hearing.
Software: Supports (Not Applicable)
Software: The product does not require the use of with Limited Hearing.
Software: Supports (Not Applicable)
Software: The product does not require the use of speech.
Software: Partially Supports
Software: Most functions of the product are usable with limited manipulation.
Exceptions include:
2.1.1 Keyboard
2.4.3 Focus Order
2.4.6 Headings and Labels
2.4.7 Focus Visible
4.1.2 Name, Role, Value
Software: Supports
Software: The product is functional with limited reach and strength.
Software: Partially Supports
Software: 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.3.1 Info and Relationships
1.3.2 Meaningful Sequence
2.1.1 Keyboard
2.4.3 Focus Order
2.4.6 Headings and Labels
2.4.7 Focus Visible
3.2.2 On Input
3.3.2 Labels or Instructions
4.1.2 Name, Role, Value
Chapter 4: Hardware
Notes: Not Applicable
Chapter 5: Software
Notes:
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) is available programmatically, so it 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 its 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
Most text, text attributes (such as whether text is static or editable), and text boundaries are programmatically determinable, so they can be perceived and conveyed 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.a 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: 4.2 Functional Performance Statements (FPS)
Notes:
Software: Partially Supports
Software: Most functions of the product are usable without vision.
Exceptions include:
1.3.1 Info and Relationships
1.3.2 Meaningful Sequence
2.1.1 Keyboard
2.4.3 Focus Order
2.4.6 Headings and Labels
3.2.2 On Input
4.1.2 Name, Role, Value
4.1.3 Status Messages
Software: Partially Supports
Software: Most functions of the product are usable With Limited Vision.
Exceptions include:
1.3.1 Info and Relationships
1.3.2 Meaningful Sequence
1.4.3 Contrast (minimum)
1.4.11 Non-Text Contrast
1.4.13 Content on Hover or Focus
2.1.1 Keyboard
2.4.3 Focus Order
2.4.6 Headings and Labels
2.4.7 Focus Visible
3.2.2 On Input
3.3.2 Labels or Instructions
4.1.2 Name, Role, Value
Software: Partially Supports
Software: Most functions of the product are usable without perception of color.
Exceptions include:
1.4.3 Contrast (minimum)
1.4.11 Non-Text Contrast
Software: Supports (Not Applicable)
Software: The product does not require the use of hearing.
Software: Supports (Not Applicable)
Software: The product does not require the use of with Limited Hearing.
Software: Supports (Not Applicable)
Software: The product does not require the use of speech.
Software: Partially Supports
Software: Most functions of the product are usable with limited manipulation and strength. Exceptions include:
1.4.13 Content on Hover or Focus
2.1.1 Keyboard
2.4.3 Focus Order
2.4.6 Headings and Labels
2.4.7 Focus Visible
2.5.3 Label in Name
4.1.2 Name, Role, Value
Software: Partially Supports
Software: Most functions of the product are usable with limited reach. Exceptions include:
1.4.13 Content on Hover or Focus
2.5.3 Label in Name
Software: Supports (Not Applicable)
Software: The product does not contain flashing content.
Software: Partially Supports
Software: 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.3.1 Info and Relationships
1.3.2 Meaningful Sequence
1.4.13 Content on Hover or Focus
2.1.1 Keyboard
2.4.3 Focus Order
2.4.6 Headings and Labels
2.4.7 Focus Visible
2.5.3 Label in Name
3.2.2 On Input
3.3.2 Labels or Instructions
4.1.2 Name, Role, Value
4.1.3 Status Messages
Software: Supports (Not Applicable)
Software: The product does not ask for or display legal, financial, or personal data.
Chapter 5: Generic Requirements
Notes:
The product has only non-mechanical operable parts, such as on-screen buttons. Most operable parts have an accessible name which enables them to be discernible without user vision. Exceptions include:
4.1.2 Name, Role, Value.
Chapter 6: ICT with Two-Way Voice Communication
Notes: Not Applicable
Chapter 7: ICT with Video Capabilities
Notes: Not Applicable
Chapter 8: Hardware
Notes: Not applicable to this product.
Chapter 9: Web
Notes: See WCAG 2.0 section.
Chapter 10: Non-web Documents
Notes: Not Applicable
Chapter 11: Software
Notes:
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.a 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) is available programmatically, so it can be perceived and conveyed by 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.a Name, Role, Value
Most text, text attributes (such as whether text is static or editable), and text boundaries are programmatically determinable, so they can be perceived and conveyed 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.a Status Messages
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
For most objects that allow the user to set or modify its 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
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