Adobe Accessibility Conformance Report

International Edition

(Based on VPAT® Version 2.4)

Name of Product/Version:

Adobe Journey Optimizer

 

Report Date: 

April 2023

 

Product Description: 

Natively built on the industry leading Adobe Experience Platform, Journey Optimizer lets you manage inbound customer engagement and outbound omni channel campaigns in one cloud-native application. With unified, real-time profiles, identity resolution, and segmentation at scale, users can leverage email, push, and in-app messages to engage customers throughout the brand experience. Journey Optimizer provides intelligent offer-decisioning based on real-time customer behavior, extensible across all enterprise content and data applications.

 

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: 

  • Informative images missing text alternative in 'Header', 'Message frequency rules - List view', 'Landing pages - Create landing Page 1', 'Campaigns - List view' screens.
  • Short text alternative is missing in 'Reporting - Journeys (All Time)', 'Reporting - Campaigns (All Time) (Email tab)', 'Reporting - Subscription Lists (All Time)', 'Reporting - Landing Pages (All Time)', 'Reporting - Campaigns (All Time) (Objective tab)' screens.
  • The decorative image is not hidden from screen readers in 'Campaigns - Create campaign 1', 'Campaigns - Create campaign 2' 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: Supports (Not Applicable)

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

1.2.2 Captions (Prerecorded) (Level A)
Also applies to:
EN 301 549 Criteria

  • 9.1.2.2 (Web)
  • 10.1.2.2 (Non-web document)
  • 11.1.2.2 (Open Functionality Software)
  • 11.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 such as headings, lists and checkbox grouping is provided through element semantics or object information or are available in text.

Exceptions include: 

  • Heading levels are out of order in 'Landing pages - Create landing Page 1', 'Message frequency rules - List view', 'Subscription lists - List view', 'Landing pages - List view', 'Landing pages - Presets', 'Message frequency rules - Edit Rule', 'Message frequency rules - Create', 'Landing pages - Create landing Page 2' screens.
  • The group label is not associated with its checkboxes in 'Campaigns - Create campaign 2', 'Message frequency rules - Edit Rule', 'Message frequency rules - Create' screens.
  • Text should not be marked as a heading in 'Reporting - Campaigns (24 hours) (Email tab)', 'Reporting - Landing Pages (All Time)', 'Reporting - Journeys (24 hours)', 'Reporting - Campaigns (All Time) (Email tab)', 'Reporting - Journeys (All Time) - Modify', 'Reporting - Journeys (All Time)', 'Reporting - Subscription Lists (All Time)' screens.
  • List or list item is not marked up properly in 'Alerts - Browse ' screen.
  • Visual heading text is not marked as heading in 'Alerts - History' screen.
  • Headings have two heading levels in 'Reporting - Journeys (24 hours)', ' Reporting - Journeys (All-Time)', ' Reporting - Campaigns (24 hours) (Campaign tab)', ' Reporting - Campaigns (24 hours) (Email tab)', ' Reporting - Campaigns (All Time) (Delivery tab)', ' Reporting - Campaigns (All Time) (Objective tab)', ' Reporting - Campaigns (All Time) (Email tab)', ' Reporting - Landing Pages (All Time) ', ' Reporting - Subscription Lists (All Time)', ' Reporting - Journeys (All Time) - Modify' 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:

  • Informative (static) content is not readable by a screen reader in 'Landing pages - Presets' screen.
  • Hidden content is readable with a screen reader in 'Message frequency rules - Edit Rule', 'Message frequency rules - Create' screens.
  • Reading order of the content changes meaning in 'Landing pages - Create landing Page 1' 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 that 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 functions of the product do not convey information through color alone.

Exceptions include:

  • Link contrast is not at least 3:1 with surrounding text in 'Header' component.
  • Color alone is used to convey info in 'Spectrum Calendar' component.

 

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

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

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

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

Revised Section 508

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

Web: Partially Supports

Web: Most text meets minimum contrast requirements. 

