Adobe Accessibility Conformance Report

VPAT® Version 2.3 – December 2018

Product Information

Name of Product/Version: Adobe Experience Manager (AEM) 6.5 Forms - Adaptive Forms
Product Description: Adobe Experience Manager Forms is a forms authoring tool that allows users to build end-to-end digital enrollment and onboarding journeys that deliver a personal touch to millions of customers.
Date: November 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 Experience Manager Adaptive Forms 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

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

Revised Section 508 standards as published by the U.S. Access Board in the Federal Register on January 18, 2017
Corrections to the ICT Final Rule as published by the US Access Board in the Federal Register on January 22, 2018

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: The product has not been evaluated against the criterion. This can be used only in WCAG 2.0 Level AAA.


WCAG 2.x Report

All WCAG Sections below 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.  

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

  • 9.1.1.1 (Web)
  • 10.1.1.1 (Non-web document)
  • 11.1.1.1.1 (Open Functionality Software)
  • 11.1.1.1.2 (Closed Functionality Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)

Web: Partially Supports

Authored Content (HTML): Supports

Web: The product provides sufficient text alternatives for many instances of non-text content, such as images and image buttons. However, the product does not provide sufficient text alternatives for some non-text content, such as:

  • Some images and image buttons have non-meaningful text alternatives.
  • Some decorative images have redundant, non-meaningful text alternatives.

Authored Content (HTML): Authors can provide alternative text for meaningful images. Authors can provide descriptive identification of non-text content.

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

  • 9.1.2.1 (Web)
  • 10.1.2.1 (Non-web document)
  • 11.1.2.1.1 (Open Functionality Software)
  • 11.1.2.1.2.1 and 11.1.2.1.2.2 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)

Web: Supports

Authored Content (HTML): Supports

Web: The product does not contain prerecorded audio-only or video-only media.

Authored Content (HTML): Audio and video components are not available in the product. However, authors may be able to add custom components or audio or video from an asset. Authors can provide an alternative for time-based media or an audio track to meet this requirement.

1.2.2 Captions (Prerecorded) (Level A)

Also applies to:
EN 301 549 Criteria

  • 9.1.2.2 (Web)
  • 10.1.2.2 (Non-web document)
  • 11.1.2.2 (Open Functionality Software)
  • 11.1.2.2 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)

Web: Supports

Authored Content (HTML): Supports

Web: The product does not contain prerecorded synchronized media.

Authored Content (HTML): Audio and video components are not available in the product. However, authors may be able to add custom components or audio or video from an asset. Authors will need to verify that their content conforms to this requirement.

1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A)

Also applies to:
EN 301 549 Criteria

  • 9.1.2.3 (Web)
  • 10.1.2.3 (Non-web document)
  • 11.1.2.3.1 (Open Functionality Software)
  • 11.1.2.3.2 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)

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): Audio and video components are not available in the product. However, authors may be able to add custom components or audio or video from an asset. Authors will need to verify that their content conforms to this requirement.

1.2.4 Captions (Live) (Level AA)
Also applies to:
EN 301 549 Criteria

  • 9.1.2.4 (Web)
  • 10.1.2.4 (Non-web document)
  • 11.1.2.4 (Open Functionality Software)
  • 11.1.2.4 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)

Web: Supports

Authored Content (HTML): Supports

 

Web: The product does not contain live synchronized media.

Authored Content (HTML): Audio and video components are not available in the product. However, authors may be able to add custom components or audio or video from an asset. Authors will need to verify that their content conforms to this requirement.

1.2.5 Audio Description (Prerecorded) (Level AA)
Also applies to:
EN 301 549 Criteria

  • 9.1.2.5 (Web)
  • 10.1.2.5 (Non-web document)
  • 11.1.2.5 (Open Functionality Software)
  • 11.1.2.5 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)

Web: Supports

Authored Content (HTML): Supports

Web: The product does not contain prerecorded video content that would require audio description.

Authored Content (HTML): Audio and video components are not available in the product. However, authors may be able to add custom components or audio or video from an asset. Authors will need to verify that their content conforms to this requirement.

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

  • 9.1.3.1 (Web)
  • 10.1.3.1 (Non-web document)
  • 11.1.3.1.1 (Open Functionality Software)
  • 11.1.3.1.2 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)

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:

  • Heading levels that appear out of order semantically.
  • The use of implicit headings.

Authored Content (HTML): Authors can 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

  • 9.1.3.2 (Web)
  • 10.1.3.2 (Non-web document)
  • 11.1.3.2.1 (Open Functionality Software)
  • 11.1.3.2.2 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)

Web: Supports

Authored Content (HTML): Supports

Web: The product presents content in a meaningful sequence.

Authored Content (HTML): The product allows authors to present content in a meaningful sequence.

1.3.3 Sensory Characteristics (Level A)

Also applies to:
EN 301 549 Criteria

  • 9.1.3.3 (Web)
  • 10.1.3.3 (Non-web document)
  • 11.1.3.3 (Open Functionality Software)
  • 11.1.3.3 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)

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.

1.3.4 Orientation (Level AA 2.1 only)
Also applies to:
EN 301 549 Criteria

  • 9.1.3.4 (Web)
  • 10.1.3.4 (Non-web document)
  • 11.1.3.4 (Open Functionality Software)
  • 11.1.3.4 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

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): Authors can 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

  • 9.1.3.5 (Web)
  • 10.1.3.4 (Non-web document)
  • 11.1.3.5 (Open Functionality Software)
  • 11.1.3.5 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

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.

