Adobe Admin Console 04-2024
Accessibility Conformance Report published by Adobe
Partial extraction. We read 30 of 31 Level A and 20 of 24 Level AA criteria from this document (91% 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 — 30 criteria
- Supports
- 8
- Partially supports
- 12
- Does not support
- 0
- Not applicable
- 10
- Not evaluated
- 0
Level AA — 20 criteria
- Supports
- 7
- Partially supports
- 10
- Does not support
- 0
- 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 (70)
| 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 functional and informative images. Exceptions include: Informative Image missing text alternative in ‘Header’ component. |
| 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 | Partially Supports | Web: Most visual structure and relationship information is not provided through element semantics or object information or are available in text. Examples include: Table data cell is marked as a header cell in ‘Product Details Page’, ‘Users Page Table’ pages. Visual heading text is not marked as heading in ‘Create a Package’, ‘Quick Assign’ pages. Certain ARIA roles do not contain particular children. |
| 1.3.2 | Meaningful Sequence | A | Partially Supports | Web: The product presents most content in a meaningful sequence. Exceptions include: aria-hidden="true" is used incorrectly in ‘Product Detail 'New Profile', ‘Support Summary 'Create case' pages. Hidden content is readable with a screen reader in ‘Add Users via CSV’ page. |
| 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 of the functions of the product do not convey information through color alone. Exceptions include: Inline links can only be distinguished by color alone. |
| 1.4.2 | Audio Control | A | Not Applicable | Web: The product does not contain audio that plays automatically. |
| 2.1.1 | Keyboard | A | Partially Supports | Web: Most product functionality can be operated through a keyboard interface. Exceptions include: Action cannot be performed with a screen reader turned on in ‘Quick Assign’ page. |
| 2.1.2 | No Keyboard Trap | A | Supports | Web: The product does not include keyboard traps. |
| 2.1.4 | Character Key Shortcuts | A | Not Applicable | Web: The product does not provide character key shortcuts. |
| 2.2.1 | Timing Adjustable | A | Not Applicable | Web: The product does not include time limits. |
| 2.2.2 | Pause, Stop, Hide | A | Not Applicable | 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 Skip link, headings which allows users to bypass repeated blocks. |
| 2.4.2 | Page Titled | A | Partially Supports | Web: Most of the titles of pages describe their purpose. Exceptions include: Page <title> does not identify purpose of page in ‘Accounts Detail Page: VIP’, ‘Create a Package’, ‘Identity Federation Setup’ pages. |
| 2.4.3 | Focus Order | A | Partially Supports | Web: Most components receive focus in a meaningful order. Exceptions include: Hidden or empty element receives focus in ‘Add Users via CSV’ page. |
| 2.4.4 | Link Purpose (In Context) | A | Partially Supports | Web: Most of the links have a purpose that can be determined from the link text alone or from the programmatic context of the link. Exceptions include: Multiple links have the same programmatic link text but different destinations in ‘Create a Package’ page. Purpose of link is not clear in context ‘Audit Logs’ page. |
| 2.5.1 | Pointer Gestures | A | Not Applicable | 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. |
| 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: Accessible name does not contain visible label in ‘Support Summary 'Create case' page. |
| 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 | Supports | Web: Components do not initiate a change of context when focused. |
| 3.2.2 | On Input | A | Supports | Web: Changes of context do not occur automatically on user input. |
| 3.3.1 | Error Identification | A | Partially Supports | Web: Most input errors are identified and described to the users in text. Exceptions include: Error message cannot be read by screen readers in ‘Quick Assign’ page. Input error is not described in text in ‘Support Summary 'Create case’ page. |
| 3.3.2 | Labels or Instructions | A | Partially Supports | Web: Labels are provided for most of the fields. Exceptions include: Visible label missing in ‘Product Details Page’, ‘Users Page Table’ pages. |
| 4.1.1 | Parsing | A | Supports | For the WCAG 2.0, 2.1, EN 301 549, and Revised 508 Standards, the September 2023 errata update indicates this criterion is always supported. See the WCAG 2.0 Editorial Errata and the WCAG 2.1 Editorial Errata . This criterion was removed from WCAG 2.2. |
| 4.1.2 | Name, Role, Value | A | Partially Supports | Web: User interface components at most of the places do not provide programmatic name, role, state, or value information. Examples include: Combo box is missing appropriate roles and/or attributes in ‘Add Users’, ‘Header’ pages. Dialog is missing appropriate role and/or attributes in ‘Add Users’, ‘Add Users via CSV’, ‘Identity Sync Setup: Sync Users and Groups’, ‘Product Detail 'New Profile'’, ‘Support Summary 'Create case' pages. Interactive controls are nested in ‘Identity Sync Setup: Sync Users and Groups’ page. The element's name is missing or incorrect in ‘Support Summary 'Create case' pa |
| 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 autocomplete attribute used incorrectly in ‘Add Users’, ‘Quick Assign’, ‘Product Detail 'New Profile'’ pages. |
| 1.4.3 | Contrast (Minimum) | AA | Partially Supports | Web: Most text meets minimum contrast requirements. Exceptions include: Text content lacks 4.5:1 contrast ratio in ‘Accounts Detail Page: Team Direct’, ‘Accounts Detail Page: VIP’, ‘Identity Federation Setup’, ‘Identity Sync Setup: Sync users and groups from Azure AD modal’, ‘Support Summary 'Create case’, ‘Support Summary Page’ pages. Placeholder text lacks 4.5:1 contrast ratio in ‘Quick Assign’ page. |
| 1.4.4 | Resize text | AA | Partially Supports | Web: Most text can be resized using browser zoom, but content and functionality is lost in some product functions. Exceptions include: Content is lost at 200% zoom in ‘Audit Logs’, ‘Contracts and Agreements Page’, ‘Footer’, ‘Header’, ‘Product Details Page’, ‘Storage Overview’ pages. |
| 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: Content does not reflow to fit 320px width equivalent in ‘Header’ component. Info or functionality is lost due to overlapping content at 320px equivalent in ‘Audit Logs’, ‘Contracts and Agreements Page’, ‘Create a Package’, ‘Homepage’, ‘Identity Federation Setup’, ‘Quick Assign’ pages. Info or functionality is unavailable at 320px width equivalent in ‘Footer’, ‘Product Details Page’, ‘Storage Overview’, ‘Sup |
| 1.4.11 | Non-text Contrast | AA | Partially Supports | Web: Most meaningful non-text content elements have sufficient contrast. Exceptions include: Active user interface component lacks 3 to 1 contrast ratio in ‘Quick Assign’ page. An icon lacks 3 to 1 contrast ratio in ‘Quick Assign’ page. State of active component lacks 3 to 1 contrast ratio in ‘Product Detail 'New Profile'’ page. |
| 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: Text spacing content cut off in ‘Header’ component. Text spacing content cut off and overlaps in ‘Users Page Table’ page. |
| 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: Additional content not dismissible in ‘Accounts Detail Page: VIP’ page. |
| 2.4.5 | Multiple Ways | AA | Supports | Web: Multiple ways are available to find other pages on the site. |
| 2.4.6 | Headings and Labels | AA | Partially Supports | Web: Most of the Headings and labels are descriptive. Exceptions include: Controls have same name but different actions in ‘Create a Package’, ‘Identity Sync Setup: Sync users and groups from Azure AD modal’, ‘Product Detail 'New Profile'’ pages. Label does not convey purpose of control in ‘Product Detail 'New Profile'’ page. Programmatic label does not convey purpose of control in ‘Create a Package’, ‘Support Summary 'Create case' pages. |
| 2.4.7 | Focus Visible | AA | Supports | Web: The keyboard focus indicator is visible by default. |
| 3.1.2 | Language of Parts | AA | Partially Supports | Web: Most of the Change of language for passages or phrases can be programmatically determined. Exceptions include: Change in language is not marked in ‘Footer’ component. |
| 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, the error is identified, and an error message is suggested to fix. |
| 3.3.4 | Error Prevention (Legal, Financial, Data) | AA | Not Applicable | Web: The product does not process legal commitments or financial transactions and does not modify user-controllable data. |
| 4.1.3 | Status Messages | AA | Partially Supports | Web: When status messages do not receive focus, the product does not provide the dynamic update to the assistive technology. Exceptions include: Status message not automatically announced in ‘Audit Logs’, ‘Product Detail 'New Profile'’, ‘Product Details Page’, ‘Quick Assign’, ‘Support Summary 'Create case’, ‘Support Summary Page’, ‘Users Page Table’ pages. |
| 4.2.1 | Usage without vision | - | Partially Supports | Web: Most of web functions are usable without vision. Exceptions include: 1.1.1 Non-text Content 1.3.1 Info and Relationships 1.3.2 Meaningful Sequence 1.4.1 Use of Color 2.1.1 Keyboard 2.4.2: Page Titled 2.4.3 Focus Order 2.4.4 Link Purpose 2.4.6 Headings and Labels 3.1.2 Language of Parts 3.3.2 Labels or Instructions 4.1.2 Name, Role, Value 4.1.3 Status messages |
| 4.2.2 | Usage with limited vision | - | Partially Supports | Web: Most of the web functions are usable with limited vision. Exceptions include: 1.1.1 Non-text Content 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 2.4.2: Page Titled 2.4.3 Focus Order 2.4.4 Link Purpose 2.4.6 Headings and Labels 3.1.2 Language of Parts 3.3.2 Labels or Instructions 4.1.2 Name, Role, Value 4.1.3 Status messages |
| 4.2.3 | Usage without perception of colour | - | Partially Supports | Web: Most of the web functions are usable with limited or no perception of color. Exceptions include: 1.4.1 Use of color 1.4.3 Contrast (Minimum) 1.4.11 Non-Text Contrast |
| 4.2.4 | Usage without hearing | - | Partially Supports | Web: Most functionality is usable without hearing. Exceptions include: 1.1.1 Non-Text Content 3.1.2 Language of Parts |
| 4.2.5 | Usage with limited hearing | - | Partially Supports | Web: Most functionality is usable with limited hearing. Exceptions include: 1.1.1 Non-Text Content 3.1.2 Language of Parts |
| 4.2.6 | Usage with no or limited vocal capability | - | Not Applicable | The product does not require the use of speech or other vocal output. |
| 4.2.7 | Usage with limited manipulation or strength | - | Partially Supports | Web: Most of the web functions are usable with limited manipulation or strength. Exceptions include: 1.3.5 Identify Input Purpose 1.4.13 Content on Hover or Focus 2.1.1 Keyboard 2.4.2: Page Titled 2.4.3 Focus Order 2.4.4 Link Purpose 2.4.6 Headings and Labels 2.5.3 Label in name 3.3.2 Labels or Instructions 4.1.2 Name, Role, Value |
| 4.2.8 | Usage with limited reach | - | Partially Supports | Web: Most of the web functions are usable with limited reach. Exceptions include: 1.3.5 Identify Input Purpose 1.4.13 Content on Hover or Focus 2.5.3 Label in name |
| 4.2.9 | Minimize photosensitive seizure triggers | - | Not Applicable | Web: The web pages do not contain flashing content or media. |
| 4.2.10 | Usage with limited cognition, language or learning | - | Partially Supports | Web: Most of the web functions are usable with limited language, cognitive, and learning abilities. Exceptions include: 1.3.2 Meaningful Sequence 1.3.5 Identify Input Purpose 1.4.12: Text Spacing 2.4.2: Page Titled 2.4.3 Focus Order 2.4.4 Link Purpose 2.4.6 Headings and Labels 3.1.2 Language of Parts 3.3.2 Labels or Instructions 4.1.2 Name, Role, Value 4.1.3 Status messages |
| 4.2.11 | Privacy | - | Not Applicable | Web: The web does not provide any privacy features. |
| 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 | The product does not have closed functionality. |
| 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 are noted in 1.3.1 Info and Relationships , 2.4.6 Headings and Labels and 4.1.2 Name, Role, Value. |
| 5.6.1 | Tactile or auditory status | - | Not Applicable | Tactile or auditory status is not included in the product. |
| 5.6.2 | Visual status | - | Supports | The visual status of controls is discernible in the product. |
| 12.1.1 | Accessibility and compatibility features | - | Not Applicable | There are no accessibility and compatibility feature present to be documented. |
| 12.2.2 | Information on accessibility and compatibility features | - | Not Applicable | Information on accessibility and compatibility features are not provided. |
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.