Adobe Accessibility Conformance Report International Edition
(Based on VPAT® Version 2.4)
Product Information
Name of Product/Version: Adobe Frame.io iOS
Report Dated: September 30, 2025
Product Description: Frame.io is a creative collaboration tool that lets you share media, track feedback, and streamline your workflow so your team can work closely together from anywhere in the world.
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, screen magnifiers, and speech recognition software. Native platform accessibility features were also used to assist with testing. These were supplemented with techniques such as manual inspection of Accessibility API output.
Applicable Standards/Guidelines
This report covers the degree of conformance for the following accessibility standards/guidelines:
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.
Software: The product provides sufficient text alternatives for most instances of images, such as informative images.
Exceptions include:
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 page: Sign-In.
Software: Most visual structure and relationship information, such as headings, are provided through element semantics.
Exceptions include:
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: Notifications; Feedback; App Settings.
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 page: App Settings.
Some information, structure, and/or relationships are only presented visually but not conveyed programmatically, so context provided to sighted users is not available to people who are blind. This occurs on the following page: Text Markup.
Data is arranged visually like a data table, but the table does not have proper markup for the table headers, so 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 page: App Settings.
Software: The product presents most content in a meaningful sequence.
Exceptions include:
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 page: Recently Deleted.
Screen reader focus is lost or misplaced due to user interaction or content update, making navigation difficult or impossible for people who are blind and/or use a screen reader or other assistive technology. This occurs on the following page: Document Type Asset.
When a modal is closed, screen reader focus is not returned to the control that opened the modal or to another logical location, making navigation difficult for people who are blind and/or use a screen reader. This occurs on the following pages: Share Settings; Create / Rename/ Delete new folder; Recently Deleted.
A hidden or empty interactive element receives screen reader focus, so people who are blind and/or use a screen reader will navigate to an element that is not intended to be part of the reading order on the page or has no content/functionality. This occurs on the following page: Feedback.
Software: 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 page: App Settings.
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: Search; Feedback; Text Markup.
Software: Most product functionality cannot be operated through a keyboard interface.
Exceptions include:
An action cannot be performed when using a screen reader, so people who are blind and others who use a screen reader cannot perform this action. This occurs on the following pages: Feedback; Share Settings; Project Navigation; Custom Sort in Share Builder; Playback - Video Asset; Navigate through recent workspaces; Share Viewer; Metadata; App Settings.
An action cannot be performed when using voice control, so people who rely on voice control to navigate and operate content cannot perform that action. This issue occurs on the following pages: Edit Share, Customize Fields & Share Header, Share Settings, Feedback, Custom Sort in Share Builder, Playback – Video Asset, Fields Panel.
Software: Most of the product supports the adjustment or cancellation of time-based limits.
Exceptions include:
Some content visually appears and disappears with no ability to adjust how long the content is visible, potentially preventing people who are blind, have low vision, or have mobility or cognitive disabilities from locating or reading the content. This occurs on the following page: Feedback.
Software: Most of the time moving, blinking, scrolling, and auto-updating information can be paused, stopped or hidden by the user.
Exceptions include:
The user cannot pause, stop, or hide content that automatically moves, blinks, or scrolls, so people who cannot read text quickly, have attention deficit disorders or other cognitive disabilities, or use a screen reader may not be able to read or understand the content. This occurs on the following page: Sign-In.
The user cannot pause, stop, or hide auto-updating content, so people who cannot read text quickly, have attention deficit disorders or other cognitive disabilities, or use a screen reader may not be able to read or understand the content before it updates. This occurs on the following page: Search.
Guideline 2.3 Seizures:
Do not design content in a way that is known to cause seizures.
Software: Most of the product does not rely on multipoint or path-based gestures.
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 page: Add / delete Assets.
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.
Software: On web 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.
Software: Most input errors are identified and described to the users in text.
Exceptions include:
A form field with an error is not identified in the text error message or a text alternative for an image, and the error message with the field name is not programmatically associated with the form field (so it is announced when a screen reader user navigates to the field), so people who are blind and/or use a screen reader will not be able to identify in which form field the error occurred. This occurs on the following pages: Fields Panel; Create / Rename/ Delete new folder.
Software: 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: Feedback; Text Markup; Navigation; Custom Sort in Share Builder; Add New Member; Send Feedback.
The label for a dropdown selection control is missing, so the dropdown selection control purpose is not clear. This occurs on the following pages: Share Settings; Project Navigation.
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.
Software: User interface components in most product functions provide programmatic name, role, state, or value information.
Exceptions include:
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: Feedback; Text Markup.
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: Fields Panel; Feedback.
A form control (such as a text input field or checkbox) is not programmatically associated with its visible label, so people who are blind and/or use a screen reader or other assistive technology may not be able to understand the purpose of the form control or what input it requires. This occurs on the following pages: Feedback; Text Markup; Share Settings; Create / Rename/ Delete new folder; Delete Project; Metadata; Create new project; Document Type Asset.
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: Upload Files / Photos; Notification Settings; App Settings.
Some informative static text is assigned an interactive role that is announced by a screen reader, so people who are blind and/or use a screen reader may be confused. This occurs on the following pages: Navigate through recent workspaces; Add New Member.
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: Add / delete Assets; Edit Share.
Software: The product restricts its view to portrait orientation.
Exceptions include:
When the display orientation is changed (from portrait to landscape or vice versa), the content does not adjust to the new orientation, so people who require a particular display orientation may not be able to access some of that content or functionality. This issue occurs on all pages evaluated.
Software: 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 page: Project Navigation.
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: Notifications; Add / delete Assets; Fields Panel; Manage Existing Members Access; Feedback; Text Markup; Image Type Asset; Share Settings; Create / Rename/ Delete new folder; Custom Sort in Share Builder; Add New Member; Recently Deleted; Delete Project; Metadata; Sign-In; App Settings; Document Type Asset; Playback - landscape (video asset).
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.
Software: Most meaningful non-text content elements do not have sufficient contrast.
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: Add / delete Assets; Manage Existing Members Access; Upload Files / Photos; Share Settings; Project Navigation; Playback - Video Asset; Add New Member; Edit Share; Notification Settings; Delete Project; Metadata; Customize Fields & Share Header; App Settings.
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 issue occurs on all pages evaluated.
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: Search; Add / delete Assets; Fields Panel; Manage Existing Members Access; Upload Files / Photos; Feedback; Text Markup; Share Settings; Project Navigation; Custom Sort in Share Builder; Playback - Video Asset; Add New Member; Edit Share; Notification Settings; Metadata; Customize Fields & Share Header; Create new project; App Settings; Account Switcher.
Software: Most headings and labels are descriptive.
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 issue occurs on all pages evaluated.
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: Search; Upload Files / Photos; Share Settings; Share Viewer; Recently Deleted; Open a Project.
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 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: Feedback; Custom Sort in Share Builder; Playback - Video Asset; Share Viewer; Metadata.
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.
Software: The product does not process legal commitments or financial transactions. Changes to user-controllable data are reversible or can be confirmed before finalizing.
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 website.
Software: In most cases, when status updates do not receive focus, the product provides the update to assistive technology.
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: Search; Fields Panel; Manage Existing Members Access; Upload Files / Photos; Feedback; Share Settings; Project Navigation; Create / Rename/ Delete new folder; Custom Sort in Share Builder; Metadata; Sign-In; Document Type Asset.
Software: The product is functional for users without vision.
Exceptions include:
As noted in 1.1.1 Non-Text Content
As noted in 1.3.1 Info and Relationships
As noted in 1.3.2 Meaningful Sequence
As noted in 1.4.1 Use of Color
As noted in 2.1.1 Keyboard
As noted in 2.2.1 Timing Adjustable
As noted in 2.4.6 Headings and Labels
As noted in Error Identification
As noted in 4.1.2 Name, Role, Value
302.2 With Limited Vision
Software: Partially Supports
Software: Most functions of the product is usable with limited vision.
Exceptions include:
As noted in 1.1.1 Non-Text Content
As noted in 1.3.1 Info and Relationships
As noted in 1.3.2 Meaningful Sequence
As noted in 1.4.1 Use of Color
As noted in 1.4.3 Contrast (minimum)
As noted in 2.1.1 Keyboard
As noted in 2.2.1 Timing Adjustable
As noted in 2.4.6 Headings and Labels
As noted in 3.3.1 Error Identification
As noted in 3.3.2 Labels or Instructions
As noted in 4.1.2 Name, Role, Value
302.3 Without Perception of Color
Software: Partially Supports
Software: Most functions of the product are usable without perception of color.
Exceptions include:
As noted in 1.4.1 Use of Color
As noted in 1.4.3 Contrast (minimum)
As noted in 3.3.1 Error Identification
302.4 Without Hearing
Software: Supports
Software: The product is functional for users without hearing.
302.5 With Limited Hearing
Software: Supports
Software: The product is functional for users with limited hearing.
302.6 Without Speech
Software: Supports (Not Applicable)
Software: The product does not require the use of speech.
302.7 With Limited Manipulation
Software: Partially Supports
Software: Most functionality is usable with limited manipulation and does not require fine motor control or simultaneous manual operations.
Exceptions include:
As noted in 2.1.1 Keyboard
As noted in 2.2.1 Timing Adjustable
As noted in 2.4.6 Headings and Labels
As noted in 4.1.2 Name, Role, Value
302.8 With Limited Reach and Strength
The product is functional with limited reach.
The product is functional with limited reach.
302.9 With Limited Language, Cognitive, and Learning Abilities
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 descriptive labels, instructions, and error identification and suggestions for most user input.
The role, states, properties, boundary, name, and description of most objects can be programmatically determined, so those attributes can be perceived and conveyed by assistive technology
Exceptions include:
As noted in 4.1.2 Name, Role, Value
502.3.2 Modification of Object Information
Partially Supports
For most objects that allow the user to set their respective properties and/or state, the act of setting a property or state is available programmatically, so that it can be perceived and performed using assistive technology.
Exceptions include:
As noted in 4.1.2 Name, Role, Value
502.3.3 Row, Column, and Headers
Partially Supports
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:
As noted in 1.3.1 Info and Relationships
502.3.4 Values
Partially Supports
For most objects that have a current value or have a set or range of values associated with the object, the values are available programmatically, so they can be perceived and conveyed by assistive technology.
Exceptions include:
As noted in 4.1.2 Name, Role, Value
502.3.5 Modification of Values
Partially Supports
For most objects that allow the user to set or modify their value, the act of setting a value is available programmatically, so that it can be perceived and performed using assistive technology.
Exceptions include:
As noted in 4.1.2 Name, Role, Value
502.3.6 Label Relationships
Partially Supports
For most elements that act as a label for another element and elements that are labeled by another element, the labeling relationship is programmatically determinable, so it can be perceived and conveyed by assistive technology.
Exceptions include:
As noted in 4.1.2 Name, Role, Value
502.3.7 Hierarchical Relationships
Partially Supports
When a page contains elements that have a parent-child relationship, those relationships are programmatically determinable, so they can be perceived by assistive technology.
Exceptions include:
As noted in 1.3.1 Info and Relationships
502.3.8 Text
Supports
The product’s text objects, text attributes, and on-screen text boundaries are exposed to assistive technology.
502.3.9 Modification of Text
Supports
The product allows assistive technology to modify the text.
502.3.10 List of Actions
Partially Supports
Most controls in the product expose programmatic role information, which conveys available actions to assistive technology.
Exceptions include
As noted in 4.1.2 Name, Role, Value.
502.3.11 Actions on Objects
Partially Supports
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:
As noted in 2.1.1 Keyboard
502.3.12 Focus Cursor
Supports
The product exposes focus location, text insertion point, and object selection state for user interface components.
502.3.13 Modification of Focus Cursor
Supports
When a user can focus or change selection state of a control in the product via keyboard, then the focus or selection state can also be changed programmatically.
502.3.14 Event Notification
Partially Supports
In most cases, status messages relevant to user interactions are available to, and presented by, assistive technology.
Exceptions include:
4.1.3 Status Messages
502.4 Platform Accessibility Features
Not Applicable
The product does not disrupt accessibility features.
The product does not permit user preferences from platform settings.
503.3 Alternative User Interfaces
Not Applicable
The product does not provide an alternative user interface that functions as assistive technology.
503.4 User Controls for Captions and Audio Description
Heading cell – no response required
Heading cell – no response required
503.4.1 Caption Controls
Partially Supports
The product provides user controls for closed captions; however, the caption controls are not at the same level as the volume or program selection controls.
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.
Software: Most functions of the product are usable without vision.
Exceptions include:
As noted in 1.1.1 Non-Text Content
As noted in 1.3.1 Info and Relationships
As noted in 1.3.2 Meaningful Sequence
As noted in 1.4.1 Use of Color
As noted in 2.1.1 Keyboard
As noted in 2.2.1 Timing Adjustable
As noted in 2.4.6 Headings and Labels
As noted in Error Identification
As noted in 4.1.2 Name, Role, Value
As noted in 4.1.3 Status Messages
4.2.2 Usage with limited vision
Software: Most functions of the product is usable with limited vision.
Exceptions include:
As noted in 1.1.1 Non-Text Content
As noted in 1.3.1 Info and Relationships
As noted in 1.3.2 Meaningful Sequence
As noted in 1.3.4 Device Orientation
As noted in 1.4.1 Use of Color
As noted in 1.4.3 Contrast (minimum)
As noted in 1.4.11 Non-Text Contrast
As noted in 2.1.1 Keyboard
As noted in 2.2.1 Timing Adjustable
As noted in 2.4.6 Headings and Labels
As noted in 3.3.1 Error Identification
As noted in 3.3.2 Labels or Instructions
As noted in 4.1.2 Name, Role, Value
4.2.3 Usage without perception of colour
Software: Partially Supports
Software: Most functions of the product are usable without perception of color.
Exceptions include:
As noted in 1.4.1 Use of Color
As noted in 1.4.3 Contrast (minimum)
As noted in 3.3.1 Error Identification
4.2.4 Usage without hearing
Software: Supports
Software: The product is functional for users without hearing.
4.2.5 Usage with limited hearing
Software: Supports
Software: The product is functional for users with limited hearing.
4.2.6 Usage with no or limited vocal capability
Software: Supports (Not Applicable)
Software: The product does not require the use of speech.
4.2.7 Usage with limited manipulation or strength
Software: Partially Supports
Software: Most functionality is usable with limited manipulation and does not require fine motor control or simultaneous manual operations.
Exceptions include:
As noted in 1.3.4 Device Orientation
As noted in 2.1.1 Keyboard
As noted in 2.2.1 Timing Adjustable
As noted in 2.4.6 Headings and Labels
As noted in 2.5.1 Pointer Gestures
As noted in 4.1.2 Name, Role, Value
4.2.8 Usage with limited reach
Software: Supports (Not Applicable)
Software: The product is functional with limited reach.
4.2.9 Minimize photosensitive seizure triggers
Software: Supports
Software: The product does not contain flashing content.
4.2.10 Usage with limited cognition, language or learning
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 descriptive labels, instructions, and error identification and suggestions for most user input.
Exceptions include:
As noted in 1.1.1 Non-Text Content
As noted in 1.3.1 Info and Relationships
As noted in 1.3.2 Meaningful Sequence
As noted in 1.3.4 Device Orientation
As noted in 1.4.1 Use of Color
As noted in 2.1.1 Keyboard
As noted in 2.2.1 Timing Adjustable
As noted in 2.2.2 Pause, Stop, Hide
As noted in 2.4.6 Headings and Labels
As noted in 2.5.1 Pointer Gestures
As noted in 3.3.1 Error Identification
As noted in 3.3.2 Labels or Instructions
As noted in 4.1.2 Name, Role, Value
As noted in 4.1.3 Status Messages
4.2.11 Privacy
Software: Supports (Not Applicable)
Software: The product does not ask for or display legal, financial, or personal data.
5.1.3.16 Receipts, tickets, and transactional outputs
Not Applicable
The product does not have closed functionality.
5.1.4 Functionality closed to text enlargement
Not Applicable
The product does not have closed functionality.
5.1.5 Visual output for auditory information
Not Applicable
The product does not have closed functionality.
5.1.6 Operation without keyboard interface
Heading cell – no response required
Heading cell – no response required
5.1.6.1 Closed functionality
See 5.1.3.1 through 5.1.3.16
See information in 5.1.3.1 through 5.1.3.16
5.1.6.2 Input focus
Not Applicable
The product does not have closed functionality.
5.1.7 Access without speech
Not Applicable
The product does not have closed functionality.
5.2 Activation of accessibility features
Not Applicable
The product does not have specific documented accessibility features. The product instead relies upon platform accessibility features.
5.3 Biometrics
Not Applicable
Biometrics is not included in the product.
5.4 Preservation of accessibility information during conversion
Not Applicable
The product does not convert content.
5.5 Operable parts
Heading cell – no response required
Heading cell – no response required
5.5.1 Means of operation
Not Applicable
The product has only non-mechanical operable parts, such as on-screen buttons, which do not require grasping, pinching, or twisting of the wrist to operate.
5.5.2 Operable parts discernibility
Not Applicable
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.
5.6 Locking or toggle controls
Heading cell – no response required
Heading cell – no response required
5.6.1 Tactile or auditory status
Not Applicable
Tactile or auditory status is not included in the product.
5.6.2 Visual status
Not Applicable
Visual status of controls is discernible in the product.
5.7 Key repeat
Not Applicable
Key repeat functionality is not found in the product.
5.8 Double-strike key acceptance
Not Applicable
Double-strike key acceptance is not found in the product.
5.9 Simultaneous user actions
Not Applicable
The product does not require simultaneous user actions to achieve any functionality.
Chapter 6: ICT with Two-Way Voice Communication
Notes: Not Applicable
Chapter 7: ICT with Video Capabilities
Notes:
Criteria
Conformance Level
Remarks and Explanations
7.1 Caption processing technology
Heading cell – no response required
Heading cell – no response required
7.1.1 Captioning playback
Supports
The product displays closed captions.
7.1.2 Captioning synchronization
Supports
When the product displays captions, synchronization is preserved between the captions and the corresponding audio.
7.1.3 Preservation of captioning
Supports
The product preserves available caption data when transmitting the video.
7.1.4 Captions characteristics
Does Not Support
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.
7.1.5 Spoken subtitles
Does Not Support
The product does not provide access to subtitles with an option for the subtitles to be read aloud.
7.2.1 Audio description playback
Does Not Support
The product does not provide a mechanism to select and play closed audio descriptions.
7.2.2 Audio description synchronization
Not Applicable
The product does have a mechanism to play closed audio descriptions.
7.2.3 Preservation of audio description
Not Applicable
The Product does not support audio descriptions for video content. As a result, there are no mechanisms in place to preserve audio descriptions when videos are processed, reviewed, or shared within the platform. The platform is designed primarily for video collaboration and review, without support for managing or preserving audio descriptions.
7.3 User controls for captions and audio description
Does Not Support
The product does not provide user controls for captions or audio descriptions.
11.5.2.1 Platform accessibility service support for software that provides a user interface
See 11.5.2.5 through 11.5.2.17
See information in 11.5.2.5 through 11.5.2.17
11.5.2.2 Platform accessibility service support for assistive technologies
See 11.5.2.5 through 11.5.2.17
See information in 11.5.2.5 through 11.5.2.17
11.5.2.3 Use of accessibility services
See information in 11.5.2.5 through 11.5.2.17
See information in 11.5.2.5 through 11.5.2.17
11.5.2.4 Assistive technology
Not Applicable
The product is not assistive technology.
11.5.2.5 Object information
Partially Supports
Most objects in the product expose name, role, state, boundary, or description information to assistive technology.
Exceptions include:
As noted in 4.1.2 Name, Role, Value
11.5.2.6 Row, column, and headers
Partially Supports
The product exposes the row, column, and headers of most table cells to assistive technology.
Exceptions include:
As noted in 1.3.1 Info and Relationships.
11.5.2.7 Values
Partially Supports
The product exposes the values of most [input] controls to assistive technology.
Exceptions include:
As noted in 4.1.2 Name, Role, Value
11.5.2.8 Label relationships
Partially Supports
The product exposes most label relationships to assistive technology.
Exceptions include:
As noted in 4.1.2. Name, Role, Value
11.5.2.9 Parent-child relationships
Partially Supports
The product exposes most hierarchical parent-child relationships to assistive technology.
Exceptions include:
As noted in 1.3.1 Info and Relationships
11.5.2.10 Text
Supports
The product exposes text content and text values to assistive technology.
11.5.2.11 List of available actions
Partially Supports
Most controls in the product expose programmatic role information, which conveys available actions to assistive technology.
Exceptions include
As noted in 4.1.2 Name, Role, Value.
11.5.2.12 Execution of available actions
Partially Supports
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:
As noted in 2.1.1 Keyboard
11.5.2.13 Tracking of focus and selection attributes
Supports
The product exposes focus location, text insertion point, and object selection state for user interface components.
11.5.2.14 Modification of focus and selection attributes
Supports
When a user can focus or change selection state of a control in the product via keyboard, then the focus or selection state can also be changed programmatically.
11.5.2.15 Change notification
Partially Supports
In most cases, status messages relevant to user interactions are available to, and presented by, assistive technology.
Exceptions include:
4.1.3 Status Messages
11.5.2.16 Modifications of states and properties
Partially Supports
The product allows assistive technology to modify most states and properties of controls.
Exceptions include:
As noted in 4.1.2 Name, Role, Value.
11.5.2.17 Modifications of values and text
Partially Supports
The product allows assistive technology to modify the values and text of most [input] controls.
Exceptions include:
As noted in 4.1.2 Name, Role, Value.
11.6 Documented accessibility usage
Heading cell – no response required
Heading cell – no response required
11.6.1 User control of accessibility features
Not Applicable
The product does not disrupt platform accessibility features.
11.6.2 No disruption of accessibility features
Not Applicable
The product does not disrupt platform accessibility features.
11.7 User preferences
Does Not Support
The product does not adapt to platform settings for contrast and font size.
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.
You can control how Adobe websites use cookies and similar technologies by making choices below. But note that if you disable cookies and similar technologies entirely, Adobe websites may not function properly.
Cookies are small text files stored by your web browser when you use websites. There are also other technologies that can be used for similar purposes like HTML5 Local Storage and local shared objects, web beacons, and embedded scripts. These technologies help us do things like remembering you and your preferences when you return to our sites, measure how you use the website, conduct market research, and gather information about the ads you see and interact with.
You can make choices in the menu below about what cookies and other technologies you want us to use on Adobe sites when you visit them from this browser. You can always change those choices later by clicking on the Cookie Preferences link at the bottom of the page.
If enabled:
We can improve your experience by tailoring the site and the content to things we think might be of interest
We can better keep track of your preferences — like what language you prefer to use
We will better understand your likely interests so we can provide you more relevant Adobe ads and content on non-Adobe websites and in non-Adobe apps
It will help us improve the performance of our website and those of our partners who use the Adobe Experience Cloud
If disabled:
We won’t be able to remember you from session to session so the experience may not be tailored to your interests
You’ll still have access to the content of the site but certain features that depend on cookies may not function
You’ll still see ads, they just may not be as relevant to you
General information
You can control how Adobe websites use cookies and similar technologies by making choices below. But note that if you disable cookies and similar technologies entirely, Adobe websites may not function properly.
Cookies are small text files stored by your web browser when you use websites. There are also other technologies that can be used for similar purposes like HTML5 Local Storage, web beacons, and embedded scripts. These technologies help us do things like remembering you and your preferences when you return to our sites, measure how you use the website, conduct market research, and gather information about the ads you see and interact with.
You can make choices in the menu below about what cookies and other technologies you want us to use on Adobe sites when you visit them from this browser. You can always change those choices later by clicking on the Cookie Preferences link at the bottom of the page.
If enabled:
We can improve your experience by tailoring the site and the content to things we think might be of interest
We can better keep track of your preferences — like what language you prefer to use
We will better understand your likely interests so we can provide you more relevant Adobe ads and content on non-Adobe websites and in non-Adobe apps
It will help us improve the performance of our website and those of our partners who use the Adobe Experience Cloud
If disabled:
We won’t be able to remember you from session to session so the experience may not be tailored to your interests
We’ll still count your use of our site and services
You’ll still have access to the content of the site but certain features that depend on cookies may not function
You’ll still see ads, they just may not be as relevant to you
Operate the site and core servicesOperate site and measure engagement
Always active
These cookies are required, and they are used to enable the site and related services core functionality. Without them the site could not operate, so they cannot be disabled.
These cookies enable the site and related services’ core functionality and collect statistics about user engagement, such as counting active use to help us understand trends. These cookies cannot be disabled.
Measure performance
These cookies are used to analyze site usage to measure and improve performance. Without them Adobe cannot know what content is most valued and how often unique visitors return to the site, making it hard to improve information we offer to you.
These cookies are used to analyze site usage to measure and improve performance. Without them Adobe cannot know what content is most valued, making it hard to improve information we offer to you.
Extend functionality
These cookies are used to enhance the functionality of Adobe sites such as remembering your settings and preferences to deliver a personalized experience; for example, your username, your repeated visits, preferred language, your country, or any other saved preference.
Personalize advertising
These cookies are used to enable Adobe and our partners to serve ads more relevant to your interests. Without them you will still see ads, but they might not be as relevant to you.
