Adobe Experience Manager (AEM) Forms Document Security 6.5
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
- 20
- Partially supports
- 4
- Does not support
- 6
- Not applicable
- 0
- Not evaluated
- 0
Level AA — 20 criteria
- Supports
- 15
- Partially supports
- 2
- Does not support
- 3
- 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 (61)
| Criterion | Name | Level | Conformance | Remarks from vendor |
|---|---|---|---|---|
| 1.1.1 | Non-text Content | A | Does Not Support | While several meaningful images contain text alternatives, many meaningful and decorative images and icons do not. |
| 1.2.1 | Audio-only and Video-only (Prerecorded) | A | Supports | The product does not contain prerecorded audio-only or video-only media. |
| 1.2.2 | Captions (Prerecorded) | A | Supports | The product does not contain any content that requires captions. |
| 1.2.3 | Audio Description or Media Alternative (Prerecorded) | A | Supports | The product does not contain prerecorded video content that would require audio description or a media alternative. |
| 1.2.4 | Captions (Live) | AA | Supports | The product does not contain live synchronized media. |
| 1.2.5 | Audio Description (Prerecorded) | AA | Supports | The product does not contain prerecorded video content that would require audio description. |
| 1.3.1 | Info and Relationships | A | Partially Supports | Most visual structure and relationship information is provided through object information or in text. Exceptions include: Table heading cells are not identified correctly Landmark regions are not provided Grouping elements for radio button and check box groups are not provided Error messages are not associated with the control causing the error |
| 1.3.2 | Meaningful Sequence | A | Partially Supports | The product presents most content in a meaningful sequence. |
| 1.3.3 | Sensory Characteristics | A | Supports | Instructions provided for understanding and operating content do not rely solely on sensory characteristics. |
| 1.3.4 | Orientation | AA | Supports | Content does not restrict its view and operation to a single display orientation. |
| 1.3.5 | Identify Input Purpose | AA | Does Not Support | The product does not identify the purpose of the inputs on the Local User Options screen. |
| 1.4.1 | Use of Color | A | Supports | In the product color is not used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element. |
| 1.4.2 | Audio Control | A | Supports | The product does not contain audio that plays automatically. |
| 1.4.3 | Contrast (Minimum) | AA | Partially Supports | Some components on the product do not meet the minimum contrast requirements, including the following: Links on the breadcrumb bar |
| 1.4.4 | Resize text | AA | Partially Supports | Throughout the product, when resizing text by up to 200%, some text is no longer contained within its containers and overlaps with elements, causing it to be difficult to read. |
| 1.4.5 | Images of Text | AA | Supports | The product uses text instead of images of text. |
| 1.4.10 | Reflow | AA | Does Not Support | Throughout the system, when the view port is reduced to 320px wide, content can only be viewed by scrolling in two dimensions. Some content also overlaps other content and functionality is impeded. |
| 1.4.11 | Non-text Contrast | AA | Supports | Throughout the system, links and controls have sufficient contrast. |
| 1.4.12 | Text Spacing | AA | Supports | There is no loss of content or functionality when users override author specified text styles. |
| 1.4.13 | Content on Hover or Focus | AA | Supports | Throughout the product, content is not made visible via hover or focus. |
| 2.1.1 | Keyboard | A | Partially Supports | Most product functionality can be operated through a keyboard interface. Exceptions include: Pop-up calendar controls |
| 2.1.2 | No Keyboard Trap | A | Supports | The product does not feature any content or controls that cause a keyboard trap. |
| 2.1.4 | Character Key Shortcuts | A | Supports | No shortcuts are used in the product. |
| 2.2.1 | Timing Adjustable | A | Supports | The product does not include time limits less than 20 hours. |
| 2.2.2 | Pause, Stop, Hide | A | Supports | The product does not include elements which move, blink, scroll, or auto-update. |
| 2.3.1 | Three Flashes or Below Threshold | A | Supports | The product does not contain flashing content. |
| 2.4.1 | Bypass Blocks | A | Supports | The product uses the HTML heading elements to provide structure following the main navigation. |
| 2.4.2 | Page Titled | A | Does Not Support | Throughout the site, the page titles are generally not descriptive or unique. |
| 2.4.3 | Focus Order | A | Does Not Support | Many elements in the product receive focus in an order that does not match the visual presentation. |
| 2.4.4 | Link Purpose (In Context) | A | Supports | Links within the product make sense within their context of use. |
| 2.4.5 | Multiple Ways | AA | Supports | All pages are linked from the home screen of the application. |
| 2.4.6 | Headings and Labels | AA | Supports | Headings and labels are descriptive. |
| 2.4.7 | Focus Visible | AA | Supports | Focus indicators are clear and obvious on the product. |
| 2.5.1 | Pointer Gestures | A | Supports | The product does not use multipoint or path-based gestures for operation. |
| 2.5.2 | Pointer Cancellation | A | Partially Supports | The product contains only functionality that can be activated on the up event of a single pointer. |
| 2.5.3 | Label in Name | A | Does Not Support | For components that have visible text labels, that text usually exists in the component's accessible name. Controls which are not correctly labeled provide exceptions to this criterion. |
| 2.5.4 | Motion Actuation | A | Supports | The product does not contain any functionality that can be operated by device motion or user motion. |
| 3.1.1 | Language of Page | A | Does Not Support | The human language of the page is not defined in markup. |
| 3.1.2 | Language of Parts | AA | Supports | Content is only presented in one language at a time. |
| 3.2.1 | On Focus | A | Supports | Components do not initiate a change of context when focused. |
| 3.2.2 | On Input | A | Supports | Changes of context do not occur automatically on user input. |
| 3.2.3 | Consistent Navigation | AA | Supports | When navigational mechanisms are repeated in the product, they occur in a consistent relative order. |
| 3.2.4 | Consistent Identification | AA | Supports | Components with the same functionality, such as form controls with the same purpose are identified consistently. |
| 3.3.1 | Error Identification | A | Supports | Input errors are identified and described to the users in text. |
| 3.3.2 | Labels or Instructions | A | Supports | Controls within the product have visual labels and/or instructions. |
| 3.3.3 | Error Suggestion | AA | Supports | Most input validation errors are accompanied by a textual explanation that provides guidance about how to fix the error. |
| 3.3.4 | Error Prevention (Legal, Financial, Data) | AA | Supports | The product does not process legal commitments or financial transactions. Changes to user-controllable data are reversible or can be confirmed before finalizing. |
| 4.1.1 | Parsing | A | Supports | The product does not contain any parsing errors that cause accessibility problems. |
| 4.1.2 | Name, Role, Value | A | Does Not Support | Numerous controls and richly interactive widgets do not provide appropriate semantics necessary for conveying name, role, and value. Some examples include: Tab bar controls Pop-up calendar controls Multiple input controls are incorrectly labeled due to incorrect labeling relationships |
| 4.1.3 | Status Messages | AA | Does Not Support | Status messages that provide feedback when the user updates information in the product are not announced to assistive technologies. |
| 4.2.1 | Usage without vision | - | Does Not Support | Several pieces of functionality within the product is inaccessible to users without vision, as shown in 1.1.1 Non-text content , 1.3.1 Info and Relationships , 2.1.1 Keyboard , and 4.1.2 Name, Role, Value . |
| 4.2.2 | Usage with limited vision | - | Partially Supports | Most of the product can be used by users with low vision. Exceptions are listed in 1.4.4 Resize Text , and 2.4.3 (Focus Order) . |
| 4.2.3 | Usage without perception of colour | - | Supports | Users who cannot perceive color will be able to use the product. |
| 4.2.4 | Usage without hearing | - | Supports | The product does not contain any audio content that requires hearing. |
| 4.2.5 | Usage with limited hearing | - | Supports | The product does not contain any audio content that requires hearing. |
| 4.2.6 | Usage without vocal capability | - | Supports | The product does not require user speech. |
| 4.2.7 | Usage with limited manipulation or strength | - | Partially Supports | Most functionality within the product is accessible to users with limited manipulation, as shown in 2.1.1 Keyboard , although the issues identified in 2.4.3 Focus Order will present challenges. |
| 4.2.8 | Usage with limited reach | - | Supports | The product is functional with limited reach. |
| 4.2.9 | Minimize photosensitive seizure triggers | - | Supports | The product does not contain flashing content. |
| 4.2.10 | Usage with limited cognition | - | Partially Supports | Some features of the product will present challenges for users with cognitive impairments. Exceptions include: Issues identified in 1.3.5 Identify Input Purpose |
| 4.2.11 | Privacy | - | Supports | The product does not ask for legal, financial, or personal data. |
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 May 4, 2020. 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.