Adobe Experience Manager 6.5 Forms Designer
Accessibility Conformance Report published by Adobe
Partial extraction. We read 24 of 31 Level A and 13 of 24 Level AA criteria from this document (67% 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 — 24 criteria
- Supports
- 19
- Partially supports
- 5
- Does not support
- 0
- Not applicable
- 0
- Not evaluated
- 0
Level AA — 13 criteria
- Supports
- 10
- Partially supports
- 2
- 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 (79)
| Criterion | Name | Level | Conformance | Remarks from vendor |
|---|---|---|---|---|
| 1.1.1 | Non-text Content | A | Supports | Software: Non-text content within AEM Forms Designer, when present, contains appropriate textual alternatives. PDF Output: When content creators supply information within AEM Forms Designer, label information will be transferred to output PDF content. |
| 1.2.1 | Audio-only and Video-only (Prerecorded) | A | Supports | Software: No audio-only or video-only content is present within AEM Forms Designer. PDF Output: No audio-only or video-only content will be exported from AEM Forms Designer. |
| 1.2.2 | Captions (Prerecorded) | A | Supports | Software: AEM Forms Designer does not include any prerecorded audio or video content. PDF Output: Content authored by AEM Forms Designer will not include any prerecorded audio or video content |
| 1.2.3 | Audio Description or Media Alternative (Prerecorded) | A | Supports | Software: AEM Forms Designer does not include any prerecorded audio or video content. PDF Output: PDF content output from AEM Forms Designer does not include any prerecorded audio or video content. |
| 1.2.4 | Captions (Live) | AA | Supports | Software: AEM Forms Designer does not include live audio or video content. PDF Output: AEM Forms Designer output does not include live audio or video content. |
| 1.2.5 | Audio Description (Prerecorded) | AA | Supports | Software: AEM Forms Designer does not include prerecorded video content. PDF Output: AEM Forms Designer output does not include prerecorded video content. |
| 1.3.1 | Info and Relationships | A | Partially Supports | Software: The majority of content within AEM Forms Designer contains information about relationships programmatically. However, a rating of Partially Supports has been given because within the Design view, content, such as tables, does not have any programmatic relationships set and some groups of forms fields are not set within a GroupBox. PDF Output: Content creators can generate forms where information and relationships are conveyed programmatically. Labels can be explicitly associated with form fields, table headers with columns, and headings. |
| 1.3.2 | Meaningful Sequence | A | Supports | Software: Reading order of content within AEM Forms Designer is logical and intuitive. PDF Output: Content creators can explicitly define the focus and reading order of exported PDF content within AEM Forms Designer, using either automatic and custom reading / focus orders. |
| 1.3.3 | Sensory Characteristics | A | Supports | Software: Supports PDF Output: Supports |
| 1.4.1 | Use of Color | A | Supports | Software: Supports PDF Output: Supports |
| 1.4.2 | Audio Control | A | Supports | Software: No audio within the AEM Forms Designer plays automatically. PDF Output: No audio will automatically play within PDF output of AEM Forms Designer. |
| 1.4.3 | Contrast (Minimum) | AA | Partially Supports | Software: The majority of content within AEM Forms Designer contains sufficient color contrast, displaying black text on white or grey backgrounds. However, a rating of Partially Supports has been given because the “HOW TO” and “TIP” text appears in a light orange color, on a white background. PDF Output: Content creators are able to generate forms that contain sufficient color contrast ratios. |
| 1.4.4 | Resize text | AA | Partially Supports | Software: Most components within AEM Forms Designer will respect platform standard magnification. However, a rating of Partially Supports has been given because some content will not scale appropriately, notably the toolbar items. Additionally, some content is lost when magnification occurs, notably on the Welcome to Designer dialog. PDF Output: Content within AEM Forms Designer can be magnified to at least 200% without loss of content. |
| 1.4.4 | Resize text | AA | Supports | Software: AEM Forms Designer rarely uses images of text. A rating of Partially Supports has been given because the only instances of images of text are peripheral to the main application, and occur in a very limited capacity on tips dialogs. PDF Output: Images of text are never required within any forms generated by AEM Forms Designer. |
| 2.1.1 | Keyboard | A | Partially Supports | Software: Partially Supports PDF Output: Supports |
| 2.1.2 | No Keyboard Trap | A | Supports | Software: Supports PDF Output: Supports |
| 2.2.1 | Timing Adjustable | A | Supports | Software: AEM Forms Designer does not have time limits. PDF Output: PDF content output by AEM Forms Designer does not present users with timeouts. |
| 2.3.1 | Three Flashes or Below Threshold | A | Supports | Software: AEM Forms Designer does not include elements which flash. PDF Output: Content creators can design forms that do not flash at all, or that flash less than three times per second. |
| 2.4.1 | Bypass Blocks | A | Supports | Software: Does not apply. PDF Output: PDF Forms do not contain blocks of repeated content unless specifically designed. |
| 2.4.2 | Page Titled | A | Supports | Software: AEM Forms Designer windows, and modal dialogs contain appropriate and descriptive page titles. PDF Output: Content creators are able to specify meaningful titles. |
| 2.4.3 | Focus Order | A | Supports | Software: The focus order of form field controls within AEM Forms Designer is logical. PDF Output: AEM Forms Designer provides both automatic and manual methods to specify a logical focus order for forms exported through the product. |
| 2.4.4 | Link Purpose (In Context) | A | Supports | Software: Links within AEM Forms Designer, such as the How To links, all contain appropriate labels ensuring users will be able to determine what the purpose of a link is. PDF Output: Content creators can supply informative link names within forms. |
| 2.4.5 | Multiple Ways | AA | Supports | Software: Supports PDF Output: Supports |
| 2.4.6 | Headings and Labels | AA | Supports | Software: The labels for fields, tabs, and other controls within AEM Forms Designer are descriptive of their topic and purpose. PDF Output: Content creators are able to set custom heading and label text, ensuring that all of these elements are informative of both their topic and purpose. |
| 2.4.7 | Focus Visible | AA | Supports | Software: A high visible indication of focus is provided to elements as they receive keyboard focus. Typically, the native Windows focus indicator for a control is provided visually. PDF Output: PDF content output by AEM Forms Designer uses the native PDF focus indicators. |
| 3.1.1 | Language of Page | A | Supports | Software: AEM Forms Designer contains content that is programmatically defined within the program. PDF Output: By default, the language exported for Forms will be the default system language. However, content creators can specify separate languages for the entire page within AEM Forms Designer. |
| 3.1.2 | Language of Parts | AA | Does Not Support | Software: Content creators can add content that includes languages outside the product’s specified language, and AEM Forms Designer supports multiple character sets. However, a rating of Does Not Support has been given because no method exists to programmatically identify this content in another language. PDF Output: PDF Output from AEM Forms Designer supports specifying alternative languages for passages of content. |
| 3.2.1 | On Focus | A | Partially Supports | Software: Partially Supports PDF Output: Supports |
| 3.2.2 | On Input | A | Partially Supports | Software: For the vast majority of content within AEM Forms Designer, no changes of context occur on input. However, a rating of Partially Supports has been given because when an object’s Appearance combobox has the option of “Custom” selected, a modal dialog pops up and context is changed to this dialog. PDF Output: Content creators can design forms in such a way that no changes of context occur on user input. |
| 3.2.3 | Consistent Navigation | AA | Supports | Software: Does not apply. PDF Output: Repeated navigation elements, such as those that appear at the tops of pages, are able to be set in such a way that they have the same relative order every time they appear. |
| 3.2.4 | Consistent Identification | AA | Supports | Software: Does not apply. PDF Output: Repeated components within PDF output can be designed by content creators so that they are consistently identified. |
| 3.3.1 | Error Identification | A | Supports | Software: Generally, AEM Forms Designer prevents user errors by disabling controls or input fields which cannot be used. If an error occurs, the user is informed using standard dialogs. PDF Output: Content Creators can detect errors using the action builder and can add appropriate messages alerting users of errors. |
| 3.3.2 | Labels or Instructions | A | Supports | Software: AEM Forms Designer provides labels for form field controls, indicating what information users should input. PDF Output: AEM Forms Designer supports labelling of controls and actively helps content creators place labels next to form fields. |
| 3.3.3 | Error Suggestion | AA | Supports | Software: AEM Forms Designer detects when errors in form output may occur and provides prompts to users on how corrections can be made. PDF Output: Content creators can provide methods to automatically detect errors, and supply suggestions for how to correct them. |
| 3.3.4 | Error Prevention (Legal, Financial, Data) | AA | Supports | Software: Any changes to user controllable-data within AEM Forms Designer can be reversed if necessary. No legal commitments or financial transactions occur within AEM Forms Designer. PDF Output: If PDF content designed within AEM Forms Designer submits legal or financial data, content creators are able to ensure data is either reversible, checked, or confirmed. |
| 4.1.1 | Parsing | A | Supports | Software: Supports PDF Output: Supports |
| 4.1.2 | Name, Role, Value | A | Partially Supports | Software: AEM Forms Designer largely provides name, role, and state information for controls. However, a rating of Partially Supports has been given because the Objects in the Welcome screen, such as the New Form button, color pickers in application dialog boxes, and palette names, are not available. PDF Output: Using default components, content creators can create forms with appropriate names, roles, and values. |
| 502.2.1 | User Control of Accessibility Features | - | Not Applicable | AEM Forms Designer is not platform software. |
| 502.2.2 | No Disruption of Accessibility Features | - | Partially Supports | The majority of platform accessibility features are respected by AEM Forms Designer. However, a rating of Partially Supports has been given because certain sections, such as the Welcome modal dialog, the Tab Order list, and the images of text, do not respect high contrast mode settings. |
| 502.3.1 | Object Information | - | Partially Supports | AEM Forms Designer largely provides name, role, and state information for controls. However, a rating of Partially Supports has been given because as noted within 4.1.2 Name, Role, Value, a number of exceptions exist. Most notably that the New Form button on the Welcome screen, color pickers in application dialog boxes, and palette names are not available. |
| 502.3.2 | Modification of Object Information | - | Supports | States of controls within AEM Forms Designer are capable of being programmatically updated. |
| 502.3.3 | Row, Column, and Headers | - | Does Not Support | Data table structure is implied to users within the hierarchy pane. However, a rating of Does Not Support has been given because no communication of table structure, including headings, is provided to users when navigating through the Design View pane. |
| 502.3.4 | Values | - | Supports | Values for controls are able to be programmatically determined by assistive technologies. |
| 502.3.5 | Modification of Values | - | Supports | All values that can be set by users can be set programmatically within the User Interface. |
| 502.3.6 | Label Relationships | - | Supports | All label relationships between components are programmatically available to users. |
| 502.3.7 | Hierarchical Relationships | - | Partially Supports | As noted within 1.3.1 Info and Relationships, the majority of hierarchical relationships within AEM Forms Designer are programmatically defined. However, a rating of Partially Supports has been given because some exceptions exist. |
| 502.3.8 | Text | - | Supports | AEM Forms Designer exposes text content programmatically. |
| 502.3.9 | Modification of Text | - | Supports | AEM Forms Designer allows users, including those using assistive technologies, to edit text content. |
| 502.3.10 | List of Actions | - | Partially Supports | The vast majority of controls list the available actions to users. However, a rating of Partially Supports has been given because as noted in 4.1.2 Name, Role, Value, some controls do not expose appropriate roles to users that identify the number of actions available. |
| 502.3.11 | Actions on Objects | - | Supports | AEM Forms Designer allows assistive technology to programmatically execute all available programmatic actions. |
| 502.3.12 | Focus Cursor | - | Supports | As noted within 2.4.7 Focus Visible, AEM Forms Designer provides a visual indication of keyboard focus. |
| 502.3.13 | Modification of Focus Cursor | - | Partially Supports | As noted within 2.1.1 Keyboard, the vast majority of components receive programmatic keyboard focus. However, a rating of Partially Supports has been given because within the main design view, individual components receive a visual, but not programmatic, indication of focus. |
| 502.3.14 | Event Notification | - | Supports | Notifications, such as when spell checking is not supported, are made programmatically available to screen reader users. |
| 503.4.1 | Caption Controls | - | Not Applicable | As noted in 1.2.2 Captions (Prerecorded) and 1.2.4 Captions (Live), AEM Forms Designer does not contain any audio content, and does not have any controls for audio control or caption selection. |
| 503.4.2 | Audio Description Controls | - | Not Applicable | As noted in 1.2.3 Audio Description or Media Alternative (Prerecorded) and 1.2.5 Audio Description (Prerecorded), AEM Forms Designer does not contain any video content, and does not have controls for program selection. |
| 504.2.1 | Preservation of Information Provided for Accessibility in Format Conversion | - | Supports | AEM Forms Designer preserves accessibility content specified by the user within content that is exported from the application. |
| 504.2.2 | PDF Export | - | Partially Supports | PDFs exported from AEM Forms Designer contain a majority of the tags required for PDF/UA conformance. But, a rating of Partially Supports has been given because the exported content does not contain languages exported within the tag structure, and also will not display programmatically defined document titles on initial view. |
| 4.2.1 | Usage without vision | - | Partially Supports | Software: As noted previously within success criteria 1.1.1 , 1.3.1 , 2.1.1 , and 4.1.2 a large portion of the content of AEM Forms Designer does not require user vision to operate. However, a rating of Partially Supports has been given because certain areas, notably the Design view, will not be accessible. PDF Output: PDF Forms designed by AEM Forms Designer can be used by users without requiring the use of vision. |
| 4.2.2 | Usage with limited vision | - | Partially Supports | Software: The majority of content within AEM Forms Designer will be accessible to users with limited vision. However, a rating of Partially Supports has been given because, as noted within 1.4.3 Contrast and Section 508 502.2.2 , not all content of AEM Forms Designer has sufficient color contrast, or conforms to Windows High Contrast mode. PDF Output: PDF content exported from AEM Forms Designer can be authored to be usable with limited vision. |
| 4.2.3 | Usage without perception of colour | - | Supports | Software: As noted in 1.4.1 Use of Color , perception of color is never required to use AEM Forms Designer. PDF Output: PDF content exported from AEM Forms Designer can be authored to not require the perception of color. |
| 4.2.4 | Usage without hearing | - | Supports | Software: As noted within 1.2.2 , and 1.2.4 no content within AEM Forms designer includes audio, and thus no portion of the application requires hearing. PDF Output: PDF content exported from AEM Forms Designer will have no audio content, and will not require user hearing. |
| 4.2.5 | Usage with limited hearing | - | Supports | Software: As noted previously, no content within AEM Forms designer includes audio, and thus no portion of the application requires hearing. PDF Output: PDF content exported from AEM Forms Designer will have no audio content, and will not require user hearing. |
| 4.2.6 | Usage without vocal capability | - | Supports | Software: No content within AEM Forms Designer requires user speech PDF Output: PDF content exported from AEM Forms Designer will have not require user speech. |
| 4.2.7 | Usage with limited manipulation or strength | - | Partially Supports | Software: Users with limited strength will not find any issues in utilizing AEM Forms Designer. The vast majority of content within AEM Forms Designer will be usable with limited manipulation. However, a rating of Partially Supports has been given because as noted in 2.1.1 , some components are not entirely accessible through the use of the keyboard alone, most notably the design view. Elsewhere, components noted in 4.1.2 do not have fully sufficient accessible names, which may pose challenging for users of Dragon® NaturallySpeaking to interact with. PDF Output: PDF content exported from AEM F |
| 4.2.8 | Usage with limited reach | - | Partially Supports | Software: A rating of Partially Supports has been given because users with limited reach, who rely on the keyboard alone may run into accessibility issues, as previously noted within 2.1.1 Keyboard . PDF Output: Content exported from AEM Forms Designer can be authored to be operable with limited reach. |
| 4.2.9 | Minimize photosensitive seizure triggers | - | Supports | Software: Nothing within AEM Forms Designer will automatically blink or flash. PDF Output: PDF output does not require users to include blinking or flashing element in PDF forms. |
| 4.2.10 | Usage with limited cognition | - | Supports | Software: AEM Forms Designer provides wizards and other features to assist users with limited cognitive, language and learning abilities. In addition, icons are often used in conjunction with words to provide multiple means of determining what a specific function does. PDF Output: Content output by AEM Forms Designer can be authored with sufficient explanation and simplicity so as to be usable by individuals with limited cognitive, language, and learning abilities. |
| 4.2.11 | Privacy | - | Supports | Software: AEM Forms Designer supports platform features for programmatically defining password fields, ensuring user privacy. PDF Output: PDF output for password fields supports native PDF password fields, ensuring that end-user platform support for privacy is respected. Forms that deal with legal or financial data can be designed to ensure user privacy. |
| 5.5.1 | Means of operation | - | Not Applicable | AEM Forms Designer has no operable parts. |
| 5.5.2 | Operable parts discernibility | - | Not Applicable | AEM Forms Designer has no operable parts. |
| 5.6.1 | Tactile or auditory status | - | Not Applicable | AEM Forms Designer has no locking or toggle controls. |
| 5.6.2 | Visual status | - | Not Applicable | AEM Forms Designer has no locking or toggle controls. |
| 10.2.39 | Caption positioning | - | Not Applicable | AEM Forms Designer has no content requiring captioning. |
| 10.2.40 | Audio description timing | - | Not Applicable | AEM Forms Designer has no content requiring audio description. |
| 11.4.1 | User control of accessibility features | - | Not Applicable | AEM Forms Designer is not platform software. |
| 11.4.2 | No disruption of accessibility features | - | Partially Supports | The majority of platform accessibility features are respected by AEM Forms Designer. However, a rating of Partially Supports has been given because certain sections, such as the Welcome modal dialog, the Tab Order list, and the images of text, do not respect high contrast mode settings. |
| 11.6.3 | Preservation of accessibility information in transformations | - | Supports | AEM Forms Designer preserves accessibility content specified by the user that is exported from the application. |
| 11.6.4 | Repair assistance | - | Supports | AEM Forms Designer provides prompts to users within normal use of the application as to when content would be created with a decreased level of accessibility. |
| 11.6.5 | Templates | - | Supports | Default templates for sample forms provide users with an accessible layout that can be customized. |
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 January 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.