The purpose of the Voluntary Product Accessibility Template is to assist Federal contracting officials in making preliminary assessments regarding the availability of commercial Electronic and Information Technology products and services with features that support accessibility. It is assumed that offerers will provide additional contact information to facilitate more detailed inquiries.
The first table of the Template provides a summary view of the section 508 Standards. The subsequent tables provide more detailed views of each subsection. There are three columns in each table. Column one of the Summary Table describes the subsections of subparts B and C of the Standards. The second column describes the supporting features of the product or refers you to the corresponding detailed table, "e.g., equivalent facilitation." The third column contains any additional remarks and explanations regarding the product. In the subsequent tables, the first column contains the lettered paragraphs of the subsections. The second column describes the supporting features of the product with regard to that paragraph. The third column contains any additional remarks and explanations regarding the product.
Date: April 21, 2016
Name of product: Adobe® Experience Manager (AEM) 6.2 Forms - PDF Generator
Contact for more information: access@adobe.com
Summary
Guideline |
Applicable |
Compliance |
|
Section 1194.21 – Software Applications and Operating Systems |
Applicable |
See AEM Forms Server Administration VPAT |
|
Section 1194.22 – Web-based Intranet and Internet Information and Systems |
Applicable |
Supports with Exceptions |
|
Section 1194.23 – Telecommunications Products |
Not Applicable |
— |
|
Section 1194.24 – Video and Multimedia Products |
Not Applicable |
— |
|
Section 1194.25 – Self-Contained, Closed Products |
Not Applicable |
— |
|
Section 1194.26 – Desktop and Portable Computers |
Not Applicable |
— |
|
Section 1194.31 – Functional Performance Criteria |
Applicable |
Supports with Exceptions |
|
Section 1194.41 – Information, Documentation, Support |
Applicable |
Supports |
|
Applicable, see the Livecycle Server Administration VPAT |
Criteria |
Supporting features |
Remarks and explanations |
|
(a) A text equivalent for every non-text element shall be provided (e.g., via "alt", "longdesc", or in element content). |
Supports with Exceptions |
In most cases PDF documents created using AEM Forms PDF Generator can include alternate text descriptions for non-text elements with some exceptions including documents converted from HTML pages and some other formats, including some Open Office documents. |
|
(b) Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation. |
Not Applicable |
AEM Forms PDF Generator does not utilize multimedia presentations. |
|
(c) Web pages shall be designed so that all information conveyed with color is also available without color, for example from context or markup. |
Supports |
It is possible for authors to meet this requirement with AEM Forms PDF Generator but they must check their source documents to ensure compliance. |
|
(d) Documents shall be organized so they are readable without requiring an associated style sheet. |
Not Applicable |
PDF documents do not use style sheets. |
|
(e) Redundant text links shall be provided for each active region of a server-side image map. |
Not Applicable |
AEM Forms PDF Generator does not generate server-side image maps. |
|
(f) Client-side image maps shall be provided instead of server-side image maps except where the regions cannot be defined with an available geometric shape. |
Not Applicable |
AEM Forms PDF Generator does not generate client-side image maps. |
|
(g) Row and column headers shall be identified for data tables. |
Supports |
PDF documents created with AEM Forms PDF Generator can include programmatically identifiable row and column headers for data tables. |
|
(h) Markup shall be used to associate data cells and header cells for data tables that have two or more logical levels of row or column headers. |
Supports through equivalent facilitation |
Nested table headers are not supported in AEM Forms PDF Generator output but users can add these headers in Acrobat Professional after conversion. |
|
(i) Frames shall be titled with text that facilitates frame identification and navigation |
Not Applicable |
Documents created using AEM Forms PDF Generator do not contain frames. |
|
(j) Pages shall be designed to avoid causing the screen to flicker with a frequency greater than 2 Hz and lower than 55 Hz. |
Supports |
Documents created using AEM Forms PDF Generator do not use flashing or blinking text, objects, or other elements in the user interface. |
|
(k) A text-only page, with equivalent information or functionality, shall be provided to make a web site comply with the provisions of this part, when compliance cannot be accomplished in any other way. The content of the text-only page shall be updated whenever the primary page changes. |
Not Applicable |
It should be possible to create an accessible version of a document using AEM Forms PDF Generator. |
|
(l) When pages utilize scripting languages to display content, or to create interface elements, the information provided by the script shall be identified with functional text that can be read by Assistive Technology. |
Not Applicable |
Documents created using AEM Forms PDF Generator do not contain scripting. . |
|
(m) When a web page requires that an applet, plug-in or other application be present on the client system to interpret page content, the page must provide a link to a plug-in or applet that complies with §1194.21(a) through (l). |
Supports |
It is possible for authors to provide links to plug-ins wherever documents created using AEM Forms PDF Generator are provided. |
|
(n) When electronic forms are designed to be completed on-line, the form shall allow people using Assistive Technology to access the information, field elements, and functionality required for completion and submission of the form, including all directions and cues. |
Supports |
Forms in documents created using AEM Forms PDF Generator can include identity, role and state information that is available to Assistive Technology. These forms can be fully operable using a keyboard alone. However, successful conversion of all of these attributes depends on the format and structure of the source document. Forms that have been generated from insufficiently prepared source files may need additional modification using either Adobe Acrobat Professional or AEM Forms Designer to ensure compliance. |
|
(o) A method shall be provided that permits users to skip repetitive navigation links. |
Supports |
In general, documents created using PDF generator do not contain repetitive navigation links. Authors can use structural tags, such as headings, lists and tables that can be utilized by Assistive Technology to skip over repetitive blocks of content. |
|
(p) When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required. |
Not Applicable |
Documents created using AEM Forms PDF Generator do not require timed responses. |
Note to 1194.22: The Board interprets paragraphs (a) through (k) of this section as consistent with the following Priority 1 checkpoints of the Web Content Accessibility Guidelines 1.0 (WCAG 1.0) (May 5, 1999) published by the Web Accessibility Initiative of the World Wide Web Consortium: Paragraph (a) – 1.1, (b) – 1.4, (c) – 2.1, (d) – 6.1, (e) – 1.2, (f) – 9.1, (g) – 5.1, (h) – 5.2, (i) – 12.1, (j) – 7.1, (k) – 11.4.
Criteria |
Supporting features |
Remarks and explanations |
|
(a) At least one mode of operation and information retrieval that does not require user vision shall be provided, or support for Assistive Technology used by people who are blind or visually impaired shall be provided. |
Supports |
Most accessibility attributes in source documents can be converted to attributes that work with screen readers in Acrobat with AEM Forms PDF Generator. For example, header elements in HTML pages can be converted to header tags in PDF documents. In most cases PDF documents created using AEM Forms PDF Generator can include alternate text descriptions for non-text elements with some exceptions including documents converted from HTML pages and some other formats, including some Open Office documents. Forms in documents created using AEM Forms PDF Generator can include identity, role and state information that is available to Assistive Technology. These forms can be fully operable using a keyboard alone. However, successful conversion of all of these attributes depends on the format and structure of the source document. Forms may need further tagging in Acrobat Professional to ensure compliance. |
|
(b) At least one mode of operation and information retrieval that does not require visual acuity greater than 20/70 shall be provided in audio and enlarged print output working together or independently, or support for Assistive Technology used by people who are visually impaired shall be provided. |
Supports with Exceptions |
Authors can ensure they meet this requirement with documents converted using AEM Forms PDF Generator. However, in some cases read order may not be converted correctly and the Acrobat Reflow function may not work correctly as a result. |
|
(c) At least one mode of operation and information retrieval that does not require user hearing shall be provided, or support for Assistive Technology used by people who are deaf or hard of hearing shall be provided |
Supports |
|
|
(d) Where audio information is important for the use of a product, at least one mode of operation and information retrieval shall be provided in an enhanced auditory fashion, or support for assistive hearing devices shall be provided. |
Not Applicable |
|
|
(e) At least one mode of operation and information retrieval that does not require user speech shall be provided, or support for Assistive Technology used by people with disabilities shall be provided. |
Not Applicable |
|
|
(f) At least one mode of operation and information retrieval that does not require fine motor control or simultaneous actions and that is operable with limited reach and strength shall be provided. |
Supports |
|
Criteria |
Supporting features |
Remarks and explanations |
|
(a) Product support documentation provided to end-users shall be made available in alternate formats upon request, at no additional charge. |
Supports |
Adobe provides electronic versions of all product support documentation. |
|
(b) End-users shall have access to a description of the accessibility and compatibility features of products in alternate formats or alternate methods upon request, at no additional charge. |
Supports |
Adobe provides information on accessibility features in the documentation. Electronic versions of all product support documentation are provided. |
|
(c) Support services for products shall accommodate the communication needs of end-users with disabilities. |
Supports |
Product support for Adobe products is available in a variety of formats and from a number of online sources available from Adobe. |