Exceptions include:

  • Placeholder text lacks 4.5:1 contrast ratio in 'Message frequency rules - Edit Rule', 'Message frequency rules - Create', 'Landing pages - Create landing Page 2', 'Subscription lists - List view', 'Alerts - Browse', 'Header', 'Subscription lists - Create Subscription List', 'Landing pages - List view' screens.
  • Text content lacks 4.5:1 contrast ratio in 'Header', 'Campaigns - View campaign', 'Reporting - Campaigns (All Time) (Email tab)', 'Reporting - Subscription Lists (All Time)', 'Reporting - Journeys (All Time)', 'Reporting - Campaigns (All Time) (Objective tab)', 'Reporting - Landing Pages (All Time)', 'Subscription lists - List view' 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:

  • Content is lost at 200% zoom in 'Message frequency rules - List view', 'Copy objects - Copy to sandbox capability in journey management', 'Reporting - Journeys (All Time)', 'Campaigns - List view', 'Landing pages - Create landing Page 1', 'Landing pages - Create landing Page 2' screens.
  • Functionality is lost at 200% zoom in 'Landing pages - Create landing Page 2' screen.

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

Web: At the required width of 320 CSS pixels, most functions of the product do not meet this criterion. There is loss of information or functionality occurs.

Examples Include:

  • Content does not reflow to fit 320px width equivalent in 'Reporting - Campaigns (24 hours) (Email tab)', 'Reporting - Campaigns (All Time) (Objective tab)', 'Campaigns - Create campaign 2', 'Campaigns - Create campaign 1', 'Message frequency rules - Edit Rule', 'Message frequency rules - Create', 'Campaigns - View campaign', 'Reporting - Campaigns (All Time) (Email tab)', 'Reporting - Campaigns (All Time) (Delivery tab)', 'Campaigns - List view', 'Reporting - Journeys (All Time) - Modify', 'Landing pages - Create landing Page 2', 'Reporting - Campaigns (24 hours) (Campaign tab)', 'Subscription lists - Create Subscription List', 'Reporting - Journeys (All Time)', 'Reporting - Journeys (24 hours)', 'Copy objects - Copy to sandbox capability in journey management' screens.
  • Content overlaps other content at 320px width equivalent in 'Reporting - Journeys (24 hours)', 'Message frequency rules - List view', 'Reporting - Campaigns (All Time) (Delivery tab)', 'Landing pages - Create landing Page 1', 'Subscription lists - List view', 'Campaigns - Create campaign 1', 'Reporting - Subscription Lists (All Time)', 'Landing pages - Create landing Page 2', 'Reporting - Journeys (All Time)', 'Subscription lists - Create Subscription List', 'Header', 'Copy objects - Copy to sandbox capability in journey management', 'Reporting - Journeys (All Time) - Modify', 'Campaigns - List view', 'Alerts - History', 'Reporting - Landing Pages (All Time)', 'Reporting - Campaigns (All Time) (Email tab)' 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 meaningful non-text content elements such as active user interface components, informative graphic icons do not have sufficient contrast. 

Examples include:

  • State of active component lacks 3 to 1 contrast ratio in 'React -calendar', 'Spectrum Calendar', 'Project Wide issues', 'Reporting - Journeys (All Time) - Modify' screens.
  • Active user interface component lacks 3 to 1 contrast ratio in 'Header', 'Message frequency rules - Edit Rule', 'Message frequency rules - Create', 'Alerts - Browse', 'Landing pages - List view', 'Landing pages - Create landing Page 1', 'Reporting - Journeys (All Time)', 'Copy objects - Copy to sandbox capability in journey management', 'Subscription lists - List view', 'Subscription lists - Create Subscription List', 'Landing pages - Create landing Page 2' screens.
  • Graphical object lacks 3 to 1 contrast ratio in 'Reporting - Journeys (All Time)', 'Reporting - Campaigns (All Time) (Objective tab)', 'Reporting - Subscription Lists (All Time)', 'Reporting - Campaigns (All Time) (Email tab)', 'Landing pages - Create landing Page 2', 'Reporting - Landing Pages (All Time)' 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: Partially Supports

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

Exceptions Include: 

  • Text spacing content cut off in 'Campaigns - List view', 'Reporting - Journeys (All Time)', 'Subscription lists - Create Subscription List' screens.
  • Text spacing content overlaps in 'Reporting - Journeys (All Time)' screen.

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 product functions, content does not become visible and then hidden in response to pointer hover or keyboard focus. 

