Adobe Accessibility Conformance Report
VPAT® Version 2.3 – December 2018
Product Information
Name of Product/Version: Adobe Experience Manager 6.5 Forms Designer
Product Description: Designer is a point-and-click graphical form design tool that simplifies the creation of forms. Form recipients can fill a form online, submit the data, and print it, or print and fill the form by hand. You can design a form, define its logic, and modify it to match paper counterparts or to meet strict legislative requirements. Form developers can use Designer to create applications that generate dynamic, data-driven documents and produce customized business documents for print, web, or archival.
Date: January 2020
Contact information: access@adobe.com
Notes: The information contained in this report applies to the product itself. Information about product help and support documentation is located at: http://www.adobe.com/accessibility/compliance.html.
Evaluation Methods Used: Testing Adobe AEM Forms Designer involved extensive use of leading assistive technology, such as screen readers, screen magnifiers, and speech recognition software, as well exclusive use of the keyboard. Native platform accessibility features were also used to assist with testing. These were supplemented with techniques such as manual inspection of Accessibility API output.
Applicable Standards/Guidelines
This report covers the degree of conformance for the following accessibility standard/guidelines:
Standard/Guideline |
Included in Report |
Level A: Yes |
|
Yes |
|
Yes |
Terms
The terms used in the Conformance Level information are defined as follows:
- Supports: The functionality of the product has at least one method that meets the criterion without known defects or meets with equivalent facilitation.
- Partially Supports: Some functionality of the product does not meet the criterion.
- Does Not Support: The majority of product functionality does not meet the criterion.
- Not Applicable: The criterion is not relevant to the product.
- Not Evaluated: The product has not been evaluated against the criterion. This can be used only in WCAG 2.0 Level AAA.
WCAG 2.x Report
This section also documents conformance with:
- EN 301 549: Chapter 9 - Web, Chapter 10 - Non-Web documents, Section 11.2.1- Non-Web Software (excluding closed functionality), and Section 11.2.2 - Non-Web Software (closed functionality).
- Revised Section 508: Chapter 5 – 501.1 Scope, 504.2 Content Creation or Editing, and Chapter 6 – 602.3 Electronic Support Documentation.
Note: When reporting on conformance with the WCAG 2.x Success Criteria, they are scoped for full pages, complete processes, and accessibility-supported ways of using technology as documented in the WCAG 2.0 Conformance Requirements.
Guideline 1.1 Text Alternatives:
Provide text alternatives for any non-text content so that it can be changed into other forms people need, such as large print, braille, speech, symbols or simpler language.
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
1.1.1 Non-text Content (Level A)
Revised Section 508
|
Software: Supports PDF Output: 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. |
Guideline 1.2 Time-based Media:
Provide alternatives for time-based media.
Criteria |
Conformance Level |
Remarks and Explanations |
|
---|---|---|---|
1.2.1 Audio-only and Video-only (Prerecorded) (Level A)
Revised Section 508
|
Software: Supports PDF Output: 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) (Level A)
Revised Section 508
|
Software: Supports PDF Output: 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) (Level A)
Revised Section 508
|
|
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) (Level AA)
Revised Section 508
|
Software: Supports PDF Output: 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) (Level AA)
Revised Section 508
|
Software: Supports PDF Output: Supports |
Software: AEM Forms Designer does not include prerecorded video content. PDF Output: AEM Forms Designer output does not include prerecorded video content. |
Guideline 1.3 Adaptable:
Create content that can be presented in different ways (for example simpler layout) without losing information or structure.
Criteria |
Conformance Level |
Remarks and Explanations |
|
---|---|---|---|
1.3.1 Info and Relationships (Level A)
Revised Section 508
|
Software: Partially Supports PDF Output: 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 (Level A)
Revised Section 508
|
Software: Supports PDF Output: 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 (Level A)
Revised Section 508
|
|
Software: The AEM Forms Designer uses programmatic methods, such as tree structures within the hierarchy pane, to expose parent-child relationships, rather than rely on visual location to imply meaning. Shape, size, and orientation are not used to imply meaning. PDF Output: PDF output can be generated in a fashion so that sensory characteristics are not used as the sole means of conveying information. |
Guideline 1.4 Distinguishable:
Make it easier for users to see and hear content including separating foreground from background.
Criteria |
Conformance Level |
Remarks and Explanations |
||
---|---|---|---|---|
1.4.1 Use of Color (Level A)
Revised Section 508
|
|
|
||
1.4.2 Audio Control (Level A)
Revised Section 508
|
Software: Supports PDF Output: 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) (Level AA)
Revised Section 508
|
Software: Partially Supports PDF Output: 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 (Level AA)
Revised Section 508
|
Software: Partially Supports PDF Output: 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 (Level AA)
Revised Section 508
|
Software: Supports PDF Output: Supports |
|
Guideline 2.1 Keyboard Accessible:
Make all functionality available from a keyboard.
Criteria |
Conformance Level |
Remarks and Explanations |
|
---|---|---|---|
2.1.1 Keyboard (Level A)
Revised Section 508
|
|
Software: User interface controls and functions in AEM Forms Designer can be executed via the keyboard, but a rating of Partially Supports has been given because the Signature Settings button and dialog, Inline hyperlinked text in palettes, and "Corners" controls in Border panel cannot be executed via the keyboard. PDF Output: Content within the PDF output can be accessed through the use of the keyboard. |
|
2.1.2 No Keyboard Trap (Level A)
Revised Section 508
|
|
Software: AEM Forms Designer does not have controls which trap keyboard focus. PDF Output: PDF content generated within AEM Forms Designer does not contain keyboard traps. |
Guideline 2.2 Enough Time:
Provide users enough time to read and use content.
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
2.2.1 Timing Adjustable (Level A)
Revised Section 508
|
Software: Supports PDF Output: 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.2.2 Pause, Stop, Hide (Level A)
Revised Section 508
|
Software: AEM Forms Designer does not have time limits. PDF Output: PDF content output by AEM Forms Designer does not present users with timeouts. |
Software: AEM Forms Designer does not include elements which move, blink, scroll or auto-update. PDF Output: Content creators are able to design forms within AEM Forms Designer that do not have animation. Additionally, no content within forms auto-updates. |
Guideline 2.3 Seizures:
Do not design content in a way that is known to cause seizures.
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
2.3.1 Three Flashes or Below Threshold (Level A)
Revised Section 508
|
Software: Supports PDF Output: 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. |
Guideline 2.4 Navigable:
Provide ways to help users navigate, find content, and determine where they are.
Criteria |
Conformance Level |
Remarks and Explanations |
|
---|---|---|---|
2.4.1 Bypass Blocks (Level A)
Revised Section 508
|
Software: Supports PDF Output: Supports |
Software: Does not apply. PDF Output: PDF Forms do not contain blocks of repeated content unless specifically designed. |
|
2.4.2 Page Titled (Level A)
Revised Section 508
|
Software: Supports PDF Output: 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 (Level A)
Revised Section 508
|
Software: Supports PDF Output: 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) (Level A)
Revised Section 508
|
Software: Supports PDF Output: 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 (Level AA)
Revised Section 508
|
|
Software: Does not apply. PDF Output: Output generated by AEM Forms Designer will not have multiple pages that are not sequential. |
|
2.4.6 Headings and Labels (Level AA)
Revised Section 508
|
Software: Supports PDF Output: 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 (Level AA)
Revised Section 508
|
Software: Supports PDF Output: Supports |
|
Guideline 3.1 Readable:
Make text content readable and understandable.
Criteria |
Conformance Level |
Remarks and Explanations |
|
---|---|---|---|
3.1.1 Language of Page (Level A)
Revised Section 508
|
Software: Supports PDF Output: Supports |
|
|
3.1.2 Language of Parts (Level AA)
Revised Section 508
|
Software: Does Not Support PDF Output: Supports |
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. |
Guideline 3.2 Predictable:
Make Web pages appear and operate in predictable ways.
Criteria |
Conformance Level |
Remarks and Explanations |
|
---|---|---|---|
3.2.1 On Focus (Level A)
Revised Section 508
|
|
Software: The vast majority of content within AEM Forms Designer does not institute a change of context on focus. A rating of Partially Supports was given because of the tips and hints. By default, tip modals will display when a user navigates to content related to the tip dialog. AEM Forms Designer allows users to select to never show these dialogs again. PDF Output: Content creators can design forms in such a way that no content changes on user focus. |
|
3.2.2 On Input (Level A)
Revised Section 508
|
Software: Partially Supports PDF Output: 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 (Level AA)
Revised Section 508
|
Software: Supports PDF Output: 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 (Level AA)
Revised Section 508
|
Software: Supports PDF Output: Supports |
Software: Does not apply. PDF Output: Repeated components within PDF output can be designed by content creators so that they are consistently identified. |
Guideline 3.3 Input Assistance:
Help users avoid and correct mistakes.
Criteria |
Conformance Level |
Remarks and Explanations |
|
---|---|---|---|
3.3.1 Error Identification (Level A)
Revised Section 508
|
Software: Supports PDF Output: Supports |
|
|
3.3.2 Labels or Instructions (Level A)
Revised Section 508
|
Software: Supports PDF Output: Supports |
|
|
3.3.3 Error Suggestion (Level AA)
Revised Section 508
|
Software: Supports PDF Output: 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) (Level AA)
Revised Section 508
|
Software: Supports PDF Output: 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. |
Guideline 4.1 Compatible:
Maximize compatibility with current and future user agents, including assistive technologies.
Criteria |
Conformance Level |
Remarks and Explanations |
||
---|---|---|---|---|
4.1.1 Parsing (Level A)
Revised Section 508
|
|
|
||
4.1.2 Name, Role, Value (Level A)
Revised Section 508
|
Software: Partially Supports PDF Output: 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. |
Criteria |
Conformance Level |
Remarks and Explanations |
||
---|---|---|---|---|
302.1 Without Vision |
Software: Partially Supports PDF Output: 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. |
||
302.2 With Limited Vision |
Software: Partially Supports PDF Output: 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. |
||
302.4 Without Hearing |
|
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. |
||
302.5 With Limited Hearing |
Software: Supports PDF Output: 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. |
||
302.6 Without Speech |
|
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. |
||
302.7 With Limited Manipulation |
Software: Partially Supports PDF Output: Supports |
Software: The 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 Forms Designer can be authored so that fine motor control or simultaneous manual operation is not required. |
||
302.8 With Limited Reach and Strength |
Software: Partially Supports PDF Output: Supports |
|
||
302.9 With Limited Language, Cognitive, and Learning Abilities |
Software: Supports PDF Output: 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. |
Chapter 4: Hardware
Notes: Not Applicable
Chapter 5: Software
Notes:
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
501.1 Scope – Incorporation of WCAG 2.0 AA |
See WCAG 2.x section |
See information in WCAG section. |
502 Interoperability with Assistive Technology
502.1 General. Software shall interoperate with assistive technology and shall conform to 502.
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
502.2 Documented Accessibility Features |
See 502.2.1-502.2.2 |
Not applicable. |
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 Accessibility Services |
See 502.3.1-502.3.14 |
Not applicable. |
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. |
502.4 Platform Accessibility Features |
Not Applicable |
AEM Forms Designer is neither a platform, not platform software. |
503 Applications
503.1 General. Applications shall conform to 503.
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
503.2 User Preferences |
Partially Supports |
AEM Forms Designer allows user preferences for focus cursor and font size to inherit from platform settings. However, a rating of Partially Supports has been given because as noted in 502.2.2, certain areas of AEM Forms Designer do not support user’s high contrast mode. |
503.3 Alternative User Interfaces |
Not Applicable |
AEM Forms Designer does not provide an alternative user interface that functions as assistive technology. |
503.4 User Controls for Captions and Audio Description |
See 503.4.1-503.4.2 |
Not applicable. |
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 Authoring Tools
504.1 General. Where an application is an authoring tool, the application shall conform to 504 to the extent that information required for accessibility is supported by the destination format.
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
504.2 Content Creation or Editing (if not authoring tool, enter “not applicable”) |
See WCAG 2.0 section |
See information in the WCAG section |
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. |
504.3 Prompts |
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. |
504.4 Templates |
Supports |
Default templates for sample forms provide users with an accessible layout that can be customized. |
Chapter 6: Support Documentation and Services
Notes: Information regarding Support Documentation and Services is available in the Accessibility Conformance Report for the Adobe Help Center.
EN 301 549 Report
Notes:
Chapter 4: Functional Performance Statements (FPS)
Notes:
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
4.2.1 Usage without vision |
Software: Partially Supports PDF Output: 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 |
Software: Partially Supports PDF Output: 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 |
Software: Supports PDF Output: 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 |
Software: Supports PDF Output: 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 |
Software: Supports PDF Output: 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 |
Software: Supports PDF Output: 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 |
Software: Partially Supports PDF Output: 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 Forms Designer can be authored so that fine motor control, strength, or simultaneous manual operation is not required. |
4.2.8 Usage with limited reach |
Software: Partially Supports PDF Output: 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 |
Software: Supports PDF Output: 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 |
Software: Supports PDF Output: 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 |
Software: Supports PDF Output: 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. |
Chapter 5: Generic Requirements
Notes:
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
5.1 Closed functionality |
Not Applicable |
5.1.2.2-5.1.6.2 are not applicable for this product. AEM Forms Designer has no closed functionality. |
5.2 Activation of accessibility features |
Not Applicable |
AEM Forms Designer relies upon platform accessibility features. |
5.3 Biometrics |
Not Applicable |
AEM Forms Designer does not utilize biometrics. |
5.4 Preservation of accessibility information during conversion |
Supports |
AEM Forms Designer supports accessibility features when documents are exported from the application. |
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. |
5.7 Key repeat |
Not Applicable |
AEM Forms Designer has no locking or toggle controls. |
5.8 Double-strike key acceptance |
Not Applicable |
AEM Forms Designer has no locking or toggle controls. |
5.9 Simultaneous user actions |
Not Applicable |
AEM Forms Designer has no locking or toggle controls. |
Chapter 6: ICT with Two-Way Voice Communication
Notes: Not Applicable
Chapter 7: ICT with Video Capabilities
Notes:
Chapter 8: Hardware
Notes: Not Applicable
Chapter 9: Web (see WCAG 2.x section)
Notes:
Chapter 10: Non-web Documents
Notes:
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
10.2.1 - 10.2.38 |
See WCAG 2.x section |
See information in WCAG section. |
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. |
Chapter 11: Software
Notes:
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
11.2.1 Software success criteria (excluding closed functionality) |
See WCAG 2.x section |
See information in WCAG section |
11.2.2 Software success criteria (closed functionality) |
See WCAG 2.x section |
See information in WCAG section |
11.3.2.3 Use of accessibility services |
Supports |
AEM Forms Designer uses the native Windows accessibility APIs to expose content to assistive technologies. |
11.3.2.4 Assistive technology |
Not Applicable |
AEM Forms Designer is not assistive technology. |
11.3.2.5 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, the New Form button on the Welcome screen, color pickers in application dialog boxes, and palette names are not available. |
11.3.2.6 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. |
11.3.2.7 Values |
Supports |
Values for controls are able to be programmatically determined by assistive technologies. |
11.3.2.8 Label relationships |
Supports |
Label relationships between components are programmatically available to users. |
11.3.2.9 Parent-child 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. |
11.3.2.10 Text |
Supports |
AEM Forms Designer exposes text content programmatically. |
11.3.2.11 List of available actions |
Partially Supports |
The 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, identifying the number of actions available. |
11.3.2.12 Execution of available actions |
Supports |
AEM Forms Designer allows assistive technology to programmatically execute available programmatic actions. |
11.3.2.13 Tracking of focus and selection attributes |
Supports |
As noted within 2.4.7 Focus Visible, AEM Forms Designer provides a visual indication of keyboard focus. |
11.3.2.14 Modification of focus and selection attributes |
Partially Supports |
As noted within 2.1.1 Keyboard, the 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. |
11.3.2.15 Change notification |
Supports |
Notifications, such as when spell checking is not supported, are made programmatically available to screen reader users. |
11.3.2.16 Modifications of states and properties |
Supports |
States and properties of controls within AEM Forms Designer are capable of being programmatically updated. |
11.3.2.17 Modifications of values and text |
Supports |
Values and text that can be set and edited by users can be set programmatically within the User Interface. |
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.5 User preferences |
Partially Supports |
AEM Forms Designer allows user preferences for focus cursor and font size to inherit from platform settings. However, a rating of Partially Supports has been given because as noted in 502.2.2, certain areas of AEM Forms Designer do not support user’s high contrast mode. |
11.6.2 Accessible content creation (if not authoring tool, enter “not applicable”) |
See WCAG 2.x section |
See information in the WCAG section |
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. |
Chapter 12: Documentation and Support Services
Notes: Information regarding Support Documentation and Services is available in the Accessibility Conformance Report for the Adobe Help Center.
Chapter 13: ICT Providing Relay or Emergency Service Access
Notes: Not Applicable
Voluntary Product Accessibility Template® and VPAT® are a registered trademark of Information Technology Industry Council (ITI)