Adobe Accessibility Conformance Report International Edition
(Based on VPAT® Version 2.4)
Product Information
- Name of Product/Version: Adobe Developer Console
- Product Description: The Developer Console enables third-party developers (Customer’s IT team, system integrators, partner developers, and individuals) to access various developer offerings across our three clouds. On the Developer Console, a developer creates projects that map 1:1 to an application (or plugin, extension, integration) they are trying to build. In the project, they add different Adobe APIs, Events, and Functions as would be required by her application, thereby gaining API keys and other credentials needed to make their application work.
- Date: November 2022
- 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:
Level A (Yes)
Level AA (Yes)
Level AAA (No)
Level A (Yes)
Level AA (Yes)
Level AAA (No)
Terms
The terms used in the Conformance Level information are defined as follows:
- Supports: The functionality of the product has at least one method that meets the criterion without known defects or meets with equivalent facilitation.
- Partially Supports: Some functionality of the product does not meet the criterion.
- Does Not Support: The majority of product functionality does not meet the criterion.
- Not Applicable: The criterion is not relevant to the product.
- Not Evaluated: The product has not been evaluated against the criterion. This can be used only in WCAG 2.0 Level AAA.
WCAG 2.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.
Table 1: Success Criteria, Level A and AA
Notes:
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: The product provides sufficient text alternatives for most instances of active and informative images.
Exceptions include:
The text alternative does not present the same information as the image in the Project screens.
Decorative images are not hidden from screen readers throughout the site experience.
Text alternative is missing in the Events, and Project screens.
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)
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)
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)
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)
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)
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: Most visual structure and relationship information is provided through object information or are available in text.
Exceptions include:
Data table has missing or incomplete header cell markup in the Events screens.
Checkboxes and radio buttons are not consistently grouped with a reference to their labels.
Text should not be marked as a heading in the API, and Events screens.
Visual heading text is not marked as heading in the on several overview screens.
Visual list is not marked up as list in the Project 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: The product presents most content in a meaningful sequence.
Exceptions include:
aria-hidden="true" is used incorrectly Events, and Project screens.
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)
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
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
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: Most functions of the product do not convey information through color alone.
Exceptions include:
Color alone is used to convey info in the Events screens.
Some link text relies on color to distinguish interactivity from surrounding text.
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: Most text meets minimum contrast requirements.
Exceptions include:
Text lacks 4.5:1 contrast ratio in the Project screens.
Placeholder text lacks 4.5:1 contrast ratio in the Projects screen.
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: 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 the Events and Project 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)
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: 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:
Some page content does not reflow to fit horizontally when the page width is changed to 320 CSS pixels on the Home screen, the APIs & Services screens, and the Project screens.
Some page content overlaps other content at 320px width equivalent in the Service Account generation, API, Events, Project and SDK Download 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: Most meaningful non-text content elements have sufficient contrast requirements.
Exceptions include:
Active user interface component lacks 3 to 1 contrast ratio in the Service Account generation screens.
An icon lacks 3 to 1 contrast ratio in the Project screen.
State of active component lacks 3 to 1 contrast ratio throughout the site experience.
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: Most functions of the product support the required text style properties without loss of content or functionality.
Exceptions include:
Some content cannot be seen because it is cut off when the text spacing is adjusted in the API, Events, and Project screens.
Some content is getting overlapped when the text spacing is adjusted in the Projects screens.
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: In most product functions, content becomes visible and then hidden in response to pointer hover or keyboard focus.
Exceptions include
Additional content not dismissible in the API, Events, and APIs & Services screen.
Hover content disappearing in the APIs & Services screen.
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: Most product functionality can be operated through a keyboard interface.
Exceptions include:
Device-dependent event handlers are used in the APIs & Services, and Project screens.
Function cannot be performed by keyboard alone in the API screens.
Scrollable content is not keyboard accessible in the Projects 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)
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
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)
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)
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)
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)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
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: Most of the titles of pages describe their purpose.
Exceptions include:
Page <title> does not identify purpose of page in the Home screen.
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: Most components receive focus in a meaningful order.
Exceptions include:
Hidden or empty element receives keyboard focus in the API screen.
Modal is closed, focus is not returned to trigger in the API screen.
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: Most links purpose in the product can be determined from the link text alone or from the programmatic context of the link.
Exceptions include:
Multiple links have the same programmatic link text but different destinations in the API, and APIs & Services screens.
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
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: Most headings and labels are descriptive.
Exceptions include:
Buttons have same name but different actions in the APIs & Services, and Project screens.
Programmatic label does not convey purpose of control in the API, APIs & Services, Projects, home screen, and SDK Download 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: Most focusable elements have a visible keyboard focus indicator.
Exceptions include:
Focus indicator is missing in the API, Events, home screen, and Projects screens.
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
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
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: The accessible names of most controls contain the text of their visible labels.
Exceptions include:
Accessible name does not contain visible label in the Projects 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
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)
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)
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)
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)
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
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
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: Most input errors are identified and described to the users in text.
Exceptions include:
Input error is not described in the Events 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)
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)
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)
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: 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:
Interactive controls must not be nested in the Projects screen.
IDs used in ARIA and labels must be unique in the Projects screen.
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) – Not required
- 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: User interface components in most product functions provide programmatic name, role, and/or state information. However, some controls do not provide name, role, and/or state information to assistive technology.
Exceptions include:
Elements must only use allowed ARIA attributes in the API, and Project screens.
The element's role is missing or incorrect in the API , Events, and Project screens.
The element has missing or incorrect states or properties in the API screens.
The element functions as if it has two roles in the API, and Events screens.
Toolbar is missing appropriate role and/or attributes in the Service Account generation screen.
Tooltip content is not accessible to screen readers in the APIs & Services, and Project screens.
Button does not have a role in the API, Events, Projects, and Service Account generation screens.
Button pressed state is not conveyed in the API, and Events screens.
Expand/collapse state of the element is missing or incorrect add API, Project, SDK Download, and Service Account generation screens.
Selected state of the element is missing or incorrect in the Project 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) – 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: When status messages do not receive focus, the product does not provide the dynamic and automatic update to the assistive technology.
Exceptions include:
Status message and the status update are not automatically in the APIs & Services, and Project screens.
Revised Section 508 Report
Notes:
Chapter 3: Functional Performance Criteria (FPC)
Notes:
Web: Most functions of the product are usable without vision.
Exceptions include:
As noted in 1.1.1 Non-text Content, text alternative does not serve same purpose as image, the decorative image is not hidden from screen readers, text alternative does not present same info as image, text alternative is missing.
As noted in 1.3.1 Info and Relationships, data table has missing or incomplete header cell markup, group label is not associated with its group of radio buttons, group label is not associated with its group of checkboxes , text should not be marked as a heading, visual heading text is not marked as heading, visual list is not marked up as list.
As noted in 1.3.2 Meaningful Sequence, aria-hidden="true" is used incorrectly.
As noted in 1.4.1 Use of Color, color alone is used to convey info .
As noted in 1.4.3 Contrast (Minimum), text lacks 4.5:1 contrast ratio, Placeholder text lacks 4.5:1 contrast ratio.
As noted in 1.4.4 Resize text, content is lost at 200% zoom.
As noted in 2.1.1 Keyboard, device-dependent event handlers are used, function cannot be performed by keyboard alone, scrollable region is not keyboard accessible.
As noted in 2.4.2 Page Titled, page <title> does not identify purpose of page.
As noted in 2.4.3 Focus Order, hidden or empty element receives focus, modal is closed, focus is not returned to trigger.
As noted in 2.4.4 Link Purpose (In Context), multiple links have the same programmatic link text but different destinations.
As noted in 2.4.6 Headings and Labels, buttons have same name but different actions, Programmatic label does not convey purpose of control.
As noted in 2.4.7 Focus Visible, focus indicator is missing, focus indicator is not visible.
As noted in 2.5.3 Label in Name, accessible name does not contain visible label.
As noted in 3.3.1 Errors Identification, Input error is not described in text.
As noted in 4.1.1 Parsing, interactive controls must not be nested, IDs used in ARIA and labels must be unique.
As noted in 4.1.2 Name, Role, Value, elements must only use allowed ARIA attributes, the element's role is missing or incorrect, the element has missing or incorrect states or properties, the element functions as if it has two roles, toolbar is missing appropriate role and attributes, tooltip content is not accessible to screen readers, button does not have a role, button pressed state is not conveyed, expand/collapse state of the element is missing or incorrect, selected state of the element is missing or incorrect.
Web: Most functions of the product are usable with limited vision.
Exceptions include:
As noted in 1.4.3 Contrast (Minimum), text lacks 4.5:1 contrast ratio, Placeholder text lacks 4.5:1 contrast ratio.
As noted in 1.4.4 Resize text, content is lost at 200% zoom.
As noted in 2.4.7 Focus Visible, focus indicator is missing, focus indicator is not visible.
Web: Most functions of the product are usable without perception of color.
Exceptions include:
As noted in 1.4.3 Contrast (Minimum), text lacks 4.5:1 contrast ratio, Placeholder text lacks 4.5:1 contrast ratio.
As noted in 1.4.1 Use of Color, Color alone is used to convey info.
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, device-dependent event handlers are used, function cannot be performed by keyboard alone, scrollable region is not keyboard accessible.
Web: Users with limited reach and strength will have difficulty navigating to controls.
Exceptions include:
As noted in 2.1.1 Keyboard, device-dependent event handlers are used, function cannot be performed by keyboard alone, scrollable region is not keyboard accessible.
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 3.3.1 Errors Identification, input error is not described in text.
As noted in 2.4.4 Link Purpose (In Context), Multiple links have the same programmatic link text but different destinations.
As noted in 2.4.6 Descriptive Labels, Buttons have same name but different actions, Programmatic label does not convey purpose of control.
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:
Web: Most functions of the product are usable without vision.
Exceptions include:
As noted in 1.1.1 Non-text Content, text alternative does not serve same purpose as image, the decorative image is not hidden from screen readers, text alternative does not present same info as image, text alternative is missing.
As noted in 1.3.1 Info and Relationships, data table has missing or incomplete header cell markup, group label is not associated with its group of radio buttons, group label is not associated with its group of checkboxes , text should not be marked as a heading, visual heading text is not marked as heading, visual list is not marked up as list.
As noted in 1.3.2 Meaningful Sequence, aria-hidden="true" is used incorrectly.
As noted in 1.4.1 Use of Color, Color alone is used to convey info .
As noted in 1.4.10 Reflow, content does not reflow to fit 320px width equivalent, content overlaps other content 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, state of active component lacks 3 to 1 contrast ratio.
As noted in 1.4.12 Text Spacing, text spacing content cut off, text spacing content overlaps.
As noted in 1.4.13 Content on Hover or Focus, additional content not dismissible, hover content disappearing.
As noted in 1.4.3 Contrast (Minimum), text lacks 4.5:1 contrast ratio, Placeholder text lacks 4.5:1 contrast ratio.
As noted in 1.4.4 Resize text, content is lost at 200% zoom.
As noted in 2.1.1 Keyboard, device-dependent event handlers are used, function cannot be performed by keyboard alone, scrollable region is not keyboard accessible.
As noted in 2.4.2 Page Titled, page <title> does not identify purpose of page.
As noted in 2.4.3 Focus Order, Hidden or empty element receives focus, modal is closed, focus is not returned to trigger.
As noted in 2.4.4 Link Purpose (In Context), multiple links have the same programmatic link text but different destinations.
As noted in 2.4.6 Headings and Labels, buttons have same name but different actions, Programmatic label does not convey purpose of control.
As noted in 2.4.7 Focus Visible, focus indicator is missing, focus indicator is not visible.
As noted in 2.5.3 Label in Name, accessible name does not contain visible label.
As noted in 3.3.1 Errors Identification, Input error is not described in text.
As noted in 4.1.1 Parsing, interactive controls must not be nested, IDs used in ARIA and labels must be unique.
As noted in 4.1.2 Name, Role, Value, elements must only use allowed ARIA attributes, the element's role is missing or incorrect, the element has missing or incorrect states or properties, the element functions as if it has two roles, toolbar is missing appropriate role and/or attributes, tooltip content is not accessible to screen readers, button does not have a role, button pressed state is not conveyed, expand/collapse state of the element is missing or incorrect, selected state of the element is missing or incorrect.
As noted in 4.1.3 Status Messages, status message not automatically announced.
Web: Most functions of the product are usable with limited vision.
Exceptions include:
As noted in 1.4.1 Use of Color, Color alone is used to convey info.
As noted in 1.4.10 Reflow, content does not reflow to fit 320px width equivalent, content overlaps other content 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, state of active component lacks 3 to 1 contrast ratio.
As noted in 1.4.12 Text Spacing, text spacing content cut off, text spacing content overlaps.
As noted in 1.4.13 Content on Hover or Focus, additional content not dismissible, hover content disappearing.
As noted in 1.4.3 Contrast (Minimum), text lacks 4.5:1 contrast ratio, Placeholder text lacks 4.5:1 contrast ratio.
As noted in 1.4.4 Resize text, content is lost at 200% zoom.
As noted in 2.4.7 Focus Visible, focus indicator is missing, focus indicator is not visible.
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, and Link contrast is not at least 3:1 with surrounding text.
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, state of active component lacks 3 to 1 contrast ratio.
As noted in 1.4.3 Contrast (Minimum), text lacks 4.5:1 contrast ratio, Placeholder text lacks 4.5:1 contrast ratio.
Web: Users with limited manipulation or strength who use speech recognition or switch control software will have difficulty navigating to controls.
Exceptions include:
As noted in 2.1.1 Keyboard, device-dependent event handlers are used, function cannot be performed by keyboard alone, scrollable region is not keyboard accessible.
As noted in 1.4.13 Content on Hover or Focus, additional content not dismissible, hover content disappearing.
Web: Users with limited reach will have difficulty navigating to controls.
Exceptions include:
As noted in 2.1.1 Keyboard, device-dependent event handlers are used, function cannot be performed by keyboard alone, scrollable region is not keyboard accessible.
As noted in 1.4.13 Content on Hover or Focus, additional content not dismissible, hover content disappearing.
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 3.3.1 Errors Identification, input error is not described in text.
As noted in 2.4.4 Link Purpose (In Context), Multiple links have the same programmatic link text but different destinations.
As noted in 2.4.6 Descriptive Labels, Buttons have same name but different actions, Programmatic label does not convey purpose of control.
Chapter 5: Generic Requirements
Notes:
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