Adobe Accessibility Conformance Report

International Edition

(Based on VPAT® Version 2.4)

Product Information

Name of Product/Version: Adobe Portfolio
Product Description: With Adobe Portfolio, a user can build a website quickly and simply to showcase creative work using variety of layouts.
Report Date: December 2020
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 Portfolio involved extensive use of leading assistive technologies 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

Level A (Yes)

Level AA (Yes)

Level AAA (No)

Web Content Accessibility Guidelines 2.1

Level A (Yes)

Level AA (Yes)

Level AAA (No)

Revised Section 508 standards published January 18, 2017 and corrected January 22, 2018  

(Yes)

EN 301 549 Accessibility requirements suitable for public procurement of ICT products and services in Europe, - V3.1.1 (2019-11)

(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

Documents conformance with:

  • EN 301 549:  Chapter 9 - Web, Sections 10.1-10.4 of Chapter 10 - Non-Web documents, and Sections 11.1-11.4 and 11.8.2 of Chapter 11 - Non-Web Software (open and closed functionality), and Sections 12.1.2 and 12.2.4 of Chapter 12 – Documentation
  • Revised Section 508: Chapter 5 – 501.1 Scope, 504.2 Content Creation or Editing, and Chapter 6 – 602.3 Electronic Support Documentation.

Note: When reporting on conformance with the WCAG 2.x Success Criteria, they are scoped for full pages, complete processes, and accessibility-supported ways of using technology as documented in the WCAG 2.0 Conformance Requirements.

Guideline 1.1 Text Alternatives:

Provide text alternatives for any non-text content so that it can be changed into other forms people need, such as large print, braille, speech, symbols or simpler language.

Criteria

Conformance Level

Remarks and Explanations

1.1.1 Non-text Content (Level A)
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.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 (Web): Partially Supports

Web: The product does not provide sufficient text alternatives for most non-text content. Examples include:

  • Multiple images lack alternative text, such as SVG elements used for many icons in the left panel.
  • Image buttons and links lack meaningful accessible names, such as the Account button in the left panel.

Authored Content (Web): Authors can provide text alternatives for most images. Exceptions include:

  • Images with alternative text on other pages used as image links on the homepage do not provide alternative text. 

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.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 (Web): Does Not Support

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

Authored Content (Web): The product does not allow authors to provide audio description or transcripts for video-only media imported by users, and the product does not allow authors to provide transcripts for audio-only media.

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.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 (Web): Supports

Web: The product does not contain prerecorded synchronized media.

Authored Content (Web): Authors can create open captions for audio content in video.

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.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 (Web): Supports

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

Authored Content (Web): Authors can provide open audio description for video.

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.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 (Web): Supports 

Web: The product does not contain live synchronized media.

Authored Content (Web): Authored content does not contain live synchronized media.

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

  • 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.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 (Web): Supports 

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

Authored Content (Web): Authors can provide open audio description for video. 

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 AA)
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.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 (Web): Does Not Support

Web: Some structure and relationship information, such as some headings and labels for form fields, is provided through element semantics. However, most structure and relationship information is not provided programmatically or in text. Examples include:

  • Multiple buttons lack proper labels, such as those used in the left panel of the editor. 
  • Form fields, such as those used when creating a new page, or radio buttons in left panel, lack valid labels. 
  • Form fields in groups, such as radio button groups in the left panel, do not convey their group label. 
  • Some pages use visual cues, such as larger or bold text to indicate section headings, without proper markup.
  • Heading elements on some pages do not properly convey the visual page hierarchy. 
  • Content that is visually hidden, such as hidden controls in the Editor UI, is available to assistive technology.
  • Dialogs, such as the New page dialog, lack proper structure. 

Authored Content (Web): The product does not allow authors to provide appropriate programmatic or textual equivalents for most visual structure and relationship information, such as: 

  • Inline error messages in Contact Us authored content is not explicitly associated with the fields in error. 
  • Some headings in the Authored content are not rendered with proper markup. 
  • Form fields, such as those used in the Contact Us form, lack valid labels. 

1.3.2 Meaningful Sequence (Level AA)
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.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 (Web): Supports

