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: 8/5/2011
Name of Product: Adobe® Digital Enterprise Platform – Experience Services – Core v10.x
Contact for more Information: access@adobe.com
Summary Table
| Guideline | Applicable | Compliance |
|---|---|---|
Section 1194.21 - Software Applications and Operating Systems |
Applicable |
Supports with exceptions |
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 |
| Criteria | Supporting Features | Remarks and explanations |
|---|---|---|
(a) When software is designed to run on a system that has a keyboard, product functions shall be executable from a keyboard where the function itself or the result of performing a function can be discerned textually. |
Supports with Exceptions |
Most features and controls in ADEP Experience Services – Core are operable with the keyboard alone with some exceptions, including: It is not possible to navigate over UI elements in the browser-based development environment, using the keyboard alone. Working with the development environment requires the use of a mouse. Some admin interfaces are not operable without a mouse. |
(b) Applications shall not disrupt or disable activated features of other products that are identified as accessibility features, where those features are developed and documented according to industry standards. Applications also shall not disrupt or disable activated features of any operating system that are identified as accessibility features where the application programming interface for those accessibility features has been documented by the manufacturer of the operating system and is available to the product developer. |
Supports |
ADEP Experience Services – Core does not interfere with or deactivate accessibility features of the operating system. |
(c) A well-defined on-screen indication of the current focus shall be provided that moves among interactive interface elements as the input focus changes. The focus shall be programmatically exposed so that Assistive Technology can track focus and focus changes. |
Supports with exceptions |
There is a clear indication of current focus for most controls in the ADEP Experience Services – Core interface with some exceptions, including: Tab focus in grids, such as the user list in the User section, does not include a visual indicator. |
(d) Sufficient information about a user interface element including the identity, operation and state of the element shall be available to Assistive Technology. When an image represents a program element, the information conveyed by the image must also be available in text. |
Supports with exceptions |
Identity, role and state information is available for most controls in the ADEP Experience Services – Core interface with some exceptions including: Identity information is not available for icons on toolbars, such as the main toolbar. Information about the state, role and identity of editable regions in content is not available to assistive technology. |
(e) When bitmap images are used to identify controls, status indicators, or other programmatic elements, the meaning assigned to those images shall be consistent throughout an application's performance. |
Supports |
|
(f) Textual information shall be provided through operating system functions for displaying text. The minimum information that shall be made available is text content, text input caret location, and text attributes. |
Supports |
Textual information is provided to assistive technologies in most cases in the ADEP Experience Services – Core interface, with some exceptions, including: Text in some content objects in edit mode, such as data tables, does not provide sufficient information. |
(g) Applications shall not override user selected contrast and color selections and other individual display attributes. |
Supports with exceptions |
ADEP Experience Services – Core supports Windows High Contrast Mode in most panels and dialogs but some elements in the interface do not inherit user settings, including: Icons on tree controls, panels and toolbars, such as the main toolbar, are not visible with some schemes. Drop down menus, such as the New menu on the Websites toolbar, are not visible in High Contrast Mode. |
(h) When animation is displayed, the information shall be displayable in at least one non-animated presentation mode at the option of the user. |
Supports |
ADEP Experience Services – Core does not use animation in the user interface. |
(i) Color coding shall not be used as the only means of conveying information, indicating an action, prompting a response, or distinguishing a visual element. |
Supports with exceptions |
The ADEP Experience Services – Core interface does not use color as the only means of conveying information. |
(j) When a product permits a user to adjust color and contrast settings, a variety of color selections capable of producing a range of contrast levels shall be provided. |
Not applicable |
ADEP Experience Services – Core does not permit a user to adjust color and contrast settings in the user interface. |
(k) Software shall not use flashing or blinking text, objects, or other elements having a flash or blink frequency greater than 2 Hz and lower than 55 Hz. |
Supports |
ADEP Experience Services – Core does not include flashing or blinking text. |
(l) When electronic forms are used, 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 with exceptions |
Most form controls in the ADEP Experience Services – Core interface can be operated using assistive technology with some exceptions, including: Information about some form controls in toolbars, such as search inputs and buttons, is not available to assistive technologies. Some inputs, such as the text input in the development environment, trap keyboard focus and it is not possible to move focus to another element, such as the toolbar, using the keyboard alone. |
| 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 |
Images, such as icons on the main toolbar, or in the context menus in the development environment, do not include alternate text descriptions. |
(b) Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation. |
Not applicable |
The ADEP Experience Services – Core interface does not include multimedia. |
(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 |
The ADEP Experience Services – Core interface does not use color as the only means of conveying information. |
(d) Documents shall be organized so they are readable without requiring an associated style sheet. |
Supports with Exceptions |
The ADEP Experience Services – Core interface is not fully readable without associated style sheets. |
(e) Redundant text links shall be provided for each active region of a server-side image map. |
Not applicable |
The ADEP Experience Services – Core interface does not include 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 |
The ADEP Experience Services – Core interface does not include client-side image maps. |
(g) Row and column headers shall be identified for data tables. |
Supports with Exceptions |
Grids in the ADEP Experience Services – Core interface, such as the grid in the development environment, do only partially include table header information. |
(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. |
Does not support |
Grids in the ADEP Experience Services – Core interface, such as the Content Explorer property grid, do not include header information. |
(i) Frames shall be titled with text that facilitates frame identification and navigation |
Does not support |
Frames in the ADEP Experience Services – Core interface, do not include titles. |
(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 |
The ADEP Experience Services – Core interface does not cause the screen to flicker. |
(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 use ADEP Experience Services – Core without requiring a text alternative. |
(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. |
Supports with exceptions |
Some scripted controls do not include functional text equivalents. |
(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 Section 1194.21(a) through (l). |
Not applicable |
ADEP Experience Services – Core does not require plug-ins or applets. |
(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 with exceptions
|
Most form controls in the ADEP Experience Services – Core interface can be operated using assistive technology with some exceptions, including: Information about some form controls, such as search inputs and buttons, is not available to assistive technologies. |
(o) A method shall be provided that permits users to skip repetitive navigation links. |
Supports with exceptions |
ADEP Experience Services – Core does not include a method to skip repetitive navigation links. Collapsible controls, such as drop down menus and tree controls do help to reduce repetitive links and contain structural markup. |
(p) When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required. |
Not applicable |
ADEP Experience Services – Core does not require time-based 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. |
Does not support |
Most features and controls in the ADEP Experience Services – Core interface are operable with the keyboard alone. However, there are some exceptions including: It is not possible to select and activate many objects in grids, such as those in the content or administrative view, using the keyboard alone. Identity, role and state information is available for most controls in the ADEP Experience Services – Core interface with some exceptions including: Identity information is not available for icons on toolbars, such as the main toolbar. |
(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 |
ADEP Experience Services – Core supports the use of screen magnifiers. However, not all elements provide a clear visual indication of current focus and focus is not programmatically exposed in some cases, such as when the arrow keys are used to move through grids. |
(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. |
Supports |
|
(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 with exceptions |
Most operations and interface objects in ADEP Experience Services – Core do not require fine motor control. However, some advanced controls, such as tree menus, do include small icons and require fine levels of control. In some cases these can be operated using the keyboard but in others, such as the Permissions tree menu in the User section, they cannot. |
| Criteria | Supporting Features | Remarks and explanations |
|---|---|---|
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 Systems. |