Authored Content (HTML): Authors can give form fields an autocomplete value from a list of options; however, the list of options does not include all possible input purposes and authors cannot manually type in an autocomplete value. Enable autofill is available for the Text Box component.

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

  • 9.1.4.1 (Web)
  • 10.1.4.1 (Non-web document)
  • 11.1.4.1 (Open Functionality Software)
  • 11.1.4.1 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)

Web: Partially Supports

Authored Content (HTML): Supports

Web: Most parts of the product do not convey information through color alone. Exceptions include:

  • Some content is highlighted visually, but no textual or non-color alternative is present to convey the highlighting to users who cannot perceive it. For example, the current step for creating an adaptive form is shown by color alone.

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

  • 9.1.4.2 (Web)
  • 10.1.4.2 (Non-web document)
  • 11.1.4.2 (Open Functionality Software)
  • 11.1.4.2 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)

Web: Supports

Authored Content (HTML): Supports

Web: The product does not contain audio that plays automatically.

Authored Content (HTML): Authors can create content that provides a mechanism to pause or stop the audio.

1.4.3 Contrast (Minimum) (Level AA)
Also applies to:
EN 301 549 Criteria

  • 9.1.4.3 (Web)
  • 10.1.4.3 (Non-web document)
  • 11.1.4.3 (Open Functionality Software)
  • 11.1.4.3 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)

Web: Partially Supports

Authored Content (HTML): Supports

Web: Most text meets minimum contrast requirements. Exceptions include:

  • In some cases, text and background colors do not meet minimum contrast requirements.

Authored Content (HTML): Authors can ensure that content meets this criterion. There is a color contrast issue with Terms and Conditions, but authors can change the color using Theme Editor.

1.4.4 Resize Text (Level AA)
Also applies to:
EN 301 549 Criteria

  • 9.1.4.4 (Web)
  • 10.1.4.4 (Non-web document)
  • 11.1.4.4.1 (Open Functionality Software)
  • 11.1.4.4.2 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)

Web: Partially Supports

Authored Content (HTML): Supports

Web: Most text can be resized up to 200% without loss of functionality. There are some exceptions.

Authored Content (HTML): Authors can ensure that content can be resized up to 200% without loss of functionality.

1.4.5 Images of Text (Level AA)
Also applies to:
EN 301 549 Criteria

  • 9.1.4.5 (Web)
  • 10.1.4.5 (Non-web document)
  • 11.1.4.5.1 (Open Functionality Software)
  • 11.1.4.5.2 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)

Web: Supports

Authored Content (HTML): Supports

Web: The product uses text instead of images of text, except for branding elements that are considered essential.

Authored Content (HTML): Authors can ensure that content meets this criterion.

1.4.10 Reflow (Level AA 2.1 only)
Also applies to:
EN 301 549 Criteria

  • 9.1.4.10 (Web)
  • 10.1.4.10 (Non-web document)
  • 11.1.4.10.1 (Open Functionality Software)
  • 11.1.4.10.2 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508 – Does not apply

Web: Partially Supports

Authored Content (HTML): Supports

Web: At the required width of 320 CSS pixels, some content is presented without loss of information or functionality, and without requiring scrolling in two dimensions. Exceptions include:

  • Some content does not reflow appropriately at the required width.

Authored Content (HTML): Authors can ensure that content meets this criterion.

1.4.11 Non-text Contrast (Level AA 2.1 only)
Also applies to:
EN 301 549 Criteria

  • 9.1.4.11 (Web)
  • 10.1.4.11 (Non-web document)
  • 11.1.4.11 (Open Functionality Software)
  • 11.1.4.11 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508 – Does not apply

Web: Supports

Authored Content (HTML): Supports

Web: User interface components and graphical objects within the product meet contrast requirements.

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

  • 9.1.4.12 (Web)
  • 10.1.4.12 (Non-web document)
  • 11.1.4.12 (Open Functionality Software)
  • 11.1.4.12 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508 – Does not apply

Web: Supports

Authored Content (HTML): Supports

Web: Content and functionality within the product supports the required text style properties without loss of content or functionality.

Authored Content (HTML): Authors can ensure that content meets this criterion.

1.4.13 Content on Hover or Focus (Level AA 2.1 only)
Also applies to:
EN 301 549 Criteria

  • 9.1.4.13 (Web)
  • 10.1.4.13 (Non-web document)
  • 11.1.4.13 (Open Functionality Software)
  • 11.1.4.13 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508 – Does not apply

Web: Supports

Authored Content (HTML): Supports

Web: Content which is triggered by hover or focus is dismissible, hoverable, and persistent.

Authored Content (HTML): Authors can ensure that content meets this criterion.

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

  • 9.2.1.1 (Web)
  • 10.2.1.1 (Non-web document)
  • 11.2.1.1.1 (Open Functionality Software)
  • 11.2.1.1.2 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)

Web: Does Not Support

Authored Content (HTML): Partially Supports

Web: Some functionality, such as moving between tab panels, is available via the keyboard. However, most functionality is not available to keyboard users, such as:

  • A significant amount of core product functionality is only available through the use of a mouse. Examples include; the main form editing functionality, drag-and-drop functionality, and some buttons that have been removed from the tab order.
  • Some content that is visually hidden is not appropriately hidden from the keyboard and assistive technology.