Exceptions Include: 

  • Hover content disappearing in 'Reporting - Campaigns (All Time) (Objective tab)', 'Reporting - Subscription Lists (All Time)', 'Reporting - Campaigns (All Time) (Email tab)', 'Reporting - Landing Pages (All Time)', 'Reporting - Journeys (All Time)' 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:

  • Drag and drop features are not keyboard accessible in 'Reporting - Campaigns (All Time) (Email tab)', 'Reporting - Journeys (All Time)', 'Reporting - Campaigns (All Time) (Objective tab)', 'Reporting - Subscription Lists (All Time)', 'Reporting - Campaigns (24 hours) (Email tab)', 'Reporting - Journeys (All Time) - Modify', 'Reporting - Journeys (24 hours)', 'Reporting - Landing Pages (All Time)' screens.
  • Function cannot be performed by keyboard alone in 'Reporting - Landing Pages (All Time)', 'Reporting - Subscription Lists (All Time)' screens.
  • Scrollable region must have keyboard access in 'Reporting - Campaigns (All Time) (Email tab)', 'Campaigns - View campaign' screens.
  • Device-dependent event handlers are used in 'Reporting - Campaigns (All Time) (Objective tab)', 'Reporting - Campaigns (All Time) (Email tab)', 'Reporting - Subscription Lists (All Time)', 'Reporting - Journeys (All Time)', 'Reporting - Landing Pages (All Time)' screens.
  • Action cannot be performed with a screen reader turned on in 'Landing pages - Presets' screen.

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

Web: The product does not provide character key shortcuts.

Guideline 2.2 Enough Time:

Provide users enough time to read and use content.

Criteria

Conformance Level

Remarks and Explanations

2.2.1 Timing Adjustable (Level A)
Also applies to:
EN 301 549 Criteria

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

Revised Section 508

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

Web: Supports (Not Applicable)

Web: The product does not include time limits.

2.2.2 Pause, Stop, Hide (Level A)
Also applies to:
EN 301 549 Criteria

  • 9.2.2.2 (Web)
  • 10.2.2.2 (Non-web document)
  • 11.2.2.2 (Open Functionality Software)
  • 11.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 skip link, 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: Supports

Web: The titles of pages describe their purpose.

2.4.3 Focus Order (Level A)
Also applies to:
EN 301 549 Criteria

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

Revised Section 508

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

Web: Partially Supports

Web: Most of the Components receive focus in a meaningful order. 

Exceptions Include: 

  • Keyboard focus order is not logical in 'Header', 'Campaigns - View campaign', 'Alerts - History', 'Landing pages - Create landing Page 1' screens.
  • Hidden or empty element receives focus in 'Landing pages - Create landing Page 2', 'Message frequency rules - Edit Rule', 'Message frequency rules - Create' screens.
  • Keyboard focus is lost or misplaced due to user interaction or content update in 'Reporting - Campaigns (All Time) (Email tab)' 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: Supports

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

2.4.5 Multiple Ways (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 menu and options in the main section.

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

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

Revised Section 508

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

Web: Partially Supports

Web: Most headings and labels are descriptive.

Exceptions include:

  • Buttons have same name but different actions in 'Reporting - Campaigns (24 hours) (Email tab)', 'Reporting - Campaigns (All Time) (Email tab)', 'Reporting - Subscription Lists (All Time)', 'Reporting - Journeys (24 hours)', 'Reporting - Journeys (All Time) - Modify', 'Reporting - Landing Pages (All Time)', 'Reporting - Campaigns (All Time) (Objective tab)', 'Reporting - Journeys (All Time)' screens.
  • Programmatic label does not convey purpose of control in 'Reporting - Subscription Lists (All Time)', 'Subscription lists - List view', 'Alerts - Browse', 'Landing pages - List view', 'Message frequency rules - List view', 'Reporting - Journeys (All Time)' 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 focusable elements have a visible keyboard focus indicator.

Exceptions include:

  • Focus indicator is missing in 'Header' component.

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: In most product functions, accessible names of controls contain the text of their visible labels. 

Exceptions include: 

  • Accessible name does not contain visible label in 'Reporting - Subscription Lists (All Time)', 'Reporting - Journeys (All Time)' 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: Supports

Web: The language is programmatically determinable within the product.

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

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

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

  • Input error is not described in text in 'Landing pages - Create landing Page 2', 'Landing pages –List view', 'Reporting - Journeys (All Time)', 'Subscription lists - Create Subscription List', 'Subscription lists – List view' screens.

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

Web: Labels are provided for input fields.

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)
  • 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: In most product functions, elements have complete start and end tags, elements are nested according to their specifications, elements do not contain duplicate attributes, and any IDs are unique. 

