Adobe Accessibility Conformance Report
VPAT® Version 2.3 (Revised) – April 2019
Product Information
Name of Product/Version: Adobe ColdFusion 2018 Release (v13.0) API Manager
Product Description: API Manager is a full-featured API Management platform integrated with ColdFusion that enables one to create, test, debug, secure, monitor and monetize APIs.
Date: December 2019
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 ColdFusion API Manager 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 |
|
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
Tables 1 and 2 also document conformance with:
- EN 301 549: Chapter 9 - Web, Sections 10.1-10.4 of Chapter 10 - Non-Web documents, and Sections 11.1-11.4 and 11.8.2 of Chapter 11 - Non-Web Software (open and closed functionality), and Sections 12.1.2 and 12.2.4 of Chapter 12 – Documentation
- 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
|
Web: Does Not Support |
Web: The product does not provide sufficient text alternatives for most images, such as:
|
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
|
Web: Supports |
Web: The product does not contain prerecorded audio-only or video-only media. |
1.2.2 Captions (Prerecorded) (Level A)
Revised Section 508
|
Web: Supports |
Web: The product does not contain prerecorded synchronized media. |
1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A)
Revised Section 508
|
Web: Supports |
Web: The product does not contain prerecorded video content that would require audio description or a media alternative. |
1.2.4 Captions (Live) (Level AA)
Revised Section 508
|
Web: Supports |
Web: The product does not contain live synchronized media. |
1.2.5 Audio Description (Prerecorded) (Level AA)
Revised Section 508
|
Web: Supports |
Web: The product does not contain prerecorded video content that would require audio description. |
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
|
Web: Does Not Support |
Web: Some structure and relationship information, such as the table structure in the Key Stores page, is provided through element semantics. However, most structure and relationship information is not provided programmatically or in text, such as:
|
1.3.2 Meaningful Sequence (Level A)
Revised Section 508
|
Web: Supports |
Web: The product presents content in a meaningful sequence. |
1.3.3 Sensory Characteristics (Level A)
Revised Section 508
|
Web: Partially Supports |
Web: Some instructions do not rely solely on sensory characteristics. Exceptions include:
|
1.3.4 Orientation (Level AA 2.1 only)
Revised Section 508 – Does not apply |
Web: Supports |
Web: Content does not restrict its view and operation to a single display orientation. |
1.3.5 Identify Input Purpose (Level AA 2.1 only)
Revised Section 508 – Does not apply |
Web: Partially Supports |
Web: Most input fields in the product do not collect information about the user. However, some input fields collect information about the user and do not programmatically convey their purpose. Examples include:
|
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
|
Web: Partially Supports |
Web: Color is not used as the only visual means of conveying information for some content. Exceptions include:
|
1.4.2 Audio Control (Level A)
Revised Section 508
|
Web: Supports |
Web: The product does not contain audio that plays automatically. |
1.4.3 Contrast (Minimum) (Level AA)
Revised Section 508
|
Web: Partially Supports |
Web: Most text meets minimum contrast requirements. Exceptions include:
|
1.4.4 Resize text (Level AA)
Revised Section 508
|
Web: Does Not Support |
Web: The product does not provide its own text resizing function. When text is resized using browser zoom, content and functionality is lost in most product functions. Examples include:
|
1.4.5 Images of Text (Level AA)
Revised Section 508
|
Web: Partially Supports |
Web: Text is used to convey information rather than images of text for some content. Exceptions include:
|
1.4.10 Reflow (Level AA 2.1 only)
Revised Section 508 – Does not apply |
Web: Supports |
Web: Content reflows appropriately. |
1.4.11 Non-text Contrast (Level AA 2.1 only)
Revised Section 508 – Does not apply |
Web: Supports |
Web: At the required width of 320 CSS pixels, content is presented without loss of information or functionality, and without requiring scrolling in two dimensions. |
1.4.12 Text Spacing (Level AA 2.1 only)
Revised Section 508 – Does not apply |
Web: Supports |
Web: The product supports the required text style properties without loss of content or functionality. |
1.4.13 Content on Hover or Focus (Level AA 2.1 only)
Revised Section 508 – Does not apply |
Web: Supports |
Web: Authored content does not contain content elements triggered by hover or focus. |
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
|
Web: Does Not Support |
Web: Most product functionality cannot be operated through a keyboard interface. Examples include:
|
2.1.2 No Keyboard Trap (Level A)
Revised Section 508
|
Web: Supports |
Web: The product does not include keyboard traps. |
2.1.4 Character Key Shortcuts (Level A 2.1 only)
Revised Section 508 – Does not apply |
Web: Supports |
Web: The product does not provide character key shortcuts. |
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
|
Web: Partially Supports |
Web: Most content do not require timed responses. Exceptions include:
|
2.2.2 Pause, Stop, Hide (Level A)
Revised Section 508
|
Web: Supports |
Web: The product does not include elements which move, blink, scroll, or auto-update. |
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
|
Web: Supports |
Web: The product does not contain flashing content. |
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
|
Web: Does Not Support |
Web: The product does not provide a mechanism to bypass repeated heading and navigation content. |
2.4.2 Page Titled (Level A)
Revised Section 508
|
Web: Does Not Support |
Web: While the page titles within publisher login page and the analytics portion of the product are context-specific, the titles of most pages do not describe their purpose. Examples include:
|
2.4.3 Focus Order (Level A)
Revised Section 508
|
Web: Supports |
Web: Components receive focus in a meaningful order. |
2.4.4 Link Purpose (In Context) (Level A)
Revised Section 508
|
Web: Supports |
Web: The purpose of links in the product can be determined from the link text alone or from the programmatic context of the link. |
2.4.5 Multiple Ways (Level AA)
Revised Section 508
|
Web: Supports |
Web: Users can locate web pages in the product through the primary navigation, which serves as a site map for the product. |
2.4.6 Headings and Labels (Level AA)
Revised Section 508
|
Web: Supports |
Web: Headings and labels are descriptive. |
2.4.7 Focus Visible (Level AA)
Revised Section 508
|
Web: Partially Supports |
Web: Most focusable elements have a visible keyboard focus indicator. Exceptions include:
|
Guideline 2.5 Input Modalities:
Make it easier for users to operate functionality through various inputs beyond keyboard.
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
2.5.1 Pointer Gestures (Level A 2.1 only)
Revised Section 508 – Does not apply |
Web: Supports |
Web: The product does not rely on multipoint or path-based gestures. |
2.5.2 Pointer Cancellation (Level A 2.1 only)
Revised Section 508 – Does not apply |
Web: Supports |
Web: Product functions that use a single pointer are completed when the user releases the pointer. |
2.5.3 Label in Name (Level A 2.1 only)
Revised Section 508 – Does not apply |
Web: Supports |
Web: The accessible names of controls contain the text of their visible labels. |
2.5.4 Motion Actuation (Level A 2.1 only)
Revised Section 508 – Does not apply |
Web: Supports |
Web: The product does not have functionality operated by device motion or user motion. |
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
|
Web: Does Not Support |
Web: The language of pages cannot be programmatically determined. |
3.1.2 Language of Parts (Level AA)
Revised Section 508
|
Web: Supports |
Web: Content is only presented in one language at a time. |
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
|
Web: Supports |
Web: Components do not initiate a change of context when focused. |
3.2.2 On Input (Level A)
Revised Section 508
|
Web: Supports |
Web: Changes of context that occur automatically on user input are clearly indicated to the user before invoking them. |
3.2.3 Consistent Navigation (Level AA)
Revised Section 508
|
Web: Supports |
Web: When navigational mechanisms are repeated in the product, such as the Admin and Publisher navigation menus, they occur in a consistent relative order. |
3.2.4 Consistent Identification (Level AA)
Revised Section 508
|
Web: Supports |
Web: Components with the same functionality are identified consistently. |
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
|
Web: Supports |
Web: Where input errors are automatically detected, such as when logging in, items in error are identified and error messages are provided as text. |
3.3.2 Labels or Instructions (Level A)
Revised Section 508
|
Web: Supports |
Web: Labels are provided for input fields. |
3.3.3 Error Suggestion (Level AA)
Revised Section 508
|
Web: Supports |
Web: Where input errors are automatically detected, such as when entering in port numbers or URLs, suggestions for correction are provided to the user. |
3.3.4 Error Prevention (Legal, Financial, Data) (Level AA)
Revised Section 508
|
Web: Supports |
Web: The product does not process legal commitments or financial transactions. Changes to user-controllable data are reversible or can be confirmed before finalizing. |
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
|
Web: Partially Supports |
Web: In most product functions, elements have complete start and end tags, elements are nested according to their specifications, elements do not contain duplicate attributes, and any IDs are unique. Exceptions include:
|
4.1.2 Name, Role, Value (Level A)
Revised Section 508
|
Web: Does Not Support |
Web: User interface components in most product functions do not provide programmatic name, role, or value information. Examples include:
|
4.1.3 Status Messages (Level AA 2.1 only)
Revised Section 508 – Does not apply |
Web: Partially Supports |
Web: Most status updates that do not receive focus, such as those in the Publisher portion of the product, provide the update to assistive technology as a live region. However, the status updates within the Admin portion of the product do not provide these updates to assistive technology. |
Revised Section 508 Report
Notes:
Chapter 3: Functional Performance Criteria (FPC)
Notes: This table documents instances of equivalent facilitation or instances of functions not addressed by technical requirements. Responses which cite technical requirements are informative only.
Criteria |
Conformance Level |
Remarks and Explanations |
|
---|---|---|---|
302.1 Without Vision |
Web: Does Not Support |
Web: Most functions of the product are not usable without vision. Examples include:
|
|
302.2 With Limited Vision |
Web: Does Not Support |
Software or Web: The product allows users to reflow and adjust the type of text displayed. However, most functions of the product will not be usable with limited vision. Examples include:
|
|
|
Web: Partially Supports |
Web: Most functions of the product are usable without perception of color. Exceptions include:
|
|
302.4 Without Hearing |
Web: Supports |
Web: The product does not require the use of hearing. |
|
302.5 With Limited Hearing |
Web: Supports |
Web: The product does not require the use of hearing. |
|
302.6 Without Speech |
Web: Supports |
Web: The product does not require the use of speech. |
|
302.7 With Limited Manipulation |
Web: Does Not Support |
Software or Web: Most functions of the product are not usable with limited manipulation. Examples include:
|
|
302.8 With Limited Reach and Strength |
Web: Supports |
Web: The product is functional with limited reach and strength. |
|
302.9 With Limited Language, Cognitive, and Learning Abilities |
Web: Supports |
Software or Web: The product is functional for users with limited language, cognitive, and learning abilities. Users with cognitive disabilities have varying needs for features that allow them to adapt content and work with assistive technology or accessibility features of the platform. The product provides icons along with most button text for users who do not speak English. |
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 |
Web: Does Not Support |
Web: Most functions of the product are not usable without vision. Examples include:
|
4.2.2 Usage with limited vision |
Web: Does Not Support |
Web: The product allows users to reflow and adjust the type of text displayed. However, most functions of the product will not be usable with limited vision. Examples include:
|
4.2.3 Usage without perception of colour |
Web: Partially Supports |
Web: Most functions of the product are usable without perception of color. Exceptions include: |
4.2.4 Usage without hearing |
Web: Supports |
Web: The product does not require the use of hearing. |
4.2.5 Usage with limited hearing |
Web: Supports |
Web: The product does not require the use of hearing. |
4.2.6 Usage without vocal capability |
Web: Supports |
Web: The product does not require the use of speech. |
4.2.7 Usage with limited manipulation or strength |
Web: Does Not Support |
Web: Most functions of the product are not usable with limited manipulation or strength. Examples include:
|
4.2.8 Usage with limited reach |
Web: Supports |
Web: The product is functional with limited reach. |
4.2.9 Minimize photosensitive seizure triggers |
Web: Supports |
Web: The product does not contain flashing content. |
4.2.10 Usage with limited cognition |
Web: Supports |
Web: The product is functional for users with limited language, cognitive, and learning abilities. Users with cognitive disabilities have varying needs for features that allow them to adapt content and work with assistive technology or accessibility features of the platform. The product provides icons along with most button text for users who do not speak English. |
4.2.11 Privacy |
Web: Supports |
Web: The product maintains user privacy when accessibility features are used. Examples include:
|
Chapter 5: Generic Requirements
Notes:
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
5.1 Closed Functionality |
Not Applicable |
The product does not have closed functionality. |
5.2 Activation of accessibility features |
Not Applicable |
The product does not have specific documented accessibility features. The product instead relies upon platform accessibility features. |
5.3 Biometrics |
Not Applicable |
The product does not use biological characteristics for user identification or for control of the product. |
5.4 Preservation of accessibility information during conversion |
Not Applicable |
The product is not an authoring tool. |
5.5.1 Means of operation |
Not Applicable |
The product has only non-mechanical operable parts, such as on-screen buttons, which do not require grasping, pinching, or twisting of the wrist to operate. |
5.5.2 Operable parts discernibility |
Does Not Support |
The product has only non-mechanical operable parts, such as on-screen buttons. As noted in 4.1.2 Name, Role, Value, most operable parts lack an accessible name which would enable them to be discernible without user vision. |
5.6.1 Tactile or auditory status |
Not Applicable |
The product does not have locking or toggle controls. |
5.6.2 Visual status |
Not Applicable |
The product does not have locking or toggle controls. |
5.7 Key repeat |
Not Applicable |
The product relies on platform software to turn off or adjust key repeat. |
5.8 Double-strike key acceptance |
Not Applicable |
The product does not provide a keyboard or keypad. |
5.9 Simultaneous user actions |
Supports |
The product relies on platform software features, such as Sticky Keys, to ensure simultaneous user actions are not required. |
Chapter 6: ICT with Two-Way Voice Communication
Notes: Not Applicable
Chapter 7: ICT with Video Capabilities
Notes: Not Applicable
Chapter 8: Hardware
Notes: Not Applicable
Chapter 9: Web (see WCAG 2.x section)
Notes:
Chapter 10: Non-web Software
Notes: Not Applicable
Chapter 11: Software
Notes:
Criteria |
Conformance Level |
Remarks and Explanations |
|
---|---|---|---|
11.1.1.1 through 11.4.1.3 |
See WCAG 2.x section |
See information in WCAG 2.x section |
|
11.5.2.1 Platform accessibility service support for software that provides a user interface |
See 11.5.2.5 through 11.5.2.17 |
See information in 11.5.2.5 through 11.5.2.17 |
|
11.5.2.2 Platform accessibility service support for assistive technologies |
See 11.5.2.5 through 11.5.2.17 |
See information in 11.5.2.5 through 11.5.2.17 |
|
11.5.2.3 Use of accessibility services |
See 11.5.2.5 through 11.5.2.17. |
See information in 11.5.2.5 through 11.5.2.17 |
|
11.5.2.4 Assistive technology |
Not Applicable |
Not applicable to web. |
|
11.5.2.5 Object information |
Not Applicable |
Not applicable to web. |
|
11.5.2.6 Row, column, and headers |
Not Applicable |
Not applicable to web. |
|
11.5.2.7 Values |
Not Applicable |
Not applicable to web. |
|
11.5.2.8 Label relationships |
Not Applicable |
Not applicable to web. |
|
11.5.2.9 Parent-child relationships |
Not Applicable |
Not applicable to web. |
|
11.5.2.10 Text |
Not Applicable |
Not applicable to web. |
|
11.5.2.11 List of available actions |
Not Applicable |
Not applicable to web. |
|
|
Not Applicable |
Not applicable to web. |
|
11.5.2.13 Tracking of focus and selection attributes |
Not Applicable |
Not applicable to web. |
|
11.5.2.14 Modification of focus and selection attributes |
Not Applicable |
Not applicable to web. |
|
11.5.2.15 Change notification |
Not Applicable |
Not applicable to web. |
|
11.5.2.16 Modifications of states and properties |
Not Applicable |
Not applicable to web. |
|
11.5.2.17 Modifications of values and text |
Not Applicable |
Not applicable to web. |
|
11.6.1 User control of accessibility features |
Not Applicable |
The product is not platform software. |
|
11.6.2 No disruption of accessibility features |
Supports |
The product does not disrupt platform accessibility features. |
|
11.7 User preferences |
Not Applicable |
Web pages are isolated from their underlying platform. |
|
11.8.2 Accessible content creation |
Not Applicable |
The product is not an authoring tool. |
|
11.8.3 Preservation of accessibility information in transformations |
Not Applicable |
The product is not an authoring tool. |
|
11.8.4 Repair assistance |
Not Applicable |
The product is not an authoring tool. |
|
11.8.5 Templates |
Not Applicable |
The product is not an authoring tool. |
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)