Adobe frame-io-v4-webapp-2025
Accessibility Conformance Report published by Adobe
Conformance by level
Reported by the vendor. WCAG Level AA is the benchmark referenced by ADA Title II, Section 508 and the European Accessibility Act; Level AAA is optional and often left unevaluated.
Level A — 32 criteria
- Supports
- 13
- Partially supports
- 11
- Does not support
- 4
- Not applicable
- 4
- Not evaluated
- 0
Level AA — 24 criteria
- Supports
- 8
- Partially supports
- 13
- Does not support
- 1
- Not applicable
- 2
- Not evaluated
- 0
Source: View the original report published by Adobe.
These figures are extracted from that document. They are the vendor's own statements, not an independent assessment, and automated extraction can misread a table.
All reported criteria (105)
| Criterion | Name | Level | Conformance | Remarks from vendor |
|---|---|---|---|---|
| 1.1.1 | Non-text Content | A | Partially Supports | Web: The product provides sufficient text alternatives for most instances of non-text content. An image does not have a text alternative, so people who are blind and/or use a screen reader will not be able to access the information available in the image, and if it is an active image, will not understand its function. This occurs on the following pages: Landing page; Workspace Settings; Configuration Panel; All Shares Page. An image does not have a text alternative, so people who are blind and/or use a screen reader will not be able to access the information available in the image, and if it i |
| 1.2.1 | Audio-only and Video-only (Prerecorded) | A | Not Applicable | Web: The product does not contain prerecorded audio-only or video-only media. |
| 1.2.2 | Captions (Prerecorded) | A | Partially Supports | The product contains audio content in media and closed captions are provided for most instances. Exceptions include: The captions provided for media that include audio and video do not identify all the speakers, so people who are deaf or hard of hearing will lose some of the context when reading the dialogue. This occurs on the following page: Video Asset. |
| 1.2.3 | Audio Description or Media Alternative (Prerecorded) | A | Partially Supports | Web: The product provides audio description | transcripts for most video. Exceptions include: The text transcript provided for a video is incorrect or inadequate, so the visual content presented by the video will be misrepresented to people who are blind or have low vision. This occurs on the following page: Video Asset. |
| 1.3.1 | Info and Relationships | A | Does Not Support | Web: Some structure and relationship information, is provided through element semantics | object information or in text. However, most structure and relationship information are not provided programmatically or in text, such as: Content is arranged visually like a data table, but it is not programmatically marked up as a table, so the table's structure and relationships are not conveyed to people who are blind and/or use a screen reader. This occurs on the following pages: Configuration Panel; Views / Filter / Sort. A group of form controls is not programmatically associated with their group l |
| 1.3.2 | Meaningful Sequence | A | Partially Supports | Web: The product presents most content in a meaningful sequence. Exceptions include: Some visually hidden content is announced by a screen reader, so people who are blind and/or use a screen reader may be misled or confused when hearing content that is not intended to be part of the reading order on the page. This occurs on the following pages: Purchase flow; Login. The screen reader skips and does not announce informative static content (text or images), so the intended meaning of that content will be lost or changed for people who are blind and/or use a screen reader. This occurs on the foll |
| 1.3.3 | Sensory Characteristics | A | Supports | Web: Instructions do not rely solely on sensory characteristics. |
| 1.4.1 | Use of Color | A | Partially Supports | Web: Most functions of the product do not convey information through color alone. Exceptions include: Color is the only visual method used to identify a link, and a link text's contrast ratio with the color of the surrounding text is less than 3:1, so people who are colorblind or have low vision may not be able to identify the link. This occurs on the following pages: Account; Workspace Settings; Purchase flow; Account - Content Security. Color is used as the only method to identify errors on a form field, so the error will not be available to people who are colorblind and people who are blind |
| 1.4.2 | Audio Control | A | Not Applicable | Web: The product does not contain audio that plays automatically. |
| 2.1.1 | Keyboard | A | Does Not Support | Web: Most product functionality cannot be operated through a keyboard interface. Examples include: A function cannot be performed using only the keyboard, so people who use the keyboard alone to navigate and operate content cannot use this function. This occurs on the following pages: Document Viewer; Panels; Views / Filter / Sort; Video Asset; Create New Project; Configuration Panel; Manage Metadata; Main Asset Grid; Personal - Profile; Manage Members - Inherit Access; Purchase flow; Account - Users; Filtered By; Image Viewer; All Shares Page. The content in a scrollable region cannot be acce |
| 2.1.2 | No Keyboard Trap | A | Supports | Web: The product does not include keyboard traps |
| 2.1.4 | Character Key Shortcuts | A | Supports | Web: The product provides character key shortcuts; it is only active when the relevant user interface component is in focus. |
| 2.2.1 | Timing Adjustable | A | Supports | Web: The product does not include time limits |
| 2.2.2 | Pause, Stop, Hide | A | Supports | Web: The product does not include elements which move, blink, scroll, or auto-update. |
| 2.3.1 | Three Flashes or Below Threshold | A | Not Applicable | Web: The product does not contain flashing content. |
| 2.4.1 | Bypass Blocks | A | Supports | Web: The product provides mechanism to bypass repeated blocks. |
| 2.4.2 | Page Titled | A | Supports | Web: The titles of pages describe their purpose |
| 2.4.3 | Focus Order | A | Partially Supports | Web: Most components receive focus in a meaningful order. Exceptions include: Keyboard focus or touch screen swiping goes to an element that is hidden or empty, so people who use the keyboard to navigate content (including screen reader users) may become disoriented or confused. This occurs on the following pages: Login; Main Asset Grid - Left Nav; Video Asset; Manage Members - Inherit Access; Purchase flow. Keyboard focus is lost or misplaced as a result of user interaction or content update, or refresh, so people who use the keyboard to navigate content (including screen reader users) will b |
| 2.4.4 | Link Purpose (In Context) | A | Supports | Web: 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 | A | Partially Supports | Web: The product does not rely on multipoint or path-based gestures except where essential. Exceptions include: Functionality (excluding operating system, user agents [like a browser], or assistive technology functions) relies on path-based gestures that require the user to move the finger or pointer in a specific path or sequence, so people with motor disabilities or limited dexterity and people who use certain assistive technology to interact with the page will not be able to operate this functionality. This occurs on the following pages: All Shares Page; Account – Users; Account - Workspace |
| 2.5.2 | Pointer Cancellation | A | Supports | Web: Product functions that use a single pointer are completed when the user releases the pointer and allow the user to cancel the pointer action before completing the pointer click. |
| 2.5.3 | Label in Name | A | Does Not Support | Web: In most product functions, accessible names of controls do not contain the text of their visible labels. Examples include: The accessible name of an interactive element (such as a link, button, or form input) does not contain the visible label, so people who use speech input to navigate and operate content will not be able to access the element. This occurs on the following pages: Main Asset Grid - Left Nav; Document Viewer; Views / Filter / Sort; Reel Share; Video Asset; All Shares Page; Personal - Profile; Manage Members - Inherit Access; Create New Project; Configuration Panel; Account |
| 2.5.4 | Motion Actuation | A | Not Applicable | Web: The product does not have functionality operated by device motion or user motion. |
| 3.1.1 | Language of Page | A | Supports | Web: The language is programmatically determinable within the product. |
| 3.2.1 | On Focus | A | Partially Supports | Web: In most product functions, components do not initiate a change of context when focused. Exceptions include: When an element receives keyboard focus, it results in a substantial, unanticipated context change (such as a change in the page content that changes the meaning of the page), so people who use a keyboard to navigate content (including screen reader users) may become confused or disoriented. This occurs on the following page: Landing page. |
| 3.2.2 | On Input | A | Partially Supports | Web: In most cases, when a user inputs information or interacts with a control, it does not result in a substantial change to the page that could disorient the user, or the user is informed about the change ahead of time. Exceptions include: When a user changes the setting of a user interface control (such as entering text in an input field or selecting a checkbox or radio button), it results in an unanticipated context change (such as opening a new window, moving focus to another element, or submitting a form), so people who have cognitive disabilities and others may be confused or disoriente |
| 3.2.6 | Consistent Help | A | Supports | Web: 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. |
| 3.3.1 | Error Identification | A | Partially Supports | Web: Most input errors are identified and described to the users in text. Exceptions include: An error for a form input (such as a text input field, radio button, select dropdown, or checkbox) is not identified with a text error message or a text alternative for an image, so people who are blind and/or use a screen reader will not be made aware that an error has occurred. This occurs on the following page: Purchase flow. |
| 3.3.2 | Labels or Instructions | A | Partially Supports | Web: Labels are provided for most input fields. Exceptions include: The label of an element is not persistent (always visible on the page), so the element's purpose may be difficult to discover. This occurs on the following pages: Configuration Panel; Manage Members - Invite New Members; Account - Content Security; Document Viewer; Panels. The label for a form field is missing, so the field's purpose is not clear. This occurs on the following pages: Purchase flow; Document Viewer; Configuration Panel. Select or dropdown control missing a visible label so the Select or dropdown control purpose |
| 3.3.7 | Redundant Entry | A | Supports | Web: If information previously entered by, or provided to, the user is required to be entered again in the same process, that information is either automatically populated or available for the user to select unless the previously entered information is no longer valid or re-entering the information is essential or required to ensure security. |
| 4.1.1 | Parsing | A | Supports | Elements have complete start and end tags, elements are nested according to their specifications, elements do not contain duplicate attributes, and any IDs are unique. |
| 4.1.2 | Name, Role, Value | A | Does Not Support | Web: User interface components in most product functions do not provide programmatic [name, role, state, or value] information. Examples include: An element has an invalid attribute in its HTML code that is intended to provide its programmatic role, name, state, or another property to assistive technology, so people who are blind and/or use a screen reader or other assistive technology may not be able to understand the name, purpose, or content of the element or how to interact with it. This occurs on the following pages: Manage Metadata; All Shares Page; Configuration Panel; Project Switcher; |
| 1.2.4 | Captions (Live) | AA | Not Applicable | Web: The product does not contain live synchronized media. |
| 1.2.5 | Audio Description (Prerecorded) | AA | Not Applicable | Web: The product does not contain prerecorded video content that would require audio description. |
| 1.3.4 | Orientation | AA | Supports | Web: Content does not restrict its view and operation to a single display orientation. |
| 1.3.5 | Identify Input Purpose | AA | Partially Supports | Web: Most input fields in the product do not collect information about the user. However, some input fields collect information about the user and do not programmatically convey their purpose. Exceptions include: The programmatic purpose provided for an input element (like a text input field) is not accurate, so information automatically suggested by the browser or assistive technology to fill in the input will be incorrect. This occurs on the following pages: Login; Personal - Profile. |
| 1.4.3 | Contrast (Minimum) | AA | Partially Supports | Web: Most text meets minimum contrast requirements. Exceptions include: The color contrast ratio between placeholder text in an input and the input's background is less than 4.5:1, so people who are colorblind or have low vision may have difficulty reading the placeholder text. This occurs on the following pages: Purchase flow; Panels. The color contrast ratio between text and its background is less than 4.5:1, so people who are colorblind or have low vision may have difficulty reading the text. This occurs on the following pages: Project Search; Document Viewer; Panels; Video Asset; Landing p |
| 1.4.4 | Resize text | AA | Partially Supports | Web: Most content is readable and functional when browser zoom is set to 200% of its initial size. Exceptions include: Content is lost, clipped, or obscured when the page is zoomed to 200%, so people who have low vision and need to enlarge text to read it may not have access to that content. This occurs on the following pages: Project Settings; Reel Share. Functionality is lost when the page is zoomed to 200%, so people who have low vision and need to enlarge text to read it may not have access to this functionality. This occurs on the following pages: Panels; Set Source; Configuration Panel; |
| 1.4.5 | Images of Text | AA | Supports | Web: The product uses text instead of images of text, except for branding elements that are considered essential. |
| 1.4.10 | Reflow | AA | Partially Supports | Web: At the required width of 320 CSS pixels, most content is presented without loss of information or functionality, and without requiring scrolling in two dimensions. Exceptions include: When the page is adjusted to an equivalent width of 320 pixels and content reflows to fit within the viewport, some content or functionality becomes unavailable, so people with low vision who increase the size of text and other content using the browser zoom will not be able to access all of the page's content and/or functionality. This occurs on the following pages: Configuration Panel; Manage Metadata; Pro |
| 1.4.11 | Non-text Contrast | AA | Does Not Support | Web: Most of the boundaries and indicators of the visual states of each active user component and any graphics required to understand content have a 3:1 color contrast ratio with adjacent colors or their background. Exceptions include: The visual boundary of an interactive element (like a radio button or input field) does not have a 3:1 color contrast ratio with the background, so people who are colorblind or have low vision may have difficulty in perceiving the boundaries of the interactive element. This occurs on the following pages: Project Switcher; Document Viewer; Panels; Video Asset; Al |
| 1.4.12 | Text Spacing | AA | Partially Supports | Web: Most functions of the product support the required text style properties without loss of content or functionality. Exceptions include: When text spacing is adjusted to help people with vision, reading, and/or cognitive disabilities, some content cannot be seen because it is cut off. This occurs on the following pages: Account - Workspaces; Account – Users; Configuration Panel. |
| 1.4.13 | Content on Hover or Focus | AA | Partially Supports | Web: In most product functions, content does not become visible and then hidden in response to pointer hover or keyboard focus. Exceptions include: Content that appears on mouse hover or keyboard focus (such as tooltips, drop-down menus, or popups) is not dismissible, so it obscures all or part of the original content on the page. This occurs on the following pages: Main Asset Grid - Left Nav; Video Asset; All Shares Page; Video Asset - Transcriptions; Configuration Panel; Account - Users; Delete Asset; Manage Members - Invite New Members; Main Asset Grid; User Profile Settings; Context Menu; |
| 2.4.5 | Multiple Ways | AA | Supports | Web: Users can locate web pages in the product through multiple ways in the site. |
| 2.4.6 | Headings and Labels | AA | Partially Supports | Web: Most headings and labels for form and interactive controls are informative. Exceptions include: A programmatic label for a control or form input field does not convey the purpose of the control or input, so people who are blind and/or use a screen reader may not understand what the control does or what data to enter. This occurs on the following pages: Project Search; Document Viewer; Panels; Views / Filter / Sort; Video Asset; Personal - Profile; Video Asset - Transcriptions; Configuration Panel; Account - Workspaces; Account - Users; Landing page; Delete Asset; Workspace Settings; Main |
| 2.4.7 | Focus Visible | AA | Partially Supports | Web: Most focusable elements have a visible keyboard focus indicator. Exceptions include: An interactive element (such as a link, button, or form input) does not have a visual focus indicator, so sighted people who use a keyboard to navigate content will not know when that element is receiving focus. This occurs on the following pages: Notifications; Project Search; Document Viewer; Panels; Manage Members - Inherit Access; Video Asset - Transcriptions; Create New Project; Filtered By; Manage Members - Invite New Members; Main Asset Grid; Image Viewer; Open Viewer; Metadata - Set the status; Ma |
| 2.4.11 | Focus Not Obscured (Minimum) | AA | Partially Supports | Web: When most user interface components receive keyboard focus, each component is not entirely hidden due to author-created content. Exceptions include: A focused element is completely covered by other author-created content, which may cause people who use the keyboard to navigate content to become disoriented. This occurs on the following pages: Project Switcher; Filtered By; Customize Sort; Uploads; Account; Panels; Video Asset; Configuration Panel; Manage Metadata. |
| 2.5.7 | Dragging Movements | AA | Partially Supports | Web: Most functionality that uses a dragging movement can be achieved by a single pointer without dragging, unless dragging is essential or the functionality is determined by the user agent and not modified by the author. Exceptions include: Some functionality relies on a dragging movement with no single-pointer, single-touch alternative, making it difficult or impossible for persons with motor difficulties and users of assistive technology to perform the gesture on the following pages: Video Asset; Configuration Panel; Customize Metadata; Manage Metadata; Views / Filter / Sort; Landing page; |
| 2.5.8 | Target Size (Minimum) | AA | Partially Supports | Web: The size of the target for most clickable controls is at least 24 by 24 CSS pixels, except where the target size is determined by the user agent; there is a different control with equivalent functionality; the target is in line with text; the presentation of the target is essential to the function or otherwise exempted under the rule; or each control is spaced such that a 24-pixel circle placed around the bounding box of the control will not intersect any similar circle for another control. Exceptions include: A target's hit area does not meet a minimum 24x24 pixel size or spacing. making |
| 3.1.2 | Language of Parts | AA | Partially Supports | Web: On most pages, the language of each section of content that is different from the default language of the page is correctly identified and can be determined programmatically. Exceptions include: A portion of content on a page that is in a different language from the rest of the content on the page is not programmatically assigned the language for that portion of content, so screen readers may mispronounce that part of the content. This occurs on the following page: Video Asset - Transcriptions. |
| 3.2.3 | Consistent Navigation | AA | Supports | Web: When navigational mechanisms are repeated in the product, such as the primary navigation menu and the sub menu in settings, they occur in a consistent relative order. |
| 3.2.4 | Consistent Identification | AA | Supports | Web: Components with the same functionality are identified consistently. |
| 3.3.3 | Error Suggestion | AA | Supports | Web: Where input errors are automatically detected suggestions for correction are provided to the user. |
| 3.3.4 | Error Prevention (Legal, Financial, Data) | AA | Supports | Web: 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) | AA | Supports | Web: A cognitive function test (such as remembering a password or solving a puzzle) is not required for any step in an authentication process unless either another method is available that does not rely on a cognitive function test; help is available to assist the user in completing the test; or the test is to recognize objects or identify non-text content the user provided to the website. |
| 4.1.3 | Status Messages | AA | Partially Supports | Web: In most cases, status messages can be programmatically determined and presented by assistive technologies without receiving focus. Exceptions include: A status message is not automatically announced by the screen reader, so people who are blind and/or use a screen reader or other assistive technology may completely miss the status message, or they may not hear it in a timely fashion. This occurs on the following pages: Login; Project Switcher; Panels; Views / Filter / Sort; Purchase flow; Video Asset - Transcriptions; Configuration Panel; Account - Users; Filtered By; Customize Sort; Main |
| 502.3.8 | Text | - | Supports | The product exposes text content and text values to assistive technology. |
| 502.3.9 | Modification of Text | - | Supports | The product exposes text content and text values to assistive technology. |
| 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 | The product allows assistive technology to perform most actions on objects. Exceptions include: Zoom In/Out button, Voiceover only announces a percentage (e.g., “27%”) without indicating that the button controls zoom functionality. Users are not informed that pressing the button will zoom in or out. Add Pin Button, The action required after pressing the “Add Pin” button is not conveyed to the voiceover users, leading to confusion and inability to complete the task. |
| 502.3.12 | Focus Cursor | - | Supports | The product exposes a highly visual focus indicator as a mechanism to track focus. Text insertion point, and selection are tracked using native platform features. |
| 502.3.13 | Modification of Focus Cursor | - | Supports | The product allows assistive technology to move focus and modify selection attributes. |
| 502.3.14 | Event Notification | - | Does Not Support | The product does not notify assistive technology about most attribute changes in user interface elements. |
| 503.4.1 | Caption Controls | - | Does Not Support | The product does not provide user controls for captions. |
| 503.4.2 | Audio Description Controls | - | Does Not Support | The product does not provide user controls for audio descriptions. |
| 502.2.1 | User Control of Accessibility Features | - | Not Applicable | The product is not platform software. |
| 502.2.2 | No Disruption of Accessibility Features | - | Not Applicable | The product is not platform software. |
| 502.3.1 | Object Information | - | Partially Supports | 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 |
| 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: 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: 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 value(s) are available programmatically, so they can be perceived and conveyed by assistive technology. Exceptions include: 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: 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: 1.3.1 Info and Relationships 4.1.2 Name, Role, Value |
| 502.3.7 | Hierarchical Relationships | - | Partially Supports | For most elements that have a parent-child relationship, those relationships are programmatically determinable, so they can be perceived by assistive technology. Exceptions include: 1.3.1 Info and Relationships |
| 502.3.12 | Focus Cursor | - | Partially Supports | 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 |
| 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 |
| 503.4.1 | Caption Controls | - | Supports | Each multimedia player provides the closed caption controls at the same level as other media controls, so people who are deaf and others who need closed captions are able to find the controls and activate the captions. |
| 503.4.2 | Audio Description Controls | - | Supports | The product does not contain media with a video component that offers audio descriptions. |
| 504.2.1 | Preservation of Information Provided for Accessibility in Format Conversion | - | Not Applicable | This product is not an authoring tool. |
| 504.2.2 | PDF Export | - | Not Applicable | This product is not an authoring tool. |
| 4.2.1 | Usage without vision | - | Partially Supports | Web: Most functions of the product are usable without vision. Exceptions include: 1.1.1 Non-Text Content 1.2.3 Audio Description or Media Alternative (prerecorded) 1.3.1 Info and Relationships 1.3.2 Meaningful Sequence 1.4.1 Use of Color 2.1.1 Keyboard Navigation 2.4.3 Focus Order 2.4.6 Headings and Labels 3.1.2 Language of Parts 3.2.1 On Focus 3.2.2 On Input 3.3.1 Error Identification 4.1.2 Name, Role, Value 4.1.3 Status Messages |
| 4.2.2 | Usage with limited vision | - | Partially Supports | Web: Most functions of the product are usable With Limited Vision. Exceptions include: 1.1.1 Non-Text Content 1.2.3 Audio Description or Media Alternative (prerecorded) 1.3.1 Info and Relationships 1.3.2 Meaningful Sequence 1.4.1 Use of Color 1.4.3 Contrast (minimum) 1.4.4 Resize Text 1.4.10 Reflow 1.4.11 Non-Text Contrast 1.4.12 Text Spacing 1.4.13 Content on Hover or Focus 2.1.1 Keyboard Navigation 2.4.3 Focus Order 2.4.6 Headings and Labels 2.4.7 Focus Visible 3.1.2 Language of Parts 3.2.1 On Focus 3.2.2 On Input 3.3.1 Error Identification 3.3.2 Labels or Instructions 4.1.2 Name, Role, Valu |
| 4.2.3 | Usage without perception of colour | - | Partially Supports | Web: Most functions of the product are usable without perception of color. Exceptions include: 1.4.1 Use of Color 1.4.3 Contrast (minimum) 1.4.11 Non-Text Contrast 3.3.1 Error Identification |
| 4.2.4 | Usage without hearing | - | Partially Supports | Web: Most functions of the product are usable without hearing. Exceptions include: 1.2.2 Captions (prerecorded) |
| 4.2.5 | Usage with limited hearing | - | Partially Supports | Web: Most functions of the product are usable with limited hearing. Exceptions include: 1.2.2 Captions (prerecorded) |
| 4.2.6 | Usage with no or limited vocal capability | - | Not Applicable | The product does not require the use of speech. |
| 4.2.7 | Usage with limited manipulation or strength | - | Partially Supports | Most functions of the product are usable by people with limited manipulation and does not require manipulation, simultaneous action, or hand strength. Exceptions include: 1.3.5 Identify Input Purpose 1.4.13 Content on Hover or Focus 2.1.1 Keyboard Navigation 2.4.3 Focus Order 2.4.6 Headings and Labels 2.4.7 Focus Visible 2.5.1 Pointer Gestures 2.5.3 Label in Name 3.2.1 On Focus 4.1.2 Name, Role, Value |
| 4.2.8 | Usage with limited reach | - | Partially Supports | Most functions of the product are usable with limited reach. Exceptions include: 1.3.5 Identify Input Purpose 1.4.13 Content on Hover or Focus 2.5.1 Pointer Gestures 2.5.3 Label in Name |
| 4.2.9 | Minimize photosensitive seizure triggers | - | Not Applicable | The product does not contain flashing content. |
| 4.2.10 | Usage with limited cognition, language or learning | - | Partially Supports | Most functions of the product are usable with limited language, cognitive, and learning abilities. Users with cognitive disabilities have varying needs for features that allow them to adapt content and work with assistive technology or accessibility features of the platform. The product provides. Exceptions include: 1.1.1 Non-Text Content 1.2.2 Captions (prerecorded) 1.2.3 Audio Description or Media Alternative (prerecorded) 1.3.1 Info and Relationships 1.3.2 Meaningful Sequence 1.3.5 Identify Input Purpose 1.4.1 Use of Color 1.4.10 Reflow 1.4.12 Text Spacing 1.4.13 Content on Hover or Focus 2 |
| 4.2.11 | Privacy | - | Not Applicable | Web: The product does not ask for or display legal, financial, or personal data. |
| 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.7 | Access without speech | - | Supports | Adobe Frame.io does not require speech input for any functionality. All operations can be performed using mouse and keyboard input. The application does not rely on voice commands or speech recognition features. |
| 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, which do not require grasping, pinching, or twisting of the wrist to operate. |
| 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 isn’t discernible in the product |
| 7.1.1 | Captioning playback | - | Supports | The product displays closed captions | provides video with open captions. |
| 7.1.3 | Preservation of captioning | - | Not Applicable | The product does not transmit, convert, or record video with synchronized audio. |
| 7.1.4 | Captions characteristics | - | Does Not Support | The product has the ability to show closed captions however the appearance of those closed captions cannot be modified by the user. A multimedia player does not provide a way for the user to modify the appearance of captions to their individual needs, so people who are deaf, have limited hearing, and others who rely on captions to understand the content may not have access to the information. This occurs on the following page: Video Asset. |
| 7.1.5 | Spoken subtitles | - | Does Not Support | The product supports language subtitles however it does not have a function to speak those subtitles out loud. A multimedia player that provides access to subtitles does not provide an option for the subtitles to be read aloud, so people who are blind or low vision may not be able to hear the dialogue in a language they can understand. This occurs on the following page: Video Asset. |
| 7.2.1 | Audio description playback | - | Does Not Support | The product does not provide a mechanism to select and play closed audio description. A multimedia player cannot play an audio description track, so people who are blind or have low vision are not able to access the information in the video portion of the multimedia described in the audio track. This occurs on the following page: Video Asset. |
| 7.2.2 | Audio description synchronization | - | Not Applicable | The product does have a mechanism to play closed audio description. |
| 7.2.3 | Preservation of audio description | - | Not Applicable | The product does not transmit, convert, or record video with synchronized audio. |
Is this your product? If this report is out of date or misrepresented, we will correct or remove it. Contact us to claim this listing.
Get told when this changes
This report is dated Not stated. An ACR can be quietly replaced at any time, and the published date is the only signal a buyer gets. We will email you when this one is updated.
Double opt-in — we email you once to confirm, and send nothing until you do. One-click unsubscribe on every message. We store your address and what you are watching, nothing else. Privacy.