Exceptions include:

  • Certain ARIA roles do not contain particular children in 'Landing pages - List view', 'Reporting - Journeys (All Time)', 'Reporting - Campaigns (All Time) (Email tab)', 'Message frequency rules - List view', 'Reporting - Subscription Lists (All Time)', 'Spectrum Calendar', 'Subscription lists - List view', 'Reporting - Landing Pages (All Time)', 'Alerts - Browse' screens.
  • The page contains a duplicate id attribute value in 'Landing pages - Presets', 'Message frequency rules - Edit Rule', 'Message frequency rules - Create', 'Subscription lists - Create Subscription List' screens.
  • Interactive controls are nested in 'Message frequency rules - Edit Rule', 'Message frequency rules - Create' 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 in most product functions do not provide programmatic name, role, and/or state information.

Examples include:

  • ARIA attributes missing valid values in 'Campaigns - Create campaign 2' screen.
  • Elements uses ARIA attributes which are not allowed in 'Landing pages - List view', 'Alerts - History', 'Message frequency rules - List view', 'Landing pages - Create landing Page 2', 'Reporting - Journeys (24 hours)', 'Reporting - Journeys (All-Time)','Subscription lists - Create Subscription List', 'Subscription lists - List view', 'Alerts - Browse', 'Campaigns - Create campaign 2' screens.
  • Buttons do not have a name in 'Alerts - Browse', 'Message frequency rules - Edit Rule', 'Message frequency rules - Create' screens.
  • Elements missing allowed ARIA attributes in 'Reporting - Journeys (All Time) - Modify' screen.
  • The element's name is missing or incorrect in 'Landing pages - Create landing Page 2' screen.
  • The element's role is missing or incorrect in 'Header' component.
  • Selected state of the element is missing or incorrect in 'Alerts - History', 'Reporting - Campaigns (All Time) (Email tab)' screens.
  • ARIA hidden elements are focusable or contain focusable elements in 'Reporting - Subscription Lists (All Time)', 'Message frequency rules - Edit Rule', 'Message frequency rules - Create', 'Reporting - Campaigns (All Time) (Objective tab)', 'Campaigns - Create campaign 2' screens.
  • Button does not have a role in 'Alerts - History', 'Landing pages - List view', 'Alerts - Browse', 'Subscription lists - List view', 'Message frequency rules - List view', 'Campaigns - List view' screens.
  • ARIA commands do not have an accessible name in 'Message frequency rules - Edit Rule', 'Message frequency rules - Create' screens.
  • Expand/collapse state of the element is missing or incorrect in 'Alerts - History', 'Header', 'Campaigns - Create campaign 2', 'Alerts - Browse' screens.
  • Tooltip content is not accessible to screen readers in 'Reporting - Subscription Lists (All Time)', 'Reporting - Journeys (All Time)', 'Message frequency rules - Edit Rule', 'Message frequency rules - Create', 'Reporting - Landing Pages (All Time)', 'Reporting - Campaigns (All Time) (Email tab)', 'Reporting - Campaigns (All Time) (Objective tab)' screens.

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)
  • 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 updates do not receive focus, the product mostly provides the update to assistive technology users.

Exception includes:

  • Status message not automatically announced in 'Landing pages - List view', 'Reporting - Campaigns (All Time) (Email tab)', 'Reporting - Campaigns (All Time) (Objective tab)', 'Alerts - Browse', 'Reporting - Subscription Lists (All Time)', 'Subscription lists - List view', 'Alerts - History', 'Message frequency rules - Create', 'Reporting - Journeys (24 hours)', 'Campaigns - List view', 'Reporting - Journeys (All Time) ', 'Reporting - Journeys (All Time) - Modify' screens.

 

