Adobe Experience Manager (AEM) Forms-Cloud
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
- 7
- Partially supports
- 12
- Does not support
- 0
- Not applicable
- 11
- Not evaluated
- 0
Level AA — 20 criteria
- Supports
- 4
- Partially supports
- 8
- Does not support
- 0
- Not applicable
- 8
- 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 (67)
| 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 active and informative images. Exceptions include: role=“img” is used on decorative images in “Test Form Data Model”, “Form Data Model Editor”, “Create Form Data Model (Select Datasource)”, “Form Editor - Side Panel (Components)”, “Rule Editor - Create Rule”, “Create Form Step 3 - Add Properties (Form Model tab)”, “Download Dialog”, “Form Style Editor”, “Rule Editor” screens. Images do not have alternate text in “Form Editor - Side Panel (Document of Record)” screen. Text alternative does not present same information |
| 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.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.1 | Info and Relationships | A | Partially Supports | Web: Structure and relationship information such as headings and tables is provided through element semantics. Exceptions include: Visible label/form field are not associated in “Test Form Data Model”, “Create Form Step 3 - Add Properties (Form Model tab)”, “Form Data Model Editor - select a data model object - Edit Properties”, “Create Form Step 1 - Select Template (Delivery Tab)”, “Create Form Step 1 - Select Template (Source Tab)”, “Create Form Step 1 - Select Template (Style Tab)”, “Create Form Step 1 - Select Template (Data Tab)” screens. Form field is not labeled in “Form Editor”, “Form |
| 1.3.2 | Meaningful Sequence | A | Partially Supports | Web: The product presents most content in a meaningful sequence. Exceptions includes: Hidden content is readable with a screen reader in “Rule Editor”, “Form Editor - Side Panel (Document of Record)” screens. |
| 1.3.3 | Sensory Characteristics | A | Not Applicable | Web: The product does not contain any instructions that rely solely on sensory characteristics. |
| 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.1 | Use of Color | A | Partially Supports | Web: Most functions of the product do not convey information through color alone. Exceptions include: Link contrast is not at least 3:1 with surrounding text in “Form Editor - Side Panel (Document of Record)” screen. |
| 1.4.2 | Audio Control | A | Not Applicable | Web: The product does not contain audio that plays automatically. |
| 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 “Create Form Step 1 - Select Template (Source Tab)”, “Form Editor”, “Rule Editor”, “Form Style Editor”, “Header”, “Preview as HTML - General - Basic Information tab”, “View - page container and header”, “Core Component – Runtime”, “Preview as HTML - Expenditure tab”, “Form Editor”, “Create Form Step 1 - Select Template (Style Tab)”, “Create Form Step 1 - Select Template (Data Tab)” screens. Link or button text lacks 4.5:1 contrast ratio on hover or focus in “Rule Editor”, “Form St |
| 1.4.4 | Resize text | AA | Partially Supports | Web: Most text can be resized using browser zoom, without content and functionality is loss. Exceptions include: Content is lost at 200% zoom in “View - page container and header”, “Form Editor - Side Panel (Document of Record)”, “Create Form Step 1 - Select Template (Source Tab)”, “Create Form Step 1 - Select Template (Submission Tab)”, “Test Form Data Model”, “Form Editor - Side Panel (Properties)”, “Form Editor” , “Create Form Step 1 - Select Template (Style Tab)”, “Create Form Step 1 - Select Template (Data Tab)” screens. |
| 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 overlaps other content at 320px width equivalent in “Rule Editor”, “Form Editor - Side Panel (Properties)”, “Create Form Step 1 - Select Template (Source Tab)”, “Create Form Step 1 - Select Template (Submission Tab)”, “View - page container and header”, “Create Form Step 3 - Add Properties (Form Model tab)”, “Form Data Model Editor”, “Form Editor”, “Create Form Step 1 - Select Template (Style Tab)”, |
| 1.4.11 | Non-text Contrast | AA | Partially Supports | Web: Most meaningful non-text content elements have sufficient contrast requirements. Exceptions include: State of active component lacks 3 to 1 contrast ratio in “Create Form Step 1 - Select Template (Source Tab)”, “View - page container and header”, “Form Editor”, “Create Form Step 1 - Select Template (Style Tab)”, “Create Form Step 1 - Select Template (Data Tab)” screens. Active user interface component lacks 3 to 1 contrast ratio in “View - page container and header”, “Form Editor - Side Panel (Properties)”, “Create Form Step 1 - Select Template (Delivery Tab)”, “Create Form Step 1 - Selec |
| 1.4.12 | Text Spacing | AA | Supports | Web: All functions of the product support the required text style properties without loss of content or functionality. |
| 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: Hover content disappearing in “Form Editor - Side Panel (Properties)” screen. Additional content not dismissible in “Header” screen. |
| 2.1.1 | Keyboard | A | Partially Supports | Web: Most product functionality can be operated through a keyboard interface. Exceptions include: Function cannot be performed by keyboard alone in “Form Editor - Side Panel (Document of Record)”, “Create Form Step 3 - Add Properties (Form Model tab)”, “Form Editor - Side Panel (Properties)”, “Form Style Editor”, “Create Form Step 2 - Add Properties (Basic tab)” screens. Drag and drop feature is not keyboard accessible in “Form Data Model Editor” screen. |
| 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 ch |
| 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 | Partially Supports | Web: The product provides mechanism to bypass most repeated blocks. Exceptions include: Frames are missing an accessible name in “View - page container and header” screen. |
| 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 is lost or misplaced due to user interaction or content update in “Form Editor - Side Panel (Properties)” screen. Hidden or empty element receives focus in “Form Editor”, “View - page container and header”, “Form Editor - Side Panel (Document of Record)”, “Rule Editor” screens. Keyboard focus order is not logical in “Form Style Editor”, “Rule Editor” screens. |
| 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.4.5 | Multiple Ways | AA | Not Applicable | Web: Users can locate web pages in the product through the menu and options in the main section. |
| 2.4.6 | Headings and Labels | AA | Partially Supports | Web: Most headings and labels are descriptive. Exceptions include: Buttons have same name but different actions in “Create Form Step 1 - Select Template (Delivery Tab)”, “Create Form Step 2 - Add Properties (Basic tab)” screens. Programmatic label does not convey purpose of control in “Header” screen. |
| 2.4.7 | Focus Visible | AA | Partially Supports | Web: Most focusable elements have a visible keyboard focus indicator. Exceptions include: Focus indicator is missing in “Form Style Editor”, “Create Form Step 1 - Select Template (Source Tab)”, “Create Form Step 1 - Select Template (Style Tab)”, “Create Form Step 1 - Select Template (Data Tab)”. Screens. |
| 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 control contain text of their visible labels. Exceptions include: Accessible name missing in “Create Form Step 1 - Select Template (Delivery Tab)”, “Form Editor”, “Create Form Step 3 - Add Properties (Form Model tab)”, “Create Form Step 1 - Select Template (Source Tab)”, “Create Form Step 2 - Add Properties (Basic tab)”, “Create Form Step 1 - Select Template (Style Tab)”, “Create Form Step 1 - Select Template (Data Tab)” screens. |
| 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.1.2 | Language of Parts | AA | Not Applicable | Web: Content is only presented in one language at a |
| 3.2.1 | On Focus | A | Supports | Web: Components do not initiate a change of context when focused. |
| 3.2.2 | On Input | A | Partially Supports | Web: Changes of context do not occur automatically on user input. Exceptions include: Form field causes unexpected change in “Form Editor - Side Panel (Properties)” screen. |
| 3.2.3 | Consistent Navigation | AA | Not Applicable | Web: When navigational mechanisms are repeated in the product, they occur in a consistent relative order. |
| 3.2.4 | Consistent Identification | AA | Not Applicable | Web: Components with the same functionality are identified consist |
| 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: Instructions missing for assistive technology users in “Form Editor - Side Panel (Properties)” screen. Label is not persistent in “Create Form Step 1 - Select Template (Delivery Tab)” screen. |
| 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 | Not Applicable | Web: The product does not process legal commitments or financial transactions and does not modify user-controllable data. |
| 4.1.1 | Parsing | A | Partially Supports | Web: In most product functions, 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. Exceptions include: Interactive controls must not be nested in “Rule Editor”, “View - page container and header”, “Rule Editor - Create Rule” screens. id attribute value must be unique in “Form Editor - Side Panel (Document of Record)”, “View - page container and header”, “Form Style Editor”, “Form Data Model Editor”, “Form Editor”, “Form Data Model Editor - select a data model object - Edit Prope |
| 4.1.2 | Name, Role, Value | A | Partially Supports | Web: User interface components in most product functions provide programmatic name, role, and/or state information. Exceptions include: Button does not have a name in “Form Style Editor”, “Form Data Model Editor”, “Create Form Step 1 - Select Template (Submission Tab)” screens. Button does not have a role in “Create Form Step 3 - Add Properties (Form Model tab)”, “Form Style Editor”, “Create Form Step 1 - Select Template (Source Tab)”, “Create Form Step 1 - Select Template (Style Tab)”, “Create Form Step 1 - Select Template (Data Tab)” screens. Expand/collapse state of the element is missing o |
| 4.1.3 | Status Messages | AA | Partially Supports | Web: When status messages do not receive focus, the product provides the dynamic and automatic update to the assistive technology. Exception includes: Status message not automatically announced in “Create Form Step 1 - Select Template (Source Tab)”, “Create Form Step 1 - Select Template (Style Tab)”, “Create Form Step 1 - Select Template (Data Tab)” screens. |
| 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 , role=“img” is used on decorative images, Images must have alternate text, Text alternative does not present same info as image, [role=”img”] elements does not have an alternative text, The decorative image is not hidden from screen readers. As noted in 1.3.1 Info and Relationships , Visible label/form field are not associated, Form field is not labeled, Visual heading text is not marked as heading, Heading levels are out of order, Visual list is not marked up as list, List or |
| 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 , role=“img” is used on decorative images, Images must have alternate text, Text alternative does not present same info as image, [role=”img”] elements does not have an alternative text, The decorative image is not hidden from screen readers. As noted in 1.3.1 Info and Relationships , Visible label/form field are not associated, Form field is not labeled, Visual heading text is not marked as heading, Heading levels are out of order, Visual list is not marked up as list, Lis |
| 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 , Link contrast is not at least 3:1 with surrounding text. As noted in 1.4.3 Contrast (Minimum) , Text content lacks 4.5:1 contrast ratio, Elements must have sufficient color contrast, Link or button text lacks 4.5:1 contrast ratio on hover or focus, Placeholder text lacks 4.5:1 contrast ratio. As noted in 1.4.11 Non-text Contrast , State of active component lacks 3 to 1 contrast ratio, Active user interface component lacks 3 to 1 contrast ratio, an icon lacks 3 to 1 co |
| 4.2.4 | Usage without hearing | - | Not Applicable | Web: The product does not require the use of hearing. |
| 4.2.5 | Usage with limited hearing | - | Not Applicable | Web: The product does not require the use of hearing. |
| 4.2.6 | Usage without 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 with limited manipulation or strength with the help of speech recognition or switch control. Exceptions include: As noted in 1.4.13 Content on Hover or Focus , Hover content disappearing, Additional content not dismissible. As noted in 2.1.1 Keyboard , Function cannot be performed by keyboard alone, Drag and drop feature is not keyboard accessible. As noted in 2.4.1 Bypass Blocks , Frames must have an accessible name. As noted in 2.4.3 Focus Order , Keyboard focus is lost or misplaced due to user interaction or content update, Hidden or empty eleme |
| 4.2.8 | Usage with limited reach | - | Partially Supports | Web: Most functions of the product are usable with limited reach. Exceptions include: As noted in 1.4.13 Content on Hover or Focus , Hover content disappearing, Additional content not dismissible. As noted in 2.1.1 Keyboard , Function cannot be performed by keyboard alone, Drag and drop feature is not keyboard accessible. As noted in 2.4.1 Bypass Blocks , Frames must have an accessible name. As noted in 2.4.3 Focus Order , Keyboard focus is lost or misplaced due to user interaction or content update, Hidden or empty element receives focus, Keyboard focus order is not logical. As noted in 2.4.6 |
| 4.2.9 | Minimize photosensitive seizure triggers | - | Not Applicable | Web: The product does not contain flashing content or media. |
| 4.2.10 | Usage with limited cognition, language or learning | - | Partially Supports | Web: 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. The product provides labeling for most controls. Exceptions include: As noted in 1.3.2 Meaningful Sequence , Hidden content is readable with a screen reader. As noted in 2.4.1 Bypass Blocks , Frames must have an accessible name. As noted in 2.4.3 Focus Order , Keyboard focus is lost or misplaced due to user interaction or content update, Hidden or empty element re |
| 4.2.11 | Privacy | - | Not Applicable | Web: The product 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.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 | Visual status of controls is discernible in the product. |
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 April 2023. 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.