Adobe Accessibility Conformance Report

International Edition

(Based on VPAT® Version Rev2.4)

Name of Product/Version:

Adobe Express

Report Date: 

October 2023

Product Description: 

Adobe Express is an application that inspires and empowers everyone, regardless of skillset, to stand out and drive engagement with a radically easy, intent-driven all-in-one solution differentiated by Adobe’s domain expertise, creative ecosystem, innovative AI, and leading community of creators.

Contact Information: 

access@adobe.com

Evaluation Methods Used: 

Product testing involved use of leading assistive technology, such as screen readers, screen magnifiers, and speech recognition software, as well 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.1 Level AAA.

 

WCAG 2.1 Report

Tables 1 and 2 also document conformance with:

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

 

Note: When reporting on conformance with the WCAG 2.1 Success Criteria, the criteria are scoped for full pages, complete processes, and accessibility-supported ways of using technology as documented in the WCAG 2.1 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

Web: The product provides sufficient text alternatives for most instances of active and informative images. 

Exceptions include: 

  • Functional image text alternative does not include essential text on image, present in ‘Layers’, ‘Search’ screens.
  • Functional image text alternative does not serve same purpose as image in ‘Generative AI - Text to Image’, 'Generative AI - Text Effects' screens.
  • The decorative image is not hidden from screen readers in ‘Comments’ screen.
  • Informative Images are missing alternate text in ‘Files - Grid View’, ‘Files - List View’, ‘Notifications / Share file Modal’, ‘Library Details’, ‘Add-ons’, ‘Quick Actions - Convert To PDF/PNG/JPG Modals’, ‘Quick Actions - Generate QR Code Dialog’, ‘Your Stuff - Files’, 'Brands' screens. 
  • Informative Image text alternative does not present same info as image in ‘Create New File’, ‘Text/ Add Your Text’ screens.

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

Web: The product provides audio description or text transcripts for most of the video or audio only media. Exceptions include: 

  • No text or audio description available for the video-only media in the ‘Discover Dialog’ screen.

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 (Not Applicable)

Web: The product does not contain prerecorded synchronized media.

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 (Not Applicable)

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

1.2.4 Captions (Live) (Level AA)
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 (Not Applicable)

Web: The product does not contain live synchronized media.

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 (Not Applicable)

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

Guideline 1.3 Adaptable:

Create content that can be presented in different ways (for example simpler layout) without losing information or structure.

Criteria

Conformance Level

Remarks and Explanations

1.3.1 Info and Relationships (Level A)
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

Web: Most visual structure and relationship information is provided through element semantics or object information or are available in text. Exceptions include:

  • The content visually appears to be a data table but is not marked up as a table in ‘Schedule’ screen.
  • The group label is not associated with its checkboxes in ‘Report Abuse Modal’, ‘Resize’, ‘Video’ screens.
  • Group of form controls not associated with group label in ‘Generative AI - Text Effects’, ‘Generative AI - Text to Image’, ‘Share to Social Media Modal’ screens.
  • The group label is not associated with its radio buttons in ‘Add-ons’, ‘Text - Animation’, ‘Video’ screens.
  • Heading levels are out of order in ‘Account Settings - All tabs (General / Account / About)’, ‘Add-ons’, ‘Resize’, ‘Share to Social Media Modal’ screens.
  • Text inappropriately coded as a heading in ‘Home’ screen.
  • Visual heading text is not marked as heading in ‘Account Settings - All tabs (General / Account / About)’, ‘Brands & Libraries’, ‘Color Theme’, ‘Create New File’, ‘Files - List View’, ‘Left Navigation’, ‘Report Abuse Modal’, ‘Search’, ‘Text/ Add Your Text’, ‘You are Offline’ screens.
  • <ul> list does not directly contain <li> elements in ‘Home’ screen.
  • List or list item is not marked up properly in ‘Header’ screen.
  • Visual list is not marked up as list in ‘Generative AI - Text to Image’, ‘Report Abuse Modal’, ‘Resize’, ‘Share to Social Media Modal’, ‘Video’ screens.

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

Web: The product presents most content in a meaningful sequence. 

Exceptions include: 

  • Able to browse outside the modal content with screen reader in ‘Brands & Libraries’, ‘Files - List View’, ‘Quick Actions - Generate QR Code Dialog’, ‘Share to Social Media Modal’ screens.
  • aria-hidden="true" is used incorrectly in ‘Discover Dialog’, ‘Notifications / Share file Modal’ screens.
  • Correct reading order of dynamic content not determinable in ‘Comments’, ‘Create New File’, ‘Discover Dialog’, ‘Version History’ screens.
  • Hidden content is readable with a screen reader in ‘Ellipse’, ‘Home’, ‘Layers’, ‘Quick Actions - Convert To PDF/PNG/JPG Modals’, ‘View All Pages’ screens.
  • Informative (static) content is not readable by a screen reader in ‘Download’, ‘Header’ screens.
  • Informative content is not readable by a screen reader in ‘Create New File’ screen.
  • Reading order of static content changes meaning in ‘Add-ons’ screen.
  • Screen reader focus is lost or misplaced due to user interaction or content update in ‘Notifications / Share file Modal’ screen.  

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

Web: Instructions do not rely solely on sensory characteristics. 

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

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

1.3.5 Identify Input Purpose (Level AA 2.1 only)
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.1.3.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 (Not Applicable)

Web: The product does not contain input fields that collect information about the user.

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

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

Exceptions include: 

  • Color alone is used to convey information in ‘Color Theme’, ‘Generative AI - Text Effects’, ‘Generative AI - Text to Image’, ‘Quick Actions - Generate QR Code Dialog’, ‘Share to Social Media Modal’, ‘Text - Shadow’, ‘Text - Shapes’, ‘Text/ Add Your Text’, ‘Video - Effects’ screens.
  • Link contrast is not at least 3:1 with surrounding text in ‘Elements - Templates’, ‘Library Details’, ‘Media - Audio’, ‘Media - Photos/Videos’, ‘Quick Actions - Animate from Audio’, ‘Quick Actions - Convert To PDF/PNG/JPG Modals’, ‘Quick Actions - Resize Image’, 'Brands' screens.

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

Web: Audio content can be controlled by the user.

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

Web: Most of the text does not meet minimum contrast requirements. Examples include:

  • Text content lacks 4.5:1 contrast ratio in ‘Notifications / Share file Modal’, ‘Account Settings - All tabs (General / Account / About)’, ‘Add-ons’, ‘Comments’, ‘Generative AI - Text to Image’, ‘Header’, ‘Home’, ‘Library Details’, ‘Media - Audio’, ‘Media - Photos/Videos’, ‘Quick Actions - Animate From Audio’, ‘Quick Actions - Generate QR Code Dialog’, ‘Quick Actions - Resize Image’, ‘Resize’, ‘Schedule’, ‘Search’, ‘Share to Social Media Modal’, ‘Text/ Add Your Text’, ‘Video’, ‘Video - Adjustments’, ‘Your Stuff - Files’, 'Generative AI - Text Effects', 'Create New File' screens.
  • Link or button text lacks 4.5:1 contrast ratio on hover or focus in ‘Comments’, ‘Files - Grid View’, ‘Files - List View’, ‘Home’, ‘Share to Social Media Modal’, ‘Text/ Add Your Text’ screens.
  • Placeholder text lacks 4.5:1 contrast ratio in ‘Brands & Libraries’, ‘Comments’, ‘Library Details’, ‘Notifications / Share file Modal’, ‘Share to Social Media Modal’, 'Brands' screens.

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