Revised Section 508 Report

Notes:
 

Chapter 3: Functional Performance Criteria (FPC)

Notes: 

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, text alternatives are missing, short text alternative are missing, and decorative images are not hidden from screen readers.
  • As noted in 1.3.1 Info and Relationships, Heading levels are out of order, The group label is not associated with its checkboxes, text uses heading markup inappropriately, lists or list items are not marked up properly, and few heading has two heading levels
  • As noted in 1.3.2 Meaningful Sequence, Informative (static) content is not readable by a screen reader, Hidden content is readable with a screen reader, and Reading order of the content changes meaning.
  • As noted in 2.1.1 Keyboard, some interactive elements like buttons are not operable by keyboard.
  • As noted in 2.4.3 Focus Order, Keyboard focus order is not logical, Hidden or empty element receives focus, and Keyboard focus is lost or misplaced due to user interaction or content update.
  • As noted in 2.4.6 Headings and Labels, buttons have same name but different actions and programmatic labels does not convey purpose of control.
  • As noted in 3.3.1 Error Identification, Input error is not described in text.
  • As noted in 4.1.1 Parsing, certain ARIA roles do not contain particular children, pages contains duplicate id attribute values, interactive controls are nested.
  • As noted in 4.1.2 Name, Role, Value, most interactive elements missing accessible name, role and value.

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, text alternatives are missing, short text alternative are missing, and decorative images are not hidden from screen readers.
  • As noted in 1.3.1 Info and Relationships, Heading levels are out of order, The group label is not associated with its checkboxes, text uses heading markup inappropriately, lists or list items are not marked up properly, and few heading has two heading levels
  • As noted in 1.3.2 Meaningful Sequence, Informative (static) content is not readable by a screen reader, Hidden content is readable with a screen reader, and Reading order of the content changes meaning.
  • As noted in 1.4.1 Use of Color, Links do not have sufficient contrast with surrounding text and color alone is used to convey info.
  • As noted in 1.4.3 Contrast (Minimum), regular text and placeholder text lacks minimum color contrast.
  • As noted in 2.1.1 Keyboard, some interactive elements like buttons are not operable by keyboard.
  • As noted in 2.4.3 Focus Order, Keyboard focus order is not logical, Hidden or empty element receives focus, and Keyboard focus is lost or misplaced due to user interaction or content update.
  • As noted in 2.4.6 Headings and Labels, buttons have same name but different actions and programmatic labels does not convey purpose of control.
  • As noted in 2.4.7 Focus Visible, Focus indicator is missing.
  • As noted in 3.3.1 Error Identification, Input error is not described in text.
  • As noted in 4.1.1 Parsing, certain ARIA roles do not contain particular children, pages contains duplicate id attribute values, interactive controls are nested.
  • As noted in 4.1.2 Name, Role, Value, most interactive elements missing accessible name, role and value.

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, Links do not have sufficient contrast with surrounding text and color alone is used to convey info.
  • As noted in 1.4.3 Contrast (Minimum), some text does not meet minimum contrast requirements.
  • As noted in 3.3.1 Error Identification, Input error is not described in text.

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 have difficulty navigating to controls.

Exceptions include:

  • As noted in 2.1.1 Keyboard, some interactive elements like buttons are not operable by keyboard.
  • As noted in 2.4.3 Focus Order, Keyboard focus order is not logical, Hidden or empty element receives focus, and Keyboard focus is lost or misplaced due to user interaction or content update.
  • As noted in 2.4.6 Headings and Labels, buttons have same name but different actions and programmatic labels does not convey purpose of control.
  • As noted in 2.4.7 Focus Visible, Focus indicator is missing.
  • As noted in 4.1.1 Parsing, certain ARIA roles do not contain particular children, pages contains duplicate id attribute values, interactive controls are nested.
  • As noted in 4.1.2 Name, Role, Value, most interactive elements missing accessible name, role and value.

302.8 With Limited Reach and Strength

Web: Partially Supports

Web: Users with limited reach and strength will not have difficulty navigating to controls.

