Adobe Substance 3D Stager – windows
Accessibility Conformance Report published by Adobe
Partial extraction. We read 29 of 31 Level A and 20 of 24 Level AA criteria from this document (89% coverage). The remainder are missing from our extraction, not necessarily from Adobe's report — their table layout defeated our parser. Treat the figures below as incomplete and read the source document for the full picture.
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 — 29 criteria
- Supports
- 19
- Partially supports
- 6
- Does not support
- 4
- Not applicable
- 0
- Not evaluated
- 0
Level AA — 20 criteria
- Supports
- 16
- Partially supports
- 3
- Does not support
- 1
- Not applicable
- 0
- 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 (84)
| Criterion | Name | Level | Conformance | Remarks from vendor |
|---|---|---|---|---|
| 1.2.1 | Audio-only and Video-only (Prerecorded) | A | Supports | Software: The product does not contain prerecorded audio-only or video-only media. |
| 1.2.2 | Captions (Prerecorded) | A | Supports | Software: The product does not contain prerecorded synchronized media. |
| 1.2.3 | Audio Description or Media Alternative (Prerecorded) | A | Supports | Software: The product does not contain prerecorded video content that would require audio description or a media alternative. |
| 1.2.4 | Captions (Live) | AA | Supports | Software: The product does not contain live synchronized media. |
| 1.2.5 | Audio Description (Prerecorded) | AA | Supports | Software: The product does not contain prerecorded video content that would require audio description. |
| 1.3.1 | Info and Relationships | A | Does Not Support | Software: Some structure and relationship information, such as labels for some form controls, is provided through element semantics or in text. However, most structure and relationship information is not provided programmatically or in text, such as: Labels for form groups including transform controls (e.g., “Position”, “Rotation”, “Scale”, and “Size”) are not programmatically associated with each control. Labels for form controls including inputs, radio buttons, sliders, and dropdowns. Table headers are not programmatically associated with their respective data cells. Headings are not identif |
| 1.3.2 | Meaningful Sequence | A | Supports | Software: The product presents content in a meaningful sequence. |
| 1.3.3 | Sensory Characteristics | A | Supports | Software: Instructions do not rely solely on sensory characteristics. |
| 1.3.4 | Orientation | AA | Supports | Software: Content does not restrict its view and operation to a single display orientation. |
| 1.3.5 | Identify Input Purpose | AA | Supports | Software: The product’s technology does not have support for programmatic identification of input purpose. |
| 1.4.1 | Use of Color | A | Supports | Software: The product does not convey information through color alone. |
| 1.4.2 | Audio Control | A | Supports | Software: The product does not contain audio that plays automatically. |
| 1.4.3 | Contrast (Minimum) | AA | Partially Supports | Software: Most text meets minimum contrast requirements. Exceptions include: Buttons on focus have insufficient color contrast. File name, time remaining, and percentage of render status have insufficient color contrast. |
| 1.4.4 | Resize text | AA | Does Not Support | Software: The product does not provide its own text resizing function. When text is resized using operating system display scaling, content and functionality is lost in most product functions. Examples include: The font size for text within the product does not increase when using operating system display scaling |
| 1.4.5 | Images of Text | AA | Supports | Software: The product uses text instead of images of text. |
| 1.4.10 | Reflow | AA | Supports | Software: At the required width of 320 CSS pixels, content is presented without loss of information or functionality, and without requiring scrolling in two dimensions. |
| 1.4.11 | Non-text Contrast | AA | Partially Supports | Software: Most meaningful non-text content elements, such as iconography, have sufficient contrast. Exceptions include: The “Take a snapshot” button does not have sufficient color contrast. |
| 1.4.12 | Text Spacing | AA | Supports | Software: The product is not implemented using markup languages. |
| 1.4.13 | Content on Hover or Focus | AA | Supports | Software: When content is triggered by hover or focus, it becomes visible and then hidden in a manner which meets this criterion. |
| 2.1.1 | Keyboard | A | Partially Supports | Software: Most product functionality can be operated through a keyboard interface. Exceptions include: The application menu is not accessible via the keyboard. Button menus and tooltips cannot be accessed with the keyboard. Manipulation controls within the view port cannot be used with the keyboard. Some sliders and buttons rely on the mouse to utilize. |
| 2.1.2 | No Keyboard Trap | A | Supports | Software: The product does not include keyboard traps. |
| 2.1.4 | Character Key Shortcuts | A | Supports | Software: The product provides character key shortcuts for activating the tools, manipulating objects, and using the camera. Users can remap the shortcuts to non-printable keys. |
| 2.2.1 | Timing Adjustable | A | Supports | Software: The product does not include time limits. |
| 2.2.2 | Pause, Stop, Hide | A | Supports | Software: The product does not include elements which move, blink, scroll, or auto-update. |
| 2.3.1 | Three Flashes or Below Threshold | A | Supports | Software: The product does not contain flashing content. |
| 2.4.1 | Bypass Blocks | A | Supports | Software: This criterion does not apply to non-web software. |
| 2.4.2 | Page Titled | A | Partially Supports | Software: Exceptions include: Dialogs do not describe their topic or purpose. |
| 2.4.3 | Focus Order | A | Partially Supports | Software: Most components receive focus in a meaningful order. Exceptions include: Programmatic focus does not return to spawning elements of dialogs and dropdown menus. Focus is lost when activating some buttons and closing dialogs. Focus is not set on some dialogs when they open. |
| 2.4.4 | Link Purpose (In Context) | A | Supports | Software: The purpose of links in the product can be determined from the link text alone or from the programmatic context of the link. |
| 2.4.5 | Multiple Ways | AA | Supports | Software: This criterion does not apply to non-web software. |
| 2.4.6 | Headings and Labels | AA | Partially Supports | Software: Exceptions include: Icons within labels (e.g., in the “Keyboard shortcuts” section adjacent to each input) do not describe meaning or purpose, causing the labels to be non-descriptive. |
| 2.4.7 | Focus Visible | AA | Supports | Software: The keyboard focus indicator is visible by default. |
| 2.5.1 | Pointer Gestures | A | Supports | Software: The product does not rely on multipoint or path-based gestures except where essential, such as directly manipulating the positioning of the object within the viewport. |
| 2.5.2 | Pointer Cancellation | A | Supports | Software: Product functions that use a single pointer are completed when the user releases the pointer and allow the user to cancel the pointer action before completing the pointer click. |
| 2.5.3 | Label in Name | A | Does Not Support | Software: In most product functions, accessible names of controls do not contain the text of their visible labels. Examples include: Labels for form controls, including inputs, radio buttons, sliders, and dropdowns. In most forms, input fields have a visible label but do not provide a programmatic name. |
| 2.5.4 | Motion Actuation | A | Supports | Software: The product does not have functionality operated by device motion or user motion. |
| 3.1.1 | Language of Page | A | Does Not Support | Software: The language cannot be programmatically determined. |
| 3.1.2 | Language of Parts | AA | Supports | Software: Changes of language for passages or phrases can be programmatically determined. |
| 3.2.1 | On Focus | A | Partially Supports | Software: In most product functions, components do not initiate a change of context when focused. Exceptions include: Context changes when some sliders receive focus. |
| 3.2.2 | On Input | A | Partially Supports | Software: Exceptions include: Context changes on input in form controls within the “Keyboard shortcuts” section. The Tab key is recognized, and the user cannot change the value when navigating to each control. |
| 3.2.3 | Consistent Navigation | AA | Supports | Software: This criterion does not apply to non-web software. |
| 3.2.4 | Consistent Identification | AA | Supports | Software: This criterion does not apply to non-web software. |
| 3.3.1 | Error Identification | A | Supports | Software: Where input errors are automatically detected, such as the input fields within “Keyboard shortcuts”, items in error are identified and error messages are provided programmatically (e.g., “invalid entry” is announced), an error icon is provided, and a red border outlines the input. |
| 3.3.2 | Labels or Instructions | A | Partially Supports | Software: Labels are provided for most input fields. Exceptions include: A placeholder is used for the “Search Scene…” field that disappears on input. |
| 3.3.3 | Error Suggestion | AA | Supports | Software: Where input errors are automatically detected, such as the input fields within “Keyboard shortcuts”, suggestions for correction are provided to the user. |
| 3.3.4 | Error Prevention (Legal, Financial, Data) | AA | Supports | Software: The product does not process legal commitments or financial transactions. When editing files, changes to user-controllable data are reversible or can be confirmed before finalizing. |
| 4.1.1 | Parsing | A | Supports | Software: The product is not implemented using markup languages. |
| 4.1.2 | Name, Role, Value | A | Does Not Support | Software: User interface components in most product functions do not provide programmatic name, role, state, or value information. Examples include: Tab controls do not provide the correct selected state to the user. Disabled links do not have a disabled state or role. Tool buttons do not represent their current selected state. Many buttons do not have an accessible name (including, but not limited to, tools) or state (e.g., the expandable controls do not announce expanded state). The view port and information contained within list boxes and list items are not available to assistive technology |
| 4.1.3 | Status Messages | AA | Supports | Software: This criterion does not apply to non-web software |
| 502.2.1 | User Control of Accessibility Features | - | Not Applicable | The product is not platform software. |
| 502.2.2 | No Disruption of Accessibility Features | - | Partially Supports | Most product functions do not disrupt platform accessibility features. Exceptions include: As noted in 1.4.4 Resize Text, the user is unable to increase the font size of the application. |
| 502.3.1 | Object Information | - | Does Not Support | Most objects in the product do not expose name, role, state, boundary, or description information to assistive technology. |
| 502.3.2 | Modification of Object Information | - | 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 , some controls do not allow the user to change the state. |
| 502.3.3 | Row, Column, and Headers | - | Does Not Support | The product does not expose the row, column, and headers of most table cells to assistive technology. |
| 502.3.4 | Values | - | Supports | The product exposes the values of input controls to assistive technology. |
| 502.3.5 | Modification of Values | - | Supports | The product allows assistive technology to modify the values and text of input controls. |
| 502.3.6 | Label Relationships | - | Does Not Support | The product does not expose most label relationships to assistive technology. |
| 502.3.7 | Hierarchical Relationships | - | Does Not Support | The product does not expose most hierarchical parent-child relationships to assistive technology. |
| 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 allows assistive technology to modify the values and text of input controls. |
| 502.3.10 | List of Actions | - | Does Not Support | Most controls in the product do not expose programmatic role information and actions which can be taken on objects to assistive technology. |
| 502.3.11 | Actions on Objects | - | Partially Supports | The product allows assistive technology to perform most actions on objects. Exceptions include: As noted in 2.1.1 Keyboard , many menus, buttons, and tooltips cannot be accessed using the keyboard. |
| 502.3.12 | Focus Cursor | - | Supports | The product exposes text content and text values to assistive technology. |
| 502.3.13 | Modification of Focus Cursor | - | Supports | Where components receive focus, the product allows assistive technology to move focus and modify selection attributes. |
| 502.3.14 | Event Notification | - | Supports | The product notifies assistive technology about attribute changes in user interface elements. |
| 503.4.1 | Caption Controls | - | Not Applicable | The product does not have elements that require caption controls. |
| 503.4.2 | Audio Description Controls | - | Not Applicable | The product does not have elements that require audio description controls. |
| 4.2.1 | Usage without vision | - | Does Not Support | Software: Most functions of the product are not usable without vision. Examples include: As noted in 1.1.1 Non-text Content , some images do not have alternative text. As noted in 1.3.1 Info and Relationships , most form fields are not labeled, tables do not have headers, form controls groups do not have common labels, and most headings are not identified or are out of order. As noted in 2.1.1 Keyboard , many menus, buttons, and tooltips cannot be accessed using the keyboard. As noted in 2.4.2 Page Titled , dialogs are not properly labeled. As noted in 2.4.3 Focus Order , programmatic focus do |
| 4.2.2 | Usage with limited vision | - | Partially Supports | Software: Most functions of the product are usable with limited vision. Exceptions include: As noted in 1.4.3 Contrast (Minimum) , some text and buttons on focus do not have sufficient color contrast. As noted in 1.4.4 Resize Text , the user is unable to increase the font size within the application. As noted in 11.7 User Preferences , the user is unable to increase the font size within the application. As noted in 503.2 User Preferences , the user is unable to increase the font size within the application. |
| 4.2.3 | Usage without perception of colour | - | Supports | Software: The product does not rely solely on color to communicate information. |
| 4.2.4 | Usage without hearing | - | Supports | Software: The product does not require the use of hearing. |
| 4.2.5 | Usage with limited hearing | - | Supports | Software: The product does not require the use of hearing. |
| 4.2.6 | Usage with no or limited vocal capability | - | Supports | Software: The product does not require the use of speech. |
| 4.2.7 | Usage with limited manipulation or strength | - | Partially Supports | Software: Most of the product is functional with limited manipulation. Exceptions include: As noted in 2.1.1 Keyboard , many menus, buttons, and tooltips cannot be accessed using the keyboard. As noted in 2.4.3 Focus Order, programmatic focus does not shift to new content such as dialogs nor return to spawning elements. Focus is lost when some actions occur. As noted in 3.2.1 On Focus , context changes on focus occur on some controls. |
| 4.2.8 | Usage with limited reach | - | Supports | Software: The product is functional with limited reach. |
| 4.2.9 | Minimize photosensitive seizure triggers | - | Supports | Software: The product does not contain flashing content. |
| 4.2.10 | Usage with limited cognition, language or learning | - | Supports | Software: The product is functional for users 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 visible labels and error identification in the form of iconography and use of color. |
| 4.2.11 | Privacy | - | Supports | Software: The product does not ask for or display legal, financial, or personal data. |
| 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 | - | Partially Supports | The product has only non-mechanical operable parts, such as on-screen buttons. Most operable parts have an accessible name which enables them to be discernible without user vision. Exceptions include: Some graphical on-screen buttons do not have an accessible name. |
| 5.6.1 | Tactile or auditory status | - | Not Applicable | The product does not have locking or toggle controls. |
| 5.6.2 | Visual status | - | Not Applicable | The product does not have locking or toggle controls. |
| 11.6.1 | User control of accessibility features | - | Not Applicable | The product is not platform software. |
| 11.6.2 | No disruption of accessibility features | - | Partially Supports | Most product functions do not disrupt platform accessibility features. Exceptions include: As noted in 1.4.4 Resize Text , the user is unable to increase the font size of the application. |
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 March 2022. 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.