EN 301 549 Report
Notes:
(Based on VPAT® Version 2.4)
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
Revised Section 508
Software: The product provides sufficient text alternatives for most instances of images, such as the Stager logo and tools icons. Exceptions include:
Icons within the labels in the “Keyboard shortcuts” section.
Provide alternatives for time-based media.
1.2.1 Audio-only and Video-only (Prerecorded) (Level A)
Also applies to:
EN 301 549 Criteria
Revised Section 508
1.2.2 Captions (Prerecorded) (Level A)
Also applies to:
EN 301 549 Criteria
Revised Section 508
1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A)
Also applies to:
EN 301 549 Criteria
Revised Section 508
1.2.4 Captions (Live) (Level AA)
Also applies to:
EN 301 549 Criteria
Revised Section 508
1.2.5 Audio Description (Prerecorded) (Level AA)
Also applies to:
EN 301 549 Criteria
Revised Section 508
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
Revised Section 508
Software: Some structure and relationship information, such as labels for some form controls, is provided through element semantics or in text. However, most structure and relationship information is not provided programmatically or in text, such as:
Labels for form groups including transform controls (e.g., “Position”, “Rotation”, “Scale”, and “Size”) are not programmatically associated with each control.
Labels for form controls including inputs, radio buttons, sliders, and dropdowns.
Table headers are not programmatically associated with their respective data cells.
Headings are not identified, or the heading level is out of order.
1.3.2 Meaningful Sequence (Level A)
Also applies to:
EN 301 549 Criteria
Revised Section 508
1.3.3 Sensory Characteristics (Level A)
Also applies to:
EN 301 549 Criteria
Revised Section 508
1.3.4 Orientation (Level AA 2.1 only)
Also applies to:
EN 301 549 Criteria
Revised Section 508 – Does not apply
1.3.5 Identify Input Purpose (Level AA 2.1 only)
Also applies to:
EN 301 549 Criteria
Revised Section 508 – Does not apply
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
Revised Section 508
1.4.2 Audio Control (Level A)
Also applies to:
EN 301 549 Criteria
Revised Section 508
1.4.3 Contrast (Minimum) (Level AA)
Also applies to:
EN 301 549 Criteria
Revised Section 508
Software: Most text meets minimum contrast requirements. Exceptions include:
Buttons on focus have insufficient color contrast.
File name, time remaining, and percentage of render status have insufficient color contrast.
1.4.4 Resize text (Level AA)
Also applies to:
EN 301 549 Criteria
Revised Section 508
Software: The product does not provide its own text resizing function. When text is resized using operating system display scaling, content and functionality is lost in most product functions. Examples include:
The font size for text within the product does not increase when using operating system display scaling
1.4.5 Images of Text (Level AA)
Also applies to:
EN 301 549 Criteria
Revised Section 508
1.4.10 Reflow (Level AA 2.1 only)
Also applies to:
EN 301 549 Criteria
Revised Section 508 – Does not apply
1.4.11 Non-text Contrast (Level AA 2.1 only)
Also applies to:
EN 301 549 Criteria
Revised Section 508 – Does not apply
Software: Most meaningful non-text content elements, such as iconography, have sufficient contrast. Exceptions include:
The “Take a snapshot” button does not have sufficient color contrast.
1.4.12 Text Spacing (Level AA 2.1 only)
Also applies to:
EN 301 549 Criteria
Revised Section 508 – Does not apply
1.4.13 Content on Hover or Focus (Level AA 2.1 only)
Also applies to:
EN 301 549 Criteria
Revised Section 508 – Does not apply
Make all functionality available from a keyboard.
2.1.1 Keyboard (Level A)
Also applies to:
EN 301 549 Criteria
Revised Section 508
Software: Most product functionality can be operated through a keyboard interface. Exceptions include:
The application menu is not accessible via the keyboard.
Button menus and tooltips cannot be accessed with the keyboard.
Manipulation controls within the view port cannot be used with the keyboard.
Some sliders and buttons rely on the mouse to utilize.
2.1.2 No Keyboard Trap (Level A)
Also applies to:
EN 301 549 Criteria
Revised Section 508
2.1.4 Character Key Shortcuts (Level A 2.1 only)
Also applies to:
EN 301 549 Criteria
Revised Section 508 – Does not apply
Provide users enough time to read and use content.
2.2.1 Timing Adjustable (Level A)
Also applies to:
EN 301 549 Criteria
Revised Section 508
2.2.2 Pause, Stop, Hide (Level A)
Also applies to:
EN 301 549 Criteria
Revised Section 508
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
Revised Section 508
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
Revised Section 508
2.4.2 Page Titled (Level A)
Also applies to:
EN 301 549 Criteria
Revised Section 508
Software: Exceptions include:
Dialogs do not describe their topic or purpose.
2.4.3 Focus Order (Level A)
Also applies to:
EN 301 549 Criteria
Revised Section 508
Software: Most components receive focus in a meaningful order. Exceptions include:
Programmatic focus does not return to spawning elements of dialogs and dropdown menus.
Focus is lost when activating some buttons and closing dialogs.
Focus is not set on some dialogs when they open.
2.4.4 Link Purpose (In Context) (Level A)
Also applies to:
EN 301 549 Criteria
Revised Section 508
2.4.5 Multiple Ways (Level AA)
Also applies to:
EN 301 549 Criteria
Revised Section 508
2.4.6 Headings and Labels (Level AA)
Also applies to:
EN 301 549 Criteria
Revised Section 508
Software: Exceptions include:
Icons within labels (e.g., in the “Keyboard shortcuts” section adjacent to each input) do not describe meaning or purpose, causing the labels to be non-descriptive.
2.4.7 Focus Visible (Level AA)
Also applies to:
EN 301 549 Criteria
Revised Section 508
Make it easier for users to operate functionality through various inputs beyond keyboard.
2.5.1 Pointer Gestures (Level A 2.1 only)
Also applies to:
EN 301 549 Criteria
Revised Section 508 – Does not apply
2.5.2 Pointer Cancellation (Level A 2.1 only)
Also applies to:
EN 301 549 Criteria
Revised Section 508 – Does not apply
2.5.3 Label in Name (Level A 2.1 only)
Also applies to:
EN 301 549 Criteria
Revised Section 508 – Does not apply
Software: In most product functions, accessible names of controls do not contain the text of their visible labels. Examples include:
Labels for form controls, including inputs, radio buttons, sliders, and dropdowns.
In most forms, input fields have a visible label but do not provide a programmatic name.
2.5.4 Motion Actuation (Level A 2.1 only)
Also applies to:
EN 301 549 Criteria
Revised Section 508 – Does not apply
Make text content readable and understandable.
3.1.1 Language of Page (Level A)
Also applies to:
EN 301 549 Criteria
Revised Section 508
3.1.2 Language of Parts (Level AA)
Also applies to:
EN 301 549 Criteria
Revised Section 508
Make Web pages appear and operate in predictable ways.
3.2.1 On Focus (Level A)
Also applies to:
EN 301 549 Criteria
Revised Section 508
Software: In most product functions, components do not initiate a change of context when focused. Exceptions include:
Context changes when some sliders receive focus.
3.2.2 On Input (Level A)
Also applies to:
EN 301 549 Criteria
Revised Section 508
Software: Exceptions include:
Context changes on input in form controls within the “Keyboard shortcuts” section. The Tab key is recognized, and the user cannot change the value when navigating to each control.
3.2.3 Consistent Navigation (Level AA)
Also applies to:
EN 301 549 Criteria
Revised Section 508
3.2.4 Consistent Identification (Level AA)
Also applies to:
EN 301 549 Criteria
Revised Section 508
Help users avoid and correct mistakes.
3.3.1 Error Identification (Level A)
Also applies to:
EN 301 549 Criteria
Revised Section 508
3.3.2 Labels or Instructions (Level A)
Also applies to:
EN 301 549 Criteria
Revised Section 508
Software: Labels are provided for most input fields. Exceptions include:
A placeholder is used for the “Search Scene…” field that disappears on input.
3.3.3 Error Suggestion (Level AA)
Also applies to:
EN 301 549 Criteria
Revised Section 508
3.3.4 Error Prevention (Legal, Financial, Data) (Level AA)
Also applies to:
EN 301 549 Criteria
Revised Section 508
Maximize compatibility with current and future user agents, including assistive technologies.
4.1.1 Parsing (Level A)
Also applies to:
EN 301 549 Criteria
Revised Section 508
4.1.2 Name, Role, Value (Level A)
Also applies to:
EN 301 549 Criteria
Revised Section 508
Software: User interface components in most product functions do not provide programmatic name, role, state, or value information. Examples include:
Tab controls do not provide the correct selected state to the user.
Disabled links do not have a disabled state or role.
Tool buttons do not represent their current selected state.
Many buttons do not have an accessible name (including, but not limited to, tools) or state (e.g., the expandable controls do not announce expanded state).
The view port and information contained within list boxes and list items are not available to assistive technology users.
4.1.3 Status Messages (Level AA 2.1 only)
Also applies to:
EN 301 549 Criteria
Revised Section 508 – Does not apply
Notes:
Notes: This table documents instances of equivalent facilitation or instances of functions not addressed by technical requirements. Responses which cite technical requirements are informative only.
Software: Most functions of the product are not usable without vision. Examples include:
As noted in 1.1.1 Non-text Content, some images do not have alternative text.
As noted in 1.3.1 Info and Relationships, most form fields are not labeled, tables do not have headers, form controls groups do not have common labels, and most headings are not identified or are out of order.
As noted in 2.1.1 Keyboard, many menus, buttons, and tooltips cannot be accessed using the keyboard.
As noted in 2.4.2 Page Titled, dialogs are not properly labeled.
As noted in 2.4.3 Focus Order, programmatic focus does not shift to new content such as dialogs nor return to spawning elements. Focus is lost when some actions occur.
As noted in 3.1.1 Language of Page, the default language of the application cannot be programmatically determined.
As noted in 3.2.1 On Focus, context changes on focus occur on some controls.
As noted in 3.2.2 On Input, context changes on input occur on some controls.
As noted in 3.3.2 Labels and Instructions, the placeholder attribute is used to provide a visible label.
As noted in 4.1.2 Name, Role, Value, most elements do not have an accessible name or role that can be programmatically determined. Most elements do not provide the correct state to the user or no state at all.
As noted in 502.2.2 No Disruption of Accessibility Features, the user is unable to resize the text within the application.
Software: : Most functions of the product are usable with limited vision. Exceptions include:
As noted in 1.4.3 Contrast (Minimum), some text and buttons on focus do not have sufficient color contrast.
As noted in 1.4.4 Resize Text, the user is unable to increase the font size within the application.
As noted in 11.7 User Preferences, the user is unable to increase the font size within the application.
As noted in 503.2 User Preferences, the user is unable to increase the font size within the application.
Software: Most of the product is functional with limited manipulation. Exceptions include:
As noted in 2.1.1 Keyboard, many menus, buttons, and tooltips cannot be accessed using the keyboard.
As noted in 2.4.3 Focus Order, programmatic focus does not shift to new content such as dialogs nor return to spawning elements. Focus is lost when some actions occur.
As noted in 3.2.1 On Focus, context changes on focus occur on some controls.
Most product functions do not disrupt platform accessibility features. Exceptions include:
As noted in 1.4.4 Resize Text, the user is unable to increase the font size of the application.
The product allows assistive technology to modify most states and properties of controls. Exceptions include:
As noted in 4.1.2 Name, Role, Value, some controls do not allow the user to change the state.
The product allows assistive technology to perform most actions on objects. Exceptions include:
As noted in 2.1.1 Keyboard, many menus, buttons, and tooltips cannot be accessed using the keyboard.
The product adapts to platform settings for color, contrast, and focus cursor. Exceptions include:
As noted in 1.4.4 Resize Text, the user is unable to increase the font size within the application.
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.
Notes:
Notes:
Software: Most functions of the product are not usable without vision. Examples include:
As noted in 1.1.1 Non-text Content, some images do not have alternative text.
As noted in 1.3.1 Info and Relationships, most form fields are not labeled, tables do not have headers, form controls groups do not have common labels, and most headings are not identified or are out of order.
As noted in 2.1.1 Keyboard, many menus, buttons, and tooltips cannot be accessed using the keyboard.
As noted in 2.4.2 Page Titled, dialogs are not properly labeled.
As noted in 2.4.3 Focus Order, programmatic focus does not shift to new content such as dialogs nor return to spawning elements. Focus is lost when some actions occur.
As noted in 3.1.1 Language of Page, the default language of the application cannot be programmatically determined.
As noted in 3.2.1 On Focus, context changes on focus occur on some controls.
As noted in 3.2.2 On Input, context changes on input occur on some controls.
As noted in 3.3.2 Labels and Instructions, the placeholder attribute is used to provide a visible label.
As noted in 4.1.2 Name, Role, Value, most elements do not have an accessible name or role that can be programmatically determined. Most elements do not provide the correct state to the user or no state at all.
As noted in 502.2.2 No Disruption of Accessibility Features, the user is unable to resize the text within the application.
Software: Most functions of the product are usable with limited vision. Exceptions include:
As noted in 1.4.3 Contrast (Minimum), some text and buttons on focus do not have sufficient color contrast.
As noted in 1.4.4 Resize Text, the user is unable to increase the font size within the application.
As noted in 11.7 User Preferences, the user is unable to increase the font size within the application.
As noted in 503.2 User Preferences, the user is unable to increase the font size within the application.
Software: Most of the product is functional with limited manipulation. Exceptions include:
As noted in 2.1.1 Keyboard, many menus, buttons, and tooltips cannot be accessed using the keyboard.
As noted in 2.4.3 Focus Order, programmatic focus does not shift to new content such as dialogs nor return to spawning elements. Focus is lost when some actions occur.
As noted in 3.2.1 On Focus, context changes on focus occur on some controls.
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:
Some graphical on-screen buttons do not have an accessible name.
Notes: Not Applicable
Notes: Not Applicable
Notes: Not Applicable
Notes: See WCAG 2.x section
Notes: Not Applicable
Notes:
The product allows assistive technology to perform most actions on objects. Exceptions include:
Some content, such as tooltips and menus, cannot be accessed using assistive technology.
The product allows assistive technology to modify most states and properties of controls. Exceptions include:
As noted in 4.1.2 Name, Role, Value, some controls do not allow the user to change the state.
Most product functions do not disrupt platform accessibility features. Exceptions include:
As noted in 1.4.4 Resize Text, the user is unable to increase the font size of the application.
The product adapts to platform settings for color, contrast, and focus cursor. Exceptions include:
As noted in 1.4.4 Resize Text, the user is unable to increase the font size within the application.
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.
Notes: Not Applicable
Voluntary Product Accessibility Template® and VPAT® are a registered trademark of Information Technology Industry Council (ITI)