Web: The product presents content in a meaningful sequence.

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

1.3.3 Sensory Characteristics (Level AA)
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.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 (Web): Supports

Web: Instructions do not rely solely on sensory characteristics.

Authored Content (Web): 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.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508 – Does not apply

Web: Supports

Authored Content (Web): Supports

Web: Content does not restrict its view and operation to a single display orientation.

Authored Content (Web): 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.5 (Non-web document)
  • 11.1.3.5.1 (Open Functionality 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 (Web): Does Not Support

Web: The product contains input fields that collect information about the user and programmatically conveys their purpose.

Authored Content (Web): When input fields that collect information about the user are rendered in authored content, such as name and email address in the Contact Us form, they do not programmatically convey their purpose. 

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.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 (Web): Supports

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

  • Color is used to indicate selection, such as the selected element in the left navigation and the selected platform when viewing the created site in desktop, tablet or mobile view.

Authored Content (Web): 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.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 (Web): Supports

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

Authored Content (Web): Authored content does not contain audio that plays automatically.

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.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 (Web): Supports

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

  • The light blue text over darker blue background used in the global header of the Portfolio site. 
  • Light gray text over white background such as the “Start building your page” instruction in the editor or warning messages found in the left panel. 
  • White text used on green background for the “Update Live Site” button in the editor. 

Authored Content (Web): Authors can ensure that text meets contrast requirements.

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.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 (Web): Supports

Web: The product allows browser zoom to resize text up to 200 percent without loss of content or functionality for most of its content. Exceptions include:

  • Some pages do not allow content to be resized in mobile view, such as using pinch and zoom.
  • Some content, such as part of the New Page dialog, is lost when text is resized. 

Authored Content (Web): Using browser zoom, text can be resized up to 200 percent without loss of content or 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.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 (Web): Supports

Web: The product uses text instead of images of text.

Authored Content (Web):  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 (Open Functionality 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 (Web): Supports

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

  • Content is lost in some pages, such as the theme view page.
  • Parts of dialogs are no longer visible, such as the New Page dialog.
  • The Editor’s left panel becomes garbled.

Authored Content (Web): At the required width of 320 CSS pixels, authored content is presented without loss of information or functionality.

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.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 (Web): Supports

Web: Most meaningful non-text content elements, such as the Add New Page control or sliders in the left panel, have sufficient contrast. Exceptions include:

  • The light gray on white used for controls, such as the Back icon in the left panel to navigate back to previous options. 
  • The gray platform controls over the darker gray background in the Preview page

Authored Content (Web): 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.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 (Web): Supports

Web: Most functions of the product support the required text style properties without loss of content or functionality. Exceptions include:

  • The banner in the Home page is cropped when text spacing is applied.

Authored Content (Web): 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.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508 – Does not apply

Web: Supports

Authored Content (Web): Supports

Web: The product does not contain elements triggered by hover or focus.

Authored Content (Web): Authored content does not contain elements triggered by hover or focus.

Guideline 2.1 Keyboard Accessible:

Make all functionality available from a keyboard.

Criteria

Conformance Level

Remarks and Explanations

2.1.1 Keyboard (Level A)
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.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 (Web): Partially Supports

Web: Most product functionality cannot be operated through a keyboard interface. Examples include:

  • Links in the footer area of the main website are not keyboard accessible. 
  • The Change Region modal dialog is not keyboard accessible. 
  • There is drag-and-drop functionality in the Editor that does not have equivalent keyboard access. 
  • Multiple custom controls, such as ones used in the left panel, the Add a Page icon and Back icon, the platform selection icons, and the pencil icons to edit the containers in the Editor. 
  • Focus is not properly redirected to updated content or dialogs. For example, focus remains on the Preview page when the published content is displayed. 

Authored Content (Web): Authored content can be made keyboard accessible for the most part. Exceptions include:

  • The Play button in videos rendered in authored content is not keyboard accessible. 
  • The Submit button in the Contact Form authored content lacks keyboard access. 

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.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 (Web): Supports

Web: The product does not include keyboard traps.

Authored Content (Web): Authored content does not include keyboard traps.

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.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508 – Does not apply

Web: Supports

Authored Content (Web): Supports

Web: The product does not provide character key shortcuts.

Authored Content (Web): 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.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 (Web): Supports

Web: Users are logged out without warning. The product does not provide a mechanism to adjust or cancel the time limit.

Authored Content (Web): Authored content does not include time limits.

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.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 (Web): Supports

Web: The product does not include elements which move, blink, scroll, or auto-update.

Authored Content (Web): 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.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 (Web): Supports

Web: The product does not contain flashing content.

Authored Content (Web): 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.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: Partially Supports

Authored Content (Web): Partially Supports

Web: The product provides headings, which allows assistive technology users to bypass repeated blocks, such as the top navigation links. However, for users without assistive technology, a bypass mechanism is not provided.

Authored Content (Web): Authors can implement semantic structures, such as headings, for assistive technology users to bypass repeated blocks. However, the product does not enable authors to provide bypass mechanisms, such as skip links, for users without assistive technology.

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.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 (Web): Supports

Web: The titles of most pages describe their purpose. Exceptions include:

  • Some pages, such as the Theme Review page and the Preview page, do not have meaningful titles that describe their purpose. 

Authored Content (Web): The product allows authors to customize the page title.

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.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 (Web): Supports

Web: Components receive focus in a meaningful order.

Authored Content (Web): 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.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 (Web): Partially Supports

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

  • The Adobe Portfolio image link in the global header lacks meaningful link text.
  • Sample Sites link text in the home page is not meaningful. 

Authored Content (Web): The purpose of most links in the authored content can be determined from the link text alone or from the programmatic context of the link. Exceptions include: 

  • Social media image links and the Back to Top image link lack meaningful accessible names.

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.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 (Web): Supports

Web: Users can locate web pages in the product through navigation links.

Authored Content (Web): Authors can provide more than one way to locate a page in a set of pages, such as navigation links.

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.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 (Web): Supports

Web: Headings and labels are descriptive.

Authored Content (Web): 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.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 (Web): Does Not Support

Web: Focusable elements do not have a visible keyboard focus indicator.

Authored Content (Web): Authored content focusable elements do not have a visible keyboard focus indicator. 

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.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508 – Does not apply

Web: Supports

Authored Content (Web): Supports

Web: The product does not rely on multipoint or path-based gestures.

Authored Content (Web): Authored content does not rely on multipoint or path-based gestures.

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.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508 – Does not apply

Web: Supports

Authored Content (Web): Supports

Web: Product functions that use a single pointer are completed when the user releases the pointer.

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

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.1 (Open Functionality 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 (Web): Does Not Support

Web: The accessible names of controls, such as the Update Live Site button, contain the text of their visible labels.

Authored Content (Web): In most authored content functions, user interface components do not provide programmatic name information.

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.8.2 (Authoring Tool)
  • 12.1.2 (Product Docs)
  • 12.2.4 (Support Docs)

Revised Section 508 – Does not apply

Web: Supports

Authored Content (Web): Supports

Web: The product does not have functionality operated by device motion or user motion.

Authored Content (Web): Authored content does not have functionality operated by device motion or user motion.

Guideline 3.1 Readable:

Make text content readable and understandable.

Criteria

Conformance Level

Remarks and Explanations

3.1.1 Language of Page (Level A)
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.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 (Web): Does Not Support

Web: The language is programmatically determinable within the product.

Authored Content (Web): The product does not allow authors to set the language of the page.

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.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 (Web): Does Not Support

Web: When content is presented in another language, the change is not programmatically determined:

  • The change of language in the Change Your Region dialog is not programmatically conveyed.

Authored Content (Web): The product does not allow 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.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.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 (Web): Supports

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

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

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.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 (Web): Supports

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

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

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.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 (Web): Supports

Web: When navigational mechanisms are repeated in the product, such as the top navigation and footer navigation, they occur in a consistent relative order.

Authored Content (Web): Navigational mechanisms are repeated in the same relative order in a set of pages.

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.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 (Web): Supports

Web: Components with the same functionality are identified consistently.

Authored Content (Web): 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.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 (Web): Supports

Web: Where input errors are automatically detected, such as in the New Page form, items in error are identified and error messages are provided as inline messages.

Authored Content (Web): Forms in authored content, such as the Contact Us form, identify items in error and error messages are provided as inline messages. 

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.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 (Web): Supports

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

  • Some form fields lack on-screen labels, such as the Page Title Edit field when creating a new page. 
  • Some form fields lack their group labels as part of their accessible names, such as groups of buttons for different styles or alignment.  

Authored Content (Web): 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.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 (Web): Supports

Web: Where input errors are automatically detected, such as New Page form, suggestions for correction are provided to the user.

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

  • 9.3.3.4 (Web)
  • 10.3.3.4 (Non-web document)
  • 11.3.3.4 (Open 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: Supports

Authored Content (Web): Supports

Web: The product does not process legal commitments or financial transactions. When editing pages, changes to user-controllable data are reversible or can be confirmed before finalizing.

Authored Content (Web): Authored content does not contain legal or financial data and does not modify user-controllable data.

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.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 (Web): Supports

Web: In most product functions, elements have complete start and end tags, elements are nested according to their specifications, elements do not contain duplicate attributes, and any IDs are unique. Exceptions include:

  • Some elements have duplicate IDs.

Authored Content (Web): Elements have complete start and end tags, elements are nested according to their specifications, elements do not contain duplicate attributes, and any IDs are unique.

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

Web: User interface components in most product functions do not provide programmatic name, role, state, or value information. Examples include:

  • Multiple custom controls, such as the various actionable icons and expandable section the Editor’s left panel, do not convey the proper name, role or state information.
  • Multiple buttons and form elements lack meaningful accessible names.
  • Dialogs, such as the New Page dialog, lack proper structure.
  • Frame elements, such as the one that contains the themes demo when starting a portfolio, do not have informative titles.
  • Content updates when browsing through themes is not communicated to screen reader users.
  • In some instances, ARIA attributes are used incorrectly, such as the Global Application control implemented as a menu button without the attached menu.

Authored Content (Web): Authored content renders some controls that do not provide the proper role information. Example includes:

  • The Submit button in the authored content’s Contact Us form lacks the proper role.
  • Form fields do not programmatically render their labels as accessible names.

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)
  • 11.4.1.3 (Open Functionality 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 (Web): Supports

Web: The product does not contain status messages.

Authored Content (Web): Authored content does not contain status messages.

 

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 (Web): Does Not Support

Web: Most functions of the product are not usable without vision. Examples include:

  • As noted in 1.1.1 Non-text Content, images lack informative alternative text and image links and image buttons do not describe their purpose properly.
  • As noted in 1.3.1 Info and Relationships, heading structure is not properly conveyed, form fields lack meaningful accessible labels, form field errors are not properly rendered or associated to the fields in error, and visually hidden content is available to screen reader users.
  • As noted in 2.1.1 Keyboard, some actionable elements are not keyboard accessible, some functionality is not available with the keyboard and focus is not properly redirected to the right places.
  • As noted in 2.2.1 Timing, users are logged out without warning.
  • As noted in 2.4.1 Bypass Blocks, there is no link to skip past navigation links.
  • As noted in 2.4.2 Page Titled, some pages lack meaningful titles.
  • As noted in 2.4.4 Link Purpose (In Context), multiple links and image links lack meaningful accessible names.
  • As noted in 3.1.2 Language of Parts, change in language is not programmatically conveyed.
  • As noted in 3.3.2 Labels and Instructions, some form fields lack proper labels.
  • As noted in 4.1.1 Parsing, multiple elements have duplicate IDs.
  • As noted in 4.1.2 Name, Role, Value, multiple custom controls do not provide the proper name, role and state information, form fields lack accessible names, frames lack meaningful titles and dialogs do not convey their structure programmatically. 

Authored Content (Web): The product does not allow authors to create content which is functional for users without vision. Examples include:

  • As noted in 1.3.1 Info and Relationships, headings are not rendered with proper markup, form fields lack valid labels, and error messages are not properly associated with the fields in error. 
  • As noted in 2.1.1 Keyboard, some actionable elements are not keyboard accessible.
  • As noted in 2.4.1 Bypass Blocks, the authored content does not provide a mechanism to skip past repetitive links.
  • As noted in 2.4.4 Link Purpose (In Context), some image links lack meaningful accessible names.
  • As noted in 3.1.1 Language of Page, the author cannot set the language of a page.
  • As noted in 3.1.2 Language of Parts, the author cannot set the language for individual phrases.
  • As noted in 4.1.2 Name, Role, Value, some elements lack the proper role.

 

302.2 With Limited Vision

Web: Does Not Support

Authored Content (Web): Supports

Web: Most functions of the product are not usable with limited vision. Examples include:

  • As noted in 1.4.3 Contrast (Minimum), many text elements lack sufficient color contrast against the background.
  • As noted in 1.4.4 Resize Text, content does not allow text to resize in mobile view, and some content is lost when page is resized.

Authored Content (Web): Authors can create content which is functional for users with limited vision. 

302.3 Without Perception of Color

Web: Partially Supports

Authored Content (Web): Supports

Web: Most functions of the product are usable without perception of color. Exceptions include:

  • As noted in 1.4.1 Use of Color, some elements rely on color alone to indicate selection.

Authored Content (Web): Authors can create content which is functional for users without perception of color.

302.4 Without Hearing

Web: Supports

Authored Content (Web): Supports

Web: The product does not require the use of hearing.

Authored Content (Web): Authors can create content which is functional for users without hearing.

302.5 With Limited Hearing

Web: Supports

Authored Content (Web): Supports

Web: The product does not require the use of hearing.

Authored Content (Web): Authors can create content which is functional for users without hearing.

302.6 Without Speech

Web: Supports

Authored Content (Web): Supports

Web: The product does not require the use of speech.

Authored Content (Web): Authors can create content which is functional for users without speech.

302.7 With Limited Manipulation

Web: Does Not Support

Authored Content (Web): Does Not Support

Web: Most functions of the product are not usable with limited manipulation. Examples include:

  • As noted in 2.1.1 Keyboard, some actionable elements are not keyboard accessible, some functionality is not available with the keyboard and focus is not properly redirected to the right places.
  • As noted in 2.2.1 Timing, users are logged out without warning.
  • As noted in 2.4.1 Bypass Blocks, there is no link to skip past navigation links.
  • As noted in 2.4.7 Focus Visible, there is no keyboard focus indicator for actionable elements.

Authored Content (Web): Most functions of the authored content are not usable with limited manipulation. Examples include:

  • As noted in 2.1.1 Keyboard, some actionable elements are not keyboard accessible.
  • As noted in 2.4.1 Bypass Blocks, the authored content does not provide a mechanism to skip past repetitive links.
  • As noted in 2.4.7 Focus Visible, there is no keyboard focus indicator for actionable elements.

302.8 With Limited Reach and Strength

Web: Supports

Authored Content (Web): Supports

Web: The product is functional with limited reach and strength.

Authored Content (Web): Authors can create content which is functional with limited reach and strength.

302.9 With Limited Language, Cognitive, and Learning Abilities

Web: Supports

Authored Content (Web): Supports

Web: Most functions of the product are usable with limited language, cognitive, and learning abilities. Users with cognitive disabilities have varying needs for features that allow them to adapt content and work with assistive technology or accessibility features of the platform. The product provides descriptive labels and instructions. Exceptions include:

  • As noted in 2.2.1 Timing, users are logged out without warning.
  • As noted in 2.4.2 Page Titled, some pages lack meaningful title.

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

Criteria

Conformance Level

Remarks and Explanations

501.1 Scope – Incorporation of WCAG 2.0 AA

See WCAG 2.x section

See information in WCAG 2.x section.

502.2.1 User Control of Accessibility Features

Not Applicable

The product is not platform software.

502.2.2 No Disruption of Accessibility Features

Not Applicable

Not applicable to web.

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.2 User Preferences

Not Applicable

Not applicable to web.

503.3 Alternative User Interfaces

Not Applicable

Not applicable to web.

503.4.1 Caption Controls

Not Applicable

Not applicable to web.

503.4.2 Audio Description Controls

Not Applicable

Not applicable to web.

504.2 Content Creation or Editing  (if not authoring tool, enter “not applicable”)

See WCAG 2.x section

See information in WCAG 2.x section.

504.2.1 Preservation of Information Provided for Accessibility in Format Conversion

Does Not Support

When converting video content, the product does not preserve closed captions or closed audio descriptions.

504.2.2 PDF Export

Not Applicable

The product does not export PDF documents.

504.3 Prompts

Does Not Support

The product does not prompt users to create accessible content. For example, it does not prompt for alternative text when creating images. 

504.4 Templates

Does Not Support

Templates in the product do not allow authors to create content which conforms to WCAG 2.0 Levels A and AA. Examples include:

  • As noted in 1.3.1 Info and Relationships, headings are not rendered with proper markup, form fields lack valid labels, and error messages are not properly associated with the fields in error. 
  • As noted in 2.1.1 Keyboard, some actionable elements are not keyboard accessible. 
  • As noted in 2.4.4 Link Purpose (In Context), some image links lack meaningful accessible names. 
  • As noted in 2.4.7 Focus Visible, there is no keyboard focus indicator for actionable elements.
  • As noted in 3.1.1 Language of Page, the author cannot set the language of a page. 
  • As noted in 3.1.2 Language of Parts, the author cannot set the language for individual phrases. 
  • As noted in 4.1.2 Name, Role, Value, some elements lack the proper role.

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: Functional Performance Statements (FPS)

Notes:

Criteria

Conformance Level

Remarks and Explanations

4.2.1 Usage without vision

Web: Does Not Support

Authored Content (Web): Does Not Support

Web: Most functions of the product are not usable without vision. Examples include:

  • As noted in 1.1.1 Non-text Content, images lack informative alternative text and image links and image buttons do not properly describe their purpose.
  • As noted in 1.3.1 Info and Relationships, heading structure is not properly conveyed, form fields lack meaningful accessible labels, form field errors are not properly rendered or associated to the fields in error, and visually hidden content is available to screen readers.
  • As noted in 2.1.1 Keyboard, some actionable elements are not keyboard accessible, some functionality is not available with the keyboard and focus is not properly redirected to the right places. 
  • As noted in 2.2.1 Timing, users are logged out without warning.
  • As noted in 2.4.1 Bypass Blocks, there is no link to skip past navigation links.
  • As noted in 2.4.2 Page Titled, some pages lack meaningful titles.
  • As noted in 2.4.4 Link Purpose (In Context), multiple links and image links lack meaningful accessible names.
  • As noted in 3.1.2 Language of Parts, a change in language is not programmatically conveyed.
  • As noted in 3.3.2 Labels and Instructions, some form fields lack proper labels.
  • As noted in 4.1.1 Parsing, multiple elements have duplicate IDs.
  • As noted in 4.1.2 Name, Role, Value, multiple custom controls do not provide the proper name, role and state information, form fields lack accessible names, frames lack meaningful title and dialogs do not convey their structure programmatically. 

 

Authored Content (Web): The product does not allow authors to create content which is functional for users without vision. Examples include: 

  • As noted in 1.1.1 Non-text Content, there is no mechanism to provide alternative text for images.
  • As noted in 1.3.1 Info and Relationships, headings are not rendered with proper markup, form fields lack valid labels, and error messages are not properly associated with the fields in error.
  • As noted in 2.1.1 Keyboard, some actionable elements are not keyboard accessible.
  • As noted in 2.4.1 Bypass Blocks, the authored content does not provide a mechanism to skip past repetitive links.
  • As noted in 2.4.4 Link Purpose (In Context), some image links lack meaningful accessible names.
  • As noted in 2.5.3 Label in Name, user interface components lack programmatic accessible names.
  • As noted in 3.1.1 Language of Page, the author cannot set the language of a page.
  • As noted in 4.1.2 Name, Role, Value, some elements lack the proper role. 

4.2.2 Usage with limited vision

Web: Does Not Support

Authored Content (Web): Supports

Web: Most functions of the product are not usable with limited vision. Examples include:

  • As noted in 1.4.3 Contrast (Minimum), many text elements lack sufficient color contrast against the background.
  • As noted in 1.4.4 Resize Text, content does not allow text to resize in mobile view, and some content is lost when the page is resized.
  • As noted in 1.4.10 Reflow, some content is lost when a page is viewed at the required width of 320 CSS pixels.
  • As noted in 1.4.11 Non-text Contrast, some important controls do not attain the minimum contrast ratio requirement.
  • As noted in 1.4.12 Text Spacing, some content gets lost when text spacing is applied.

Authored Content (Web): Authors can create content that which is functional for users with limited vision. 

4.2.3 Usage without perception of colour

Web: Partially Supports

Authored Content (Web): Supports

Web: Most functions of the product are usable without perception of color. Exceptions include:

  • As noted in 1.4.1 Use of Color, some elements rely on color alone to indicate selection.

Authored Content (Web): Authors can create content which is functional for users without perception of color

4.2.4 Usage without hearing

Web: Supports

Authored Content (Web): Supports

Web: The product does not require the use of hearing. 

Authored Content (Web): Authors can create content which is functional for users without hearing. 

4.2.5 Usage with limited hearing

Web: Supports

Authored Content (Web): Supports

Web: The product does not require the use of hearing. 

Authored Content (Web): Authors can create content which is functional for users without hearing. 

4.2.6 Usage with no or limited vocal capability

Web: Supports

Authored Content (Web): Supports

Web: The product does not require the use of speech. 

Authored Content (Web): 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 (Web): Does Not Support

Web: Most functions of the product are not usable with limited manipulation or strength. Examples include:

  • As noted in 2.1.1 Keyboard, some actionable elements are not keyboard accessible, some functionality is not available with the keyboard and focus is not properly redirected to the right places.
  • As noted in 2.2.1 Timing, users are logged out without warning.
  • As noted in 2.4.1 Bypass Blocks, there is no link to skip past navigation links.
  • As noted in 2.4.7 Focus Visible, there is no keyboard focus indicator for actionable elements.

Authored Content (Web): Most functions of the authored content are not usable with limited manipulation or strength. Examples include:

  • As noted in 2.1.1 Keyboard, some actionable elements are not keyboard accessible.
  • As noted in 2.4.1 Bypass Blocks, the authored content does not provide a mechanism to skip past repetitive links.
  • As noted in 2.4.7 Focus Visible, there is no keyboard focus indicator for actionable elements.
  • As noted in 2.5.3 Label in Name, user interface components lack programmatic accessible names. 

4.2.8 Usage with limited reach

Web: Supports

Authored Content (Web): Supports 

Web: The product is functional with limited reach.

Authored Content (Web): Authors can create content which is functional with limited reach. 

4.2.9 Minimize photosensitive seizure triggers

Web: Supports

Authored Content (Web): Supports

Web: The product does not contain flashing content.

Authored Content (Web): 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, language, or learning

Web: Supports

Authored Content (Web): Supports 

Web: Most functions of the product are usable with limited language, cognitive, and learning abilities. Users with cognitive disabilities have varying needs for features that allow them to adapt content and work with assistive technology or accessibility features of the platform. The product provides descriptive labels and instructions. Exceptions include:

  • As noted in 1.4.12 Text Spacing, some content is lost when text spacing is applied.
  • As noted in 2.2.1 Timing, users are logged out without warning.
  • As noted in 2.4.2 Page Titled, some pages lack meaningful titles.

Authored Content (Web): Authors can create content with functions that are usable with limited language, cognitive, and learning abilities. Users with cognitive disabilities have varying needs for features that allow them to adapt content and work with assistive technology or accessibility features of the platform. The authored content can provide descriptive labels, instructions, and error identification and suggestions for most user input. Exceptions include:

  • As noted in 1.3.5 Identify Input Purpose, input fields do not programmatically convey their purpose.
  • As noted in 2.5.3 Label in Name, user interface components lack programmatic accessible names. 

4.2.11 Privacy

Web: Supports

Authored Content (Web): Supports 

Web: The product maintains user privacy when accessibility features are used. Examples include:

  • When text is masked visually, the private information is not announced in a screen reader.

Authored Content (Web): Authors can create content which maintains user privacy when accessibility features are used.

Chapter 5: Generic Requirements

Notes:

Criteria

Conformance Level

Remarks and Explanations

5.1. Closed functionality

Not Applicable

5.1.2.2-5.1.7 are not applicable for this product, which has no closed functionality.

5.2 Activation of accessibility features

Not Applicable

The product does not have specific documented accessibility features. The product instead relies upon platform accessibility features.

5.3 Biometrics

Not Applicable

The product does not use biological characteristics for user identification or for control of the product. 

5.4 Preservation of accessibility information during conversion

Does Not Support

When converting video content, the product does not preserve closed captions or closed audio descriptions.

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. Some operable parts have an accessible name which enables them to be discernible without user vision. Exceptions include:

  • Some graphical on-screen buttons do not have an accessible name.

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: 

Criteria

Conformance Level

Remarks and Explanations

7.1.1 Captioning playback

Web: Does Not Support

Authored Content (Web): Does Not Support

Web: The product does not provide closed caption playback.

Authored Content (Web): Authors cannot provide closed caption playback.

7.1.2 Captioning synchronization

Web: Not Applicable

Authored Content (Web): Not Applicable

Web: The product does not display closed captions.

Authored Content (Web): The product does not display closed captions.

7.1.3 Preservation of captioning

Web: Does Not Support

Web: The product does not preserve closed caption data in uploaded video.

7.1.4 Captions characteristics

Web: Not Applicable

Authored Content (Web): Not Applicable

Web: The product does not display closed captions.

Authored Content (Web): The product does not display closed captions.

7.1.5 Spoken subtitles

Web: Not Applicable

Authored Content (Web): Not Applicable

Web: The product does not display closed captions.

Authored Content (Web): The product does not display closed captions.

7.2.1 Audio description playback

Web: Does Not Support

Authored Content (Web): Does Not Support

Web: The product does not provide a mechanism to select and play closed audio description.

Authored Content (Web): Authored content does not provide a mechanism to select and play closed audio description.

7.2.2 Audio description synchronization

Web: Not Applicable

Authored Content (Web): Not Applicable

Web: The product does not have a mechanism to play closed audio description.

Authored Content (Web): The product does not have a mechanism to play closed audio description.

7.2.3 Preservation of audio description

Web: Does Not Support

Web: The product does not preserve audio description data in uploaded video.

7.3 User controls for captions and audio description

Web: Does Not Support

Authored Content (Web): Does Not Support

Web: The product does not provide user controls for captions or audio descriptions.

Authored Content (Web): Authored content does not provide user controls for captions or audio descriptions.

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 2.x section.

11.5.2.3 Use of accessibility services

See 11.5.2.5 through 11.5.2.17.

See information in 11.5.2.5 through 11.5.2.17.

11.5.2.4 Assistive technology

Not Applicable

Not applicable to web

11.5.2.5 Object information

Not Applicable

Not applicable to web

11.5.2.6 Row, column, and headers

Not Applicable

Not applicable to web

11.5.2.7 Values

Not Applicable

Not applicable to web

11.5.2.8 Label relationships

Not Applicable

Not applicable to web

11.5.2.9 Parent-child relationships

Not Applicable

Not applicable to web

11.5.2.10 Text

Not Applicable

Not applicable to web

11.5.2.11 List of available actions

Not Applicable

Not applicable to web

11.5.2.12 Execution of available actions

Not Applicable

Not applicable to web

11.5.2.13 Tracking of focus and selection attributes

Not Applicable

Not applicable to web

11.5.2.14 Modification of focus and selection attributes

Not Applicable

Not applicable to web

11.5.2.15 Change notification

Not Applicable

Not applicable to web

11.5.2.16 Modifications of states and properties

Not Applicable

Not applicable to web

11.5.2.17 Modifications of values and text

Not Applicable

Not applicable to web

11.6.1 User control of accessibility features

Not Applicable

The product is not platform software. 

11.6.2 No disruption of accessibility features

Supports

The product does not disrupt platform accessibility features.

11.7 User preferences

Not Applicable

Web pages are isolated from their underlying platform. 

11.8.2 Accessible content creation

See WCAG 2.x section

See information in WCAG 2.x section.

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

Does Not Support

The product does not provide templates that are accessible. 

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)