Authored Content (HTML): Most components are operable through a keyboard interface. There are some exceptions:

  • Date Picker Calendar component workaround to enter the date directly in the field.
  • Keyboard issues with Switch control.
  • Keyboard issues with image radio buttons.
  • Keyboard focus management issues:
    • Active panel Next and Previous
    • Attachments
    • Tables
  • Extra tabindex on Terms and Conditions text

2.1.2 No Keyboard Trap (Level A)

Also applies to:
EN 301 549 Criteria

  • 9.2.1.2 (Web)
  • 10.2.1.2 (Non-web document)
  • 11.2.1.2 (Open Functionality Software)
  • 11.2.1.2 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)

Web: Partially Supports

Authored Content (HTML): Supports

Web: Most of the product does not contain keyboard traps. Exceptions include:

  • Focus can become trapped within some places in the product, such as within the code editor.

Authored Content (HTML): There are no known keyboard traps created when using components in the authored content.

2.1.4 Character Key Shortcuts (Level A 2.1 only)

Also applies to:
EN 301 549 Criteria

  • 9.2.1.4 (Web)
  • 10.2.1.4 (Non-web document)
  • 11.2.1.4.1 (Open Functionality Software)
  • 11.2.1.4.2 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508 – Does not apply

Web: Supports

Authored Content (HTML): Supports

Web: The product does not provide character key shortcuts.

Authored Content (HTML): Authored content 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)

Also applies to:
EN 301 549 Criteria

  • 9.2.2.1 (Web)
  • 10.2.2.1 (Non-web document)
  • 11.2.2.1 (Open Functionality Software)
  • 11.2.2.1 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)

Web: Supports

Authored Content (HTML): Supports

Web: The product does not include time limits.

Authored Content (HTML): Authors can ensure that content meets this criterion.

2.2.2 Pause, Stop, Hide (Level A)

Also applies to:
EN 301 549 Criteria

  • 9.2.2.2 (Web)
  • 10.2.2.2 (Non-web document)
  • 11.2.2.2 (Open Functionality Software)
  • 11.2.2.2 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)

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

  • 9.2.3.1 (Web)
  • 10.2.3.1 (Non-web document)
  • 11.2.3.1 (Open Functionality Software)
  • 11.2.3.1(Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)

Web: Supports

Authored Content (HTML): Supports

Web: The product does not contain flashing content.

Authored Content (HTML): Authors can ensure that content does not flash.

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

  • 9.2.4.1 (Web)
  • 10.2.4.1 (Non-web document) – Does not apply
  • 11.2.4.1 (Open Functionality Software) – Does not apply
  • 11.2.4.1 (Closed Software) – Does not apply
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software) – Does not apply to non-web software
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs) – Does not apply to non-web docs

Web: Does Not Support

Authored Content (HTML): Supports

Web: The product does not provide a mechanism to bypass blocks of repeated navigational content. The keyboard user is forced to tab repeatedly through menu items.

Authored Content (HTML): Authors can ensure that content meets this criterion by providing a method to bypass repeated blocks of content in a set of pages.

2.4.2 Page Titled (Level A)

Also applies to:
EN 301 549 Criteria

  • 9.2.4.2 (Web)
  • 10.2.4.2 (Non-web document)
  • 11.2.4.2 (Open Functionality Software) - Does not apply
  • 11.2.4.2 (Closed Software) – Does not apply
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)

Web: Partially Supports

Authored Content (HTML): Supports

Web: Some pages have titles that describe topic or purpose; however, some pages are lacking unique titles. When editing specific pages, the title describes the purpose of the page. Exceptions include:

  • General titles such as “AEM Forms” or “Form Editor: <page title> do not always describe each page’s individual purpose.

Authored Content (HTML): The product allows authors to create a unique title for each page of authored content..

2.4.3 Focus Order (Level A)

Also applies to:
EN 301 549 Criteria

  • 9.2.4.3 (Web)
  • 10.2.4.3 (Non-web document)
  • 11.2.4.3 (Open Functionality Software)
  • 11.2.4.3 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)

Web: Partially Supports

Authored Content (HTML): Supports

Web: Most components receive focus in a meaningful order. Exceptions include:

  • The focus order of some active elements does not match the visual order of those elements.

Authored Content (HTML): Authors can ensure that content meets this criterion.

2.4.4 Link Purpose (In Context) (Level A)

Also applies to:
EN 301 549 Criteria

  • 9.2.4.4 (Web)
  • 10.2.4.4 (Non-web document)
  • 11.2.4.4 (Open Functionality Software)
  • 11.2.4.4 (Closed Software
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)

Web: Partially Supports

Authored Content (HTML): Supports

Web: The purpose of most links in the product can be determined from the link text alone or from programmatic context of the link.  Exceptions include:

  • Some links do not fully express their purpose in context to assistive technology users.

Authored Content (HTML): Authors can provide the purpose of links through link text alone or through programmatic context.

2.4.5 Multiple Ways (Level AA)
Also applies to:
EN 301 549 Criteria

  • 9.2.4.5 (Web)
  • 10.2.4.5 (Non-web document) – Does not apply
  • 11.2.4.5 (Open Functionality Software) – Does not apply
  • 11.2.4.5 (Closed Software) – Does not apply
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  •  501 (Web)(Software) – Does not apply to non-web software
  •  504.2 (Authoring Tool)
  • 602.3 (Support Docs) – Does not apply to non-web docs

Web: Supports

Authored Content (HTML): Supports

Web: Multiple ways exist to locate each page within the product.

Authored Content (HTML): Authors can provide more than one way to locate a page in a set of pages.