Exceptions include:

  • As noted in 2.1.1 Keyboard, some interactive elements like buttons are not operable by keyboard.
  • As noted in 2.4.3 Focus Order, Keyboard focus order is not logical, Hidden or empty element receives focus, and Keyboard focus is lost or misplaced due to user interaction or content update.
  • As noted in 2.4.6 Headings and Labels, buttons have same name but different actions and programmatic labels does not convey purpose of control.
  • As noted in 2.4.7 Focus Visible, Focus indicator is missing.
  • As noted in 4.1.1 Parsing, certain ARIA roles do not contain particular children, pages contains duplicate id attribute values, interactive controls are nested.
  • As noted in 4.1.2 Name, Role, Value, most interactive elements missing accessible name, role and value.

302.9 With Limited Language, Cognitive, and Learning Abilities

Web: Partially Supports

Web: Most functions of the product are usable with limited language, cognitive, and learning abilities.

Exceptions include:

  • As noted in 1.3.2 Meaningful Sequence, Informative (static) content is not readable by a screen reader, Hidden content is readable with a screen reader, and Reading order of the content changes meaning.
  • As noted in 2.4.3 Focus Order, Keyboard focus order is not logical, Hidden or empty element receives focus, and Keyboard focus is lost or misplaced due to user interaction or content update.
  • As noted in 2.4.6 Headings and Labels, buttons have same name but different actions and programmatic labels does not convey purpose of control.
  • As noted in 2.4.7 Focus Visible, Focus indicator is missing.
  • As noted in 3.3.1 Error Identification, Input error is not described in text.
  • As noted in 4.1.1 Parsing, certain ARIA roles do not contain particular children, pages contains duplicate id attribute values, interactive controls are nested.
  • As noted in 4.1.2 Name, Role, Value, most interactive elements missing accessible name, role and value.

Chapter 4: Hardware

Notes: Not Applicable


Chapter 5: Software

Notes: Not Applicable

 

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, text alternatives are missing, short text alternative are missing, and decorative images are not hidden from screen readers.
  • As noted in 1.3.1 Info and Relationships, Heading levels are out of order, the group label is not associated with its checkboxes , text uses heading markup inappropriately, lists or list items are not marked up properly, and few heading has two heading levels
  • As noted in 1.3.2 Meaningful Sequence, Informative (static) content is not readable by a screen reader, Hidden content is readable with a screen reader, and Reading order of the content changes meaning.
  • As noted in 2.1.1 Keyboard, some interactive elements like buttons are not operable by keyboard.
  • As noted in 2.4.3 Focus Order, Keyboard focus order is not logical, Hidden or empty element receives focus, and Keyboard focus is lost or misplaced due to user interaction or content update.
  • As noted in 2.4.6 Headings and Labels, buttons have same name but different actions and programmatic labels does not convey purpose of control.
  • As noted in 3.3.1 Error Identification, Input error is not described in text.
  • As noted in 4.1.1 Parsing, certain ARIA roles do not contain particular children, pages contains duplicate id attribute values, interactive controls are nested.
  • As noted in 4.1.2 Name, Role, Value, most interactive elements missing accessible name, role and value.
  • 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, text alternatives are missing, short text alternative are missing, and decorative images are not hidden from screen readers.
  • As noted in 1.3.1 Info and Relationships, Heading levels are out of order, the group label is not associated with its checkboxes, text uses heading markup inappropriately, lists or list items are not marked up properly, and few heading has two heading levels
  • As noted in 1.3.2 Meaningful Sequence, Informative (static) content is not readable by a screen reader, Hidden content is readable with a screen reader, and Reading order of the content changes meaning.
  • As noted in 1.4.1 Use of Color, Links do not have sufficient contrast with surrounding text and color alone is used to convey info.
  • As noted in 1.4.3 Contrast (Minimum), regular text and placeholder text lacks minimum color contrast.
  • As noted in 1.4.10 Reflow, content does not reflow to fit 320px width equivalent and content overlaps other content at 320px width equivalent
  • As noted in 1.4.11 Non-text Contrast, most of the non-text informative icons and/or components lack sufficient contrast against the surrounding background.
  • As noted in 1.4.12 Text Spacing, text spacing content cut off and text spacing content overlaps
  • As noted in 1.4.13 Content on Hover or Focus, Hover content disappearing.
  • As noted in 2.1.1 Keyboard, some interactive elements like buttons are not operable by keyboard.
  • As noted in 2.4.3 Focus Order, Keyboard focus order is not logical, Hidden or empty element receives focus, and Keyboard focus is lost or misplaced due to user interaction or content update.
  • As noted in 2.4.6 Headings and Labels, buttons have same name but different actions and programmatic labels does not convey purpose of control.
  • As noted in 2.4.7 Focus Visible, Focus indicator is missing.
  • As noted in 3.3.1 Error Identification, Input error is not described in text.
  • As noted in 4.1.1 Parsing, certain ARIA roles do not contain particular children, pages contains duplicate id attribute values, interactive controls are nested.
  • As noted in 4.1.2 Name, Role, Value, most interactive elements missing accessible name, role and value.
  • 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 functions of the product are usable without perception of color. 

