Adobe Accessibility Conformance Report
VPAT® Version 2.3 – December 2018
Product Information
Name of Product/Version: Adobe Campaign Standard v19.1
Product Description: With Adobe Campaign, use rich customer data to create, coordinate, and deliver dynamic campaigns that customers actually want — through email, mobile, offline channels, and more.
Date: June 2019 (Minor update to term definitions - July 24, 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 Campaign involved use of leading assistive technology, such as screen readers, screen magnifiers, and speech recognition software, as well as 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 standards/guidelines:
Standard/Guideline |
Included In Report |
---|---|
Web Content Accessibility Guidelines 2.0, at http://www.w3.org/TR/2008/REC-WCAG20-20081211/ |
Level A - Yes Level AA - Yes Level AAA - No |
Web Content Accessibility Guidelines 2.1, at https://www.w3.org/TR/WCAG21/ |
Level A - Yes Level AA - Yes Level AAA - No |
Section 508 as published in 2017, at http://www.Section508.gov |
Yes |
EN 301 549 Accessibility requirements suitable for public procurement of ICT products and services in Europe, - V2.1.2 (2018-08) at https://www.etsi.org/deliver/etsi_en//301500_301599/301549/02.01.02_60/en_301549v020102p.pdf |
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: This product has not been evaluated against the criterion. This can be used only in WCAG 2.x Level AAA.
WCAG 2.x Report
Tables 1 and 2 also document 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.
Section 1: Success Criteria, Level A
Notes:
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) Also applies to: EN 301 549 Criteria
Revised Section 508
|
Web: Does Not Support Authored Content (HTML): Supports |
Web: The product does not provide sufficient text alternatives for most images. Examples include:
Authored Content (HTML): When an author inserts an image in a landing page or HTML email, the product prompts the author to enter alt text for the image. |
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) Also applies to: EN 301 549 Criteria
Revised Section 508
|
Web: Supports Authored Content (HTML): Supports |
Web: The product does not contain prerecorded audio-only or video-only media. Authored Content (HTML): Authored content does not contain prerecorded audio-only or video-only media. |
1.2.2 Captions (Prerecorded) (Level A) Also applies to: EN 301 549 Criteria
Revised Section 508
|
Web: Supports Authored Content (HTML): Supports |
Web: The product does not contain prerecorded synchronized media. Authored Content (HTML): Authored content does not contain prerecorded synchronized media. |
1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A) Also applies to: EN 301 549 Criteria
Revised Section 508
|
Web: Supports Authored Content (HTML): Supports |
Web: The product does not contain prerecorded video content that would require audio description or a media alternative. Authored Content (HTML): The product does not create video content that would require audio description or a media alternative. |
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) Also applies to: EN 301 549 Criteria
Revised Section 508
|
Web: Partially Supports Authored Content (HTML): Supports |
Web: Most structure and relationship information, such as the structure of lists and tables, is provided through element semantics. Exceptions include:
Authored Content (HTML): In landing pages and HTML emails, the Show Source function enables authors to provide appropriate semantics and textual equivalents for visual structures and relationships. |
1.3.2 Meaningful Sequence (Level A) Also applies to: EN 301 549 Criteria
Revised Section 508
|
Web: Partially Supports Authored Content (HTML): Supports |
Web: The product presents most content in a meaningful sequence. Exceptions include:
Authored Content (HTML): In landing pages and HTML emails, the Show Source function enables authors to present content in a meaningful sequence. |
1.3.3 Sensory Characteristics (Level A) Also applies to: EN 301 549 Criteria
Revised Section 508
|
Web: Supports Authored Content (HTML): Supports |
Web: Instructions do not rely solely on sensory characteristics. Authored Content (HTML): Authors can ensure that content meets this criterion. |
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) Also applies to: EN 301 549 Criteria
Revised Section 508
|
Web: Partially Supports Authored Content (HTML): Supports |
Web: Most functions of the product do not convey information through color alone. Exceptions include:
Authored Content (HTML): Authors can ensure that content meets this criterion. |
1.4.2 Audio Control (Level A) Also applies to: EN 301 549 Criteria
Revised Section 508
|
Web: Supports Authored Content (HTML): Supports |
Web: The product does not contain audio that plays automatically. Authored Content (HTML): Authored Content does not contain audio that plays automatically. |
Guideline 2.1 Keyboard Accessible:
Make all functionality available from a keyboard.
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
2.1.1 Keyboard (Level A) Also applies to: EN 301 549 Criteria
Revised Section 508
|
Web: Does Not Support Authored Content (HTML): Supports |
Web: Some individual controls in the product are keyboard operable, such as card links in the home page. However, most complete processes in the product cannot be completed through sole use of a keyboard interface. Examples include:
Authored Content (HTML): In landing pages and HTML emails, the Show Source function enables authors to create content that meets this criterion. |
2.1.2 No Keyboard Trap (Level A) Also applies to: EN 301 549 Criteria
Revised Section 508
|
Web: Partially Supports Authored Content (HTML): Supports |
Web: Most product functions do not include keyboard traps. However, a keyboard trap interferes with some processes. Examples include:
Authored Content (HTML): In landing pages and HTML emails, the Show Source function enables authors to create content that does not have keyboard traps. |
2.1.4 Character Key Shortcuts (Level A 2.1 only) Also applies to: EN 301 549 Criteria
Revised Section 508 – Does not apply |
Web: Supports Authored Content (HTML): Supports |
Web: The product does not provide character key shortcuts. Authored Content (HTML): In landing pages and HTML emails, the Show Source function enables authors to create content that meets this criterion. |
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) Also applies to: EN 301 549 Criteria
Revised Section 508
|
Web: Supports Authored Content (HTML): Supports |
Web: The product does not include time limits. Authored Content (HTML): In landing pages and HTML emails, the Show Source function enables authors to create content that meets this criterion. |
2.2.2 Pause, Stop, Hide (Level A) Also applies to: EN 301 549 Criteria
Revised Section 508
|
Web: Supports Authored Content (HTML): Supports |
Web: The product does not include elements which move, blink, scroll, or auto-update. Authored Content (HTML): Authors can ensure that content meets this criterion. |
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) Also applies to: EN 301 549 Criteria
Revised Section 508
|
Web: Supports Authored Content (HTML): Supports |
Web: The product does not contain flashing content. Authored Content (HTML): Authors can ensure that content meets this criterion. |
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) Also applies to: EN 301 549 Criteria
Revised Section 508
|
Web: Partially Supports Authored Content (HTML): Supports |
Web: The product does not provide a specific mechanism to bypass the top navigation bar. The product contains some headings. Authored Content (HTML): The Show Source function enables authors to provide a mechanism to bypass repeated blocks of content in a set of landing pages. |
2.4.2 Page Titled (Level A) Also applies to: EN 301 549 Criteria
Revised Section 508
|
Web: Supports Authored Content (HTML): Supports |
Web: The titles of pages describe their purpose. Authored Content (HTML): In landing pages and HTML emails, the Show Source function enables authors to customize the page title. |
2.4.3 Focus Order (Level A) Also applies to: EN 301 549 Criteria
Revised Section 508
|
Web: Supports Authored Content (HTML): Supports |
Web: Components receive focus in a meaningful order. Authored Content (HTML): In landing pages and HTML emails, the Show Source function enables authors to create content that meets this criterion. |
2.4.4 Link Purpose (In Context) (Level A) Also applies to: EN 301 549 Criteria
Revised Section 508
|
Web: Supports Authored Content (HTML): Supports |
Web: The purpose of links in the product can be determined from the link text alone or from programmatic context of the link. Authored Content (HTML): In landing pages and HTML emails, the Show Source function enables authors to provide the purpose of links through link text alone or through programmatic context. |
2.5.1 Pointer Gestures (Level A 2.1 only) Also applies to: EN 301 549 Criteria
Revised Section 508 - Does not apply |
Web: Partially Supports Authored Content (HTML): Supports |
Web: Most functions of the product do not implement multipoint or path-based gestures. Some screens, such as Timeline and Workflow, implement a two-point pinch gesture to resize the content, while also providing the same resize function through single-point activation of buttons. However, some functions rely on path-based gestures without providing single-point activation; examples include:
Authored Content (HTML): In landing pages and HTML emails, the Show Source function enables authors to create content that meets this criterion. |
2.5.2 Pointer Cancellation (Level A 2.1 only) Also applies to: EN 301 549 Criteria
Revised Section 508 - Does not apply |
Web: Supports Authored Content (HTML): Supports |
Web: Most single-pointer operations in the product are equivalent to a simple click, and releasing the click or tap performs the action, such as activation of buttons and links. In drag-and-drop functions, such as modifying elements in a Workflow diagram, users can reverse the movement or activate a Cancel control to undo the change. Authored Content (HTML): In landing pages and HTML emails, the Show Source function enables authors to create content that meets this criterion. |
2.5.3 Label in Name (Level A 2.1 only) Also applies to: EN 301 549 Criteria
Revised Section 508 - Does not apply |
Web: Supports Authored Content (HTML): Supports |
Web: The accessible names of controls, such as links, contain the text of their visible labels. Authored Content (HTML): In landing pages and HTML emails, the Show Source function enables authors to ensure that the accessible names of controls, such as links, contain the text of their visible labels. |
2.5.4 Motion Actuation (Level A 2.1 only) Also applies to: EN 301 549 Criteria
Revised Section 508 - Does not apply |
Web: Supports Authored Content (HTML): Supports |
Web: Product functionality is not operated by device motion or user motion. Authored Content (HTML): Authors can ensure that functionality in authored content is not operated by device motion or user motion, or this functionality can also be operated by controls. |
Guideline 3.1 Readable:
Make text content readable and understandable.
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
3.1.1 Language of Page (Level A) Also applies to: EN 301 549 Criteria
Revised Section 508
|
Web: Does Not Support Authored Content (HTML): Supports |
Web: The language cannot be programmatically determined. Authored Content (HTML): In landing pages and HTML emails, the Show Source function enables authors to set the language of the page. |
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) Also applies to: EN 301 549 Criteria
Revised Section 508
|
Web: Supports Authored Content (HTML): Supports |
Web: Components do not initiate a change of context when focused. Authored Content (HTML): In landing pages and HTML emails, the Show Source function enables authors to ensure that components do not initiate a change of context when focused. |
3.2.2 On Input (Level A) Also applies to: EN 301 549 Criteria
Revised Section 508
|
Web: Supports Authored Content (HTML): Supports |
Web: Changes of context do not occur automatically on user input. Authored Content (HTML): In landing pages and HTML emails, the Show Source function enables authors to ensure that changes of context do not occur automatically on user input or are clearly indicated to the user before invoking them. |
Guideline 3.3 Input Assistance:
Help users avoid and correct mistakes.
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
3.3.1 Error Identification (Level A) Also applies to: EN 301 549 Criteria
Revised Section 508
|
Web: Partially Supports Authored Content (HTML): Supports |
Web: Most forms in the product do not generate errors. Some fields, such as required ID fields, display a graphical indicator of which field is in error. However, no error message text or text equivalent is provided. Authored Content (HTML): In landing pages and HTML emails, the Show Source function enables authors to identify items in error and provide error messages as text. |
3.3.2 Labels or Instructions (Level A) Also applies to: EN 301 549 Criteria
Revised Section 508
|
Web: Partially Supports Authored Content (HTML): Supports |
Web: Labels and instructions are provided for input fields. Exceptions include:
Authored Content (HTML): Authors can ensure that content meets this criterion. |
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) Also applies to: EN 301 549 Criteria
Revised Section 508
|
Web: Partially Supports Authored Content (HTML): Supports |
Web: Most screens and functions of the product meet the requirements of this criterion. Exceptions include:
Authored Content: In landing pages and HTML emails, the Show Source function enables authors to create content that meets this criterion. |
4.1.2 Name, Role, Value (Level A) Also applies to: EN 301 549 Criteria
Revised Section 508
|
Web: Does Not Support Authored Content (HTML): Supports |
Web: Some controls in the product have appropriate name, role, state, and value information, such as card links in the home page. However, incomplete semantic information prevents most completion of processes in the product. Examples include:
Authored Content (HTML): In landing pages and HTML emails, the Show Source function enables authors to create content that meets this criterion. |
Section 2: Success Criteria, Level AA
Notes:
Guideline 1.2 Time-based Media:
Provide alternatives for time-based media.
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
1.2.4 Captions (Live) (Level AA) Also applies to: EN 301 549 Criteria
Revised Section 508
|
Web: Supports Authored Content (HTML): Supports |
Web: The product does not contain live synchronized media. Authored Content (HTML): Authored content does not contain live synchronized media. |
1.2.5 Audio Description (Prerecorded) (Level AA) Also applies to: EN 301 549 Criteria
Revised Section 508
|
Web: Supports Authored Content (HTML): Supports |
Web: The product does not contain prerecorded video content that would require audio description. Authored Content (HTML): The product does not create video content that would require audio description. |
1.3.4 Orientation (Level AA 2.1 only) Also applies to: EN 301 549 Criteria
Revised Section 508 - Does not apply |
Web: Supports Authored Content (HTML): Supports |
Web: Content does not restrict its view and operation to a single display orientation. Authored Content (HTML): In landing pages and HTML emails, the Show Source function enables authors to ensure that content does not restrict its view and operation to a single display orientation. |
1.3.5 Identify Input Purpose (Level AA 2.1 only) Also applies to: EN 301 549 Criteria
Revised Section 508 - Does not apply |
Web: Supports Authored Content (HTML): Supports |
Web: The product does not contain input fields that collect information about the user. The Edit Personal Information control navigates the user to the Adobe Account website, which is not part of the product. Authored Content (HTML): In landing pages and HTML emails, the Show Source function enables authors to create content that meets this criterion. |
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.3 Contrast (Minimum) (Level AA) Also applies to: EN 301 549 Criteria
Revised Section 508
|
Web (EN 301 549): Does Not Support Web: (Revised Section 508): Does Not Support Authored Content (HTML): Supports |
Web (EN 301 549): Text in some functions of the product has sufficient contrast. Other instances of low contrast text have an equivalent accessible function, such as the top navigation bar in lieu of the low contrast card links in the homepage. However, text in most functions and some screen sizes has insufficient contrast; examples include:
Web (Revised Section 508): Text in some functions of the product has sufficient contrast. Other instances of low contrast text have equivalent facilitation, such as the top navigation bar in lieu of the low contrast card links in the homepage. However, text in most functions has insufficient contrast; examples include:
Authored Content (HTML): Authors can ensure that content meets this criterion. |
1.4.4 Resize text (Level AA) Also applies to: EN 301 549 Criteria
Revised Section 508
|
Web: Partially Supports Authored Content (HTML): Supports |
Web: In most product functions, text can be enlarged 200% without loss of functionality. Exceptions include:
Authored Content (HTML): In landing pages and HTML emails, the Show Source function enables authors to create content that meets this criterion. |
1.4.5 Images of Text (Level AA) Also applies to: EN 301 549 Criteria
Revised Section 508
|
Web: Supports Authored Content (HTML): Supports |
Web: The product uses text instead of images of text. Authored Content (HTML): In landing pages and HTML emails, the Show Source function enables authors to create content that meets this criterion. |
1.4.10 Reflow (Level AA 2.1 only) Also applies to: EN 301 549 Criteria
Revised Section 508 - Does not apply |
Web: Does Not Support Authored Content (HTML): Supports |
Web: At the required width of 320 CSS pixels, most of the product’s complete processes are not functional because the Next and Save buttons are off-screen and unavailable in multi-step form wizards. Authored Content (HTML): In landing pages and HTML emails, the Show Source function enables authors to create content that meets this criterion. |
1.4.11 Non-text Contrast (Level AA 2.1 only) Also applies to: EN 301 549 Criteria
Revised Section 508 - Does Not Apply |
Web: Partially Supports Authored Content (HTML): Supports |
Web: Most meaningful non-text content elements, such as indicators of form controls, have sufficient contrast. Exceptions include:
Authored Content (HTML): Authors can ensure that content meets this criterion. |
1.4.12 Text Spacing (Level AA 2.1 only) Also applies to: EN 301 549 Criteria
Revised Section 508 - Does not apply |
Web: Partially Supports Authored Content (HTML): Supports |
Web: Most functions of the product support the required text style properties without loss of content or functionality. Exceptions include:
Authored Content (HTML): In landing pages and HTML emails, the Show Source function enables authors to create content that meets this criterion. |
1.4.13 Content on Hover or Focus (Level AA 2.1 only) Also applies to: EN 301 549 Criteria
Revised Section 508 - Does not apply |
Web: Partially Supports Authored Content (HTML): Supports |
Web: In most product functions, content does not become visible and then hidden in response to pointer hover or keyboard focus. Exceptions include:
Authored Content (HTML): In landing pages and HTML emails, the Show Source function enables authors to create content that meets this criterion. |
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.5 Multiple Ways (Level AA) Also applies to: EN 301 549 Criteria
Revised Section 508
|
Web (EN 301 549): Partially Supports Web (Revised Section 508): Supports Authored Content (HTML): Supports |
Web (EN 501 549): Users can locate web pages in the product either through the top navigation bar and the advanced menu, or through the card links in the home page. However, the top navigation bar is not available for small screen breakpoints. Web (Revised Section 508): Users can locate web pages in the product either through the top navigation bar and the advanced menu, or through the card links in the home page. Authored Content (HTML): Authors can provide more than one way to locate a page in a set of landing pages, such as a navigation bar and a list of links. |
2.4.6 Headings and Labels (Level AA) Also applies to: EN 301 549 Criteria
Revised Section 508
|
Web: Supports Authored Content (HTML): Supports |
Web: Headings and labels are descriptive. Authored Content (HTML): Authors can ensure that content meets this criterion. |
2.4.7 Focus Visible (Level AA) Also applies to: EN 301 549 Criteria
Revised Section 508
|
Web: Does Not Support Authored Content (HTML): Supports |
Web: The keyboard focus indicator is visible on some controls. However, in most functions of the product, keyboard focus location is not visible for many tab stops on hidden off-screen content. Authored Content (HTML): In landing pages and HTML emails, the Show Source function enables authors to create content that meets this criterion. |
Guideline 3.1 Readable:
Make text content readable and understandable.
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
3.1.2 Language of Parts (Level AA) Also applies to: EN 301 549 Criteria
Revised Section 508
|
Web: Supports Authored Content (HTML): Supports |
Web: Content is only presented in one language at a time. Authored Content (HTML): In landing pages and HTML emails, the Show Source function enables authors to set the language for individual phrases within content. |
Guideline 3.2 Predictable:
Make Web pages appear and operate in predictable ways.
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
3.2.3 Consistent Navigation (Level AA) Also applies to: EN 301 549 Criteria
Revised Section 508
|
Web: Supports Authored Content (HTML): Supports |
Web: When navigational mechanisms are repeated in the product, such as buttons for multi-step forms, they occur in a consistent relative order. Authored Content (HTML): Authors can ensure that navigational mechanisms are repeated in the same relative order in a set of landing pages. |
3.2.4 Consistent Identification (Level AA) Also applies to: EN 301 549 Criteria
Revised Section 508
|
Web: Supports Authored Content (HTML): Supports |
Web: Components with the same functionality are identified consistently. Authored Content (HTML): Authors can ensure that components with the same functionality are identified consistently in a set of landing pages. |
Guideline 3.3 Input Assistance:
Help users avoid and correct mistakes.
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
3.3.3 Error Suggestion (Level AA) Also applies to: EN 301 549 Criteria
Revised Section 508
|
Web: Partially Supports Authored Content (HTML): Supports |
Web: Most forms in the product do not generate errors. Some fields, such as required ID fields, display a graphical indicator of which field is in error. However, no suggestions for correction are provided to the user. Authored Content (HTML): In landing pages and HTML emails, the Show Source function enables authors to provide suggestions for correction of automatically detected input errors. |
3.3.4 Error Prevention (Legal, Financial, Data) (Level AA) Also applies to: EN 301 549 Criteria
Revised Section 508
|
Web: Supports Authored Content (HTML): 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. Authored Content (HTML): In landing pages and HTML emails, the Show Source function enables authors to create content that meets this criterion. |
4.1.3 Status Messages (Level AA) Also applies to: EN 301 549 Criteria
Revised Section 508 - Does not apply |
Web: Supports Authored Content (HTML): Supports |
Web: Most functions do not contain status messages. Loading messages receive focus automatically. Authored Content (HTML): In landing pages and HTML emails, the Show Source function enables authors to create content that meets this criterion. |
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 Authored Content (HTML): Supports |
Web: Some individual controls in the product are keyboard operable and functional without vision. However, most complete processes of the product are not usable without vision:
Authored Content (HTML): The product allows authors to create content which is functional for users without vision. |
302.2 With Limited Vision |
Web: Partially Supports Authored Content (HTML): Supports |
Web: Most functions of the product are usable with limited vision. Exceptions include:
Authored Content (HTML): The product allows authors to create content which is functional for users with limited vision. |
302.3 Without Perception of Color |
Web: Partially Supports Authored Content (HTML): Supports |
Web: Most functions of the product are usable without perception of color. Exceptions include:
Authored Content (HTML): The product allows authors to create content which is functional for users with limited perception of color. |
302.4 Without Hearing |
Web: Supports Authored Content (HTML): Supports |
Web: The product does not require the use of hearing. Authored Content (HTML): Authored content does not require the use of hearing. |
302.5 With Limited Hearing |
Web: Supports Authored Content (HTML): Supports |
Web: The product does not require the use of hearing. Authored Content (HTML): Authored content does not require the use of hearing. |
302.6 Without Speech |
Web: Supports Authored Content (HTML): Supports |
Web: The product does not require the use of speech. Authored Content (HTML): Authored content does not require the use of speech. |
302.7 With Limited Manipulation |
Web: Does Not Support Authored Content (HTML): Supports |
Web: Some controls in the product are keyboard operable. However, most complete processes of the product are not usable with limited manipulation.
Authored Content (HTML): The product allows authors to create content which is functional for users with limited manipulation. |
302.8 With Limited Reach and Strength |
Web: Supports Authored Content (HTML): Supports |
Web: The product is functional with limited reach and strength. Authored Content (HTML): The product allows authors to create content which is functional for users with limited reach and strength. |
302.9 With Limited Language, Cognitive, and Learning Abilities |
Web: Partially Supports Authored Content (HTML): Supports |
Web: 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 online help and consistent identification of user interface components. However, some functions of the product are more difficult than necessary for users with limited language, cognitive, and learning abilities; examples include:
Authored Content (HTML): The product allows authors to create content which is functional for users with limited language, cognitive, and learning abilities. |
Chapter 4: Hardware
Notes: Not Applicable
Chapter 5: Software
Notes: Not Applicable
501 General
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
501.1 Scope – Incorporation of WCAG 2.0 AA |
See WCAG 2.x section. |
See information in the 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 |
|
502.2.1 User Control of Accessibility Features |
Not Applicable |
Not applicable to web. |
502.2.2 No Disruption of Accessibility Features |
Not Applicable |
Not applicable to web. |
502.3 Accessibility Services |
See 502.3.1-502.3.14 |
|
502.3.1 Object Information |
Not Applicable |
Not applicable to web. |
502.3.2 Modification of Object Information |
Not Applicable |
Not applicable to web. |
502.3.3 Row, Column, and Headers |
Not Applicable |
Not applicable to web. |
502.3.4 Values |
Not Applicable |
Not applicable to web. |
502.3.5 Modification of Values |
Not Applicable |
Not applicable to web. |
502.3.6 Label Relationships |
Not Applicable |
Not applicable to web. |
502.3.7 Hierarchical Relationships |
Not Applicable |
Not applicable to web. |
502.3.8 Text |
Not Applicable |
Not applicable to web. |
502.3.9 Modification of Text |
Not Applicable |
Not applicable to web. |
502.3.10 List of Actions |
Not Applicable |
Not applicable to web. |
502.3.11 Actions on Objects |
Not Applicable |
Not applicable to web. |
502.3.12 Focus Cursor |
Not Applicable |
Not applicable to web. |
502.3.13 Modification of Focus Cursor |
Not Applicable |
Not applicable to web. |
502.3.14 Event Notification |
Not Applicable |
Not applicable to web. |
502.4 Platform Accessibility Features |
Not Applicable |
Not applicable to web. |
503 Applications
503.1 General. Applications shall conform to 503.
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
503.2 User Preferences |
Not Applicable |
Not applicable to web. |
503.3 Alternative User Interfaces |
Not Applicable |
Not applicable to web. |
503.4 User Controls for Captions and Audio Description |
See 503.4.1-503.4.2 |
|
503.4.1 Caption Controls |
Not Applicable |
Not applicable to web. |
503.4.2 Audio Description Controls |
Not Applicable |
Not applicable to web. |
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 |
See WCAG 2.x section |
The product enables authors to create HTML content, such as landing pages and emails, which conforms to WCAG 2.0 Levels A and AA. See details for individual criteria in the WCAG 2.x section. Content can be imported from other tools or created using built-in authoring functions. Authors can use the Show Source function to edit HTML content directly to address code-level accessibility issues. |
504.2.1 Preservation of Information Provided for Accessibility in Format Conversion |
Not Applicable |
The product does not convert content. |
504.2.2 PDF Export |
Not Applicable |
The product does not export PDF files. |
504.3 Prompts |
Does Not Support |
When an author inserts an image into an HTML email or landing page, the product prompts for image alt text. However, most functions in the product’s WYSIWYG and source code editors do not prompt authors to create accessible content. |
504.4 Templates |
Not Applicable |
Default blocks in landing pages and HTML emails function as templates which enable authors to create content which conforms in most ways to WCAG 2.0 Levels A and AA. However, some content has conformance issues; examples include:
|
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 on the Adobe Accessibility Compliance website.
EN 301 549 Report
Notes:
Chapter 4: 4.2 Functional Performance Statements (FPS)
Notes: According to C.4 Functional Performance, this section is informative only.
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
4.2.1 Usage without vision |
Web: Does Not Support Authored Content (HTML): Supports |
Web: Most individual controls in the product are keyboard operable and functional without vision. However, most complete processes of the product are not usable without vision.
Authored Content (HTML): The product allows authors to create content which is functional for users without vision. |
4.2.2 Usage with limited vision |
Web: Partially Supports Authored Content (HTML): Supports |
Web: Most functions of the product are usable with limited vision. Exceptions include:
Authored Content (HTML): The product allows authors to create content which is functional for users with limited vision. |
4.2.3 Usage without perception of colour |
Web: Partially Supports Authored Content (HTML): Supports |
Web: Most functions of the product are usable without perception of color. Exceptions include:
Authored Content (HTML): The product allows authors to create content which is functional for users with limited perception of color. |
4.2.4 Usage without hearing |
Web: Supports Authored Content (HTML): Supports |
Web: The product does not require the use of hearing. Authored Content (HTML): Authored content does not require the use of hearing. |
4.2.5 Usage with limited hearing |
Web: Supports Authored Content (HTML): Supports |
Web: The product does not require the use of hearing. Authored Content (HTML): Authored content does not require the use of hearing. |
4.2.6 Usage without vocal capability |
Web: Supports Authored Content (HTML): Supports |
Web: The product does not require the use of speech. Authored Content (HTML): Authors can create content which is functional for users without speech. |
4.2.7 Usage with limited manipulation or strength |
Web: Does Not Support Authored Content (HTML): Supports |
Web: Most individual controls in the product are keyboard operable. However, most complete processes of the product are not usable with limited manipulation or strength.
Authored Content (HTML): The product allows authors to create content which is functional for users with limited manipulation or strength. |
4.2.8 Usage with limited reach |
Web: Supports Authored Content (HTML): Supports |
Web: The product is functional with limited reach. Authored Content (HTML): The product allows authors to create content which is functional for users with limited reach. |
4.2.9 Minimize photosensitive seizure |
Web: Supports Authored Content (HTML): Supports |
Web: The product does not contain flashing content. Authored Content (HTML): Authors can create content which does not flash, or flashes within an acceptable threshold, in order to minimize the potential for triggering photosensitive seizures. |
4.2.10 Usage with limited cognition |
Web: Partially Supports Authored Content (HTML): Supports |
Web: 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 online help and consistent identification of user interface components. However, some functions of the product are more difficult than necessary for users with limited language, cognitive, and learning abilities; examples include: As noted in 3.3.2 Labels or Instructions, some form fields lack clear instructions to explain that they are required. As noted in 3.3.3 Error Suggestion, some form fields display a graphical indicator of which field is in error, but no suggestions for correction are provided to the user. As noted in 2.4.5 Multiple Ways, on large screens the product offers users a choice of navigation mechanisms; however, on small screens the top navigation bar is not available. Authored Content (HTML): The product allows authors to create content which is functional for users with limited language, cognitive, and learning abilities. |
4.2.11 Privacy |
Web: Supports |
Web: The product does not ask for legal, financial, or personal data. The Edit Personal Information control navigates the user to the Adobe Account website, which is not part of the product. Authored Content (HTML): Authors can create content which does not ask for legal, financial, or personal data. |
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. |
5.1.6.2 Input focus |
Not Applicable |
The product does not have functionality that is closed to keyboards. |
5.2 Activation of accessibility features |
Not Applicable |
The product does not have specific documented accessibility features. The software 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 |
Does Not Support |
The product does not convert content. |
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 |
Partially Supports |
The product has only non-mechanical operable parts, such as on-screen buttons. Most operable parts have an accessible name which enables them to be discernible without user vision. Exceptions include:
|
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
Notes: See WCAG 2.x section.
Chapter 10: Non-web Documents
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 section. |
11.5 Interperability with assistive technology |
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 content is isolated from its underlying platform. |
11.8.2 Accessible content creation |
See WCAG 2.x section |
The product enables authors to create HTML content, such as landing pages and emails, which conforms to WCAG 2.1 Levels A and AA. See details for individual criteria in the WCAG 2.x section. Content can be imported from other tools or created using built-in authoring functions. Authors can use the Show Source function to edit HTML content directly to address code-level accessibility issues. When an author inserts an image into an HTML email or landing page, the product prompts for image alt text; however, most functions in the product’s WYSIWYG and source code editors do not actively guide authors to create accessible content. |
11.8.3 Preservation of accessibility information in transformations |
Not Applicable |
The product does not provide restructuring transformations or re-coding transformations. |
11.8.4 Repair assistance |
Not Applicable |
The product does not have accessibility checking functionality. |
11.8.5 Templates |
Not Applicable |
Default blocks in landing pages and HTML emails function as templates which enable authors to create content which conforms in most ways to WCAG 2.0 Levels A and AA. However, some content has conformance issues; examples include:
|
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 on the Adobe Accessibility Compliance website.
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)