2.4.6 Headings and Labels (Level AA)
Also applies to:
EN 301 549 Criteria

  • 9.2.4.6 (Web)
  • 10.2.4.6 (Non-web document)
  • 11.2.4.6 (Open Functionality Software)
  • 11.2.4.6 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  •  501 (Web)(Software)
  •  504.2 (Authoring Tool)
  • 602.3 (Support Docs)

Web: Partially Supports

Authored Content (HTML): Supports

Web: Most headings and labels, where identified, are descriptive. There may be some exceptions.

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

  • 9.2.4.7 (Web)
  • 10.2.4.7 (Non-web document)
  • 11.2.4.7 (Open Functionality Software)
  • 11.2.4.7 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)

Web: Partially Supports

Authored Content (HTML): Supports

Web: Many focusable elements have a visible keyboard focus indicator. In some cases, actionable controls do not exhibit a visual indication of focus.

Authored Content (HTML): Authors can ensure that content meets this criterion.

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)

Also applies to:
EN 301 549 Criteria

  • 9.2.5.1 (Web)
  • 10.2.5.1 (Non-web document)
  • 11.2.5.1 (Open Functionality Software)
  • 11.2.5.1 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508 – Does not apply

Web: Partially Supports

Authored Content (HTML): Supports

Web: Most of the product functionality can be accessed without path-based gestures.  Exceptions include:

  • In some cases, path-based gestures are required to access product functionality.

Authored Content (HTML): Authors can ensure that content meets this criterion.

2.5.2 Pointer Cancellation (Level A 2.1 only)

Also applies to:
EN 301 549 Criteria

  • 9.2.5.2 (Web)
  • 10.2.5.2 (Non-web document)
  • 11.2.5.2 (Open Functionality Software)
  • 11.2.5.2 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508 – Does not apply

Web: Supports

Authored Content (HTML): Supports

Web: The down-event of the pointer is not used to execute functionality, except where such functionality is easily reversible.

Authored Content (HTML): The down-event of the pointer is not used to execute functionality of authored content, except where such functionality is easily reversible.

2.5.3 Label in Name (Level A 2.1 only)

Also applies to:
EN 301 549 Criteria

  • 9.2.5.3 (Web)
  • 10.2.5.3 (Non-web document)
  • 11.2.5.3 (Open Functionality Software)
  • 11.2.5.3 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508 – Does not apply

Web: Supports

Authored Content (HTML): Supports

Web: The accessible names of controls contain the text of their visible labels.

Authored Content (HTML): Authors can ensure that the accessible names of controls contain the text of their visible labels.

2.5.4 Motion Actuation (Level A 2.1 only)

Also applies to:
EN 301 549 Criteria

  • 9.2.5.4 (Web)
  • 10.2.5.4 (Non-web document)
  • 11.2.5.4 (Open Functionality Software)
  • 11.2.5.4 (Closed Software
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

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): Authored content is not 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)

Also applies to:
EN 301 549 Criteria

  • 9.3.1.1 (Web)
  • 10.3.1.1 (Non-web document)
  • 11.3.1.1.1 (Open Functionality Software)
  • 11.3.1.1.2 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)

Web: Supports

Authored Content (HTML): Supports

Web: The language is programmatically determinable within the product.

Authored Content (HTML): Authors can set the language for individual phrases within content using the edit HTML code option.

3.1.2 Language of Parts (Level AA)
Also applies to:
EN 301 549 Criteria

  • 9.3.1.2 (Web)
  • 10.3.1.2 (Non-web document)
  • 11.3.1.2 (Open Functionality Software) – Does not apply
  • 11.3.1.2 (Closed Software) – Does not apply
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)

Web: Supports

Authored Content (HTML): Supports

Web: Content is only presented in one language at a time.

Authored Content (HTML): Authors can ensure that content meets this criterion. Authors can set the language for individual phrases within content using the edit HTML code option.

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

  • 9.3.2.1 (Web)
  • 10.3.2.1 (Non-web document)
  • 11.3.2.1 (Open Functionality Software)
  • 11.3.2.1 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)

Web: Supports

Authored Content (HTML): Supports

Web: Components do not initiate a change of context when focused.

Authored Content (HTML): In the default configuration, interactive components provided for authors do not initiate a change of context on focus.

3.2.2 On Input (Level A)

Also applies to:
EN 301 549 Criteria

  • 9.3.2.2 (Web)
  • 10.3.2.2 (Non-web document)
  • 11.3.2.2 (Open Functionality Software)
  • 11.3.2.2 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)

Web: Supports

Authored Content (HTML): Supports

Web: Changes of context do not occur automatically on user input.

Authored Content (HTML): Authors can ensure that 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)
Also applies to:
EN 301 549 Criteria

  • 9.3.2.3 (Web)
  • 10.3.2.3 (Non-web document) – Does not apply
  • 11.3.2.3 (Open Functionality Software) – Does not apply
  • 11.3.2.3 (Closed Software) – Does not apply
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software) – Does not apply to non-web software
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs) – Does not apply to non-web docs

Web: Supports

Authored Content (HTML): Supports

Web: When navigational mechanisms are repeated in the product, they occur in a consistent relative order.

Authored Content (HTML): Authors can ensure that the navigational mechanisms they use on the form are consistent.

3.2.4 Consistent Identification (Level AA)
Also applies to:
EN 301 549 Criteria

  • 9.3.2.4 (Web)
  • 10.3.2.4 (Non-web document) – Does not apply
  • 11.3.2.4 (Open Functionality Software) – Does not apply
  • 11.3.2.4 (Closed Software) – Does not apply
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software) – Does not apply to non-web software
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs) – Does not apply to non-web docs