Exceptions include:

  • As noted in 1.4.1 Use of Color, Links do not have sufficient contrast with surrounding text and color alone is used to convey info.
  • As noted in 1.4.3 Contrast (Minimum), some text does not meet minimum contrast requirements.
  • As noted in 1.4.11 Non-text Contrast, most of the non-text informative icons and/or components lack sufficient contrast against the surrounding background.
  • As noted in 3.3.1 Error Identification, Input error is not described in text

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 without 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 who use speech recognition or switch control software will have difficulty navigating to controls.

Exceptions include:

  • As noted in 1.4.13 Content on Hover or Focus, Hover content disappearing.
  • As noted in 2.1.1 Keyboard, some interactive elements like buttons are not operable by keyboard.
  • As noted in 2.4.3 Focus Order, Keyboard focus order is not logical, Hidden or empty element receives focus, and Keyboard focus is lost or misplaced due to user interaction or content update.
  • As noted in 2.4.6 Headings and Labels, buttons have same name but different actions and programmatic labels does not convey purpose of control.
  • As noted in 2.4.7 Focus Visible, Focus indicator is missing.
  • As noted in 2.5.3 Label in Name, Accessible name does not contain visible label.
  • As noted in 4.1.1 Parsing, certain ARIA roles do not contain particular children, pages contains duplicate id attribute values, interactive controls are nested.
  • As noted in 4.1.2 Name, Role, Value, most interactive elements missing accessible name, role and value.

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, some interactive elements like buttons are not operable by keyboard.
  • As noted in 2.4.3 Focus Order, Keyboard focus order is not logical, Hidden or empty element receives focus, and Keyboard focus is lost or misplaced due to user interaction or content update.
  • As noted in 2.4.6 Headings and Labels, buttons have same name but different actions and programmatic labels does not convey purpose of control.
  • As noted in 2.4.7 Focus Visible, Focus indicator is missing.
  • As noted in 2.5.3 Label in Name, Accessible name does not contain visible label.
  • As noted in 4.1.1 Parsing, certain ARIA roles do not contain particular children, pages contains duplicate id attribute values, interactive controls are nested.
  • As noted in 4.1.2 Name, Role, Value, most interactive elements missing accessible name, role and value.

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, Informative (static) content is not readable by a screen reader, Hidden content is readable with a screen reader, and Reading order of the content changes meaning.
  • As noted in 1.4.12 Text Spacing, text spacing content cut off and text spacing content overlaps
  • As noted in 2.4.3 Focus Order, Keyboard focus order is not logical, Hidden or empty element receives focus, and Keyboard focus is lost or misplaced due to user interaction or content update.
  • As noted in 2.4.6 Headings and Labels, buttons have same name but different actions and programmatic labels does not convey purpose of control.
  • As noted in 2.4.7 Focus Visible, Focus indicator is missing.
  • As noted in 3.3.1 Error Identification, Input error is not described in text.
  • As noted in 4.1.1 Parsing, certain ARIA roles do not contain particular children, pages contains duplicate id attribute values, interactive controls are nested.
  • As noted in 4.1.2 Name, Role, Value, most interactive elements missing accessible name, role and value.
  • 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 accessibility features requiring activation.

5.3 Biometrics

Not Applicable

Biometrics is not included in the product.

5.4 Preservation of accessibility information during conversion

Not Applicable

The product does not convert content.

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

Does Not Support

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 discernible 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: Not Applicable

 

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: Not Applicable

 

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)