Adobe Accessibility Conformance Report International Edition
(Based on VPAT® Version 2.4)
Product Information
- Name of Product/Version: Adobe Experience Manager - Forms (Cloud)
- Product Description: Adobe Experience Manager Forms as a Cloud Service offers a cloud-native, Platform as a Service (PaaS) solution for businesses to create, manage, publish, and update complex digital forms while integrating submitted data with back-end processes, business rules, and saving data in an external data store.
- Date: April 2023
- 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 AA: Yes
Level AAA: No
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.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.
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:
role=“img” is used on decorative images in “Test Form Data Model”, “Form Data Model Editor”, “Create Form Data Model (Select Datasource)”, “Form Editor - Side Panel (Components)”, “Rule Editor - Create Rule”, “Create Form Step 3 - Add Properties (Form Model tab)”, “Download Dialog”, “Form Style Editor”, “Rule Editor” screens.
Images do not have alternate text in “Form Editor - Side Panel (Document of Record)” screen.
Text alternative does not present same information as image in “Create Form Step 1 - Select Template (Source Tab)”, “Create Form Step 1 - Select Template (Style Tab)”, “Create Form Step 1 - Select Template (Data Tab)” screens.
[role=”img”] elements does not have an alternative text in “Form Editor”, “Form Editor - Side Panel (Components)”, “Core Component – Runtime”, “Form Data Model Editor - select a data model object - Edit Properties”, “Form Editor - Side Panel (Document of Record)”, “Form Editor - Side Panel (Properties)” screens.
The decorative image is not hidden from screen readers in “Create Form Step 1 - Select Template (Source Tab)”, “Forms & Documents”, “Create Form Step 1 - Select Template (Style Tab)” screens.
Guideline 1.2 Time-based Media:
Provide alternatives for time-based media.
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)
Guideline 1.3 Adaptable:
Create content that can be presented in different ways (for example simpler layout) without losing information or structure.
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: Structure and relationship information such as headings and tables is provided through element semantics.
Exceptions include:
Visible label/form field are not associated in “Test Form Data Model”, “Create Form Step 3 - Add Properties (Form Model tab)”, “Form Data Model Editor - select a data model object - Edit Properties”, “Create Form Step 1 - Select Template (Delivery Tab)”, “Create Form Step 1 - Select Template (Source Tab)”, “Create Form Step 1 - Select Template (Style Tab)”, “Create Form Step 1 - Select Template (Data Tab)” screens.
Form field is not labeled in “Form Editor”, “Form Editor - Side Panel (Document of Record)”, “Create Form Step 1 - Select Template (Submission Tab)”, “Create Form Step 2 - Add Properties (Basic tab)”screens.
Visual heading text is not marked as heading in “Form Style Editor”, “Form Editor - Side Panel (Properties)”, “Create Form Step 1 - Select Template (Source Tab)”, “View - page container and header”, “Form Editor - Side Panel (Document of Record)”, “Rule Editor”, “Form Data Model Editor - select a data model object - Edit Properties”, “Form Editor”, “Create Form Step 1 - Select Template (Style Tab)”, “Create Form Step 1 - Select Template (Data Tab)”, “Create Form Step 1 - Select Template (Submission Tab)”, “Create Form Step 1 - Select Template (Delivery Tab)” screens.
Heading levels are out of order in “Form Editor - Side Panel (Properties)”, “Test Form Data Model” screens.
Visual list is not marked up as list in “Create Form Step 3 - Add Properties (Form Model tab)” screens.
List or list item is not marked up properly in “Header” screen.
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 includes:
Hidden content is readable with a screen reader in “Rule Editor”, “Form Editor - Side Panel (Document of Record)” 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
Guideline 1.4 Distinguishable:
Make it easier for users to see and hear content including separating foreground from background.
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:
Link contrast is not at least 3:1 with surrounding text in “Form Editor - Side Panel (Document of Record)” screen.
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)
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 content lacks 4.5:1 contrast ratio in “Create Form Step 1 - Select Template (Source Tab)”, “Form Editor”, “Rule Editor”, “Form Style Editor”, “Header”, “Preview as HTML - General - Basic Information tab”, “View - page container and header”, “Core Component – Runtime”, “Preview as HTML - Expenditure tab”, “Form Editor”, “Create Form Step 1 - Select Template (Style Tab)”, “Create Form Step 1 - Select Template (Data Tab)” screens.
Link or button text lacks 4.5:1 contrast ratio on hover or focus in “Rule Editor”, “Form Style Editor” screens.
Placeholder text lacks 4.5:1 contrast ratio in “Create Form Step 1 - Select Template (Delivery Tab)” 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, without content and functionality is loss.
Exceptions include:
Content is lost at 200% zoom in “View - page container and header”, “Form Editor - Side Panel (Document of Record)”, “Create Form Step 1 - Select Template (Source Tab)”, “Create Form Step 1 - Select Template (Submission Tab)”, “Test Form Data Model”, “Form Editor - Side Panel (Properties)”, “Form Editor” , “Create Form Step 1 - Select Template (Style Tab)”, “Create Form Step 1 - Select Template (Data Tab)” 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:
Content overlaps other content at 320px width equivalent in “Rule Editor”, “Form Editor - Side Panel (Properties)”, “Create Form Step 1 - Select Template (Source Tab)”, “Create Form Step 1 - Select Template (Submission Tab)”, “View - page container and header”, “Create Form Step 3 - Add Properties (Form Model tab)”, “Form Data Model Editor”, “Form Editor”, “Create Form Step 1 - Select Template (Style Tab)”, “Create Form Step 1 - Select Template (Data Tab)” screens.
Content does not reflow to fit 320px width equivalent in “Create Form Step 1 - Select Template (Source Tab)”, “Rule Editor”, “Create Form Step 3 - Add Properties (Form Model tab)”, “Create Form Step 2 - Add Properties (Basic tab)”, “Create Form Step 1 - Select Template (Style Tab)”, “Create Form Step 1 - Select Template (Data Tab)” , “Create Form Step 1 - Select Template (Submission Tab)”, “Create Form Step 1 - Select Template (Delivery 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: Most meaningful non-text content elements have sufficient contrast requirements.
Exceptions include:
State of active component lacks 3 to 1 contrast ratio in “Create Form Step 1 - Select Template (Source Tab)”, “View - page container and header”, “Form Editor”, “Create Form Step 1 - Select Template (Style Tab)”, “Create Form Step 1 - Select Template (Data Tab)” screens.
Active user interface component lacks 3 to 1 contrast ratio in “View - page container and header”, “Form Editor - Side Panel (Properties)”, “Create Form Step 1 - Select Template (Delivery Tab)”, “Create Form Step 1 - Select Template (Submission Tab)” screens.
An icon lacks 3 to 1 contrast ratio in “View - page container and header”, “Form Editor” 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
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 does not become visible and then hidden in response to pointer hover or keyboard focus.
Exceptions include:
Hover content disappearing in “Form Editor - Side Panel (Properties)” screen.
Additional content not dismissible in “Header” screen.
Guideline 2.1 Keyboard Accessible:
Make all functionality available from a keyboard.
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:
Function cannot be performed by keyboard alone in “Form Editor - Side Panel (Document of Record)”, “Create Form Step 3 - Add Properties (Form Model tab)”, “Form Editor - Side Panel (Properties)”, “Form Style Editor”, “Create Form Step 2 - Add Properties (Basic tab)” screens.
Drag and drop feature is not keyboard accessible in “Form Data Model Editor” 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
Guideline 2.2 Enough Time:
Provide users enough time to read and use content.
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)
Guideline 2.3 Seizures:
Do not design content in a way that is known to cause seizures.
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)
Guideline 2.4 Navigable:
Provide ways to help users navigate, find content, and determine where they are.
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: The product provides mechanism to bypass most repeated blocks.
Exceptions include:
Frames are missing an accessible name in “View - page container and header” screen.
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)
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:
Keyboard focus is lost or misplaced due to user interaction or content update in “Form Editor - Side Panel (Properties)” screen.
Hidden or empty element receives focus in “Form Editor”, “View - page container and header”, “Form Editor - Side Panel (Document of Record)”, “Rule Editor” screens.
Keyboard focus order is not logical in “Form Style Editor”, “Rule Editor” 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)
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 “Create Form Step 1 - Select Template (Delivery Tab)”, “Create Form Step 2 - Add Properties (Basic tab)” screens.
Programmatic label does not convey purpose of control in “Header” screen.
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 “Form Style Editor”, “Create Form Step 1 - Select Template (Source Tab)”, “Create Form Step 1 - Select Template (Style Tab)”, “Create Form Step 1 - Select Template (Data Tab)”. Screens.
Guideline 2.5 Input Modalities:
Make it easier for users to operate functionality through various inputs beyond keyboard.
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: In most product functions, accessible names of control contain text of their visible labels.
Exceptions include:
Accessible name missing in “Create Form Step 1 - Select Template (Delivery Tab)”, “Form Editor”, “Create Form Step 3 - Add Properties (Form Model tab)”, “Create Form Step 1 - Select Template (Source Tab)”, “Create Form Step 2 - Add Properties (Basic tab)”, “Create Form Step 1 - Select Template (Style Tab)”, “Create Form Step 1 - Select Template (Data Tab)” 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
Guideline 3.1 Readable:
Make text content readable and understandable.
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)
Guideline 3.2 Predictable:
Make Web pages appear and operate in predictable ways.
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)
Web: Changes of context do not occur automatically on user input.
Exceptions include:
Form field causes unexpected change in “Form Editor - Side Panel (Properties)” screen.
3.2.3 Consistent Navigation (Level AA)
Also applies to:
EN 301 549 Criteria
- 9.3.2.3 (Web)
- 10.3.2.3 (Non-web document) – Does not apply
- 11.3.2.3 (Open Functionality Software) – Does not apply
- 11.3.2.3 (Closed Software) – Does not apply
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software) – Does not apply to non-web software
- 504.2 (Authoring Tool)
- 602.3 (Support Docs) – Does not apply to non-web docs
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
Guideline 3.3 Input Assistance:
Help users avoid and correct mistakes.
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)
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: Labels are provided for most input fields.
Exceptions include:
Instructions missing for assistive technology users in “Form Editor - Side Panel (Properties)” screen.
Label is not persistent in “Create Form Step 1 - Select Template (Delivery Tab)” screen.
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)
Guideline 4.1 Compatible:
Maximize compatibility with current and future user agents, including assistive technologies.
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: 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 “Rule Editor”, “View - page container and header”, “Rule Editor - Create Rule” screens.
id attribute value must be unique in “Form Editor - Side Panel (Document of Record)”, “View - page container and header”, “Form Style Editor”, “Form Data Model Editor”, “Form Editor”, “Form Data Model Editor - select a data model object - Edit Properties”, “Publish dialog”, “Create Form Data Model (Select Datasource)”, “Rule Editor”, “Rule Editor - Create Rule”, “Create Form Data Model (Add Properties)”, “Create Form Step 2 - Add Properties (Basic tab)”, “Create Form Step 3 - Add Properties (Form Model tab)” screens.
Certain ARIA roles must contain particular children in “Create Form Step 1 - Select Template (Delivery Tab)” screens.
The page contains a duplicate id attribute values in “Preview as HTML - General - Basic Information tab”, “Forms & Documents”, “Create Form Step 1 - Select Template (Source Tab)”, “Preview as HTML - Expenditure tab”, “Create Form Step 1 - Select Template (Style Tab)”, “Create Form Step 1 - Select Template (Data Tab)”, “Create Form Step 1 - Select Template (Submission Tab)”, “Create Form Step 1 - Select Template (Delivery Tab)” screens.
Interactive controls are nested in “Preview as HTML - General - Basic Information tab”, “Preview as HTML - Expenditure tab”, “Form Editor” screens.
IDs used in ARIA and labels must be unique in “Form Style Editor”, “Form Data Model Editor - select a data model object - Edit Properties” 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: User interface components in most product functions provide programmatic name, role, and/or state information.
Exceptions include:
Button does not have a name in “Form Style Editor”, “Form Data Model Editor”, “Create Form Step 1 - Select Template (Submission Tab)” screens.
Button does not have a role in “Create Form Step 3 - Add Properties (Form Model tab)”, “Form Style Editor”, “Create Form Step 1 - Select Template (Source Tab)”, “Create Form Step 1 - Select Template (Style Tab)”, “Create Form Step 1 - Select Template (Data Tab)” screens.
Expand/collapse state of the element is missing or incorrect in “Create Form Step 1 - Select Template (Source Tab)”, “Header”, “Rule Editor”, “Form Editor - Side Panel (Document of Record)”, “Form Data Model Editor”, “View - page container and header”, “Create Form Step 1 - Select Template (Style Tab)”, “Create Form Step 1 - Select Template (Data Tab)” screens.
ARIA hidden element must not be focusable or contain focusable elements in “Form Data Model Editor”, “Create Form Step 1 - Select Template (Source Tab)” screens.
Elements must only use allowed ARIA attributes in “Create Form Step 1 - Select Template (Delivery Tab)”, “Create Form Step 2 - Add Properties (Basic tab)”, “Create Form Step 1 - Select Template (Source Tab)”, “Create Form Step 1 - Select Template (Style Tab)”, “Create Form Step 1 - Select Template (Data Tab)” screens.
Custom radio button does not have a role and/or state in “View - page container and header”, “Form Editor” screens.
ARIA attributes must conform to valid values in “Download Dialog” screen.
Button is missing both a role and a name in “Rule Editor”, “Rule Editor - Create Rule”, “Form Style Editor” screens.
Button pressed state is not conveyed in “Rule Editor” screen.
Selected state of the element is missing or incorrect in “Form Data Model Editor”, “Form Editor”, “View - page container and header” screens.
Treeview is missing required ARIA roles and attributes in “Form Style Editor” screen.
Elements are used unallowed ARIA attributes in “Create Form Step 1 - Select Template (Source Tab)” screen.
Required ARIA attributes must be provided in “Create Form Step 2 - Add Properties (Basic tab)” screen.
4.1.3 Status Messages (Level AA 2.1 only)
Also applies to:
EN 301 549 Criteria
- 9.4.1.3 (Web)
- 10.4.1.3 (Non-web document)
- 11.4.1.3 (Open Functionality Software)
- 11.4.1.3 (Closed Software)
- 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 provides the dynamic and automatic update to the assistive technology.
Exception includes:
Status message not automatically announced in “Create Form Step 1 - Select Template (Source Tab)”, “Create Form Step 1 - Select Template (Style Tab)”, “Create Form Step 1 - Select Template (Data Tab)” 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, role=“img” is used on decorative images, Images do not have alternate text, Text alternative does not present same info as image, [role=”img”] elements does not have an alternative text, The decorative image is not hidden from screen readers.
As noted in 1.3.1 Info and Relationships, Visible label/form field are not associated, Form field is not labeled, Visual heading text is not marked as heading, Heading levels are out of order, Visual list is not marked up as list, List or list item is not marked up properly.
As noted in 1.3.2 Meaningful Sequence, Hidden content is readable with a screen reader.
As noted in 2.1.1 Keyboard, Function cannot be performed by keyboard alone, Drag and drop feature is not keyboard accessible.
As noted in 2.4.1 Bypass Blocks, Frames must have an accessible name.
As noted in 2.4.3 Focus Order, Keyboard focus is lost or misplaced due to user interaction or content update, Hidden or empty element receives focus, Keyboard focus order is not logical.
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 3.2.2 On Input, Form field causes unexpected change.
As noted in 3.3.2 Labels or Instructions, Instructions missing for assistive technology users, Label is not persistent.
As noted in 4.1.1 Parsing, Interactive controls must not be nested, id attribute value must be unique, Certain ARIA roles must contain particular children, page contains a duplicate id attribute values, Interactive controls are nested, IDs used in ARIA and labels must be unique.
As noted in 4.1.2 Name, Role, Value, most interactive elements missing accessible name, role and value.
Web: Most functions of the product are usable with limited vision.
Exceptions include:
As noted in 1.1.1 Non-text Content, role=“img” is used on decorative images, Images must have alternate text, Text alternative does not present same info as image, [role=”img”] elements does not have an alternative text, The decorative image is not hidden from screen readers.
As noted in 1.3.1 Info and Relationships, Visible label/form field are not associated, Form field is not labeled, Visual heading text is not marked as heading, Heading levels are out of order, Visual list is not marked up as list, List or list item is not marked up properly.
As noted in 1.3.2 Meaningful Sequence, Hidden content is readable with a screen reader.
As noted in 1.4.1 Use of color, Link contrast is not at least 3:1 with surrounding text.
As noted in 1.4.3 Contrast (Minimum), Text content lacks 4.5:1 contrast ratio, Elements must have sufficient color contrast, Link or button text lacks 4.5:1 contrast ratio on hover or focus, Placeholder text lacks 4.5:1 contrast ratio.
As noted in 2.1.1 Keyboard, Function cannot be performed by keyboard alone, Drag and drop feature is not keyboard accessible.
As noted in 2.4.1 Bypass Blocks, Frames must have an accessible name.
As noted in 2.4.3 Focus Order, Keyboard focus is lost or misplaced due to user interaction or content update, Hidden or empty element receives focus, Keyboard focus order is not logical.
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.
As noted in 3.2.2 On Input, Form field causes unexpected change.
As noted in 3.3.2 Labels or Instructions, Instructions missing for assistive technology users, Label is not persistent.
As noted in 4.1.1 Parsing, Interactive controls must not be nested, id attribute value must be unique, Certain ARIA roles must contain particular children, page contains a duplicate id attribute values, Interactive controls are nested, IDs used in ARIA and labels must be unique.
As noted in 4.1.2 Name, Role, Value, most interactive elements missing accessible name, role and value.
Web: Most functions of the product are usable without perception of color.
Exceptions include:
As noted in 1.4.1 Use of color, Link contrast is not at least 3:1 with surrounding text.
As noted in 1.4.3 Contrast (Minimum), Text content lacks 4.5:1 contrast ratio, Elements must have sufficient color contrast, Link or button text lacks 4.5:1 contrast ratio on hover or focus, Placeholder text lacks 4.5:1 contrast ratio.
Web: Most functions of the product are usable with limited manipulation with the help of speech recognition or switch control.
Exceptions include:
As noted in 2.1.1 Keyboard, Function cannot be performed by keyboard alone, Drag and drop feature is not keyboard accessible.
As noted in 2.4.1 Bypass Blocks, Frames must have an accessible name.
As noted in 2.4.3 Focus Order, Keyboard focus is lost or misplaced due to user interaction or content update, Hidden or empty element receives focus, Keyboard focus order is not logical.
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.
As noted in 3.3.2 Labels or Instructions, Instructions missing for assistive technology users, Label is not persistent.
As noted in 4.1.1 Parsing, Interactive controls must not be nested, id attribute value must be unique, Certain ARIA roles must contain particular children, page contains a duplicate id attribute values, Interactive controls are nested, IDs used in ARIA and labels must be unique.
As noted in 4.1.2 Name, Role, Value, most interactive elements missing accessible name, role and value.
Web: Most functions of the product are usable with limited reach and strength.
Exceptions include:
As noted in 2.1.1 Keyboard, Function cannot be performed by keyboard alone, Drag and drop feature is not keyboard accessible.
As noted in 2.4.1 Bypass Blocks, Frames must have an accessible name.
As noted in 2.4.3 Focus Order, Keyboard focus is lost or misplaced due to user interaction or content update, Hidden or empty element receives focus, Keyboard focus order is not logical.
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.
As noted in 3.3.2 Labels or Instructions, Instructions missing for assistive technology users, Label is not persistent.
As noted in 4.1.1 Parsing, Interactive controls must not be nested, id attribute value must be unique, Certain ARIA roles must contain particular children, page contains a duplicate id attribute values, Interactive controls are nested, IDs used in ARIA and labels must be unique.
As noted in 4.1.2 Name, Role, Value, most interactive elements missing accessible name, role and value.
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, Hidden content is readable with a screen reader.
As noted in 2.4.1 Bypass Blocks, Frames must have an accessible name.
As noted in 2.4.3 Focus Order, Keyboard focus is lost or misplaced due to user interaction or content update, Hidden or empty element receives focus, Keyboard focus order is not logical.
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.
As noted in 3.2.2 On Input, Form field causes unexpected change.
As noted in 3.3.2 Labels or Instructions, Instructions missing for assistive technology users, Label is not persistent.
As noted in 4.1.1 Parsing, Interactive controls must not be nested, id attribute value must be unique, Certain ARIA roles must contain particular children, page contains a duplicate id attribute values, Interactive controls are nested, IDs used in ARIA and labels must be unique.
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 on the Adobe Accessibility Compliance website.
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, role=“img” is used on decorative images, Images must have alternate text, Text alternative does not present same info as image, [role=”img”] elements does not have an alternative text, The decorative image is not hidden from screen readers.
As noted in 1.3.1 Info and Relationships, Visible label/form field are not associated, Form field is not labeled, Visual heading text is not marked as heading, Heading levels are out of order, Visual list is not marked up as list, List or list item is not marked up properly.
As noted in 1.3.2 Meaningful Sequence, Hidden content is readable with a screen reader.
As noted in 2.1.1 Keyboard, Function cannot be performed by keyboard alone, Drag and drop feature is not keyboard accessible.
As noted in 2.4.1 Bypass Blocks, Frames must have an accessible name.
As noted in 2.4.3 Focus Order, Keyboard focus is lost or misplaced due to user interaction or content update, Hidden or empty element receives focus, Keyboard focus order is not logical.
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 3.2.2 On Input, Form field causes unexpected change.
As noted in 3.3.2 Labels or Instructions, Instructions missing for assistive technology users, Label is not persistent.
As noted in 4.1.1 Parsing, Interactive controls must not be nested, id attribute value must be unique, Certain ARIA roles must contain particular children, page contains a duplicate id attribute values, Interactive controls are nested, IDs used in ARIA and labels must be unique.
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 message not automatically announced.
Web: Most functions of the product are usable with limited vision.
Exceptions include:
As noted in 1.1.1 Non-text Content, role=“img” is used on decorative images, Images must have alternate text, Text alternative does not present same info as image, [role=”img”] elements does not have an alternative text, The decorative image is not hidden from screen readers.
As noted in 1.3.1 Info and Relationships, Visible label/form field are not associated, Form field is not labeled, Visual heading text is not marked as heading, Heading levels are out of order, Visual list is not marked up as list, List or list item is not marked up properly.
As noted in 1.3.2 Meaningful Sequence, Hidden content is readable with a screen reader.
As noted in 1.4.1 Use of color, Link contrast is not at least 3:1 with surrounding text.
As noted in 1.4.3 Contrast (Minimum), Text content lacks 4.5:1 contrast ratio, Elements must have sufficient color contrast, Link or button text lacks 4.5:1 contrast ratio on hover or focus, Placeholder text lacks 4.5:1 contrast ratio.
As noted in 1.4.10 Reflow, Content overlaps other content at 320px width equivalent, Content does not reflow to fit 320px width equivalent.
As noted in 1.4.11 Non-text Contrast, State of active component lacks 3 to 1 contrast ratio, Active user interface component lacks 3 to 1 contrast ratio, an icon lacks 3 to 1 contrast ratio.
As noted in 1.4.13 Content on Hover or Focus, Hover content disappearing, Additional content not dismissible.
As noted in 2.1.1 Keyboard, Function cannot be performed by keyboard alone, Drag and drop feature is not keyboard accessible.
As noted in 2.4.1 Bypass Blocks, Frames must have an accessible name.
As noted in 2.4.3 Focus Order, Keyboard focus is lost or misplaced due to user interaction or content update, Hidden or empty element receives focus, Keyboard focus order is not logical.
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.
As noted in 3.2.2 On Input, Form field causes unexpected change.
As noted in 3.3.2 Labels or Instructions, Instructions missing for assistive technology users, Label is not persistent.
As noted in 4.1.1 Parsing, Interactive controls must not be nested, id attribute value must be unique, Certain ARIA roles must contain particular children, page contains a duplicate id attribute values, Interactive controls are nested, IDs used in ARIA and labels must be unique.
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 message not automatically announced.
Web: Most functions of the product are usable without perception of color.
Exceptions include:
As noted in 1.4.1 Use of color, Link contrast is not at least 3:1 with surrounding text.
As noted in 1.4.3 Contrast (Minimum), Text content lacks 4.5:1 contrast ratio, Elements must have sufficient color contrast, Link or button text lacks 4.5:1 contrast ratio on hover or focus, Placeholder text lacks 4.5:1 contrast ratio.
As noted in 1.4.11 Non-text Contrast, State of active component lacks 3 to 1 contrast ratio, Active user interface component lacks 3 to 1 contrast ratio, an icon lacks 3 to 1 contrast ratio.
Web: Most functions of the product are usable with limited manipulation or strength with the help of speech recognition or switch control.
Exceptions include:
As noted in 1.4.13 Content on Hover or Focus, Hover content disappearing, Additional content not dismissible.
As noted in 2.1.1 Keyboard, Function cannot be performed by keyboard alone, Drag and drop feature is not keyboard accessible.
As noted in 2.4.1 Bypass Blocks, Frames must have an accessible name.
As noted in 2.4.3 Focus Order, Keyboard focus is lost or misplaced due to user interaction or content update, Hidden or empty element receives focus, Keyboard focus order is not logical.
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.
As noted in 2.5.3 Label in Name, Accessible name missing.
As noted in 3.3.2 Labels or Instructions, Instructions missing for assistive technology users, Label is not persistent.
As noted in 4.1.1 Parsing, Interactive controls must not be nested, id attribute value must be unique, Certain ARIA roles must contain particular children, page contains a duplicate id attribute values, Interactive controls are nested, IDs used in ARIA and labels must be unique.
As noted in 4.1.2 Name, Role, Value, most interactive elements missing accessible name, role and value.
Web: Most functions of the product are usable with limited reach.
Exceptions include:
As noted in 1.4.13 Content on Hover or Focus, Hover content disappearing, Additional content not dismissible.
As noted in 2.1.1 Keyboard, Function cannot be performed by keyboard alone, Drag and drop feature is not keyboard accessible.
As noted in 2.4.1 Bypass Blocks, Frames must have an accessible name.
As noted in 2.4.3 Focus Order, Keyboard focus is lost or misplaced due to user interaction or content update, Hidden or empty element receives focus, Keyboard focus order is not logical.
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.
As noted in 2.5.3 Label in Name, Accessible name missing.
As noted in 3.3.2 Labels or Instructions, Instructions missing for assistive technology users, Label is not persistent.
As noted in 4.1.1 Parsing, Interactive controls must not be nested, id attribute value must be unique, Certain ARIA roles must contain particular children, page contains a duplicate id attribute values, Interactive controls are nested, IDs used in ARIA and labels must be unique.
As noted in 4.1.2 Name, Role, Value, most interactive elements missing accessible name, role and value.
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, Hidden content is readable with a screen reader.
As noted in 2.4.1 Bypass Blocks, Frames must have an accessible name.
As noted in 2.4.3 Focus Order, Keyboard focus is lost or misplaced due to user interaction or content update, Hidden or empty element receives focus, Keyboard focus order is not logical.
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.
As noted in 3.2.2 On Input, Form field causes unexpected change.
As noted in 3.3.2 Labels or Instructions, Instructions missing for assistive technology users, Label is not persistent.
As noted in 4.1.1 Parsing, Interactive controls must not be nested, id attribute value must be unique, Certain ARIA roles must contain particular children, page contains a duplicate id attribute values, Interactive controls are nested, IDs used in ARIA and labels must be unique.
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 message not automatically announced.
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
Voluntary Product Accessibility Template® and VPAT® are a registered trademark of Information Technology Industry Council (ITI)