Web: Supports

Authored Content (HTML): Supports

Web: Components with the same functionality, such as the checkmark button to approve changes, are identified consistently.

Authored Content (HTML): Authors can ensure that components with the same functionality are identified consistently in a set of pages.

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

  • 9.3.3.1 (Web)
  • 10.3.3.1 (Non-web document)
  • 11.3.3.1.1 (Open Functionality Software)
  • 11.3.3.1.2 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)

Web: Supports

Authored Content (HTML): Supports

Web: Where input errors are automatically detected, such as when required fields are not filled out when editing forms, items in error are identified and error messages are provided as hoverable tooltips.

Authored Content (HTML): Authors can ensure that content meets this criterion.

3.3.2 Labels or Instructions (Level A)

Also applies to:
EN 301 549 Criteria

  • 9.3.3.2 (Web)
  • 10.3.3.2 (Non-web document)
  • 11.3.3.2 (Open Functionality Software)
  • 11.3.3.2 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)

Web: Partially Supports

Authored Content (HTML): Supports

Web: Labels are provided for most input fields.  Exceptions include:

  • Some controls and form fields are missing meaningful labels.

Authored Content (HTML): Authors can ensure that content meets this criterion.

3.3.3 Error Suggestion (Level AA)
Also applies to:
EN 301 549 Criteria

  • 9.3.3.3 (Web)
  • 10.3.3.3 (Non-web document)
  • 11.3.3.3 (Open Functionality Software)
  • 11.3.3.3 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)

Web: Partially Supports

Authored Content (PDF): Supports

Web: Where input errors are automatically detected, such as form fields using invalid characters, suggestions for correction are provided to the user when possible. Some text for descriptions and suggestions may be vague.

Authored Content (HTML): Authors can add functionality to provide error suggestions. Note: Providing error suggestion functionality may require editing of the page source code or configuration of component editors.

3.3.4 Error Prevention (Legal, Financial, Data) (Level AA)
Also applies to:
EN 301 549 Criteria

  • 9.3.3.4 (Web)
  • 10.3.3.4 (Non-web document)
  • 11.3.3.4 (Open Functionality Software)
  • 11.3.3.4 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)

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): Authors can ensure that content meets this criterion. Authors can add scripted functionality to conform to this requirement. Note: Providing the scripted functionality may require editing of the page source code or configuration of component editors.

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

  • 9.4.1.1 (Web)
  • 10.4.1.1 (Non-web document)
  • 11.4.1.1.1 (Open Functionality Software)
  • 11.4.1.1.2 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)

Web: Partially Supports

Authored Content (HTML): Partially Supports

Web: In most cases, parsing errors in embedded markup were not present.  Exceptions include:

  • In some cases, elements are present with non-unique ID attributes.

Authored Content (HTML): In most cases, parsing errors in embedded markup were not present in authored content. In tested authored content, elements were present with non-unique ID attributes. Conforming documents can be created using the product. Note: Production of conforming documents may require editing of the page source code or configuration of component editors.

4.1.2 Name, Role, Value (Level A)

Also applies to:
EN 301 549 Criteria

  • 9.4.1.2 (Web)
  • 10.4.1.2 (Non-web document)
  • 11.4.1.2.1 (Open Functionality Software)
  • 11.4.1.2.2 (Closed Software)
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508

  • 501 (Web)(Software)
  • 504.2 (Authoring Tool)
  • 602.3 (Support Docs)

Web: Does Not Support

Authored Content (HTML): Partially Supports

Web: The name, role, state, and value of some controls is exposed to assistive technology. Many user interface controls do not have accessible names or do not have role or state properties exposed. Examples include:

  • Form fields are missing valid labels.
  • Simulated controls are missing ARIA attributes necessary to facilitate or allow screen reader understanding and interaction.

Authored Content (HTML): Authors can accessibly provide the name, role, state, and value of most controls in authored content. (Note: Providing Name, Role and State information for some interactive elements may require editing of the page source code or configuration of component editors.)  Exceptions include:

  • Some authored content elements do not accessibly provide necessary name, role, state, and value information by default. Simulated controls in authored content are missing necessary ARIA. For example, the “spinbutton” element is missing necessary aria-valuemin and aria-valuemax attributes.
  • Some issues with entering date format in Date Picker.
  • Drop-down list does not give state information.

4.1.3 Status Messages (Level AA 2.1 only)
Also applies to:
EN 301 549 Criteria

  • 9.4.1.3 (Web)
  • 10.4.1.3 (Non-web document) – Does not apply
  • 11.4.1.3 (Open Functionality Software) – Does not apply
  • 11.4.1.3 (Closed Software) – Does not apply
  • 11.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508 – Does not apply

Web: Does Not Support

Authored Content (HTML): Partially Supports

Web: Status messages do not announce their content to assistive technology.

Authored Content (HTML): Authors can ensure that content meets this criterion.

  • Information for “Saved Successfully” not passed to assistive technology.
  • Accessibility issues with Signature step.
  • No message announced for Reset, Save, and Submit buttons.

 

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): Partially Supports