Web: Most text can be resized using browser zoom, but content and functionality is lost in some product functions. Exceptions include:

  • Some part of the page content is lost when the page is zoomed to 200% in ‘Files - List View’ screen.
  • Functionality is lost at 200% zoom in ‘Account Settings - All tabs (General / Account / About)’, ‘Add-ons’, ‘Comments’, ‘Create New File’, ‘Files - Grid View’, ‘Files - List View’, ‘Header’, ‘Home’, ‘Media - Audio’, ‘Quick Actions - Animate from Audio’, ‘Schedule’, ‘Search’, ‘Share to Social Media Modal’, ‘Text/ Add Your Text’, ‘Video’, ‘Media - Photos/Videos’ screens.

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) – 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

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

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.1.4.10 (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

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:

  • Functionality is lost at 320px width equivalent in ‘Account Settings - All tabs (General / Account / About)’, ‘Add-ons’, ‘Comments’, ‘Create New File’, ‘Elements - Templates’, ‘Files - Grid View’, ‘Files - List View’, ‘Header’, ‘Home’, ‘Media - Audio’, ‘Media - Photos/Videos’, ‘Quick Actions - Animate from Audio’, ‘Schedule’, ‘Schedule Settings’, ‘Search’, ‘Share to Social Media Modal’, ‘Text/ Add Your Text’, ‘Video’ screens.

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

Web: Most of the meaningful non-text content does not meets sufficient color contrast requirements. Examples include:

  • Active user interface component lacks 3 to 1 contrast ratio in ‘Brands & Libraries’, ‘Comments’, ‘Ellipse’, ‘Files - Grid View’, ‘Files - List View’, ‘Image - Crop’, ‘Image - Erase’, ‘Notifications / Share file Modal’, ‘Quick Actions - Animate from Audio’, ‘Quick Actions - Resize Image’, ‘Share to Social Media Modal’, ‘Text - Animation’, ‘Text - Shadow’, ‘Text - Shapes’, ‘Text/ Add Your Text’, ‘Video’, ‘Video - Adjustments’, ‘Video - Effects’ screens.
  • An icon lacks 3 to 1 contrast ratio in ‘Add-ons’, ‘Comments’, ‘Discover Dialog’, ‘Share to Social Media Modal’ screens.
  • Graphical object lacks 3 to 1 contrast ratio in ‘Text - Shapes’ screen.
  • State of active component lacks 3 to 1 contrast ratio in ‘Generative AI - Text to Image’, ‘Header’, ‘Home’, ‘Notifications / Share file Modal’, ‘Quick Actions - Convert To PDF/PNG/JPG Modals’, ‘Schedule’, ‘Text - Shadow’, ‘Text - Shapes’, 'Generative AI - Text Effects' screens

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

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

1.4.13 Content on Hover or Focus (Level AA 2.1 only)
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: Partially Supports

Web: In most of the product’s functionality, the additional content that is displayed on hover or focus is dismissible, hoverable or persistent. Exceptions include:

  • Hover content disappearing in ‘Brands & Libraries’, ‘Color Theme’, ‘Comments’, ‘Create New File’, ‘Ellipse’, ‘Files - Grid View’, ‘Files - List View’, ‘Generative AI - Text Effects’, ‘Generative AI - Text to Image’, ‘Header’, ‘Image - Crop’, ‘Image - Erase’, ‘Left Navigation’, ‘Library Details’, ‘Media - Audio’, ‘Premium Content Badge’, ‘Quick Actions - Animate from Audio’, ‘Schedule’, ‘Schedule Settings’, ‘Share to Social Media Modal’, ‘Text - Fill Color’, ‘Text/ Add Your Text’, ‘Video’, ‘View All Pages’, ‘Your Stuff - Files’, 'Brands' screens.

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

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

  • Action cannot be performed with a screen reader turned on in ‘Add-ons’, ‘Ellipse’, ‘Explore Templates’, ‘Header’, ‘Left Navigation’ screens.
  • Device-dependent event handlers are used in ‘Add-ons’, ‘Brands & Libraries’, ‘Comments’, ‘Ellipse’, ‘Files - Grid View’, ‘Generative AI - Text to Image’, ‘Header’, ‘Left Navigation’, ‘Quick Actions - Resize Image’, ‘Schedule Settings’, ‘Share to Social Media Modal’, ‘Text - Animation’, ‘Text/ Add Your Text’, ‘Video’, ‘View All Pages’, 'Generative AI - Text Effects' screens.
  • Drag and drop feature is not keyboard accessible in ‘Layers’ screen.
  • Function cannot be performed by keyboard alone in ‘Account Settings - All tabs (General / Account / About)’, ‘Add-ons’, ‘Discover Dialog’, ‘Elements - Templates’, ‘Explore Templates’, ‘Files - Grid View’, ‘Files - List View’, ‘Generative AI - Text Effects’, ‘Generative AI - Text to Image’, ‘Home’, ‘Library Details’, ‘Media - Photos/Videos’, ‘Premium Content Badge’, ‘Quick Actions - Convert To PDF/PNG/JPG Modals’, ‘Quick Actions - Resize Image’, ‘Search’, ‘Share To Social Media Modal’, ‘Text - Shadow’, ‘Text/ Add Your Text’, ‘Video’, ‘View All Pages’, ‘Your Stuff - Files’, 'Brands' screens.
  • Link does not have an href value in ‘Library Details’, 'Brands' screens.

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

Web: The product 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.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

Web: The product provides character key shortcuts and it activates only when the appropriate user interface component receives focus.

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

Web: The product does not include functionality dependent on time limits. Exceptions include:

  • Content visually appears and disappears with no ability to adjust timing in ‘Comments’, ‘Quick Actions - Resize Image’ screens.

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 (Not Applicable)

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

Guideline 2.3 Seizures:

Do not design content in a way that is known to cause seizures. 

Criteria

Conformance Level

Remarks and Explanations

2.3.1 Three Flashes or Below Threshold (Level A)
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 (Not Applicable)

Web: The product does not contain flashing content.

Guideline 2.4 Navigable:

Provide ways to help users navigate, find content, and determine where they are. 

Criteria

Conformance Level

Remarks and Explanations

2.4.1 Bypass Blocks (Level A)
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: Supports

Web: The product provides a heading which allows users to bypass repeated blocks.

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

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

  • Page <title> does not identify the purpose of the page in ‘Explore Templates’, ‘Files - Grid View’, ‘Files - List View’ ‘Quick Actions - Convert To PDF/PNG/JPG Modals’, ‘Schedule’, ‘Schedule Settings’, 'Brands' screens.

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

Web: Most of the components does not receive the focus in a meaningful order. Examples include:

  • Hidden or empty element receives focus in ‘Add-ons’, ‘Elements - Templates’, ‘Ellipse’, ‘Explore Templates’, ‘Files - List View’, ‘Home’, ‘Layers’, ‘Media - Photos/Videos’, ‘Quick Actions - Convert To PDF/PNG/JPG Modals’, ‘Search’, ‘Text/ Add Your Text’, ‘View All Pages’ screens.
  • Keyboard focus is lost or misplaced due to user interaction or content update in ‘Account Settings - All tabs (General / Account / About)’, ‘Add-ons’, ‘Comments’, ‘Download’, ‘Text - Shadow’, ‘Text/ Add Your Text’ screens.
  • Keyboard focus is not maintained in modal in ‘Brands & Libraries’, ‘Files - List View’ screens.
  • Keyboard focus is not placed on opened modal in ‘Quick Actions - Convert To PDF/PNG/JPG Modals’, ‘Quick Actions - Resize Image’ screens.
  • Keyboard focus order is not logical in ‘Brands & Libraries’, ‘Comments’, ‘Create New File’, ‘Discover Dialog’, ‘Version History’ screens.
  • Modal is closed, focus is not returned to trigger in ‘Account Settings - All tabs (General / Account / About)’, ‘Brands & Libraries’, ‘Files - List View’, ‘Quick Actions - Convert To PDF/PNG/JPG Modals’, ‘Quick Actions - Generate QR Code Dialog’, ‘Quick Actions - Resize Image’, ‘Share to Social Media Modal’ screens.

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

Web: Most of the links have a purpose that can be determined from the link text alone or from the programmatic context of the link. Exceptions include:

  • Purpose of link is not clear in context in ‘Home’ screen.

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

Web: Users can locate web pages in the product through the header and left navigation controls.

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

Web: Most of the headings and labels are not descriptive. Examples include:

  • Buttons have same name but different actions in ‘Color Theme’, ‘Elements - Templates’, ‘Ellipse’, ‘Explore Templates’, ‘Files - List View’, ‘Home’, ‘Media - Audio’, ‘Media - Photos/Videos’, ‘Notifications / Share file Modal’, ‘Quick Actions - Animate from Audio’, ‘Schedule Settings’, ‘Search’, ‘Text - Shapes’, ‘Text/ Add Your Text’, ‘Version History’, ‘Your Stuff - Files’ screens.
  • Programmatic label does not convey purpose of control in ‘Account Settings - All tabs (General / Account / About)’, ‘Color Theme’, ‘Elements - Templates’, ‘Ellipse’, ‘Explore Templates’, ‘Files - Grid View’, ‘Files - List View’, ‘Generative AI - Text Effects’, ‘Generative AI - Text to Image’, ‘Home’, ‘Image - Erase’, ‘Media - Photos/Videos’, ‘Quick Actions - Animate From Audio’, ‘Quick Actions - Generate QR Code Dialog’, ‘Quick Actions - Resize Image’, ‘Report Abuse Modal’, ‘Resize’, ‘Search’, ‘Share To Social Media Modal’, ‘Text - Animation’, ‘Text/ Add Your Text’, ‘Version History’, ‘Video’, ‘Your Stuff - Files’ screens.

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

Web: Most of the focusable elements have a visible keyboard focus indicator. Exceptions include:

  • Focus indicator is missing in ‘Brands & Libraries’, ‘Comments’, ‘Header’, ‘Image - Crop’, ‘Layers’, ‘Looping Animations’, ‘Notifications / Share file Modal’, ‘Quick Actions - Resize Image’, ‘Text - Animation’, ‘Text - Shapes’, ‘Text/ Add Your Text’, ‘Video - Effects’, ‘Your Stuff - Files’ screens.

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: Supports (Not Applicable)

Web: The product 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.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

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

2.5.3 Label in Name (Level A 2.1 only)
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.2.5.3.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

Web: Most of the accessible names of the controls contain the text of their visible labels. Exceptions include:

  • Accessible name does not contain visible label in ‘Account Settings - All tabs (General / Account / About)’, ‘Ellipse’, ‘Generative AI - Text Effects’, ‘Generative AI - Text to Image’, ‘Image - Erase’, ‘Notifications / Share file Modal’, ‘Quick Actions - Animate from Audio’, ‘Quick Actions - Resize Image’, ‘Share to Social Media Modal’, ‘Text - Animation’, ‘Text - Shapes’, ‘Text/ Add Your Text’ screens.
  • Accessible name missing in ‘Files - Grid View’, ‘Files - List View’, ‘Quick Actions - Animate from Audio’, ‘Resize’, ‘Text - Fill Color’ screens.

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 (Not Applicable)

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

Guideline 3.1 Readable:

Make text content readable and understandable. 

Criteria

Conformance Level

Remarks and Explanations

3.1.1 Language of Page (Level A)
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: Partially Supports

Web: Most of the page’s language is programmatically determinable within the product. Exceptions include:

  • The <html> element does not have a lang attribute in ‘Library Details’ screen.

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 (Not Applicable)

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

Guideline 3.2 Predictable:

Make Web pages appear and operate in predictable ways. 

Criteria

Conformance Level

Remarks and Explanations

3.2.1 On Focus (Level A)
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

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

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

Web: Most of the components change of context does not occur automatically on user input. Exceptions include:

  • Form field causes unexpected change in ‘View All Pages’ screen.

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

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

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

Web: Components with the same functionality are identified consistently.

Guideline 3.3 Input Assistance:

Help users avoid and correct mistakes. 

Criteria

Conformance Level

Remarks and Explanations

3.3.1 Error Identification (Level A)
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: Partially Supports

Web: Most input errors are identified and described to the users in text. Exceptions include:

  • Form field with error not identified in ‘Account Settings - All tabs (General / Account / About)’, ‘Resize’ screens.
  • Input error is not described in text in ‘Text - Fill Color’ screen.

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

Web: Labels are provided for most of the input fields. 

Exceptions include:

  • Instructions missing for assistive technology users in ‘Image - Crop’ screen.
  • Navigation Instructions missing for the users in ‘Text/ Add Your Text’, 'Generative AI - Text to Image', 'Generative AI - Text Effects' screens.
  • Label is not persistent in ‘Brands & Libraries’, ‘Create New File’, ‘Header’, ‘Home’, ‘Notifications / Share file Modal’, ‘Share to Social Media Modal’, ‘Video’, ‘Text/ Add Your Text’, ‘Generative AI - Text to Image’, ‘Generative AI - Text Effects’ screens.
  • Visible label is missing in ‘Create New File’, ‘Files - Grid View’, ‘Files - List View’, ‘Resize’, ‘Share to Social Media Modal’, ‘Text - Fill Color’, ‘Text/ Add Your Text’, ‘Video’ screens. 

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

Web: Where input errors are automatically detected, suggestions for correction are provided to the user.

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 (Not Applicable)

Web: The product does not process legal commitments or financial transactions 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.4.1.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: Partially Supports

Web: Most of the elements have proper start and end tags. Elements are nested according to their specifications. Elements do not contain duplicate attributes or duplicate IDs. Exceptions include:

  • Anchor or button nested inside other anchor or button in ‘Home’ screen.
  • ARIA role does not contain particular children in ‘Text - Fill Color’, ‘Library Details’, ‘Notifications / Share file Modal’, ‘Files - List View’, ‘Account Settings - All tabs (General / Account / About)’, 'Brands' screens.
  • Certain ARIA roles missing particular parents in ‘Brands & Libraries’, ‘Files - List View’ screens.
  • Interactive controls are nested in ‘Header’, ‘Create New File’, ‘Ellipse’ screens.
  • The page contains duplicate id attribute values in ‘Generative AI - Text to Image’, ‘Account Settings - All tabs (General / Account / About)’, ‘Library Details’, 'Generative AI - Text Effects', 'Brands' screens.

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

Web: User interface components at most of the places do not provide programmatic name, role, state, or value information. Examples include:

  • Custom user interface component is not compatible with AT in ‘Image - Crop’ screen.
  • ARIA attributes are not allowed without role in ‘Share to Social Media Modal’ screen.
  • ARIA attributes need conform valid values in ‘Notifications / Share file Modal’ screen.
  • ARIA input fields need an accessible name in ‘Account Settings - All tabs (General / Account / About)’ screen.
  • Number of carousel slides is apparent visually but not programmatically in ‘Add-ons’ screen.
  • State of current carousel slide is not conveyed in ‘Add-ons’ screen.
  • Combo box is missing appropriate roles and/or attributes in ‘Account Settings - All tabs (General / Account / About)’, ‘Create New File’, ‘Header’, ‘Notifications / Share file Modal’, ‘Search’, ‘Text/ Add Your Text’ screens.
  • Dialog is missing appropriate role and/or attributes in ‘Brands & Libraries’, ‘Files - List View’, ‘Quick Actions - Animate from Audio’, ‘Quick Actions - Generate QR Code Dialog’, ‘Quick Actions - Resize Image’, ‘Share to Social Media Modal’, 'Start from Your Content Modal’ screens.
  • Unallowed attributes are used in ‘Account Settings - All tabs (General / Account / About)’, ‘View All Pages’, ‘Notifications / Share file Modal’ screens.
  • Invalid ARIA attribute names are used in ‘Color Theme’ screen.
  • The element's role is incorrect in ‘Share to Social Media Modal’, ‘Media - Photos/Videos’ screens.
  • Slider is missing appropriate role and/or attributes in ‘Quick Actions - Animate from Audio’, ‘Video’ screens.
  • The element has missing or incorrect states or properties in ‘Create New File’, ‘Generative AI - Text Effects’, ‘Text - Shapes’, ‘View All Pages’ screens.
  • Tooltip content is not accessible to screen readers in ‘Brands & Libraries’, ‘Comments’, ‘Create New File’, ‘Ellipse’, ‘Generative AI - Text to Image’, ‘Header’, ‘Image - Erase’, ‘Left Navigation’, ‘Library Details’, ‘Premium Content Badge’, ‘Quick Actions - Animate from Audio’, ‘Schedule Settings’, ‘Share to Social Media Modal’, ‘Text/ Add Your Text’, ‘Video’, 'Generative AI - Text Effects', 'Brands' screens.
  • ARIA commands are missing an accessible name in ‘Brands & Libraries’, ‘Create New File’, ‘Text - Fill Color’, ‘Ellipse’, ‘Video - Effects’, ‘Library Details’, ‘Schedule’, ‘Files - Grid View’, ‘Files - List View’, ‘Header’, ‘Your Stuff - Files’, ‘Schedule Settings’, ‘Search’, ‘Elements - Templates’, ‘Account Settings - All tabs (General / Account / About)’, ‘Quick Actions - Resize Image’, ‘View All Pages’, ‘Brands’ screens.
  • Button disabled state is not conveyed in ‘Create New File’ screen.
  • Button does not have an accessible name in ‘Add-ons’, ‘Brands & Libraries’, ‘Color Theme’, ‘Comments’, ‘Elements - Templates’, ‘Generative AI - Text to Image’, ‘Layers’, ‘Quick Actions - Animate from Audio’, ‘Quick Actions - Convert To PDF/PNG/JPG Modals’, ‘Quick Actions - Generate QR Code Dialog’, ‘Start from Your Content Modal’, ‘Text - Shapes’, ‘Text/ Add Your Text’, ‘Video’, ‘Text/ Add Your Text’, 'Generative AI - Text Effects' screens.
  • Button does not have a role in ‘Add-ons’, ‘Elements - Templates’, ‘Explore Templates’, ‘Files - Grid View’, ‘Files - List View’, ‘Home’, ‘Image - Crop’, ‘Layers’, ‘Library Details’, ‘Media - Photos/Videos’, ‘Premium Content Badge’, ‘Quick Actions - Animate from Audio’, ‘Quick Actions - Resize Image’, ‘Search’, ‘Share to Social Media Modal’, ‘Text - Animation’, ‘Video’, ‘View All Pages’, ‘Your Stuff - Files’, 'Brands' screens.
  • Button is missing both a role and an accessible name in ‘Add-ons’, ‘Ellipse’, ‘Generative AI - Text to Image’, ‘Image - Crop’, ‘Library Details’, ‘Quick Actions - Animate from Audio’, ‘Schedule Settings’, ‘Share to Social Media Modal’, ‘Text/ Add Your Text’, ‘Version History’, ‘Video’, ‘Generative AI - Text Effects’, 'Brands' screens.
  • Button pressed state is not conveyed in ‘Comments’, ‘Quick Actions - Convert To PDF/PNG/JPG Modals’, ‘Schedule’, ‘Text/ Add Your Text’ screens.
  • Button pressed state of the element is incorrect in ‘Text - Fill Color’ screen.
  • Form elements missing labels in ‘Files - List View’ screen.
  • Form field is not labeled in ‘Files - Grid View’, ‘Files - List View’, ‘Resize’, ‘Share to Social Media Modal’, ‘Text - Fill Color’, ‘View All Pages’ screens.
  • iframe does not have a title in ‘Add-ons’, ‘Quick Actions - Convert To PDF/PNG/JPG Modals’ screens.
  • Link does not have a role in ‘Account Settings - All tabs (General / Account / About)’, ‘Add-ons’, ‘Header’, ‘Notifications / Share file Modal’, ‘Schedule Settings’ screens.
  • Expand/collapse state of the element is missing or incorrect in ‘Comments’, ‘Create New File’, ‘Elements - Templates’, ‘Files - Grid View’, ‘Files - List View’, ‘Generative AI - Text Effects’, ‘Header’, ‘Home’, ‘Library Details’, ‘Media - Photos/Videos’, ‘Quick Actions - Convert To PDF/PNG/JPG Modals’, ‘Share to Social Media Modal’, ‘Start from Your Content Modal’, ‘Text - Fill Color’, ‘Text/ Add Your Text’, ‘Video’, ‘Video - Effects’, ‘Your Stuff - Files’, 'Brands' screens.
  • Selected state of the element is missing or incorrect in ‘Account Settings - All tabs (General / Account / About)’, ‘Brands & Libraries’, ‘Comments’, ‘Files - Grid View’, ‘Files - List View’,  ‘Generative AI - Text Effects’, ‘Generative AI - Text to Image’, ‘Home’, ‘Layers’, ‘Media - Photos/Videos’, ‘Quick Actions - Animate From Audio’, ‘Quick Actions - Resize Image’, ‘Schedule’, ‘Share to Social Media Modal’, ‘Text - Animation’, ‘Text - Shadow’, ‘Text - Shapes’, ‘Text/ Add Your Text’, ‘Video - Effects’, ‘View All Pages’ screens.
  • The view options button value (33%) is not exposed to the screen reader users in ‘Create New File’ screen.

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

Web: When status messages do not receive focus, the product does not provide the dynamic update to the assistive technology. Examples include:

  • Status message is not automatically announced in ‘Account Settings - All tabs (General / Account / About)’, ‘Add-ons’, ‘Color Theme’, ‘Comments’, ‘Download’, ‘Explore Templates’, ‘Files - List View’, ‘Quick Actions - Animate from Audio’, ‘Quick Actions - Convert To PDF/PNG/JPG Modals’, ‘Quick Actions - Generate QR Code Dialog’, ‘Resize’, ‘Search’, ‘Share to Social Media Modal’, ‘Text - Fill Color’, ‘Version History’ screens.

 

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

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

  • As noted in 1.1.1 Non-text Content, Functional image text alternative does not include essential text in image, functional image text alternative does not serve same purpose as image, the decorative image is not hidden from screen readers, Informative Images are missing alternate text, Informative Image text alternative does not present same info as image. 
  • As noted in 1.3.1 Info and Relationships, The content visually appears to be a data table but is not marked up as a table, the group label is not associated with its checkboxes, group of form controls not associated with group label, the group label is not associated with its radio buttons, heading levels are out of order, text inappropriately coded as a heading, visual heading text is not marked as heading, <ul> list does not directly contain <li> elements, list or list item is not marked up properly, visual list is not marked up as list.
  • As noted in 1.3.2 Meaningful Sequence, Able to browse outside the modal content with screen reader, aria-hidden="true" is used incorrectly, correct reading order of dynamic content not determinable, hidden content is readable with a screen reader, Informative (static) content is not readable by a screen reader, Informative content is not readable by a screen reader, reading order of static content changes meaning, screen reader focus is lost or misplaced due to user interaction or content update. 
  • As noted in 1.4.1 Use of Color, Color alone is used to convey info, Link contrast is not at least 3:1 with surrounding text.
  • As noted in 2.1.1 Keyboard, Action cannot be performed with a screen reader turned on, device-dependent event handlers are used, drag and drop feature is not keyboard accessible, function cannot be performed by keyboard alone, Link does not have an href value. 
  • As noted in 2.2.1 Timing Adjustable, Content visually appears and disappears with no ability to adjust timing.
  • As noted in 2.4.2 Page Titled, Page <title> does not identify the purpose of page.
  • As noted in 2.4.3 Focus Order, Hidden or empty element receives focus, keyboard focus is lost or misplaced due to user interaction or content update, keyboard focus is not maintained in modal, keyboard focus is not placed on opened modal, keyboard focus order is not logical, modal is closed, focus is not returned to trigger element. 
  • As noted in 2.4.4 Link Purpose (In Context), Purpose of link is not clear in context.
  • As noted in 2.4.6 Headings and Labels, Buttons have the same name but different actions, Programmatic label does not convey purpose of control.
  • As noted in 3.3.2 Labels or Instructions, Instructions missing for assistive technology users, navigation Instructions missing for the users, label is not persistent, visible label missing. 
  • As noted in 4.1.1 Parsing, Anchor or button nested inside another anchor or button, ARIA role does not contain particular children, certain ARIA roles missing particular parents, Interactive controls are nested, the page contains duplicate id attribute values. 
  • As noted in 4.1.2 Name, Role, Value, Custom user interface component is not compatible with AT, ARIA attributes are not allowed without role, ARIA attributes need conform valid values, ARIA input fields need an accessible name, number of carousel slides is apparent visually but not programmatically, state of current carousel slide is not conveyed, dialog is missing appropriate role and/or attributes, unallowed attributes are used, Invalid ARIA attribute names are used, the element's role is incorrect, Slider is missing appropriate role and/or attributes, the element has missing or incorrect states or properties, tooltip content is not accessible to screen readers, ARIA commands are missing an accessible name, button disabled state is not conveyed, button does not have an accessible name, button does not have a role, button is missing both a role and an accessible name, button pressed state is not conveyed, button pressed state of the element is incorrect, form elements missing labels, form field is not labeled, iframe does not have a title, link does not have a role, Expand/collapse state of the element is missing or incorrect, selected state of the element is missing or incorrect, the view options button value (33%) is not exposed to the screen reader users.

302.2 With Limited Vision

Web: Partially Supports

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

  • As noted in 1.1.1 Non-text Content, Functional image text alternative does not include essential text in image, functional image text alternative does not serve same purpose as image, the decorative image is not hidden from screen readers, Informative Images are missing alternate text, Informative Image text alternative does not present same info as image. 
  • As noted in 1.3.1 Info and Relationships, The content visually appears to be a data table but is not marked up as a table, the group label is not associated with its checkboxes, group of form controls not associated with group label, the group label is not associated with its radio buttons, heading levels are out of order, text inappropriately coded as a heading, visual heading text is not marked as heading, <ul> list does not directly contain <li> elements, list or list item is not marked up properly, visual list is not marked up as list.
  • As noted in 1.3.2 Meaningful Sequence, Able to browse outside the modal content with screen reader, aria-hidden="true" is used incorrectly, correct reading order of dynamic content not determinable, hidden content is readable with a screen reader, Informative (static) content is not readable by a screen reader, Informative content is not readable by a screen reader, reading order of static content changes meaning, screen reader focus is lost or misplaced due to user interaction or content update.  
  • As noted in 1.4.1 Use of Color, Color alone is used to convey info, Link contrast is not at least 3:1 with surrounding text.
  • As noted in 1.4.3 Contrast (Minimum), Text content lacks 4.5:1 contrast ratio, link or button text lacks 4.5:1 contrast ratio on hover or focus, Placeholder text lacks 4.5:1 contrast ratio. 
  • As noted in 2.1.1 Keyboard, Action cannot be performed with a screen reader turned on, device-dependent event handlers are used, drag and drop feature is not keyboard accessible, function cannot be performed by keyboard alone, Link does not have an href value.  
  • As noted in 2.2.1 Timing Adjustable, Content visually appears and disappears with no ability to adjust timing. 
  • As noted in 2.4.2 Page Titled, Page <title> does not identify the purpose of page.
  • As noted in 2.4.3 Focus Order, Hidden or empty element receives focus, keyboard focus is lost or misplaced due to user interaction or content update, keyboard focus is not maintained in modal, keyboard focus is not placed on opened modal, keyboard focus order is not logical, modal is closed, focus is not returned to trigger element. 
  • As noted in 2.4.4 Link Purpose (In Context), Purpose of link is not clear in context. 
  • As noted in 2.4.6 Headings and Labels, Buttons have the same name but different actions, Programmatic labels do not convey the purpose of control.
  • As noted in 2.4.7 Focus Visible, the visual focus indicator is missing.
  • As noted in 3.3.2 Labels or Instructions, Instructions missing for assistive technology users, navigation Instructions missing for the users, label is not persistent, visible label missing. 
  • As noted in 4.1.1 Parsing, Anchor or button nested inside another anchor or button, ARIA role does not contain particular children, certain ARIA roles missing particular parents, Interactive controls are nested, the page contains duplicate id attribute values.  
  • As noted in 4.1.2 Name, Role, Value, Custom user interface component is not compatible with AT, ARIA attributes are not allowed without role, ARIA attributes need conform valid values, ARIA input fields need an accessible name, number of carousel slides is apparent visually but not programmatically, state of current carousel slide is not conveyed, dialog is missing appropriate role and/or attributes, unallowed attributes are used, Invalid ARIA attribute names are used, the element's role is incorrect, Slider is missing appropriate role and/or attributes, the element has missing or incorrect states or properties, tooltip content is not accessible to screen readers, ARIA commands are missing an accessible name, button disabled state is not conveyed, button does not have an accessible name, button does not have a role, button is missing both a role and an accessible name, button pressed state is not conveyed, button pressed state of the element is incorrect, form elements missing labels, form field is not labeled, iframe does not have a title, link does not have a role, Expand/collapse state of the element is missing or incorrect, selected state of the element is missing or incorrect, the view options button value (33%) is not exposed to the screen reader users. 

302.3 Without Perception of Color

Web: Partially Supports

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

  • As noted in 1.4.1 Use of Color, Color alone is used to convey info, Link contrast is not at least 3:1 with surrounding text.
  • As noted in 1.4.3 Contrast (Minimum), Text content lacks 4.5:1 contrast ratio, link or button text lacks 4.5:1 contrast ratio on hover or focus, Placeholder text lacks 4.5:1 contrast ratio. 

302.4 Without Hearing

Web: Supports (Not Applicable)

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

302.5 With Limited Hearing

Web: Supports (Not Applicable)

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

302.6 Without Speech

Web: Supports (Not Applicable)

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

302.7 With Limited Manipulation

Web: Partially Supports

Web: Users with limited manipulation who use speech recognition or switch control software will not have difficulty navigating to most of the controls. Exceptions include:

  • As noted in 2.1.1 Keyboard, Action cannot be performed with a screen reader turned on, device-dependent event handlers are used, drag and drop feature is not keyboard accessible, function cannot be performed by keyboard alone, Link does not have an href value.   
  • As noted in 2.2.1 Timing Adjustable, Content visually appears and disappears with no ability to adjust timing.
  • As noted in 2.4.2 Page Titled, Page <title> does not identify the purpose of page.
  • As noted in 2.4.3 Focus Order, Hidden or empty element receives focus, keyboard focus is lost or misplaced due to user interaction or content update, keyboard focus is not maintained in modal, keyboard focus is not placed on opened modal, keyboard focus order is not logical, modal is closed, focus is not returned to trigger element. 
  • As noted in 2.4.4 Link Purpose (In Context), Purpose of link is not clear in context.
  • As noted in 2.4.6 Headings and Labels, Buttons have the same name but different actions, Programmatic labels do not convey purpose of control.
  • As noted in 2.4.7 Focus Visible, the visual focus indicator is missing.
  • As noted in 3.3.2 Labels or Instructions, Instructions missing for assistive technology users, navigation Instructions missing for the users, label is not persistent, visible label missing.
  • As noted in 4.1.1 Parsing, Anchor or button nested inside another anchor or button, ARIA role does not contain particular children, certain ARIA roles missing particular parents, Interactive controls are nested, the page contains duplicate id attribute values.  
  • As noted in 4.1.2 Name, Role, Value, Custom user interface component is not compatible with AT, ARIA attributes are not allowed without role, ARIA attributes need conform valid values, ARIA input fields need an accessible name, number of carousel slides is apparent visually but not programmatically, state of current carousel slide is not conveyed, dialog is missing appropriate role and/or attributes, unallowed attributes are used, Invalid ARIA attribute names are used, the element's role is incorrect, Slider is missing appropriate role and/or attributes, the element has missing or incorrect states or properties, tooltip content is not accessible to screen readers, ARIA commands are missing an accessible name, button disabled state is not conveyed, button does not have an accessible name, button does not have a role, button is missing both a role and an accessible name, button pressed state is not conveyed, button pressed state of the element is incorrect, form elements missing labels, form field is not labeled, iframe does not have a title, link does not have a role, Expand/collapse state of the element is missing or incorrect, selected state of the element is missing or incorrect, the view options button value (33%) is not exposed to the screen reader users.

 

302.8 With Limited Reach and Strength

Web: Partially Supports

Web: Users with limited reach and strength will not have difficulty navigating to most of the controls. Exceptions include:

  • As noted in 2.1.1 Keyboard, Action cannot be performed with a screen reader turned on, device-dependent event handlers are used, drag and drop feature is not keyboard accessible, function cannot be performed by keyboard alone, Link does not have an href value.    
  • As noted in 2.2.1 Timing Adjustable, Content visually appears and disappears with no ability to adjust timing.
  • As noted in 2.4.2 Page Titled, Page <title> does not identify the purpose of page.
  • As noted in 2.4.3 Focus Order, Hidden or empty element receives focus, keyboard focus is lost or misplaced due to user interaction or content update, keyboard focus is not maintained in modal, keyboard focus is not placed on opened modal, keyboard focus order is not logical, modal is closed, focus is not returned to trigger element.  
  • As noted in 2.4.4 Link Purpose (In Context), Purpose of link is not clear in context.
  • As noted in 2.4.6 Headings and Labels, Buttons have the same name but different actions, Programmatic labels do not convey purpose of control.
  • As noted in 2.4.7 Focus Visible, the visual focus indicator is missing.
  • As noted in 3.3.2 Labels or Instructions, Instructions missing for assistive technology users, navigation Instructions missing for the users, label is not persistent, visible label missing. 
  • As noted in 4.1.1 Parsing, Anchor or button nested inside another anchor or button, ARIA role does not contain particular children, certain ARIA roles missing particular parents, Interactive controls are nested, the page contains duplicate id attribute values.  
  • As noted in 4.1.2 Name, Role, Value, Custom user interface component is not compatible with AT, ARIA attributes are not allowed without role, ARIA attributes need conform valid values, ARIA input fields need an accessible name, number of carousel slides is apparent visually but not programmatically, state of current carousel slide is not conveyed, dialog is missing appropriate role and/or attributes, unallowed attributes are used, Invalid ARIA attribute names are used, the element's role is incorrect, Slider is missing appropriate role and/or attributes, the element has missing or incorrect states or properties, tooltip content is not accessible to screen readers, ARIA commands are missing an accessible name, button disabled state is not conveyed, button does not have an accessible name, button does not have a role, button is missing both a role and an accessible name, button pressed state is not conveyed, button pressed state of the element is incorrect, form elements missing labels, form field is not labeled, iframe does not have a title, link does not have a role, Expand/collapse state of the element is missing or incorrect, selected state of the element is missing or incorrect, the view options button value (33%) is not exposed to the screen reader users.

302.9 With Limited Language, Cognitive, and Learning Abilities

Web: Partially Supports

Web: The product is functional for users with limited language, cognitive, and learning abilities. Users with cognitive disabilities have varying needs for features that allow them to adapt content and work with assistive technology. The product provides labeling for most controls. Exceptions include:

  • As noted in 1.3.2 Meaningful Sequence, Able to browse outside the modal content with screen reader, aria-hidden="true" is used incorrectly, correct reading order of dynamic content not determinable, hidden content is readable with a screen reader, Informative (static) content is not readable by a screen reader, Informative content is not readable by a screen reader, reading order of static content changes meaning, screen reader focus is lost or misplaced due to user interaction or content update.   
  • As noted in 2.2.1 Timing Adjustable, Content visually appears and disappears with no ability to adjust timing.
  • As noted in 2.4.2 Page Titled, Page <title> does not identify the purpose of page.
  • As noted in 2.4.3 Focus Order, Hidden or empty element receives focus, keyboard focus is lost or misplaced due to user interaction or content update, keyboard focus is not maintained in modal, keyboard focus is not placed on opened modal, keyboard focus order is not logical, modal is closed, focus is not returned to trigger element.   
  • As noted in 2.4.4 Link Purpose (In Context), Purpose of link is not clear in context.
  • As noted in 2.4.6 Headings and Labels, Buttons have the same name but different actions, Programmatic label does not convey purpose of control.
  • As noted in 2.4.7 Focus Visible, the visual focus indicator is missing.
  • As noted in 3.3.2 Labels or Instructions, Instructions missing for assistive technology users, navigation Instructions missing for the users, label is not persistent, visible label missing.  
  • As noted in 4.1.1 Parsing, Anchor or button nested inside another anchor or button, ARIA role does not contain particular children, certain ARIA roles missing particular parents, Interactive controls are nested, the page contains duplicate id attribute values.  
  • As noted in 4.1.2 Name, Role, Value, Custom user interface component is not compatible with AT, ARIA attributes are not allowed without role, ARIA attributes need conform valid values, ARIA input fields need an accessible name, number of carousel slides is apparent visually but not programmatically, state of current carousel slide is not conveyed, dialog is missing appropriate role and/or attributes, unallowed attributes are used, Invalid ARIA attribute names are used, the element's role is incorrect, Slider is missing appropriate role and/or attributes, the element has missing or incorrect states or properties, tooltip content is not accessible to screen readers, ARIA commands are missing an accessible name, button disabled state is not conveyed, button does not have an accessible name, button does not have a role, button is missing both a role and an accessible name, button pressed state is not conveyed, button pressed state of the element is incorrect, form elements missing labels, form field is not labeled, iframe does not have a title, link does not have a role, Expand/collapse state of the element is missing or incorrect, selected state of the element is missing or incorrect, the view options button value (33%) is not exposed to the screen reader users.

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

The requirements of Chapter 5 shall apply to software where required by 508 Chapter 2 (Scoping Requirements), 255 Chapter 2 (Scoping Requirements), and where otherwise referenced in any other chapter of the Revised 508 Standards or Revised 255 Guidelines.

EXCEPTION: Where Web applications do not have access to platform accessibility services and do not include components that have access to platform accessibility services, they shall not be required to conform to 502 or 503 provided that they conform to Level A and Level AA Success Criteria and Conformance Requirements in WCAG 2.0.

See WCAG 2.1 section

See information in WCAG 2.1 section

502 Interoperability with Assistive Technology

502.2.1 User Control of Accessibility Features

Platform software shall provide user control over platform features that are defined in the platform documentation as accessibility features.

Not Applicable

The product is not platform software.

502.2.2 No Disruption of Accessibility Features

Software shall not disrupt platform features that are defined in the platform documentation as accessibility features.

Supports

The product does not disrupt platform accessibility features.

502.3 Accessibility Services

Platform software and software tools that are provided by the platform developer shall provide a documented set of accessibility services that support applications running on the platform to interoperate with assistive technology and shall conform to 502.3. Applications that are also platforms shall expose the underlying platform accessibility services or implement other documented accessibility services.

502.3.1 Object Information

The object role, state(s), properties, boundary, name, and description shall be programmatically determinable.

Partially Supports

The product exposes the name, role and state or value of most objects to assistive technology. Exceptions are noted in 4.1.2 Name, Role, Value.

502.3.2 Modification of Object Information

States and properties that can be set by the user shall be capable of being set programmatically, including through assistive technology.

Partially Supports

The product allows users to modify states and properties of controls. Exceptions are noted in 4.1.2 Name, Role, Value.

502.3.3 Row, Column, and Headers

If an object is in a data table, the occupied rows and columns, and any headers associated with those rows or columns, shall be programmatically determinable.

Partially Supports

The product has data tables, and most have programmatically determinable structure, relationships, and content. Exceptions are noted in 1.3.1 Info and Relationships. 

502.3.4 Values

Any current value(s), and any set or range of allowable values associated with an object, shall be programmatically determinable.

Supports

The values of input controls in the product are programmatically determinable.

502.3.5 Modification of Values

Values that can be set by the user shall be capable of being set programmatically, including through assistive technology.

Supports

The product allows users to modify values or text of an object using assistive technologies when those states and properties of an object in the product can be modified by users in general.

502.3.6 Label Relationships

Any relationship that a component has as a label for another component, or of being labeled by another component, shall be programmatically determinable.

Partially Supports

The product UI exposes most label relationships to assistive technologies. Exceptions are noted in 4.1.2 Name, Role, Value.

502.3.7 Hierarchical Relationships

Any hierarchical (parent-child) relationship that a component has as a container for, or being contained by, another component shall be programmatically determinable.

Partially Supports

The product exposes most hierarchical parent-child relationships (e.g., headings and lists) to assistive technology. Exceptions are noted in 1.3.1 Info and Relationships. 

502.3.8 Text

The content of text objects, text attributes, and the boundary of text rendered to the screen, shall be programmatically determinable.

Partially Supports

Most of the product’s text objects, text attributes, and on-screen text boundaries are exposed to assistive technology. Exceptions are noted in 1.3.2 Meaningful Sequence.

502.3.9 Modification of Text

Text that can be set by the user shall be capable of being set programmatically, including through assistive technology.

Supports

The product allows assistive technology to modify the text. 

502.3.10 List of Actions

A list of all actions that can be executed on an object shall be programmatically determinable.

Partially Supports

Most controls in the product expose programmatic role information and actions which can be taken on objects to assistive technology. Exceptions are noted in 4.1.2 Name, Role, Value.

502.3.11 Actions on Objects

Applications shall allow assistive technology to programmatically execute available actions on objects.

Partially Supports 

The product allows assistive technology to perform all available actions on objects.

Exceptions are noted in 2.1.1 Keyboard.

502.3.12 Focus Cursor

Applications shall expose information and mechanisms necessary to track focus, text insertion point, and selection attributes of user interface components.

Partially Supports 

The product exposes focus location, text insertion point, and object selection state for most user interface components. Exceptions are noted in 2.4.7 Focus Visible.

502.3.13 Modification of Focus Cursor

Focus, text insertion point, and selection attributes that can be set by the user shall be capable of being set programmatically, including through the use of assistive technology.

Supports

When a user can set focus, set the text insertion point, or change selection state of an object in the product, then the focus or selection state can also be changed programmatically.

502.3.14 Event Notification

Notification of events relevant to user interactions, including but not limited to, changes in the component’s state(s), value, name, description, or boundary, shall be available to assistive technology.

Partially Supports

The product notifies assistive technology to most user interaction events. Exceptions are noted in 4.1.2 Name, Role, Value.

502.4 Platform Accessibility Features

Platforms and platform software shall conform to the requirements in ANSI/HFES 200.2, Human Factors Engineering of Software User Interfaces — Part 2: Accessibility (2008) listed below:

  • Section 9.3.3 Enable sequential entry of multiple (chorded) keystrokes;
  • Section 9.3.4 Provide adjustment of delay before key acceptance;
  • Section 9.3.5 Provide adjustment of same-key double-strike acceptance;
  • Section 10.6.7 Allow users to choose visual alternative for audio output;
  • Section 10.6.8 Synchronize audio equivalents for visual events;
  • Section 10.6.9 Provide speech output services; and
  • Section 10.7.1 Display any captions provided.

Not Applicable

The product is not platform software.

503 Applications

503.1 General

Applications shall conform to 503.

503.2 User Preferences

Applications shall permit user preferences from platform settings for color, contrast, font type, font size, and focus cursor.

EXCEPTION: Applications that are designed to be isolated from their underlying platform software, including Web applications, shall not be required to conform to 503.2.

Supports 

The product permits user preferences from platform settings.

503.3 Alternative User Interfaces

Where an application provides an alternative user interface that functions as assistive technology, the application shall use platform and other industry standard accessibility services.

Not Applicable

The product does not provide an alternative user interface that functions as assistive technology.

503.4 User Controls for Captions and Audio Description

Where ICT displays video with synchronized audio, ICT shall provide user controls for closed captions and audio descriptions conforming to 503.4.

503.4.1 Caption Controls

Where user controls are provided for volume adjustment, ICT shall provide user controls for the selection of captions at the same menu level as the user controls for volume or program selection.

Not Applicable

The product does not display video with synchronized audio that requires captions.

503.4.2 Audio Description Controls

Where user controls are provided for program selection, ICT shall provide user controls for the selection of audio descriptions at the same menu level as the user controls for volume or program selection.

Not Applicable

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

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.

504.2 Content Creation or Editing

Authoring tools shall provide a mode of operation to create or edit content that conforms to Level A and Level AA Success Criteria and Conformance Requirements in WCAG 2.0 for all supported features and, as applicable, to file formats supported by the authoring tool. Authoring tools shall permit authors the option of overriding information required for accessibility.

EXCEPTION: Authoring tools shall not be required to conform to 504.2 when used to directly edit plain text source code.

See WCAG 2.1 section

See information in WCAG 2.1 section

504.2.1 Preservation of Information Provided for Accessibility in Format Conversion

Authoring tools shall, when converting content from one format to another or saving content in multiple formats, preserve the information required for accessibility to the extent that the information is supported by the destination format.

Does Not Support

Accessibility information is not preserved upon converting Word to PDF.

504.2.2 PDF Export

Authoring tools capable of exporting PDF files that conform to ISO 32000-1:2008 (PDF 1.7) shall also be capable of exporting PDF files that conform to ANSI/AIIM/ISO 14289-1:2016 (PDF/UA-1).

Partially Supports

The product is capable of creating PDF files that conform to PDF 1.7 but only partially conform to PDF/UA-1. PDFs created from Adobe Express will require remediation to be fully PDF/UA-1 conformant.

504.3 Prompts

Authoring tools shall provide a mode of operation that prompts authors to create content that conforms to Level A and Level AA Success Criteria and Conformance Requirements in WCAG 2.0 for supported features and, as applicable, to file formats supported by the authoring tool.

Does Not Support

The product does not provide a mode of operation that prompts authors to create accessible content.

504.4 Templates

Where templates are provided, templates allowing content creation that conforms to Level A and Level AA Success Criteria and Conformance Requirements in WCAG 2.0 shall be provided for a range of template uses for supported features and, as applicable, to file formats supported by the authoring tool.

Does Not Support

Most templates in the product do not allow content creation that conforms to Level A and Level AA Success Criteria and Conformance Requirements in WCAG 2.0.

Chapter 6: Support Documentation and Services

Notes: Information regarding Support Documentation and Services is available in the Accessibility Conformance Report for the Adobe Help Center.

 

EN 301 549 Report

Notes:
 

Chapter 4: Functional Performance Statements (FPS)

Notes:

Criteria

Conformance Level

Remarks and Explanations

4.2.1 Usage without vision

Web: Partially Supports

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

  • As noted in 1.1.1 Non-text Content, Functional image text alternative does not include essential text in image, functional image text alternative does not serve same purpose as image, the decorative image is not hidden from screen readers, Informative Images are missing alternate text, Informative Image text alternative does not present same info as image.
  • As noted in 1.3.1 Info and Relationships, The content visually appears to be a data table but is not marked up as a table, the group label is not associated with its checkboxes, group of form controls not associated with group label, the group label is not associated with its radio buttons, heading levels are out of order, text inappropriately coded as a heading, visual heading text is not marked as heading, <ul> list does not directly contain <li> elements, list or list item is not marked up properly, visual list is not marked up as list.
  • As noted in 1.3.2 Meaningful Sequence, Able to browse outside the modal content with screen reader, aria-hidden="true" is used incorrectly, correct reading order of dynamic content not determinable, hidden content is readable with a screen reader, Informative (static) content is not readable by a screen reader, Informative content is not readable by a screen reader, reading order of static content changes meaning, screen reader focus is lost or misplaced due to user interaction or content update.
  • As noted in 1.4.1 Use of Color, Color alone is used to convey info, Link contrast is not at least 3:1 with surrounding text.
  • As noted in 1.4.13 Content on Hover or Focus, Hover content disappearing.
  • As noted in 2.1.1 Keyboard, Action cannot be performed with a screen reader turned on, device-dependent event handlers are used, drag and drop feature is not keyboard accessible, function cannot be performed by keyboard alone, Link does not have an href value.
  • As noted in 2.2.1 Timing Adjustable, Content visually appears and disappears with no ability to adjust timing.
  • As noted in 2.4.2 Page Titled, Page <title> does not identify the purpose of page.
  • As noted in 2.4.3 Focus Order, Hidden or empty element receives focus, keyboard focus is lost or misplaced due to user interaction or content update, keyboard focus is not maintained in modal, keyboard focus is not placed on opened modal, keyboard focus order is not logical, modal is closed, focus is not returned to trigger element.  
  • As noted in 2.4.4 Link Purpose (In Context), Purpose of link is not clear in context.
  • As noted in 2.4.6 Headings and Labels, Buttons have the same name but different actions, Programmatic label does not convey purpose of control.
  • As noted in 3.3.2 Labels or Instructions, Instructions missing for assistive technology users, navigation Instructions missing for the users, label is not persistent, visible label missing.
  • As noted in 4.1.1 Parsing, Anchor or button nested inside another anchor or button, ARIA role does not contain particular children, certain ARIA roles missing particular parents, Interactive controls are nested, the page contains duplicate id attribute values.
  • As noted in 4.1.2 Name, Role, Value, Custom user interface component is not compatible with AT, ARIA attributes are not allowed without role, ARIA attributes need conform valid values, ARIA input fields need an accessible name, number of carousel slides is apparent visually but not programmatically, state of current carousel slide is not conveyed, dialog is missing appropriate role and/or attributes, unallowed attributes are used, Invalid ARIA attribute names are used, the element's role is incorrect, Slider is missing appropriate role and/or attributes, the element has missing or incorrect states or properties, tooltip content is not accessible to screen readers, ARIA commands are missing an accessible name, button disabled state is not conveyed, button does not have an accessible name, button does not have a role, button is missing both a role and an accessible name, button pressed state is not conveyed, button pressed state of the element is incorrect, form elements missing labels, form field is not labeled, iframe does not have a title, link does not have a role, Expand/collapse state of the element is missing or incorrect, selected state of the element is missing or incorrect, the view options button value (33%) is not exposed to the screen reader users.
  • As noted in 4.1.3 Status Messages, Status messages are not automatically announced.

4.2.2 Usage with limited vision

Web: Partially Supports

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

  • As noted in 1.1.1 Non-text Content, Functional image text alternative does not include essential text in image, functional image text alternative does not serve same purpose as image, the decorative image is not hidden from screen readers, Informative Images are missing alternate text, Informative Image text alternative does not present same info as image.
  • As noted in 1.3.1 Info and Relationships, The content visually appears to be a data table but is not marked up as a table, the group label is not associated with its checkboxes, group of form controls not associated with group label, the group label is not associated with its radio buttons, heading levels are out of order, text inappropriately coded as a heading, visual heading text is not marked as heading, <ul> list does not directly contain <li> elements, list or list item is not marked up properly, visual list is not marked up as list.
  • As noted in 1.3.2 Meaningful Sequence, Able to browse outside the modal content with screen reader, aria-hidden="true" is used incorrectly, correct reading order of dynamic content not determinable, hidden content is readable with a screen reader, Informative (static) content is not readable by a screen reader, Informative content is not readable by a screen reader, reading order of static content changes meaning, screen reader focus is lost or misplaced due to user interaction or content update. 
  • As noted in 1.4.1 Use of Color, Color alone is used to convey info, Link contrast is not at least 3:1 with surrounding text.
  • As noted in 1.4.10 Reflow, Functionality is lost at 320px width equivalent.
  • As noted in 1.4.11 Non-text Contrast, Active user interface component lacks 3 to 1 contrast ratio, an icon lacks 3 to 1 contrast ratio, Graphical object lacks 3 to 1 contrast ratio, State of active component lacks 3 to 1 contrast ratio.
  • As noted in 1.4.13 Content on Hover or Focus, Hover content disappearing.
  • As noted in 1.4.3 Contrast (Minimum), Text content lacks 4.5:1 contrast ratio, link or button text lacks 4.5:1 contrast ratio on hover or focus, Placeholder text lacks 4.5:1 contrast ratio.
  • As noted in 2.1.1 Keyboard, Action cannot be performed with a screen reader turned on, device-dependent event handlers are used, drag and drop feature is not keyboard accessible, function cannot be performed by keyboard alone, Link does not have an href value.  
  • As noted in 2.2.1 Timing Adjustable, Content visually appears and disappears with no ability to adjust timing.
  • As noted in 2.4.2 Page Titled, Page <title> does not identify the purpose of page.
  • As noted in 2.4.3 Focus Order, Hidden or empty element receives focus, keyboard focus is lost or misplaced due to user interaction or content update, keyboard focus is not maintained in modal, keyboard focus is not placed on opened modal, keyboard focus order is not logical, modal is closed, focus is not returned to trigger element.
  • As noted in 2.4.4 Link Purpose (In Context), Purpose of link is not clear in context.
  • As noted in 2.4.6 Headings and Labels, Buttons have the same name but different actions, Programmatic labels do not convey the purpose of control.
  • As noted in 2.4.7 Focus Visible, the visual focus indicator is missing.
  • As noted in 3.3.2 Labels or Instructions, Instructions missing for assistive technology users, navigation Instructions missing for the users, label is not persistent, visible label missing.
  • As noted in 4.1.1 Parsing, Anchor or button nested inside another anchor or button, ARIA role does not contain particular children, certain ARIA roles missing particular parents, Interactive controls are nested, the page contains duplicate id attribute values.  
  • As noted in 4.1.2 Name, Role, Value, Custom user interface component is not compatible with AT, ARIA attributes are not allowed without role, ARIA attributes need conform valid values, ARIA input fields need an accessible name, number of carousel slides is apparent visually but not programmatically, state of current carousel slide is not conveyed, dialog is missing appropriate role and/or attributes, unallowed attributes are used, Invalid ARIA attribute names are used, the element's role is incorrect, Slider is missing appropriate role and/or attributes, the element has missing or incorrect states or properties, tooltip content is not accessible to screen readers, ARIA commands are missing an accessible name, button disabled state is not conveyed, button does not have an accessible name, button does not have a role, button is missing both a role and an accessible name, button pressed state is not conveyed, button pressed state of the element is incorrect, form elements missing labels, form field is not labeled, iframe does not have a title, link does not have a role, Expand/collapse state of the element is missing or incorrect, selected state of the element is missing or incorrect, the view options button value (33%) is not exposed to the screen reader users.
  • As noted in 4.1.3 Status Messages, Status messages are not automatically announced.

4.2.3 Usage without perception of colour

Web: Partially Supports

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

  • As noted in 1.4.1 Use of Color, Color alone is used to convey info, Link contrast is not at least 3:1 with surrounding text.
  • As noted in 1.4.3 Contrast (Minimum), Text content lacks 4.5:1 contrast ratio, link or button text lacks 4.5:1 contrast ratio on hover or focus, Placeholder text lacks 4.5:1 contrast ratio.  
  • As noted in 1.4.11 Non-text Contrast, Active user interface component lacks 3 to 1 contrast ratio, an icon lacks 3 to 1 contrast ratio, Graphical object lacks 3 to 1 contrast ratio, State of active component lacks 3 to 1 contrast ratio.

4.2.4 Usage without hearing

Web: Supports (Not Applicable)

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

4.2.5 Usage with limited hearing

Web: Supports (Not Applicable)

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

4.2.6 Usage with no or limited vocal capability

Web: Supports (Not Applicable)

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

4.2.7 Usage with limited manipulation or strength

Web: Partially Supports

Web: Users with limited manipulation or strength who use speech recognition or switch control software will not have difficulty navigating to most of the controls. Exceptions include:

  • As noted in 1.4.13 Content on Hover or Focus, Hover content disappearing.
  • As noted in 2.1.1 Keyboard, Action cannot be performed with a screen reader turned on, device-dependent event handlers are used, drag and drop feature is not keyboard accessible, function cannot be performed by keyboard alone, Link does not have an href value.
  • As noted in 2.2.1 Timing Adjustable, Content visually appears and disappears with no ability to adjust timing.
  • As noted in 2.4.2 Page Titled, Page <title> does not identify the purpose of page.
  • As noted in 2.4.3 Focus Order, Hidden or empty element receives focus, keyboard focus is lost or misplaced due to user interaction or content update, keyboard focus is not maintained in modal, keyboard focus is not placed on opened modal, keyboard focus order is not logical, modal is closed, focus is not returned to trigger element.
  • As noted in 2.4.4 Link Purpose (In Context), Purpose of link is not clear in context.
  • As noted in 2.4.6 Headings and Labels, Buttons have the same name but different actions, Programmatic label does not convey purpose of control.
  • As noted in 2.4.7 Focus Visible, the visual focus indicator is missing.
  • As noted in 2.5.3 Label in Name, Accessible name does not contain visible label, Accessible name missing.
  • As noted in 3.3.2 Labels or Instructions, Instructions missing for assistive technology users, navigation Instructions missing for the users, label is not persistent, visible label missing. 
  • As noted in 4.1.1 Parsing, Anchor or button nested inside another anchor or button, ARIA role does not contain particular children, certain ARIA roles missing particular parents, Interactive controls are nested, the page contains duplicate id attribute values.  
  • As noted in 4.1.2 Name, Role, Value, Custom user interface component is not compatible with AT, ARIA attributes are not allowed without role, ARIA attributes need conform valid values, ARIA input fields need an accessible name, number of carousel slides is apparent visually but not programmatically, state of current carousel slide is not conveyed, dialog is missing appropriate role and/or attributes, unallowed attributes are used, Invalid ARIA attribute names are used, the element's role is incorrect, Slider is missing appropriate role and/or attributes, the element has missing or incorrect states or properties, tooltip content is not accessible to screen readers, ARIA commands are missing an accessible name, button disabled state is not conveyed, button does not have an accessible name, button does not have a role, button is missing both a role and an accessible name, button pressed state is not conveyed, button pressed state of the element is incorrect, form elements missing labels, form field is not labeled, iframe does not have a title, link does not have a role, Expand/collapse state of the element is missing or incorrect, selected state of the element is missing or incorrect, the view options button value (33%) is not exposed to the screen reader users.

4.2.8 Usage with limited reach

Web: Partially Supports

Web: Users with limited reach will not have difficulty navigating to most of the controls. Exceptions include:

  • As noted in 1.4.13 Content on Hover or Focus, Hover content disappearing.
  • As noted in 2.1.1 Keyboard, Action cannot be performed with a screen reader turned on, device-dependent event handlers are used, drag and drop feature is not keyboard accessible, function cannot be performed by keyboard alone, Link does not have an href value.
  • As noted in 2.2.1 Timing Adjustable, Content visually appears and disappears with no ability to adjust timing.
  • As noted in 2.4.2 Page Titled, Page <title> does not identify the purpose of page.
  • As noted in 2.4.3 Focus Order, Hidden or empty element receives focus, keyboard focus is lost or misplaced due to user interaction or content update, keyboard focus is not maintained in modal, keyboard focus is not placed on opened modal, keyboard focus order is not logical, modal is closed, focus is not returned to trigger element.
  • As noted in 2.4.4 Link Purpose (In Context), Purpose of link is not clear in context.
  • As noted in 2.4.6 Headings and Labels, Buttons have the same name but different actions, Programmatic label does not convey purpose of control.
  • As noted in 2.4.7 Focus Visible, the visual focus indicator is missing.
  • As noted in 2.5.3 Label in Name, Accessible name does not contain visible label, Accessible name missing.
  • As noted in 3.3.2 Labels or Instructions, Instructions missing for assistive technology users, navigation Instructions missing for the users, label is not persistent, visible label missing. 
  • As noted in 4.1.1 Parsing, Anchor or button nested inside another anchor or button, ARIA role does not contain particular children, certain ARIA roles missing particular parents, Interactive controls are nested, the page contains duplicate id attribute values.  
  • As noted in 4.1.2 Name, Role, Value, Custom user interface component is not compatible with AT, ARIA attributes are not allowed without role, ARIA attributes need conform valid values, ARIA input fields need an accessible name, number of carousel slides is apparent visually but not programmatically, state of current carousel slide is not conveyed, dialog is missing appropriate role and/or attributes, unallowed attributes are used, Invalid ARIA attribute names are used, the element's role is incorrect, Slider is missing appropriate role and/or attributes, the element has missing or incorrect states or properties, tooltip content is not accessible to screen readers, ARIA commands are missing an accessible name, button disabled state is not conveyed, button does not have an accessible name, button does not have a role, button is missing both a role and an accessible name, button pressed state is not conveyed, button pressed state of the element is incorrect, form elements missing labels, form field is not labeled, iframe does not have a title, link does not have a role, Expand/collapse state of the element is missing or incorrect, selected state of the element is missing or incorrect, the view options button value (33%) is not exposed to the screen reader users.

4.2.9 Minimize photosensitive seizure triggers

Web: Supports (Not Applicable)

Web: The product does not contain flashing content or media.

4.2.10 Usage with limited cognition, language or learning

Web: Partially Supports

Web: The product is functional for users with limited language, cognitive, and learning abilities. Users with cognitive disabilities have varying needs for features that allow them to adapt content and work with assistive technology. The product provides labeling for most controls. Exceptions include:

  • As noted in 1.3.2 Meaningful Sequence, Able to browse outside the modal content with screen reader, aria-hidden="true" is used incorrectly, correct reading order of dynamic content not determinable, hidden content is readable with a screen reader, Informative (static) content is not readable by a screen reader, Informative content is not readable by a screen reader, reading order of static content changes meaning, screen reader focus is lost or misplaced due to user interaction or content update.
  • As noted in 2.2.1 Timing Adjustable, Content visually appears and disappears with no ability to adjust timing.
  • As noted in 2.4.2 Page Titled, Page <title> does not identify the purpose of page.
  • As noted in 2.4.3 Focus Order, Hidden or empty element receives focus, keyboard focus is lost or misplaced due to user interaction or content update, keyboard focus is not maintained in modal, keyboard focus is not placed on opened modal, keyboard focus order is not logical, modal is closed, focus is not returned to trigger element.
  • As noted in 2.4.4 Link Purpose (In Context), Purpose of link is not clear in context.
  • As noted in 2.4.6 Headings and Labels, Buttons have the same name but different actions, Programmatic label does not convey purpose of control.
  • As noted in 2.4.7 Focus Visible, the visual focus indicator is missing.
  • As noted in 3.3.2 Labels or Instructions, Instructions missing for assistive technology users, navigation Instructions missing for the users, label is not persistent, visible label missing.
  • As noted in 4.1.1 Parsing, Anchor or button nested inside another anchor or button, ARIA role does not contain particular children, certain ARIA roles missing particular parents, Interactive controls are nested, the page contains duplicate id attribute values.  
  • As noted in 4.1.2 Name, Role, Value, Custom user interface component is not compatible with AT, ARIA attributes are not allowed without role, ARIA attributes need conform valid values, ARIA input fields need an accessible name, number of carousel slides is apparent visually but not programmatically, state of current carousel slide is not conveyed, dialog is missing appropriate role and/or attributes, unallowed attributes are used, Invalid ARIA attribute names are used, the element's role is incorrect, Slider is missing appropriate role and/or attributes, the element has missing or incorrect states or properties, tooltip content is not accessible to screen readers, ARIA commands are missing an accessible name, button disabled state is not conveyed, button does not have an accessible name, button does not have a role, button is missing both a role and an accessible name, button pressed state is not conveyed, button pressed state of the element is incorrect, form elements missing labels, form field is not labeled, iframe does not have a title, link does not have a role, Expand/collapse state of the element is missing or incorrect, selected state of the element is missing or incorrect, the view options button value (33%) is not exposed to the screen reader users.
  • As noted in 4.1.3 Status Messages, Status messages are not automatically announced.

4.2.11 Privacy

Web: Supports (Not Applicable)

Web: The product does not provide any privacy features.

Chapter 5: Generic Requirements

Notes:

Criteria

Conformance Level

Remarks and Explanations

5.1 Closed functionality

5.1.2 General

5.1.2.1 Closed functionality

See 5.2 through 13

See information in 5.2 through 13

5.1.2.2 Assistive technology

See 5.1.3 through 5.1.6

See information in 5.1.3 through 5.1.6

5.1.3 Non-visual access

5.1.3.1 Audio output of visual information

Not Applicable

The product does not have closed functionality.

5.1.3.2 Auditory output delivery including speech

Not Applicable

The product does not have closed functionality.

5.1.3.3 Auditory output correlation

Not Applicable

The product does not have closed functionality.

5.1.3.4 Speech output user control

Not Applicable

The product does not have closed functionality.

5.1.3.5 Speech output automatic interruption

Not Applicable

The product does not have closed functionality.

5.1.3.6 Speech output for non-text content

Not Applicable

The product does not have closed functionality.

5.1.3.7 Speech output for video information

Not Applicable

The product does not have closed functionality.

5.1.3.8 Masked entry

Not Applicable

The product does not have closed functionality.

5.1.3.9 Private access to personal data

Not Applicable

The product does not have closed functionality.

5.1.3.10 Non-interfering audio output

Not Applicable

The product does not have closed functionality.

5.1.3.11 Private listening volume

Not Applicable

The product does not have closed functionality.

5.1.3.12 Speaker volume

Not Applicable

The product does not have closed functionality.

5.1.3.13 Volume reset

Not Applicable

The product does not have closed functionality.

5.1.3.14 Spoken languages

Not Applicable

The product does not have closed functionality.

5.1.3.15 Non-visual error identification

Not Applicable

The product does not have closed functionality.

5.1.3.16 Receipts, tickets, and transactional outputs

Not Applicable

The product does not have closed functionality.

5.1.4 Functionality closed to text enlargement

Not Applicable

The product does not have closed functionality.

5.1.5 Visual output for auditory information

Not Applicable

The product does not have closed functionality.

5.1.6 Operation without keyboard interface

5.1.6.1 Closed functionality

See 5.1.3.1 through 5.1.3.16

See information in 5.1.3.1 through 5.1.3.16

5.1.6.2 Input focus

Not Applicable

The product does not have closed functionality.

5.2 Activation of accessibility features

Not Applicable

The product does not have specific documented accessibility features that allow preferences to be set for accessibility. 

5.3 Biometrics

Not Applicable

Biometrics is not included in the product.

5.4 Preservation of accessibility information during conversion

Does Not Support

Accessibility information is not preserved (Reading order) upon converting Word to PDF.

5.5 Operable parts

5.5.1 Means of operation

Not Applicable

The product has only non-mechanical operable parts, such as on-screen buttons, which do not require grasping, pinching, or twisting of the wrist to operate.

5.5.2 Operable parts discernibility

Partially Supports

The product has only non-mechanical operable parts, such as on-screen buttons. Most operable parts have an accessible name which enables them to be discernible without user vision. Exceptions are noted in 1.3.1 Info and Relationships, 2.4.6 Headings and Labels and 4.1.2 Name, Role, Value.

5.6 Locking or toggle controls

5.6.1 Tactile or auditory status

Not Applicable

Tactile or auditory status is not included in the product.

5.6.2 Visual status

Supports

Visual status of controls is discernable in the product.

5.7 Key repeat

Not Applicable

Key repeat functionality is not found in the product.

5.8 Double-strike key acceptance

Not Applicable

Double -strike key acceptance is not found in the product.

5.9 Simultaneous user actions

Not Applicable

The product does not require simultaneous user actions to achieve any functionality.

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 Caption processing technology

7.1.1 Captioning playback

Where ICT displays video with synchronized audio, it shall have a mode of operation to display the available captions. Where closed captions are provided as part of the content, the ICT shall allow the user to choose to display the captions.

Note: Captions may contain information about timing, colour and positioning. This caption data is important for caption users. Timing is used for caption synchronization. Colour can be used for speaker identification. Position can be used to avoid obscuring important information.

Does Not Support

The video player does not provide closed captions.

7.1.2 Captioning synchronization

Where ICT displays captions, the mechanism to display captions shall preserve synchronization between the audio and the corresponding captions.

Not Applicable

The video player does not display closed captions.

7.1.3 Preservation of captioning

Where ICT transmits, converts or records video with synchronized audio, it shall preserve caption data such that it can be displayed in a manner consistent with clauses 7.1.1 and 7.1.2.

Additional presentational aspects of the text such as screen position, text colours, text style and text fonts may convey meaning, based on regional conventions. Altering these presentational aspects could change the meaning and should be avoided wherever possible.

Not Applicable

The video player does not display captions.

7.1.4 Captions characteristics

Where ICT displays captions, it shall provide a way for the user to adapt the displayed characteristics of captions to their individual requirements, except where the captions are displayed as unmodifiable characters.

       Note 1: Defining the background and foreground colour of subtitles, font type, size opacity of the background box of subtitles, and the contour or border of the fonts can contribute to meeting this requirement.

      Note 2: Subtitles that are bitmap images are examples of unmodifiable characters.

Not Applicable

The product does not display closed captions.

7.1.5 Spoken subtitles

Where ICT displays video with synchronized audio, it shall have a mode of operation to provide a spoken output of the available captions, except where the content of the displayed captions is not programmatically determinable.

      NOTE 1: Being able to manage speech output range for spoken subtitles independently from general ICT speech is preferable for most users. That is possible when the audio file with spoken subtitle is delivered in a separate audio track and mixed in the end users device.

      NOTE 2: Presenting the separate audio track with spoken subtitles in synchronization with the displayed subtitles/captions improves understandability of the subtitles.

      NOTE 3: Providing subtitles/captions as separate text-streams, facilitates converting the respective texts into audio.

      NOTE 4: Subtitles that are bitmap images are examples where the content of the displayed captions will not be programmatically determinable.

Not Applicable

The video player does not have subtitles.

7.2.1 Audio description playback

Where ICT displays video with synchronized audio, it shall provide a mechanism to select and play available audio description to the default audio channel.

Where video technologies do not have explicit and separate mechanisms for audio description, an ICT is deemed to satisfy this requirement if the ICT enables the user to select and play several audio tracks.

Note 1: In such cases, the video content can include the audio description as one of the available audio tracks.

Note 2: Audio descriptions in digital media sometimes include information to allow descriptions that are longer than the gaps between dialogue. Support in digital media players for this "extended audio description" feature is useful, especially for digital media that is viewed personally.

Does Not Support

The video player does not have an AD (audio description) button that will play an audio description.

7.2.2 Audio description synchronization

Where ICT has a mechanism to play audio description, it shall preserve the synchronization between the audio/visual content and the corresponding audio description.

Not Applicable

The video player does not have a mechanism to play audio description.

7.2.3 Preservation of audio description

Where ICT transmits, converts, or records video with synchronized audio, it shall preserve audio description data such that it can be played in a manner consistent with clauses 7.2.1 and 7.2.2.

Not Applicable

The video player does not display audio description.

7.3 User controls for captions and audio description

Where ICT primarily displays materials containing video with associated audio content, user controls to activate subtitling and audio description shall be provided to the user at the same level of interaction (i.e. the number of steps to complete the task) as the primary media controls.

Note 1: Primary media controls are the set of controls that the user most commonly uses to control media.

Note 2: Products that have a general hardware volume control, such as a telephone, or a laptop which can be configured to display video through software but which is not its primary purpose, would not need dedicated hardware controls for captions and descriptions; however software controls, or hardware controls mapped through software, would need to be at the same level of interaction.

Note 3: It is best practice for ICT to include additional controls enabling the user to select whether captions and audio description are turned on or off by default.

Not Applicable

The video player does not provide closed captions and audio description.

Chapter 8: Hardware

Notes: Not Applicable
 

Chapter 9: Web

Notes: See WCAG 2.1 section
 

Chapter 10: Non-web Documents

Notes: Not Applicable

 

Chapter 11: Software

Notes:

Criteria

Conformance Level

Remarks and Explanations

11.0 General (informative)

11.1.1.1 through 11.4.1.3

See WCAG 2.1 section

See information in the WCAG 2.1 section.

11.5 Interoperability with assistive technology

11.5.1 Closed functionality

Where the closed functionality of software conforms to clause 5.1 (Closed functionality) it shall not be required to conform with clause 11.5.2 to clause 11.5.2.17.

11.5.2 Accessibility services

11.5.2.1 Platform accessibility service support for software that provides a user interface

Platform software shall provide a set of documented platform services that enable software that provides a user interface running on the platform software to interoperate with assistive technology.

Platform software should support requirements 11.5.2.5 to 11.5.2.17 except that, where a user interface concept that corresponds to one of the clauses 11.5.2.5 to 11.5.2.17 is not supported within the software environment, these requirements are not applicable. For example, selection attributes from 11.5.2.14 (Modification of focus and selection attributes) may not exist in environments that do not allow selection, which is most commonly associated with copy and paste.

See 11.5.2.5 through 11.5.2.17

See information in 11.5.2.5 through 11.5.2.17

11.5.2.2 Platform accessibility service support for assistive technologies

See 11.5.2.5 through 11.5.2.17

See information in 11.5.2.5 through 11.5.2.17

11.5.2.3 Use of accessibility services

Where the software provides a user interface it shall use the applicable documented platform accessibility services. If the documented platform accessibility services do not allow the software to meet the applicable requirements of clauses 11.5.2.5 to 11.5.2.17, then software that provides a user interface shall use other documented services to interoperate with assistive technology.

Note: The term "documented platform accessibility services" refers to the set of services provided by the platform according to clauses 11.5.2.1 and 11.5.2.2.

It is best practice to develop software using toolkits that automatically implement the underlying platform 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

Where the ICT is assistive technology it shall use the documented platform accessibility services.

Note 1: The term "documented platform accessibility services" refers to the set of services provided by the platform according to clauses 11.5.2.1 and 11.5.2.2.

Note 2: Assistive technology can also use other documented accessibility services.

Not applicable

The product is not assistive technology.

11.5.2.5 Object information

Where the software provides a user interface it shall, by using the services as described in clause 11.5.2.3, make the user interface elements' role, state(s), boundary, name, and description programmatically determinable by assistive technologies.

Partially Supports

The product exposes the name, role and state or value of most objects to assistive technology. Exceptions are noted in 4.1.2 Name, Role, Value.

11.5.2.6 Row, column, and headers

Where the software provides a user interface it shall, by using the services as described in clause 11.5.2.3, make the row and column of each cell in a data table, including headers of the row and column if present, programmatically determinable by assistive technologies.

Partially Supports

The product has data tables, and most have programmatically determinable structure, relationships, and content. Exceptions are noted in 1.3.1 Info and Relationships. 

11.5.2.7 Values

Where the software provides a user interface, it shall, by using the services as described in clause 11.5.2.3, make the current value of a user interface element and any minimum or maximum values of the range, if the user interface element conveys information about a range of values, programmatically determinable by assistive technologies.

Supports 

The values of input controls in the product are programmatically determinable.

11.5.2.8 Label relationships

Where the software provides a user interface it shall expose the relationship that a user interface element has as a label for another element, or of being labelled by another element, using the services as described in clause 11.5.2.3, so that this information is programmatically determinable by assistive technologies.

Partially Supports

The product UI exposes most label relationships to assistive technologies. Exceptions are noted in 4.1.2 Name, Role, Value.

11.5.2.9 Parent-child relationships

Where the software provides a user interface it shall, by using the services as described in clause 11.5.2.3, make the relationship between a user interface element and any parent or children elements programmatically determinable by assistive technologies.

Partially Supports

The product exposes most hierarchical parent-child relationships (e.g., headings and lists) to assistive technology. Exceptions are noted in 1.3.1 Info and Relationships.

11.5.2.10 Text

Where the software provides a user interface it shall, by using the services as described in clause 11.5.2.3, make the text contents, text attributes, and the boundary of text rendered to the screen programmatically determinable by assistive technologies.

Partially Supports

Most of the product’s text objects, text attributes, and on-screen text boundaries are exposed to assistive technology. Exceptions are noted in 1.3.2 Meaningful Sequence.

11.5.2.11 List of available actions

Where the software provides a user interface it shall, by using the services as described in clause 11.5.2.3, make a list of available actions that can be executed on a user interface element, programmatically determinable by assistive technologies.

Partially Supports

Most controls in the product expose programmatic role information and actions that can be taken on objects to assistive technology. Exceptions are noted in 4.1.2 Name, Role, Value.

11.5.2.12 Execution of available actions

Where permitted by security requirements, software that provides a user interface shall, by using the services as described in clause 11.5.2.3, allow the programmatic execution of the actions exposed according to clause 11.5.2.11 by assistive technologies.

Note 1: In some cases, the security requirements imposed on a software product may forbid external software from interfering with the ICT product. Examples of systems under strict security requirements are systems dealing with intelligence activities, cryptologic activities related to national security, command and control of military forces.

Note 2: Assistive technologies may be required to maintain the same level of security as the standard input mechanisms supported by the platform.

Partially Supports

The product allows assistive technology to perform all available actions on objects.

Exceptions are noted in 2.1.1 Keyboard.

11.5.2.13 Tracking of focus and selection attributes

Where software provides a user interface it shall, by using the services as described in clause 11.5.2.3, make information and mechanisms necessary to track focus, text insertion point, and selection attributes of user interface elements programmatically determinable by assistive technologies.

Partially Supports

The product exposes focus location, text insertion point, and object selection state for most user interface components. Exceptions are noted in 2.4.7 Focus Visible.

11.5.2.14 Modification of focus and selection attributes

Where permitted by security requirements, software that provides a user interface shall, by using the services as described in clause 11.5.2.3, allow assistive technologies to programmatically modify focus, text insertion point, and selection attributes of user interface elements where the user can modify these items.

Note 1: In some cases, the security requirements imposed on a software product may forbid external software from interfering with the ICT product and so this requirement would not apply. Examples of systems under strict security requirements are systems dealing with intelligence activities, cryptologic activities related to national security, command and control of military forces.

Note 2: Assistive technologies may be required to maintain the same level of security as the standard input mechanisms supported by the platform.

Supports

When a user can set focus, set the text insertion point, or change selection state of an object in the product, then the focus or selection state can also be changed programmatically.

11.5.2.15 Change notification

Where software provides a user interface it shall, by using the services as described in clause 11.5.2.3, notify assistive technologies about changes in those programmatically determinable attributes of user interface elements that are referenced in requirements 11.5.2.5 to 11.5.2.11 and 11.5.2.13.

Partially Supports

The product notifies assistive technology to most user interaction events. Exceptions are noted in 4.1.3 Status Messages, 4.1.2 Name, Role, Value.

11.5.2.16 Modifications of states and properties

Where permitted by security requirements, software that provides a user interface shall, by using the services as described in clause 11.5.2.3, allow assistive technologies to programmatically modify states and properties of user interface elements, where the user can modify these items.

Note 1: In some cases, the security requirements imposed on a software product may forbid external software from interfering with the ICT product and so this requirement would not apply. Examples of systems under strict security requirements are systems dealing with intelligence activities, cryptologic activities related to national security, command and control of military forces.

Note 2: Assistive technologies may be required to maintain the same level of security as the standard input mechanisms supported by the platform.

Partially Supports

The product allows assistive technology to modify states and properties of most of the controls. Exceptions are noted in 4.1.2 Name, Role, Value.

11.5.2.17 Modifications of values and text

Where permitted by security requirements, software that provides a user interface shall, by using the services as described in clause 11.5.2.3, allow assistive technologies to modify values and text of user interface elements using the input methods of the platform, where a user can modify these items without the use of assistive technology.

Note 1: In some cases the security requirements imposed on a software product may forbid external software from interfering with the ICT product and so this requirement would not apply. Examples of systems under strict security requirements are systems dealing with intelligence activities, cryptologic activities related to national security, command and control of military forces.

Note 2: Assistive technologies may be required to maintain the same level of security as the standard input mechanisms supported by the platform.

Supports

The product allows users to modify values and text of an object using assistive technologies when the values and text in the product can be modified by users in general.

11.6 Documented accessibility usage

11.6.1 User control of accessibility features

Where software is a platform, it shall provide sufficient modes of operation for user control over those platform accessibility features documented as intended for users.

Not Applicable

The product is not platform software.

11.6.2 No disruption of accessibility features

Where software provides a user interface it shall not disrupt those documented accessibility features that are defined in platform documentation except when requested to do so by the user during the operation of the software.

Supports

The product does not disrupt platform accessibility features.

11.7 User preferences

Where software provides a user interface it shall provide sufficient modes of operation that use user preferences for platform settings for color, contrast, font type, font size, and focus cursor except for software that is designed to be isolated from its underlying platforms.

Supports

The product permits user preferences from platform settings.

11.8 Authoring tools

11.8.1 Content technology

11.8.2 Accessible content creation

Authoring tools shall enable and guide the production of content that conforms to clauses 9 (Web content) or 10 (Non-Web content) as applicable.

Note: Authoring tools may rely on additional tools where conformance with specific requirements is not achievable by a single tool. For example, a video editing tool may enable the creation of video files for distribution via broadcast television and the web, but authoring of caption files for multiple formats may be provided by a different tool.

See WCAG 2.1 section

See information in WCAG 2.1 section

11.8.3 Preservation of accessibility information in transformations

If the authoring tool provides restructuring transformations or re-coding transformations, then accessibility information shall be preserved in the output if equivalent mechanisms exist in the content technology of the output.

Note 1: Restructuring transformations are transformations in which the content technology stays the same, but the structural features of the content are changed (e.g. linearizing tables, splitting a document into pages).

Note 2: Re-coding transformations are transformations in which the technology used to encode the content is changed.

Does Not Support

Accessibility information is not preserved upon converting PDF to Word, PowerPoint and Excel.

11.8.4 Repair assistance

If the accessibility checking functionality of an authoring tool can detect that content does not meet a requirement of clauses 9 (Web) or 10 (Non-web documents) as applicable, then the authoring tool shall provide repair suggestion(s).

Not Applicable

The product does not provide accessibility checking functionality.

11.8.5 Templates

When an authoring tool provides templates, at least one template that supports the creation of content that conforms to the requirements of clauses 9 (Web) or 10 (non-web documents) as applicable shall be available and identified as such.

Does Not Support

Most templates in the product do not allow content creation that conforms to Level A and Level AA Success Criteria and Conformance Requirements in WCAG 2.1.

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)