Adobe Accessibility Conformance Report International Edition
(Based on VPAT® Version 2.4)
Product Information
- Name of Product/Version: Adobe Experience Manager - Forms (Service Pack)
- Product Description: Adobe Experience Manager (AEM) provides an easy-to-use solution to create, manage, publish, and update complex digital forms while integrating with back-end processes, business rules, and data.
- AEM Forms combine form authoring, management, and publishing along with correspondence management capabilities, document security, and integrated analytics to create engaging end-to-end experiences.
- 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:
Images must have alternate text in “Edit - Print channel - editor panel” screen.
Text alternative does not serve same purpose as image in “Edit - Side Panel - Content tab”, “Web channel - editor panel with Channels Tab showing” screens.
role=”img” is used on decorative images in “Edit - Side Panel - Content tab” screen.
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: Most visual structure and relationship information is provided through element semantics or object information or are available in text.
Exceptions include:
Visual heading text is not marked as heading in “Interactive Content - Preview Print Channel”, “Edit - Print channel - image Properties”, “Edit - Side Panel - Content tab”, “Web channel - editor panel with Channels Tab showing”, “Edit - Print channel - Document Fragment – Properties”, “Rule Editor - Code Editor” “Interactive Content - Preview Both Channel For ICs having Print as well as Web” screens.
Form elements must have labels in “Interactive Content – Properties”.
<ul> and <ol> must only directly contain <li>, <script> or <template> elements in “Open Agent UI – Content”, “Open Agent UI - Print Preview”, “Open Agent UI – Data” screens.
<li> elements must be contained in a <ul> or <ol> in “Open Agent UI – Content”, “Open Agent UI - Print Preview”, “Open Agent UI – Data” screens.
Text should not be marked as a heading in “Edit - Print channel - Document Fragment – Properties”, “Edit - Print channel - image Properties” screens.
Visual list is not marked up as list in “Rule Editor - Code Editor”, “Web channel - editor panel with Channels Tab showing”, “View an interactive communication”, “Interactive Content – Properties” screens.
Visible label/form field are not associated in “Open Agent UI – Data” screen.
List or list item is not marked up properly in “Interactive Content - Preview Print Channel” screen.
Group of checkboxes is missing <fieldset> in “Open Agent UI – Data” 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 - Code Editor”, “Document Fragments - Edit Text” screens.
Informative (static) content is not readable by a screen reader in “Open Agent UI – Data”, “Rule Editor - Code Editor” 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:
Color alone is used to convey info in “Edit - Print channel - image Properties”, “Web channel - editor panel with Channels Tab showing”, “Interactive Content - Preview Both Channel For ICs having Print as well as Web”, “Edit - Print channel - editor panel”, “Edit - Print channel - Document Fragment – Properties” screens.
1.4.2 Audio Control (Level A)
Also applies to:
EN 301 549 Criteria
- 9.1.4.2 (Web)
- 10.1.4.2 (Non-web document)
- 11.1.4.2 (Open Functionality Software)
- 11.1.4.2 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
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 meet minimum contrast requirements.
Exceptions include:
Link or button text lacks 4.5:1 contrast ratio on hover or focus in “Document Fragments - Edit Text”, “Open Agent UI – Data”, “Edit - Side Panel - Content tab”, “Rule Editor - Code Editor” screens.
Text content lacks 4.5:1 contrast ratio in “Edit - Print channel - Document Fragment – Properties”, “Web channel - editor panel with Channels Tab showing”, “Document Fragments - Edit Text”, “Open Agent UI – Data”, “Interactive Content - Preview Print Channel”, “Edit - Side Panel - Content tab”, “Edit - Print channel - editor panel”, “Interactive Content - Delete Modal”, “Open Agent UI – Content”, “Interactive Content - Preview Web Channel”, “Authored content (web)”, “Rule Editor - Code Editor”, “Interactive Content - Preview Both Channel For ICs having Print as well as Web” screens.
Menu item text lacks 4.5:1 contrast ratio on hover and focus in “View an interactive communication” screen.
Placeholder text lacks 4.5:1 contrast ratio in “Open Agent UI – Data” 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:
Content is lost at 200% zoom in “Web channel - editor panel with Channels Tab showing”, “Interactive Content - Preview Print Channel”, “Open Agent UI – Data”, “Interactive Content - Preview Both Channel For ICs having Print as well as Web” 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 “Document Fragments - Edit Text”, “Rule Editor - Code Editor”, “Interactive Content - Preview Both Channel For ICs having Print as well as Web”, “Edit - Print channel - editor panel” 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 “Edit - Print channel - Document Fragment – Properties”, “Interactive Content - Preview Both Channel For ICs having Print as well as Web” screens.
State of active component lacks 3 to 1 contrast ratio in “Document Fragments - Edit Text”, “Edit - Print channel - editor panel”, “Rule Editor - Code Editor”, “Edit - Print channel - Document Fragment – Properties”, “Interactive Content - Preview Both Channel For ICs having Print as well as Web” screens.
An icon lacks 3 to 1 contrast ratio in “Edit - Print channel - editor panel”, “Edit - Print channel - Document Fragment – Properties” 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
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 “Edit - Side Panel - Content tab”, “Document Fragments - Edit Text”, “Edit - Print channel - editor panel”, “Web channel - editor panel with Channels Tab showing” screens.
Link does not have an href value in “Web channel - editor panel with Channels Tab showing” screens.
2.1.2 No Keyboard Trap (Level A)
Also applies to:
EN 301 549 Criteria
- 9.2.1.2 (Web)
- 10.2.1.2 (Non-web document)
- 11.2.1.2 (Open Functionality Software)
- 11.2.1.2 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
Web: Most parts of product do not include keyboard traps.
Exceptions include:
Keyboard trap in “Document Fragments - Edit Text” screen.
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)
Web: The product does not include functionality dependent on time limits.
Exceptions include:
Content visually appears and disappears with no ability to adjust timing in “Interactive Content - Preview Both Channel For ICs having Print as well as Web” screen.
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 a mechanism to bypass blocks of content that are repeated on multiple pages.
Exceptions include:
Frames must have an accessible name in “Open Agent UI – Content”, “Open Agent UI - Print Preview”, “Authored content (web)”, “Open Agent UI – Data” screens.
Frame does not have an accessible name in “View an interactive communication” 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:
Hidden or empty element receives focus in “Rule Editor - Code Editor” screen.
Keyboard focus order is not logical in “Edit - Side Panel - Content tab”, “Document Fragments - Edit Text” screens.
Keyboard focus is lost or misplaced due to user interaction or content update in “Web channel - editor panel with Channels Tab showing”, “Interactive Content - Preview Print Channel” 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:
Programmatic label does not convey purpose of control in “Interactive Content - Preview Both Channel For ICs having Print as well as Web”, “Edit - Print channel - editor panel” screens.
Buttons have same name but different actions in “Document Fragments - Edit Text” 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 “Document Fragments - Edit Text”, “View an interactive communication”, “Open Agent UI - Print Preview”, “Create Interactive Communication - Step 01 – General”, “Edit - Side Panel - Content tab”, “Open Agent UI – Data”, “Interactive Content – Properties” screens.
Focus indicator is not visible in “Create Interactive Communication - Step 01 – General” screen.
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
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)
Web: The language is programmatically determinable within the product.
Exceptions include:
<html> element must have a lang attribute in “Open Agent UI – Content”, “Open Agent UI - Print Preview”, “Open Agent UI – Data” screens.
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)
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)
Web: Most input errors are identified and described to the users in text.
Exceptions include:
Form field with error not identified in “Create Interactive Communication - Step 01 – General” screen.
3.3.2 Labels or Instructions (Level A)
Also applies to:
EN 301 549 Criteria
- 9.3.3.2 (Web)
- 10.3.3.2 (Non-web document)
- 11.3.3.2 (Open Functionality Software)
- 11.3.3.2 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
Web: Labels are provided for most input fields.
Exceptions include:
Visible label missing in “Interactive Content - Preview Both Channel For ICs having Print as well as Web” 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:
id attribute value must be unique in “Interactive Content – Properties”, “Edit - Print channel - editor panel”, “Interactive Content - Publish Modal”, “Edit - Print channel - image Properties”, “Document Fragments - Edit Text”, “Authored content (web)”, “View an interactive communication” screens.
IDs of active elements must be unique in “Document Fragments - Edit Text” screen.
IDs used in ARIA and labels must be unique in “Document Fragments - Edit Text”, “Edit - Print channel - image Properties” screens.
Certain ARIA roles must contain particular children in “Rule Editor - Code Editor” 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)
- 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.
Examples include:
Treeview is missing required ARIA roles and attributes in “Document Fragments - Edit Text”, “Edit - Side Panel - Content tab” screens.
Required ARIA attributes must be provided in “Document Fragments - Edit Text”, “Interactive Content – Properties” screens.
Elements must only use allowed ARIA attributes in “Interactive Content – Properties”, “Document Fragments - Edit Text” screens.
Button does not have a role in “Web channel - editor panel with Channels Tab showing”, “Edit - Side Panel - Content tab” screens.
Button pressed state is not conveyed in “Interactive Content - Preview Print Channel”, “Document Fragments - Edit Text” screens.
ARIA commands must have an accessible name in “Edit - Print channel - editor panel” screen.
The element's role is missing or incorrect in “Interactive Content - Preview Print Channel”, “Interactive Content - Preview Both Channel For ICs having Print as well as Web” screens.
Button does not have a name in “Edit - Side Panel - Content tab”, “Document Fragments - Edit Text” screens.
Expand/collapse state of the element is missing or incorrect in “Open Agent UI - Print Preview”, “View an interactive communication”, “Rule Editor - Code Editor”, “Document Fragments - Edit Text”, “Edit - Print channel - editor panel”, “Web channel - editor panel with Channels Tab showing”, “Interactive Content - Preview Print Channel”, “Interactive Content - Preview Both Channel For ICs having Print as well as Web” screens.
Buttons must have discernible text in “Open Agent UI – Data” screen.
Slider is missing appropriate role and/or attributes in “Interactive Content - Preview Print Channel” screen.
Accessibility feature not accessible to the user it is intended to help in “Interactive Content - Preview Both Channel For ICs having Print as well as Web” screen.
Selected state of the element is missing or incorrect in “Interactive Content - Preview Print Channel”, “Web channel - editor panel with Channels Tab showing”, “Edit - Side Panel - Content tab”, “Open Agent UI – Data”, “Interactive Content - Preview Both Channel For ICs having Print as well as Web” screens.
Custom radio button does not have a role and/or state in “Interactive Content - Preview Print Channel” screen.
Button disabled state is not conveyed in “Edit - Print channel - editor panel” screen.
Menu is missing appropriate roles and attributes in “Interactive Content - Preview Print Channel”, “Interactive Content - Preview Both Channel For ICs having Print as well as Web” screens.
Interactive controls must not be nested in “Document Fragments - Edit Text”, “Authored content (web)” screens.
4.1.3 Status Messages (Level AA 2.1 only)
Also applies to:
EN 301 549 Criteria
- 9.4.1.3 (Web)
- 10.4.1.3 (Non-web document)
- 11.4.1.3 (Open Functionality Software)
- 11.4.1.3 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508 – Does not apply
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, Images must have alternate text, text alternative does not serve same purpose as image, role=”img” is used on decorative images.
As noted in 1.3.1 Info and Relationships, Visual heading text is not marked as heading, Form elements must have labels, <ul> and <ol> must only directly contain <li>, <script> or <template> elements, <li> elements must be contained in a <ul> or <ol>, Text should not be marked as a heading, Visual list is not marked up as list, Visible label/form field are not associated, List or list item is not marked up properly, Group of checkboxes is missing <fieldset>.
As noted in 1.3.2 Meaningful Sequence, Hidden content is readable with a screen reader, Informative (static) content is not readable by a screen reader.
As noted in 2.1.1 Keyboard, Function cannot be performed by keyboard alone, Link does not have an href value.
As noted in 2.1.2 Keyboard Trap, Keyboard trap.
As noted in 2.2.1 Timing Adjustable, Content visually appears and disappears with no ability to adjust timing.
As noted in 2.4.1 Bypass Blocks, Frames must have an accessible name, Frame does not have an accessible name.
As noted in 2.4.3 Focus Order, Hidden or empty element receives focus, Keyboard focus order is not logical, Keyboard focus is lost or misplaced due to user interaction or content update.
As noted in 2.4.6 Headings and Labels, Programmatic label does not convey purpose of control, Buttons have same name but different actions.
As noted in 3.1.1 Language of Page, primary language of the page is missing.
As noted in 3.3.1 Error Identification, Form field with error not identified.
As noted in 3.3.2 Labels or Instructions, Form field does not have a visual label.
As noted in 4.1.1 Parsing, id attribute value must be unique, IDs of active elements must be, IDs used in ARIA and labels must be, The page contains a duplicate id attribute value, Certain ARIA roles must contain particular children.
As noted in 4.1.2 Name, Role, Value, Required ARIA attributes must be provided, Elements must only use allowed ARIA attributes, Button does not have a role, Button pressed state is not conveyed, ARIA commands must have an accessible name, The element's role is missing or incorrect, Button does not have a name, Expand/collapse state of the element is missing or incorrect, Buttons must have discernible text, Slider is missing appropriate role and/or attributes, Accessibility feature not accessible to the user it is intended to help, The menu is missing appropriate roles and attributes, Selected state of the element is missing or incorrect, Custom radio button does not have a role and/or state, Button disabled state is not conveyed.
Web: Most functions of the product are usable with limited vision. Exceptions include:
As noted in 1.1.1 Non-text Content, Images must have alternate text, text alternative does not serve same purpose as image, role=”img” is used on decorative images.
As noted in 1.3.1 Info and Relationships, Visual heading text is not marked as heading, Form elements must have labels, <ul> and <ol> must only directly contain <li>, <script> or <template> elements, <li> elements must be contained in a <ul> or <ol>, Text should not be marked as a heading, Visual list is not marked up as list, Visible label/form field are not associated, List or list item is not marked up properly, Group of checkboxes is missing <fieldset>.
As noted in 1.3.2 Meaningful Sequence, Hidden content is readable with a screen reader, Informative (static) content is not readable by a screen reader.
As noted in 1.4.1 Use of Color, Color alone is used to convey info.
As noted in 1.4.3 Contrast, Link or button text lacks 4.5:1 contrast ratio on hover or focus, Text content lacks 4.5:1 contrast ratio, Menu item text lacks 4.5:1 contrast ratio on hover and focus, Placeholder text lacks 4.5:1 contrast ratio.
As noted in 2.1.1 Keyboard, Function cannot be performed by keyboard alone, Link does not have an href value.
As noted in 2.1.2 Keyboard Trap, Keyboard trap.
As noted in 2.2.1 Timing Adjustable, Content visually appears and disappears with no ability to adjust timing.
As noted in 2.4.1 Bypass Blocks, Frames must have an accessible name, Frame does not have an accessible name.
As noted in 2.4.3 Focus Order, Hidden or empty element receives focus, Keyboard focus order is not logical, Keyboard focus is lost or misplaced due to user interaction or content update.
As noted in 2.4.6 Headings and Labels, Programmatic label does not convey purpose of control, Buttons have same name but different actions.
As noted in 2.4.7 Focus Visible, Focus indicator is missing, Focus indicator is not visible.
As noted in 3.1.1 Language of Page, primary language of the page is missing.
As noted in 3.3.1 Error Identification, Form field with error not identified.
As noted in 3.3.2 Labels or Instructions, Form field does not have a visual label.
As noted in 4.1.1 Parsing, id attribute value must be unique, IDs of active elements must be, IDs used in ARIA and labels must be, The page contains a duplicate id attribute value, Certain ARIA roles must contain particular children.
As noted in 4.1.2 Name, Role, Value, Required ARIA attributes must be provided, Elements must only use allowed ARIA attributes, Button does not have a role, Button pressed state is not conveyed, ARIA commands must have an accessible name, The element's role is missing or incorrect, Button does not have a name, Expand/collapse state of the element is missing or incorrect, Buttons must have discernible text, Slider is missing appropriate role and/or attributes, Accessibility feature not accessible to the user it is intended to help, The menu is missing appropriate roles and attributes, Selected state of the element is missing or incorrect, Custom radio button does not have a role and/or state, Button disabled state is not conveyed.
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.
As noted in 1.4.3 Contrast, Link or button text lacks 4.5:1 contrast ratio on hover or focus, Text content lacks 4.5:1 contrast ratio, Menu item text lacks 4.5:1 contrast ratio on hover and focus, Placeholder text lacks 4.5:1 contrast ratio.
Web: Users with limited manipulation who use speech recognition or switch control software will not have difficulty navigating to most of the controls. Exceptions include:
As noted in 2.1.1 Keyboard, Function cannot be performed by keyboard alone, Link does not have an href value.
As noted in 2.1.2 Keyboard Trap, Keyboard trap.
As noted in 2.2.1 Timing Adjustable, Content visually appears and disappears with no ability to adjust timing.
As noted in 2.4.1 Bypass Blocks, Frames must have an accessible name, Frame does not have an accessible name.
As noted in 2.4.3 Focus Order, Hidden or empty element receives focus, Keyboard focus order is not logical, Keyboard focus is lost or misplaced due to user interaction or content update.
As noted in 2.4.6 Headings and Labels, Programmatic label does not convey purpose of control, Buttons have same name but different actions.
As noted in 2.4.7 Focus Visible, Focus indicator is missing, Focus indicator is not visible.
As noted in 3.3.2 Labels or Instructions, Form field does not have a visual label.
As noted in 4.1.1 Parsing, id attribute value must be unique, IDs of active elements must be, IDs used in ARIA and labels must be, The page contains a duplicate id attribute value, Certain ARIA roles must contain particular children.
As noted in 4.1.2 Name, Role, Value, Required ARIA attributes must be provided, Elements must only use allowed ARIA attributes, Button does not have a role, Button pressed state is not conveyed, ARIA commands must have an accessible name, The element's role is missing or incorrect, Button does not have a name, Expand/collapse state of the element is missing or incorrect, Buttons must have discernible text, Slider is missing appropriate role and/or attributes, Accessibility feature not accessible to the user it is intended to help, The menu is missing appropriate roles and attributes, Selected state of the element is missing or incorrect, Custom radio button does not have a role and/or state, Button disabled state is not conveyed.
Web: Users with limited reach and strength will not have difficulty navigating to most of the controls. Exceptions include:
As noted in 2.1.1 Keyboard, Function cannot be performed by keyboard alone, Link does not have an href value.
As noted in 2.1.2 Keyboard Trap, Keyboard trap.
As noted in 2.2.1 Timing Adjustable, Content visually appears and disappears with no ability to adjust timing.
As noted in 2.4.1 Bypass Blocks, Frames must have an accessible name, Frame does not have an accessible name.
As noted in 2.4.3 Focus Order, Hidden or empty element receives focus, Keyboard focus order is not logical, Keyboard focus is lost or misplaced due to user interaction or content update.
As noted in 2.4.6 Headings and Labels, Programmatic label does not convey purpose of control, Buttons have same name but different actions.
As noted in 2.4.7 Focus Visible, Focus indicator is missing, Focus indicator is not visible.
As noted in 3.3.2 Labels or Instructions, Form field does not have a visual label.
As noted in 4.1.1 Parsing, id attribute value must be unique, IDs of active elements must be, IDs used in ARIA and labels must be, The page contains a duplicate id attribute value, Certain ARIA roles must contain particular children.
As noted in 4.1.2 Name, Role, Value, Required ARIA attributes must be provided, Elements must only use allowed ARIA attributes, Button does not have a role, Button pressed state is not conveyed, ARIA commands must have an accessible name, The element's role is missing or incorrect, Button does not have a name, Expand/collapse state of the element is missing or incorrect, Buttons must have discernible text, Slider is missing appropriate role and/or attributes, Accessibility feature not accessible to the user it is intended to help, The menu is missing appropriate roles and attributes, Selected state of the element is missing or incorrect, Custom radio button does not have a role and/or state, Button disabled state is not conveyed.
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, Informative (static) content is not readable by a screen reader.
As noted in 2.2.1 Timing Adjustable, Content visually appears and disappears with no ability to adjust timing.
As noted in 2.4.1 Bypass Blocks, Frames must have an accessible name, Frame does not have an accessible name.
As noted in 2.4.3 Focus Order, Hidden or empty element receives focus, Keyboard focus order is not logical, Keyboard focus is lost or misplaced due to user interaction or content update.
As noted in 2.4.6 Headings and Labels, Programmatic label does not convey purpose of control, Buttons have same name but different actions.
As noted in 2.4.7 Focus Visible, Focus indicator is missing, Focus indicator is not visible.
As noted in 3.1.1 Language of Page, primary language of the page is missing.
As noted in 3.3.1 Error Identification, Form field with error not identified.
As noted in 3.3.2 Labels or Instructions, Form field does not have a visual label.
As noted in 4.1.1 Parsing, id attribute value must be unique, IDs of active elements must be, IDs used in ARIA and labels must be, The page contains a duplicate id attribute value, Certain ARIA roles must contain particular children.
As noted in 4.1.2 Name, Role, Value, Required ARIA attributes must be provided, Elements must only use allowed ARIA attributes, Button does not have a role, Button pressed state is not conveyed, ARIA commands must have an accessible name, The element's role is missing or incorrect, Button does not have a name, Expand/collapse state of the element is missing or incorrect, Buttons must have discernible text, Slider is missing appropriate role and/or attributes, Accessibility feature not accessible to the user it is intended to help, The menu is missing appropriate roles and attributes, Selected state of the element is missing or incorrect, Custom radio button does not have a role and/or state, Button disabled state is not conveyed.
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, Images must have alternate text, text alternative does not serve same purpose as image, role=”img” is used on decorative images.
As noted in 1.3.1 Info and Relationships, Visual heading text is not marked as heading, Form elements must have labels, <ul> and <ol> must only directly contain <li>, <script> or <template> elements, <li> elements must be contained in a <ul> or <ol>, Text should not be marked as a heading, Visual list is not marked up as list, Visible label/form field are not associated, List or list item is not marked up properly, The group label is not associated with its checkboxes.
As noted in 1.3.2 Meaningful Sequence, Hidden content is readable with a screen reader, Informative (static) content is not readable by a screen reader.
As noted in 2.1.1 Keyboard, Function cannot be performed by keyboard alone, Link does not have an href value.
As noted in 2.1.2 Keyboard Trap, Keyboard trap.
As noted in 2.2.1 Timing Adjustable, Content visually appears and disappears with no ability to adjust timing.
As noted in 2.4.1 Bypass Blocks, Frames must have an accessible name, Frame does not have an accessible name.
As noted in 2.4.3 Focus Order, Hidden or empty element receives focus, Keyboard focus order is not logical, Keyboard focus is lost or misplaced due to user interaction or content update.
As noted in 2.4.6 Headings and Labels, Programmatic label does not convey purpose of control, Buttons have same name but different actions.
As noted in 3.1.1 Language of Page, Primary language of the page is missing.
As noted in 3.3.1 Error Identification, Form field with error not identified.
As noted in 3.3.2 Labels or Instructions, Form field does not have a visual label.
As noted in 4.1.1 Parsing, id attribute value must be unique, IDs of active elements must be, IDs used in ARIA and labels must be, Certain ARIA roles must contain particular children.
As noted in 4.1.2 Name, Role, Value, Required ARIA attributes must be provided, Elements must only use allowed ARIA attributes, Button does not have a role, Button pressed state is not conveyed, ARIA commands must have an accessible name, The element's role is missing or incorrect, Button does not have a name, Expand/collapse state of the element is missing or incorrect, Buttons must have discernible text, Slider is missing appropriate role and/or attributes, Accessibility feature not accessible to the user it is intended to help, The menu is missing appropriate roles and attributes, Selected state of the element is missing or incorrect, Custom radio button does not have a role and/or state, Button disabled state is not conveyed.
Web: Most functions of the product are usable with limited vision. Exceptions include:
As noted in 1.1.1 Non-text Content, Images must have alternate text, text alternative does not serve same purpose as image, role=”img” is used on decorative images.
As noted in 1.3.1 Info and Relationships, Visual heading text is not marked as heading, Form elements must have labels, <ul> and <ol> must only directly contain <li>, <script> or <template> elements, <li> elements must be contained in a <ul> or <ol>, Text should not be marked as a heading, Visual list is not marked up as list, Visible label/form field are not associated, List or list item is not marked up properly, Group of checkboxes is missing <fieldset>.
As noted in 1.3.2 Meaningful Sequence, Hidden content is readable with a screen reader, Informative (static) content is not readable by a screen reader.
As noted in 1.4.1 Use of Color, Color alone is used to convey info.
As noted in 1.4.3 Contrast, Link or button text lacks 4.5:1 contrast ratio on hover or focus, Text content lacks 4.5:1 contrast ratio, Menu item text lacks 4.5:1 contrast ratio on hover and focus, Placeholder text lacks 4.5:1 contrast ratio.
As noted in 1.4.10 Reflow, 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, State of active component lacks 3 to 1 contrast ratio, An icon lacks 3 to 1 contrast ratio.
As noted in 2.1.1 Keyboard, Function cannot be performed by keyboard alone, Link does not have an href value.
As noted in 2.1.2 Keyboard Trap, Keyboard trap.
As noted in 2.2.1 Timing Adjustable, Content visually appears and disappears with no ability to adjust timing.
As noted in 2.4.1 Bypass Blocks, Frames must have an accessible name, Frame does not have an accessible name.
As noted in 2.4.3 Focus Order, Hidden or empty element receives focus, Keyboard focus order is not logical, Keyboard focus is lost or misplaced due to user interaction or content update.
As noted in 2.4.6 Headings and Labels, Programmatic label does not convey purpose of control, Buttons have same name but different actions.
As noted in 2.4.7 Focus Visible, Focus indicator is missing, Focus indicator is not visible.
As noted in 3.1.1 Language of Page, Primary language of the page is missing.
As noted in 3.3.1 Error Identification, Form field with error not identified.
As noted in 3.3.2 Labels or Instructions, Form field does not have a visual label.
As noted in 4.1.1 Parsing, id attribute value must be unique, IDs of active elements must be, IDs used in ARIA and labels must be, Certain ARIA roles must contain particular children.
As noted in 4.1.2 Name, Role, Value, Required ARIA attributes must be provided, Elements must only use allowed ARIA attributes, Button does not have a role, Button pressed state is not conveyed, ARIA commands must have an accessible name, The element's role is missing or incorrect, Button does not have a name, Expand/collapse state of the element is missing or incorrect, Buttons must have discernible text, Slider is missing appropriate role and/or attributes, Accessibility feature not accessible to the user it is intended to help, The menu is missing appropriate roles and attributes, Selected state of the element is missing or incorrect, Custom radio button does not have a role and/or state, Button disabled state is not conveyed.
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.
As noted in 1.4.3 Contrast, Link or button text lacks 4.5:1 contrast ratio on hover or focus, Text content lacks 4.5:1 contrast ratio, Menu item text lacks 4.5:1 contrast ratio on hover and focus, Placeholder text lacks 4.5:1 contrast ratio.
As noted in 1.4.11 Non-text Contrast, Active user interface component lacks 3 to 1 contrast ratio, State of active component lacks 3 to 1 contrast ratio, an icon lacks 3 to 1 contrast ratio.
Web: Users with limited manipulation or strength who use speech recognition or switch control software will not have difficulty navigating to most of the controls. Exceptions include:
As noted in 2.1.1 Keyboard, Function cannot be performed by keyboard alone, Link does not have an href value.
As noted in 2.1.2 Keyboard Trap, Keyboard trap.
As noted in 2.2.1 Timing Adjustable, Content visually appears and disappears with no ability to adjust timing.
As noted in 2.4.1 Bypass Blocks, Frames must have an accessible name, Frame does not have an accessible name.
As noted in 2.4.3 Focus Order, Hidden or empty element receives focus, Keyboard focus order is not logical, Keyboard focus is lost or misplaced due to user interaction or content update.
As noted in 2.4.6 Headings and Labels, Programmatic label does not convey purpose of control, Buttons have same name but different actions.
As noted in 2.4.7 Focus Visible, Focus indicator is missing, Focus indicator is not visible.
As noted in 3.3.2 Labels or Instructions, Form field does not have a visual label.
As noted in 4.1.1 Parsing, id attribute value must be unique, IDs of active elements must be, IDs used in ARIA and labels must be, Certain ARIA roles must contain particular children.
As noted in 4.1.2 Name, Role, Value, Required ARIA attributes must be provided, Elements must only use allowed ARIA attributes, Button does not have a role, Button pressed state is not conveyed, ARIA commands must have an accessible name, The element's role is missing or incorrect, Button does not have a name, Expand/collapse state of the element is missing or incorrect, Buttons must have discernible text, Slider is missing appropriate role and/or attributes, Accessibility feature not accessible to the user it is intended to help, The menu is missing appropriate roles and attributes, Selected state of the element is missing or incorrect, Custom radio button does not have a role and/or state, Button disabled state is not conveyed.
Web: Users with limited reach will not have difficulty navigating to most of the controls. Exceptions include:
As noted in 2.1.1 Keyboard, Function cannot be performed by keyboard alone, Link does not have an href value.
As noted in 2.1.2 Keyboard Trap, Keyboard trap.
As noted in 2.2.1 Timing Adjustable, Content visually appears and disappears with no ability to adjust timing.
As noted in 2.4.1 Bypass Blocks, Frames must have an accessible name, Frame does not have an accessible name.
As noted in 2.4.3 Focus Order, Hidden or empty element receives focus, Keyboard focus order is not logical, Keyboard focus is lost or misplaced due to user interaction or content update.
As noted in 2.4.6 Headings and Labels, Programmatic label does not convey purpose of control, Buttons have same name but different actions.
As noted in 2.4.7 Focus Visible, Focus indicator is missing, Focus indicator is not visible.
As noted in 3.3.2 Labels or Instructions, Form field does not have a visual label.
As noted in 4.1.1 Parsing, id attribute value must be unique, IDs of active elements must be, IDs used in ARIA and labels must be, Certain ARIA roles must contain particular children.
As noted in 4.1.2 Name, Role, Value, Required ARIA attributes must be provided, Elements must only use allowed ARIA attributes, Button does not have a role, Button pressed state is not conveyed, ARIA commands must have an accessible name, The element's role is missing or incorrect, Button does not have a name, Expand/collapse state of the element is missing or incorrect, Buttons must have discernible text, Slider is missing appropriate role and/or attributes, Accessibility feature not accessible to the user it is intended to help, The menu is missing appropriate roles and attributes, Selected state of the element is missing or incorrect, Custom radio button does not have a role and/or state, Button disabled state is not conveyed.
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, Informative (static) content is not readable by a screen reader.
As noted in 2.2.1 Timing Adjustable, Content visually appears and disappears with no ability to adjust timing.
As noted in 2.4.1 Bypass Blocks, Frames must have an accessible name, Frame does not have an accessible name.
As noted in 2.4.3 Focus Order, Hidden or empty element receives focus, Keyboard focus order is not logical, Keyboard focus is lost or misplaced due to user interaction or content update.
As noted in 2.4.6 Headings and Labels, Programmatic label does not convey purpose of control, Buttons have same name but different actions.
As noted in 2.4.7 Focus Visible, Focus indicator is missing, Focus indicator is not visible.
As noted in 3.1.1 Language of Page, primary language of the page is missing.
As noted in 3.3.1 Error Identification, Form field with error not identified.
As noted in 3.3.2 Labels or Instructions, Form field does not have a visual label.
As noted in 4.1.1 Parsing, id attribute value must be unique, IDs of active elements must be, IDs used in ARIA and labels must be, Certain ARIA roles must contain particular children.
As noted in 4.1.2 Name, Role, Value, Required ARIA attributes must be provided, Elements must only use allowed ARIA attributes, Button does not have a role, Button pressed state is not conveyed, ARIA commands must have an accessible name, The element's role is missing or incorrect, Button does not have a name, Expand/collapse state of the element is missing or incorrect, Buttons must have discernible text, Slider is missing appropriate role and/or attributes, Accessibility feature not accessible to the user it is intended to help, The menu is missing appropriate roles and attributes, Selected state of the element is missing or incorrect, Custom radio button does not have a role and/or state, Button disabled state is not conveyed.
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)