Web: While some functionality and content can be accessed without vision, most core production functionality cannot be accomplished without vision, due to the following exceptions:

  • As described in 1.1.1 Non-text Content, images have non-meaningful text alternatives.
  • As described in 1.3.1 Info and Relationships, form fields are missing valid labels.
  • As described in 1.3.2 Meaningful Sequence, the reading order of some content does not match its visual order.
  • As described in 1.4.1 Use of Color, some information is communicated only through color.
  • As described in 2.1.1 Keyboard, a significant amount of functionality is only available through the use of a mouse.
  • As described in 2.1.2 Keyboard Trap, keyboard traps are present.
  • As described in 2.4.1 Bypass Blocks, no mechanism is present to bypass repeated navigation content.
  • As described in 2.4.2 Page Titled, most pages lack unique titles.
  • As described in 2.4.3 Focus Order, the focus order of some active elements does not match their visual order.
  • As described in 2.4.4 Link Purpose, some links and buttons are not meaningful within context.
  • As described in 2.5.1 Pointer Gestures, path-based gestures are required to access some functionality.
  • As described in 3.2.2 On Input, some input causes unexpected shifts of focus.
  • As described in 3.3.2 Labels or Instructions, some form fields and controls are missing visual labels.
  • As described in 4.1.1 Parsing, elements with non-unique ID attributes were present.
  • As described in 4.1.2 Name, Role, Value, simulated controls do not provide necessary ARIA for screen reader comprehension and interaction.

Authored Content (HTML): Authors can create content that is mostly accessible to users without vision.  Exceptions include:

  • As described in 1.1.1 Non-text Content, authors cannot accessibly convey some image content. 
  • As described in 1.3.1 Info and Relationships, authors cannot create accessible fieldsets.
  • As described in 2.4.1 Bypass Blocks, authors cannot provide a mechanism for users to bypass repeated navigation content.
  • As described in 4.1.1 Parsing, elements with non-unique ID attributes were present in authored content tested.
  • As described in 4.1.2 Name, Role, Value, some authored content elements do not provide accessible name, role, state, and value information.

302.2 With Limited Vision

Web: Partially Supports

Authored Content (HTML): Partially Supports

Web: Parts of the product are functional for users with limited vision, but other parts are inaccessible to these users. These exceptions include:

  • As described in 1.1.1 Non-text Content, images have non-meaningful text alternatives.
  • As described in 1.4.1 Use of Color, some information is communicated only through color.
  • As described in 1.4.3 Contrast (minimum), some text and background colors do not meet minimum contrast requirements.

Authored Content (HTML): Authors can create content that is mostly accessible to users with limited vision.  Exceptions include:

  • As described in 1.1.1 Non-text Content, authors cannot accessibly convey some image content.

302.3 Without Perception of Color

Web: Partially Supports

Authored Content (HTML): Supports

Web: Most of the product does not rely solely on color to communicate information. Exceptions include:

  • As described in 1.4.1 Use of Color, some information is communicated only through color.

Authored Content (HTML): Authors can create content which is functional for users without 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): Authors can create content that 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): Authors can create content that 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): Authors can create content that does not require the use of speech.

302.7 With Limited Manipulation

Web: Does Not Support

Authored Content (HTML): Partially Supports

Web: While some functionality and content can be accessed with limited manipulation, most core production functionality cannot be accomplished by these users, due to the following exceptions:

  • As described in 2.1.1 Keyboard, a significant amount of functionality is only available through the use of a mouse.
  • As described in 2.1.2 Keyboard Trap, keyboard traps are present.
  • As described in 2.4.1 Bypass Blocks, no mechanism is present to bypass repeated navigation content.
  • As described in 2.4.3 Focus Order, the focus order of some active elements does not match their visual order.
  • As described in 2.4.7 Focus Visible, some active elements do not exhibit a visual indication or focus.
  • As described in 3.2.2 On Input, some input causes unexpected shifts of focus.

Authored Content (HTML): Authors can create content that is mostly accessible to users with limited manipulation. Exceptions include:

  • As described in 2.4.1 Bypass Blocks, authors cannot provide a mechanism for users to bypass repeated navigation content.

302.8 With Limited Reach and Strength

Web: Does Not Support

Authored Content (HTML): Partially Supports

Web: While some functionality and content can be accessed with limited reach and strength, most core production functionality cannot be accomplished by these users, due to the following exceptions:

  • As described in 2.1.1 Keyboard, a significant amount of functionality is only available through the use of a mouse.
  • As described in 2.1.2 Keyboard Trap, keyboard traps are present.
  • As described in 2.4.1 Bypass Blocks, no mechanism is present to bypass repeated navigation content.
  • As described in 2.4.3 Focus Order, the focus order of some active elements does not match their visual order.
  • As described in 2.4.7 Focus Visible, some active elements do not exhibit a visual indication or focus.
  • As described in 3.2.2 On Input, some input causes unexpected shifts of focus.

Authored Content (HTML): Authors can create content that is mostly accessible to users with limited manipulation. Exceptions include:

  • As described in 2.4.1 Bypass Blocks, authors cannot provide a mechanism for users to bypass repeated navigation content.

302.9 With Limited Language, Cognitive, and Learning Abilities

Web: Partially Supports

Authored Content (HTML): Partially 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 templates for assistance creating content and help documentation is available. Some users may have difficulty, in part due to the following issues:

  • As described in 2.4.2 Page Titled, most pages lack unique titles.
  • As described in 2.4.4 Link Purpose, some links and buttons are not meaningful within context.
  • As described in 3.3.2 Labels or Instructions, some form fields and controls are missing visual labels.

Authored Content (HTML): Authors can create content which is functional for users with limited language, cognitive, and learning abilities.

