Adobe Photoshop Web
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
- 9
- Does not support
- 3
- Not applicable
- 7
- Not evaluated
- 0
Level AA — 24 criteria
- Supports
- 8
- Partially supports
- 7
- Does not support
- 6
- Not applicable
- 3
- 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 (99)
| 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. Some images do 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: Generative Fill; Selection Tool. An active image has a text alternative that does not convey the same purpose as the image. People who are blind and/or use a screen reader will be given different information than sighted users. This occurs on |
| 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 | Not Applicable | Web: The product does not contain prerecorded synchronized media. |
| 1.2.3 | Audio Description or Media Alternative (Prerecorded) | A | Not Applicable | Web: The product does not contain prerecorded video content that would require audio description or a media alternative. |
| 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: Some heading levels are out of order, 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: Xray; Selection Tool; Type; Add Image; Adjust. Content that is visually presented as a list is not marked up as a list, so the presence and structure of the list |
| 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 page: Type. |
| 1.3.3 | Sensory Characteristics | A | Partially Supports | Web: Most instructions do not rely solely on sensory characteristics. Exceptions include: Some instructions require the ability to see shape, color, size, visual location, or orientation, so they will be difficult or impossible to understand for people who are blind or have low vision. This occurs on the following pages: Home - Logged Out; Home - Logged In; Create: Interface. |
| 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 used as the only method to convey information so that information will not be available to people who are colorblind and people who are blind and/or use a screen reader. This occurs on the following page: Xray. |
| 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: Multiple functions cannot be performed using only the keyboard, so people who use the keyboard alone to navigate and operate content cannot use these functions. This occurs on the following pages: Type; Selection Tool; Xray; Home - Logged In; Adjust; Create: Upload; Body Parser Select; Generative Fill; Harmonize; Create: Interface; Retouch; Lesson: Generative Fill; Add Image. |
| 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 | Not Applicable | Web: The product does not include time limits |
| 2.2.2 | Pause, Stop, Hide | A | Partially Supports | Web: Most moving, blinking, scrolling, or auto-updating information is present, that information can be paused, stopped, hidden, or otherwise controlled 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: Lesson: Generative Fill. |
| 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: The focus order is not logical and presents content in an order that misrepresents its meaning or operability, so people who use a keyboard, switch control, or other assistive technology to navigate content may become disoriented or confused. This occurs on the following pages: Create: Interface; Lesson: Generative Fill. 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 confuse |
| 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 | Supports | Web: The product does not rely on multipoint or path-based gestures. |
| 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 | Partially Supports | Web: In most product functions, accessible names of controls contain the text of their visible labels. Exceptions include: The accessible name of multiple interactive elements (such as links, buttons, or form inputs) does not contain the visible label, so people who use speech input to navigate and operate content will not be able to access those elements. This occurs in the following component: Footer and following pages: Selection Tool; Adjust; Xray; Type; Retouch; Add Image. |
| 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: Generative Fill. |
| 3.2.2 | On Input | A | Supports | Web: Changes of context do not occur automatically on user input. |
| 3.2.6 | Consistent Help | A | Supports | Web: The product 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 | Supports | Web: Where input errors are automatically detected, items in error are identified and error messages are provided as text. |
| 3.3.2 | Labels or Instructions | A | Partially Supports | Web: Labels are provided for most input fields. Exceptions include: The label for a form field is missing, so the field's purpose is not clear. This occurs on the following page: Xray. Some labels of elements are not persistent (always visible on the page), so each element's purpose may be difficult to discover. This occurs on the following pages: Lesson: Generative Fill; Generative Fill. Select or dropdown control missing a visible label so the Select or dropdown control purpose is not clear. This occurs on the following pages: Xray; Type. |
| 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 | Web: 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: A link does not have a programmatic role, so people who are blind and/or use a screen reader or other assistive technology may not be able to understand the purpose and function of the link or how to interact with it. This occurs on the following page: Home - Logged In. 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 |
| 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 | Not Applicable | Web: The product does not contain input fields that collect information about the user. |
| 1.4.3 | Contrast (Minimum) | AA | Partially Supports | Web: Most text meets minimum contrast requirements. Exceptions include: The color contrast ratio between text and its background is less than 4.5:1, so people who are colorblind or have low vision may have difficulty reading the text. This occurs on the following pages: Home - Logged In; Generative Fill; Xray; Create: Upload; Type; Home - Logged Out. 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: Gener |
| 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: Lesson: Generative Fill; Type; Home - Logged In; Create: Upload. 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: Lesson |
| 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 | Does Not Support | 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. Examples include: When the page is adjusted to an equivalent width of 320 pixels and content reflows to fit within the viewport, some content does not fit horizontally, so it cannot be viewed without scrolling. People with low vision who increase the size of text and other content using the browser zoom may have difficulty accessing the content that can only be seen by horizontal scrolling. This occurs on the following page: Ho |
| 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. Examples include: Some icons (or parts of an icon required to understand its content) do 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 each icon. This occurs on the following pages: Type; Selection Tool; Harmonize; Adjust; Create: Interface; Add I |
| 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: Home - Logged Out; Xray; Adjust. |
| 1.4.13 | Content on Hover or Focus | AA | Does Not Support | Web: Most product functions, content does not become visible and then hidden in response to pointer hover or keyboard focus. Examples 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: Adjust; Add Image; Retouch; Type; Body Parser Select; Xray; Generative Fill; Create: Interface; Harmonize; Lesson: Generative Fill; Selection Tool; Home - Logged Out; Home - Logged In. |
| 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 | Does Not Support | Web: Most headings and/or labels for form and interactive controls are not informative. Examples include: 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: Add Image; Home - Logged In; Home - Logged Out; Create: Interface. Multiple programmatic labels for controls or form input fields do not convey the purpose of the control or input, so people who are blind and/or use |
| 2.4.7 | Focus Visible | AA | Partially Supports | Web: Most focusable elements have a visible keyboard focus indicator. Exceptions include: Multiple interactive elements (such as links, buttons, or form inputs) do not have a visual focus indicator, so sighted people who use a keyboard to navigate content will not know when those elements are receiving focus. This occurs on the following pages: Create: Interface; Xray; Selection Tool. |
| 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: Multiple focused elements are 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: Create: Upload; Add Image. |
| 2.5.7 | Dragging Movements | AA | Does Not Support | 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. Examples 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. This occurs on the following pages: Harmonize; Add Image; Retouch; Lesson: Generative Fill; Adjust; Type; Selection Tool; Generative |
| 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 in the following component: Footer. |
| 3.2.3 | Consistent Navigation | AA | Supports | Web: When navigational mechanisms are repeated in the product, 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 | Does Not Support | Web: When status messages do not receive focus, the product does not provide the update to assistive technology. Examples include: Some status messages are 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 messages, or they may not hear them in a timely fashion. This occurs on the following pages: Selection Tool; Retouch; Add Image; Type; Body Parser Select; Harmonize; Create: Upload; Create: Interface; Generative Fill; Lesson: Generative Fill. |
| 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: 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 value(s) 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 1.3.1 Info and Relationships As noted in 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: As noted in 1.3.1 Info and Relationships |
| 502.3.8 | Text | - | Supports | Most text, text attributes (such as whether text is static or editable), and text boundaries are programmatically determinable, so they can be perceived and conveyed by assistive technology. Exceptions include: As noted in 1.3.1 Info and Relationships |
| 502.3.9 | Modification of Text | - | Supports | When text can be set by the user (such as by typing in an input field), the act of adding or modifying text is available programmatically, so that it can be perceived and performed using assistive technology. |
| 502.3.10 | List of Actions | - | Partially Supports | For most of the elements on which one or more actions may be performed, all of those actions are programmatically determinable, so that each action can be perceived and conveyed by assistive technology. Exceptions include: 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 | - | 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: As noted in 2.4.7 Focus Visible |
| 502.3.13 | Modification of Focus Cursor | - | Supports | When the focus indicator, text insertion point, and/or text selector indicator can be modified, the modifications are programmatically determinable, so they can be performed by assistive technology. |
| 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: As noted in 4.1.3 Status Messages |
| 503.4.1 | Caption Controls | - | Not Applicable | The product does not display video. |
| 503.4.2 | Audio Description Controls | - | Not Applicable | The product does not provide prerecorded media that requires audio description. |
| 504.2.1 | Preservation of Information Provided for Accessibility in Format Conversion | - | Not Applicable | The product does not convert content. |
| 504.2.2 | PDF Export | - | Not Applicable | The product does not export PDF files. |
| 4.2.1 | Usage without vision | - | Partially Supports | Web: 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.3.3 Sensory Characteristics As noted in 1.4.1 Use of Color As noted in 2.1.1 Keyboard As noted in 2.4.3 Focus Order As noted in 2.4.6 Headings and Labels As noted in 3.1.2 Language of Parts As noted in 3.2.1 On Focus As noted in 4.1.2 Name, Role, Value As noted in 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: 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.3 Sensory Characteristics As noted in 1.4.1 Use of Color As noted in 1.4.3 Contrast (Minimum) As noted in 1.4.4 Resize text As noted in 1.4.10 Reflow As noted in 1.4.11 Non-text Contrast As noted in 1.4.12 Text Spacing As noted in 1.4.13 Content on Hover or Focus As noted in 2.1.1 Keyboard As noted in 2.4.3 Focus Order As noted in 2.4.6 Headings and Labels As noted in 2.4.7 Focus |
| 4.2.3 | Usage without perception of colour | - | Partially Supports | Web: 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 1.4.11 Non-Text Contrast |
| 4.2.4 | Usage without hearing | - | Partially Supports | Web: Most functions of the product are usable without hearing. Exceptions include: As noted in 1.1.1 Non-text Content As noted in 1.3.3 Sensory Characteristics As noted in 3.1.2 Language of Parts |
| 4.2.5 | Usage with limited hearing | - | Partially Supports | Web: Most functions of the product are usable with limited hearing. Exceptions include: As noted in 1.1.1 Non-text Content As noted in 1.3.3 Sensory Characteristics As noted in 3.1.2 Language of Parts |
| 4.2.6 | Usage with no or limited vocal capability | - | Not Applicable | Web: The product does not require the use of speech. |
| 4.2.7 | Usage with limited manipulation or strength | - | Partially Supports | Web: Most functions of the product are usable by people with limited manipulation and does not require manipulation, simultaneous action, or hand strength. Exceptions include: As noted in 1.4.13 Content on Hover or Focus As noted in 2.1.1 Keyboard As noted in 2.4.3 Focus Order As noted in 2.4.6 Headings and Labels As noted in 2.4.7 Focus Visible As noted in 2.5.3 Label in Name As noted in 3.2.1 On Focus As noted in 4.1.2 Name, Role, Value |
| 4.2.8 | Usage with limited reach | - | Partially Supports | Web: Most functions of the product are usable by people with limited reach. Exceptions are noted in: As noted in 1.4.13 Content on Hover or Focus As noted in 2.5.3 Label in Name |
| 4.2.9 | Minimize photosensitive seizure triggers | - | Not Applicable | Web: The product does not contain flashing content. |
| 4.2.10 | Usage with limited cognition, language or learning | - | Partially Supports | Web: Most functions of the product are usable by people with limited language, cognitive, and learning abilities. People with cognitive disabilities have varying needs for features that allow them to adapt content and work with assistive technology. Exceptions are noted in: 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.3 Sensory Characteristics As noted in 1.4.1 Use of Color As noted in 1.4.10 Reflow As noted in 1.4.12 Text Spacing As noted in 1.4.13 Content on Hover or Focus As noted in 2.1.1 Keyboard As noted |
| 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 | - | Not Applicable | Adobe Photoshop 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 rec ognition 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 |
| 11.6.1 | User control of accessibility features | - | Not Applicable | The product is not platform software. |
| 11.6.2 | No disruption of accessibility features | - | Not Applicable | The product does not disrupt platform accessibility features. |
| 11.8.3 | Preservation of accessibility information in transformations | - | Not Applicable | The product does not provide restructuring transformations or re-coding transformations. |
| 11.8.4 | Repair assistance | - | Not Applicable | The product does not have accessibility checking functionality. |
| 11.8.5 | Templates | - | Not Applicable | The product does not provide templates for authored content. |
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 December 2025. 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.