ColdFusion API Manager 2021
Accessibility Conformance Report published by Adobe
Partial extraction. We read 30 of 31 Level A and 20 of 24 Level AA criteria from this document (91% 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 — 30 criteria
- Supports
- 19
- Partially supports
- 4
- Does not support
- 7
- Not applicable
- 0
- Not evaluated
- 0
Level AA — 20 criteria
- Supports
- 14
- Partially supports
- 5
- 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 (71)
| Criterion | Name | Level | Conformance | Remarks from vendor |
|---|---|---|---|---|
| 1.1.1 | Non-text Content | A | Does Not Support | Web: The product does not provide sufficient text alternatives for most images, such as: Icons used in image buttons that do not contain textual alternatives Drag and drop content explanations that use images of text without providing text alternatives. |
| 1.2.1 | Audio-only and Video-only (Prerecorded) | A | Supports | Web: The product does not contain prerecorded audio-only or video-only media. |
| 1.2.2 | Captions (Prerecorded) | A | Supports | Web: The product does not contain prerecorded synchronized media. |
| 1.2.3 | Audio Description or Media Alternative (Prerecorded) | A | Supports | Web: The product does not contain prerecorded video content that would require audio description or a media alternative. |
| 1.2.4 | Captions (Live) | AA | Supports | Web: The product does not contain live synchronized media. |
| 1.2.5 | Audio Description (Prerecorded) | AA | Supports | Web: The product does not contain prerecorded video content that would require audio description. |
| 1.3.1 | Info and Relationships | A | 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: Table content that is not rendered using table markup. Visually displayed headings that are not explicitly rendered as HTML headings. Groups of related form fields that are not associated visually or programmatically. Checkboxes that use visual positioning to indicated enabled and disabled states. |
| 1.3.2 | Meaningful Sequence | A | Supports | Web: The product presents content in a meaningful sequence. |
| 1.3.3 | Sensory Characteristics | A | Partially Supports | Web: Some instructions do not rely solely on sensory characteristics. Exceptions include: The instructions for editing an API’s request or response policies, which rely on images of text to explain drag and drop functionality. |
| 1.3.4 | Orientation | AA | Supports | Web: Content does not restrict its view and operation to a single display orientation. |
| 1.3.5 | Identify Input Purpose | AA | 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: The username and password fields for logging into both the admin and publishing views. |
| 1.4.1 | Use of Color | A | Partially Supports | Web: Color is not used as the only visual means of conveying information for some content. Exceptions include: Adding data to required fields, such as on the Admin interface’s server options, form field borders change from the default green color to red, which let users know form fields are in error. The SMAL identity providers steps that rely on background color alone to identify the current step. |
| 1.4.2 | Audio Control | A | Supports | Web: The product does not contain audio that plays automatically. |
| 1.4.3 | Contrast (Minimum) | AA | Partially Supports | Web: Most text meets minimum contrast requirements. Exceptions include: The combination of green foreground colors against white and gray backgrounds used for branding. Buttons with white text against orange backgrounds. The selected navigation item on Analytics pages. The Aggregation, Apply, and Discard buttons on Visualization pages. |
| 1.4.4 | Resize text | AA | 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: The primary navigation of the product, which can be pushed offscreen at 200% magnification. |
| 1.4.5 | Images of Text | AA | Partially Supports | Web: Text is used to convey information rather than images of text for some content. Exceptions include: Images of text used as instructions for the API policies drag and drop control. |
| 1.4.10 | Reflow | AA | Supports | Web: Content reflows appropriately. |
| 1.4.11 | Non-text Contrast | AA | 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 | AA | Supports | Web: The product supports the required text style properties without loss of content or functionality. |
| 1.4.13 | Content on Hover or Focus | AA | Supports | Web: Authored content does not contain content elements triggered by hover or focus. |
| 2.1.1 | Keyboard | A | Does Not Support | Web: Most product functionality cannot be operated through a keyboard interface. Examples include: The publisher menu buttons that do not receive keyboard focus. Cards for available APIs within the publisher view that do not receive keyboard focus. Image buttons on the admin view, including buttons used to edit or delete exiting items, that do not receive keyboard focus. API request and response policies that require click and drag functionality without providing a keyboard alternative. |
| 2.1.2 | No Keyboard Trap | A | Supports | Web: The product does not include keyboard traps. |
| 2.1.4 | Character Key Shortcuts | A | Supports | Web: The product does not provide character key shortcuts. |
| 2.2.1 | Timing Adjustable | A | Partially Supports | Web: Most content do not require timed responses. Exceptions include: Status messages on the publisher view that time out unless hovered upon with no mechanism provided to extend or remove the timed interaction. |
| 2.2.2 | Pause, Stop, Hide | A | Supports | Web: The product does not include elements which move, blink, scroll, or auto-update. |
| 2.3.1 | Three Flashes or Below Threshold | A | Supports | Web: The product does not contain flashing content. |
| 2.4.1 | Bypass Blocks | A | Does Not Support | Web: The product does not provide a mechanism to bypass repeated heading and navigation content. |
| 2.4.2 | Page Titled | A | 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: Pages on the publisher or admin sites that are not within the analytics content. The admin login page. |
| 2.4.3 | Focus Order | A | Supports | Web: Components receive focus in a meaningful order. |
| 2.4.4 | Link Purpose (In Context) | A | 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 | AA | 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 | AA | Supports | Web: Headings and labels are descriptive. |
| 2.4.7 | Focus Visible | AA | Partially Supports | Web: Most focusable elements have a visible keyboard focus indicator. Exceptions include: The navigation within the Admin menu, which does not include a visual indication of focus. |
| 2.5.1 | Pointer Gestures | A | Supports | Web: The product does not rely on multipoint or path-based gestures. |
| 2.5.2 | Pointer Cancellation | A | Supports | Web: Product functions that use a single pointer are completed when the user releases the pointer. |
| 2.5.3 | Label in Name | A | Supports | Web: The accessible names of controls contain the text of their visible labels. |
| 2.5.4 | Motion Actuation | A | Supports | Web: The product does not have functionality operated by device motion or user motion. |
| 3.1.1 | Language of Page | A | Does Not Support | Web: The language of pages cannot be programmatically determined. |
| 3.1.2 | Language of Parts | AA | Supports | Web: Content is only presented in one language at a time. |
| 3.2.1 | On Focus | A | Supports | Web: Components do not initiate a change of context when focused. |
| 3.2.2 | On Input | A | 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 | AA | 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 | AA | Supports | Web: Components with the same functionality are identified consistently. |
| 3.3.1 | Error Identification | A | 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 | A | Supports | Web: Labels are provided for input fields. |
| 3.3.3 | Error Suggestion | AA | 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) | AA | 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. |
| 4.1.1 | Parsing | A | 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: Buttons on the publishing view that have non-unique ID attributes. |
| 4.1.2 | Name, Role, Value | A | Does Not Support | Web: User interface components in most product functions do not provide programmatic name, role, or value information. Examples include: Image buttons that do not provide programmatic name or role information. Text input elements, such as those on the admin or publisher pages, that do not provide programmatic name information. The main navigation links within the publishing view that lack programmatic roles. The navigation links within the admin view contain that lack accessible state information. |
| 4.1.3 | Status Messages | AA | 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. |
| 4.2.1 | Usage without vision | - | Does Not Support | Web: Most functions of the product are not usable without vision. Examples include: As noted in 1.1.1 Non-text Content , icons within the product do not contain textual alternatives. As noted in 1.3.1 Info and Relationships , some tables within the product do not include table markup. As noted in 2.1.1 Keyboard , many components do not receive keyboard focus or rely on mouse-based drag and drop functionality. As noted in 4.1.2 Name, Role, Value , many elements do not contain accessible names or roles. As noted in 4.1.3 Status Messages , status messages within the Admin portion of the product w |
| 4.2.2 | Usage with limited vision | - | 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: As noted in 1.4.3 Contrast (Minimum) , major branding colors contain insufficient color contrast ratios. As noted in 1.4.4 Resize Text , when users magnify their screens it is possible for the main navigation to be removed from display on the page. |
| 4.2.3 | Usage without perception of colour | - | Partially Supports | Web: Most functions of the product are usable without perception of color. |
| 4.2.4 | Usage without hearing | - | Supports | Web: The product does not require the use of hearing. |
| 4.2.5 | Usage with limited hearing | - | Supports | Web: The product does not require the use of hearing. |
| 4.2.6 | Usage without vocal capability | - | Supports | Web: The product does not require the use of speech. |
| 4.2.7 | Usage with limited manipulation or strength | - | Does Not Support | Web: Most functions of the product are not usable with limited manipulation or strength. Examples include: As noted in 2.1.1 Keyboard , many components do not receive keyboard focus, or rely on mouse-based drag and drop functionality. As noted in 2.4.7 Focus Visible , some controls do not contain visual indications of keyboard focus. |
| 4.2.8 | Usage with limited reach | - | Supports | Web: The product is functional with limited reach. |
| 4.2.9 | Minimize photosensitive seizure triggers | - | Supports | Web: The product does not contain flashing content. |
| 4.2.10 | Usage with limited cognition, language or learning | - | 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 | - | Supports | Web: The product maintains user privacy when accessibility features are used. Examples include: When text is masked visually, the private information is not announced to a screen reader. The product gives screen reader users sufficient opportunity to use their own private listening devices when reading personal data. |
| 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. |
| 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.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. |
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 April 2021. 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.