Chapter 4: Hardware

Notes: Not Applicable

 

Chapter 5: Software

Notes: 501-503 are not applicable to a web-based product.

 

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

See information in WCAG 2.x section.

504.2.1 Preservation of Information Provided for Accessibility in Format Conversion

Supports

When converting authored content to HTML, the product preserves accessibility information provided in its editor.

504.2.2 PDF Export

Not Applicable

The product does not export PDF files.

504.3 Prompts

Does Not Support

Most authoring functions do not prompt authors to create content which conforms to WCAG 2.0 Levels A and AA.

504.4 Templates

Partially Supports

Templates in the product enable authors to create HTML forms. For most of these kinds of content, the product enables authors to create content which conforms to WCAG 2.0 Levels A and AA. Exceptions include:

  • As described in 1.1.1 Non-text Content, authors cannot accessibly convey some image content.
  • As described in 1.3.1 Info and Relationships, authors cannot create accessible fieldsets.
  • As described in 2.4.1 Bypass Blocks, authors cannot provide a mechanism for users to bypass repeated navigation content.
  • As described in 4.1.1 Parsing, elements with non-unique ID attributes were present in authored content tested.
  • As described in 4.1.2 Name, Role, Value, some authored content elements do not provide accessible name, role, state, and value information.

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: 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): Partially Supports

Web: While some functionality and content can be accessed without vision, most core production functionality cannot be accomplished without vision, due to the following exceptions:

  • As described in 1.1.1 Non-text Content, images have non-meaningful text alternatives.
  • As described in 1.3.1 Info and Relationships, form fields are missing valid labels.
  • As described in 1.3.2 Meaningful Sequence, the reading order of some content does not match its visual order.
  • As described in 1.4.1 Use of Color, some information is communicated only through color.
  • As described in 2.1.1 Keyboard, a significant amount of functionality is only available through the use of a mouse.
  • As described in 2.1.2 Keyboard Trap, keyboard traps are present.
  • As described in 2.4.1 Bypass Blocks, no mechanism is present to bypass repeated navigation content.
  • As described in 2.4.2 Page Titled, most pages lack unique titles.
  • As described in 2.4.3 Focus Order, the focus order of some active elements does not match their visual order.
  • As described in 2.4.4 Link Purpose, some links and buttons are not meaningful within context.
  • As described in 2.5.1 Pointer Gestures, path-based gestures are required to access some functionality.
  • As described in 3.2.2 On Input, some input causes unexpected shifts of focus.
  • As described in 3.3.2 Labels or Instructions, some form fields and controls are missing visual labels.
  • As described in 4.1.1 Parsing, elements with non-unique ID attributes were present.
  • As described in 4.1.2 Name, Role, Value, simulated controls do not provide necessary ARIA for screen reader comprehension and interaction.
  • As described in 4.1.3 Status Messages, status messages do not receive focus or announce their content to assistive technology.

Authored Content (HTML): Authors can create content that is mostly accessible to users without vision.  Exceptions include:

  • As described in 1.1.1 Non-text Content, authors cannot accessibly convey some image content.
  • As described in 1.3.1 Info and Relationships, authors cannot create accessible fieldsets.
  • As described in 2.1.1 Keyboard, several components typical of authored content are not fully accessible to keyboard users.
  • As described in 2.4.1 Bypass Blocks, authors cannot provide a mechanism for users to bypass repeated navigation content.
  • As described in 4.1.1 Parsing, elements with non-unique ID attributes were present in authored content tested.
  • As described in 4.1.2 Name, Role, Value, some authored content elements do not provide accessible name, role, state, and value information.

4.2.2 Usage with limited vision

Web: Partially Supports

Authored Content (HTML): Partially Supports

Web: Parts of the product are functional for users with limited vision, but other parts are inaccessible to these users. These exceptions include:

  • As described in 1.1.1 Non-text Content, images have non-meaningful text alternatives.
  • As described in 1.4.1 Use of Color, some information is communicated only through color.
  • As described in 1.4.3 Contrast (minimum), some text and background colors do not meet minimum contrast requirements.
  • As described in 1.4.10 Reflow, some content does not reflow appropriately.

Authored Content (HTML): Authors can create content that is mostly accessible to users with limited vision.  Exceptions include:

  • As described in 1.1.1 Non-text Content, authors cannot accessibly convey some image content.
  • As described in 1.4.13 Content on Hover or Focus, content tested that was triggered by hover or focus was neither dismissable nor hoverable.

4.2.3 Usage without perception of colour

Web: Partially Supports

Authored Content (HTML): Supports

Web: Most of the product does not rely solely on color to communicate information.  Exceptions include:

  • As described in 1.4.1 Use of Color, some information is communicated only through color.

Authored Content (HTML): Authors can create content which is functional for users without 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): Authors can create content that 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): Authors can create content that 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 hearing.

Authored Content (HTML): Authors can create content that does not require the use of hearing.

4.2.7 Usage with limited manipulation or strength

Web: Does Not Support

Authored Content (HTML): Partially Supports

Web: While some functionality and content can be accessed with limited manipulation or strength, most core production functionality cannot be accomplished by these users, due to the following exceptions:

  • As described in 2.1.1 Keyboard, a significant amount of functionality is only available through the use of a mouse.
  • As described in 2.1.2 Keyboard Trap, keyboard traps are present.
  • As described in 2.4.1 Bypass Blocks, no mechanism is present to bypass repeated navigation content.
  • As described in 2.4.3 Focus Order, the focus order of some active elements does not match their visual order.
  • As described in 2.4.7 Focus Visible, some active elements do not exhibit a visual indication or focus.
  • As described in 2.5.1 Pointer Gestures, path-based gestures are required to access some functionality.
  • As described in 3.2.2 On Input, some input causes unexpected shifts of focus.

Authored Content (HTML): Authors can create content that is mostly accessible to users with limited manipulation.  Exceptions include:

  • As described in 1.4.13 Content on Hover or Focus, content tested that was triggered by hover or focus was neither dismissable nor hoverable.
  • As described in 2.1.1 Keyboard, several components typical of authored content are not fully accessible to keyboard users.
  • As described in 2.4.1 Bypass Blocks, authors cannot provide a mechanism for users to bypass repeated navigation content.

4.2.8 Usage with limited reach

Web: Does Not Support

Authored Content (HTML): Partially Supports

Web: While some functionality and content can be accessed with limited reach, most core production functionality cannot be accomplished by these users, due to the following exceptions:

  • As described in 2.1.1 Keyboard, a significant amount of functionality is only available through the use of a mouse.
  • As described in 2.1.2 Keyboard Trap, keyboard traps are present.
  • As described in 2.4.1 Bypass Blocks, no mechanism is present to bypass repeated navigation content.
  • As described in 2.4.3 Focus Order, the focus order of some active elements does not match their visual order.
  • As described in 2.4.7 Focus Visible, some active elements do not exhibit a visual indication or focus.
  • As described in 2.5.1 Pointer Gestures, path-based gestures are required to access some functionality.
  • As described in 3.2.2 On Input, some input causes unexpected shifts of focus.

Authored Content (HTML): Authors can create content that is mostly accessible to users with limited manipulation.  Exceptions include:

  • As described in 1.4.13 Content on Hover or Focus, content tested that was triggered by hover or focus was neither dismissable nor hoverable.
  • As described in 2.1.1 Keyboard, several components typical of authored content are not fully accessible to keyboard users.
  • As described in 2.4.1 Bypass Blocks, authors cannot provide a mechanism for users to bypass repeated navigation content.

4.2.9 Minimize photosensitive seizure triggers

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.

4.2.10 Usage with limited cognition

Web: Partially Supports

Authored Content (HTML): Partially 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 templates for assistance creating content and help documentation is available. Some users may have difficulty, in part due to the following issues:

  • As described in 2.4.2 Page Titled, most pages lack unique titles.
  • As described in 2.4.4 Link Purpose, some links and buttons are not meaningful within context.
  • As described in 3.3.2 Labels or Instructions, some form fields and controls are missing visual labels.

Authored Content (HTML): Authors can create content which is functional for users with limited language, cognitive, and learning abilities. However, one exception exists:

  • As described in 1.3.5 Identify Input Purpose, authors cannot ascribe every possible autocomplete value to form fields.

4.2.11 Privacy

Web: Supports

Authored Content (HTML): Supports

Web: The product does not ask for legal, financial, or personal data.

Authored Content (HTML): Authors can create content which does not ask for legal, financial, or personal data.

Chapter 5: Generic Requirements

Notes: 5.1.2.2-5.1.62 are not applicable for a web-based product

Criteria

Conformance Level

Remarks and Explanations

5.2 Activation of accessibility features

Partially Supports

The product does not provide accessibility features for authors; however, incorporating accessibility into authored content is not available to all users who would benefit from such accessibility. For example, users who are blind may not be able to add appropriate text alternatives to authored content.

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

Supports

When converting authored content to HTML, the product preserves accessibility information provided in its editor.

5.5.1 Means of operation

Not Applicable

The product does not have operable parts that require grasping, pinching, or twisting of the wrist to operate.

5.5.2 Operable parts discernibility

Not Applicable

The product does not have operable parts.

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)

 

Chapter 10: Non-web Documents

Notes:

 

Chapter 11: Software

Notes: 11.1.1.1-11.7 are not applicable to a web-based product.

Criteria

Conformance Level

Remarks and Explanations

11.8.2 Accessible content creation

See WCAG 2.x section

See information in WCAG 2.x section.

11.8.3 Preservation of accessibility information in transformations

Supports

When converting authored content to HTML, the product preserves accessibility information provided in its editor.

11.8.4 Repair assistance

Does Not Support

Most authoring functions do not prompt authors to fix content so that it conforms to WCAG 2.0 Levels A and AA.

11.8.5 Templates

Partially Supports

Templates in the product enable authors to create HTML forms. For most of these kinds of content, the product enables authors to create content which conforms to WCAG 2.0 Levels A and AA. Exceptions include:

  • As described in 1.1.1 Non-text Content, authors cannot accessibly convey some image content.
  • As described in 1.3.1 Info and Relationships, authors cannot create accessible fieldsets.
  • As described in 1.3.5 Identify Input Purpose, authors cannot ascribe every possible autocomplete value to form fields.
  • As described in 1.4.13 Content on Hover or Focus, content tested that was triggered by hover or focus was neither dismissable nor hoverable.
  • As described in 2.1.1 Keyboard, several components typical of authored content are not fully accessible to keyboard users.
  • As described in 2.4.1 Bypass Blocks, authors cannot provide a mechanism for users to bypass repeated navigation content.
  • As described in 4.1.1 Parsing, elements with non-unique ID attributes were present in authored content tested.
  • As described in 4.1.2 Name, Role, Value, some authored content elements do not provide accessible name, role, state, and value information.

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)