Adobe Accessibility Conformance Report International Edition
(Based on VPAT® Version 2.5)
Product Information
- Name of Product/Version: Adobe Photoshop Web Version 2025.22.1.0
- Product Description: Photoshop on the web is a versatile digital imaging and design application available directly in your browser. Its streamlined online interface, with intuitive and precise editing tools, gives you complete control over every last detail and seamless access to Photoshop's most common editing tools and generative AI capabilities.
- Date: December 2025
- Contact information: access@adobe.com
- Notes: The information contained in this report applies to the product itself. Information about product help and support documentation is located at: http://www.adobe.com/accessibility/compliance.html.
- Evaluation Methods Used: Testing Adobe Photoshop involved extensive use of leading assistive technology such as screen readers, as well exclusive use of the keyboard. These were supplemented with techniques such as manual inspection of Accessibility API output.
Applicable Standards/Guidelines
This report covers the degree of conformance for the following accessibility standard/guidelines:
Standard/Guideline
Included In Report
Level A (Yes)
Level AA (Yes)
Level AAA (No)
Level A (Yes)
Level AA (Yes)
Level AAA (No)
Level A (Yes)
Level AA (Yes)
Level AAA (No)
Terms
The terms used in the Conformance Level information are defined as follows:
- Supports: The functionality of the product has at least one method that meets the criterion without known defects or meets with equivalent facilitation.
- Partially Supports: Some functionality of the product does not meet the criterion.
- Does Not Support: The majority of product functionality does not meet the criterion.
- Not Applicable: The criterion is not relevant to the product.
- Not Evaluated: The product has not been evaluated against the criterion. This can only be used in WCAG Level AAA criteria.
WCAG 2.2 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.2 Success Criteria, they are scoped for full pages, complete processes, and accessibility-supported ways of using technology as documented in the WCAG 2.2 Conformance Requirements.
Table 1: Success Criteria, Level A
Notes:
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 non-text content.
Some images do not have a text alternative, so people who are blind and/or use a screen reader will not be able to access the information available in the image, and if it is an active image, will not understand its function. This occurs on the following pages: Generative Fill; Selection Tool.
An active image has a text alternative that does not convey the same purpose as the image. People who are blind and/or use a screen reader will be given different information than sighted users. This occurs on the following page: Create: Interface.
A complex image does not have a text alternative, so people who are blind and/or use a screen reader will not be able to understand the information available in the image. This occurs on the following page: Xray.
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)
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: Some structure and relationship information, is provided through element semantics | object information or in text. However, most structure and relationship information are not provided programmatically or in text, such as:
Some heading levels are out of order, so the structure of the content is not properly conveyed to assistive technologies and people who are blind and/or use a screen reader. This occurs on the following pages: Xray; Selection Tool; Type; Add Image; Adjust.
Content that is visually presented as a list is not marked up as a list, so the presence and structure of the list are not conveyed to assistive technologies and people who are blind and/or use a screen reader. This occurs on the following page: Home - Logged In.
A block of text is marked up as a heading but is not a heading, so the structure of the content is misrepresented to assistive technologies and people who are blind and/or use a screen reader. This occurs on the following page: Generative Fill.
A group of navigation links is missing semantic markup, so people who are blind and/or use a screen reader may not understand how the links relate to each other or the page content. This occurs in the following component: Footer.
Content is arranged visually like a data table, but it is not programmatically marked up as a table, so the table's structure and relationships are not conveyed to people who are blind and/or use a screen reader. This occurs on the following page: Home - Logged In.
Some text that visually functions as a heading is not marked up as a heading, so the structure of the content is not properly conveyed to assistive technologies and people who are blind and/or use a screen reader. This occurs on the following pages: Lesson: Generative Fill; Create: Interface; Home - Logged Out; Home - Logged In; Create: Upload.
An element's programmatic role requires one or more child element(s) but the child element(s) is/are missing, so people who are blind and/or use a screen reader or other assistive technology may not be able to understand the purpose or content of the element or its related content. This occurs on the following page: Home - Logged In.
Some information, structure, and/or relationships are only presented visually but not conveyed programmatically, so context provided to sighted users is not available to people who are blind. This occurs on the following pages: Create: Interface; Add Image.
Some groups of form controls are not programmatically associated with their group label, so the purpose of individual controls in each group cannot be understood by people who are blind and/or use a screen reader. This occurs on the following pages: Home - Logged Out; Home - Logged In; Body Parser Select; Adjust; Xray.
1.3.2 Meaningful Sequence (Level A)
Also applies to:
EN 301 549 Criteria
- 9.1.3.2 (Web)
- 10.1.3.2 (Non-web document)
- 11.1.3.2.1 (Open Functionality Software)
- 11.1.3.2.2 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
Web: The product presents most content in a meaningful sequence. Exceptions include:
Some visually hidden content is announced by a screen reader, so people who are blind and/or use a screen reader may be misled or confused when hearing content that is not intended to be part of the reading order on the page. This occurs on the following page: Type.
1.3.3 Sensory Characteristics (Level A)
Also applies to:
EN 301 549 Criteria
- 9.1.3.3 (Web)
- 10.1.3.3 (Non-web document)
- 11.1.3.3 (Open Functionality Software)
- 11.1.3.3 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
Web: Most instructions do not rely solely on sensory characteristics. Exceptions include:
Some instructions require the ability to see shape, color, size, visual location, or orientation, so they will be difficult or impossible to understand for people who are blind or have low vision. This occurs on the following pages: Home - Logged Out; Home - Logged In; Create: Interface.
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 is used as the only method to convey information so that information will not be available to people who are colorblind and people who are blind and/or use a screen reader. This occurs on the following page: Xray.
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 is used as the only method to convey information so that information will not be available to people who are colorblind and people who are blind and/or use a screen reader. This occurs on the following page: Xray.
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)
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 cannot be operated through a keyboard interface. Examples include:
Multiple functions cannot be performed using only the keyboard, so people who use the keyboard alone to navigate and operate content cannot use these functions. This occurs on the following pages: Type; Selection Tool; Xray; Home - Logged In; Adjust; Create: Upload; Body Parser Select; Generative Fill; Harmonize; Create: Interface; Retouch; Lesson: Generative Fill; Add Image.
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 and 2.2)
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)
Web: Most moving, blinking, scrolling, or auto-updating information is present, that information can be paused, stopped, hidden, or otherwise controlled by the user. Exceptions include:
The user cannot pause, stop, or hide content that automatically moves, blinks, or scrolls, so people who cannot read text quickly, have attention deficit disorders or other cognitive disabilities, or use a screen reader may not be able to read or understand the content. This occurs on the following page: Lesson: Generative Fill.
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
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:
The focus order is not logical and presents content in an order that misrepresents its meaning or operability, so people who use a keyboard, switch control, or other assistive technology to navigate content may become disoriented or confused. This occurs on the following pages: Create: Interface; Lesson: Generative Fill.
Keyboard focus or touch screen swiping goes to an element that is hidden or empty, so people who use the keyboard to navigate content (including screen reader users) may become disoriented or confused. This occurs on the following page: Type.
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)
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 and 2.2)
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 and 2.2)
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 and 2.2)
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 controls contain the text of their visible labels. Exceptions include:
The accessible name of multiple interactive elements (such as links, buttons, or form inputs) does not contain the visible label, so people who use speech input to navigate and operate content will not be able to access those elements. This occurs in the following component: Footer and following pages: Selection Tool; Adjust; Xray; Type; Retouch; Add Image.
2.5.4 Motion Actuation (Level A 2.1 and 2.2)
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)
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)
Web: In most product functions, components do not initiate a change of context when focused. Exceptions include:
When an element receives keyboard focus, it results in a substantial, unanticipated context change (such as a change in the page content that changes the meaning of the page), so people who use a keyboard to navigate content (including screen reader users) may become confused or disoriented. This occurs on the following page: Generative Fill.
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.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.6 Consistent Help (Level A 2.2 only)
EN 301 549 Criteria – Does not apply
Revised Section 508 – Does not apply
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:
The label for a form field is missing, so the field's purpose is not clear. This occurs on the following page: Xray.
Some labels of elements are not persistent (always visible on the page), so each element's purpose may be difficult to discover. This occurs on the following pages: Lesson: Generative Fill; Generative Fill.
Select or dropdown control missing a visible label so the Select or dropdown control purpose is not clear. This occurs on the following pages: Xray; Type.
3.3.7 Redundant Entry (Level A 2.2 only)
EN 301 549 Criteria – Does not apply
Revised Section 508 – Does not apply
Guideline 4.1 Compatible:
Maximize compatibility with current and future user agents, including assistive technologies.
4.1.1 Parsing (Level A)
Applies to:
WCAG 2.0 and 2.1 – Always answer ‘Supports’
WCAG 2.2 (obsolete and removed) - Does not apply
EN 301 549 Criteria
- 9.4.1.1 (Web)
- 10.4.1.1 (Non-web document)
- 11.4.1.1.1 (Open Functionality Software)
- 11.4.1.1.2 (Closed Software) – Does not apply
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
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) – Does not apply
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
Web: User interface components in most product functions do not provide programmatic [name, role, state, or value] information. Examples include:
A link does not have a programmatic role, so people who are blind and/or use a screen reader or other assistive technology may not be able to understand the purpose and function of the link or how to interact with it. This occurs on the following page: Home - Logged In.
A button does not have a programmatic name, so its name (such as "Submit" or "Cancel") is not conveyed to screen readers and other assistive technologies and will not be available to people who use those technologies. This occurs on the following page: Generative Fill.
Multiple buttons do not have a programmatic role, so each button's role (usually button, but sometimes link or something else) is not conveyed to screen readers and other assistive technologies and will not be available to people who use those technologies. This occurs on the following pages: Create: Upload; Xray; Adjust; Retouch.
An element with a "link," "button," or "menu item" role is missing or has an incorrect programmatic name, so people who are blind and/or use a screen reader or other assistive technology may not be able to determine the name of the element and may not understand its purpose or content or how to interact with it. This occurs on the following pages: Generative Fill; Home - Logged In; Home - Logged Out; Adjust.
An element has an invalid attribute in its HTML code that is intended to provide its programmatic role, name, state, or another property to assistive technology, so people who are blind and/or use a screen reader or other assistive technology may not be able to understand the name, purpose, or content of the element or how to interact with it. This occurs on the following pages: Retouch; Adjust.
Multiple buttons do not have a programmatic role and name, so each button's role (usually button, but sometimes link or something else) and its name (such as "Submit" or "Cancel") are not conveyed to screen readers and other assistive technologies and will not be available to people who use those technologies. This occurs on the following pages: Harmonize; Adjust; Xray; Selection Tool; Body Parser Select; Lesson: Generative Fill; Type; Generative Fill; Add Image.
Multiple elements do not have an attribute in their HTML code that will provide its programmatic role to assistive technology or the role assigned is not correct (like assigning a button the role of "checkbox"), so people who are blind and/or use a screen reader or other assistive technology may not be able to understand the name, purpose, or content of the element or how to interact with it. This occurs on the following pages: Generative Fill; Home - Logged In.
A form field does not have a programmatic name, so people who are blind and/or use a screen reader or other assistive technology may not be able to understand the purpose of the form field or what input it requires. This occurs on the following page: Type.
Multiple elements that appear and function like a slider control does not have the required attributes in its HTML code needed to provide its programmatic role, name, state, and other properties to assistive technology, so people who are blind and/or use a screen reader or other assistive technology may not be able to understand the element's name, purpose, or current value or how to interact with it. This occurs on the following pages: Type; Xray.
For some elements that allow a user either to select or not select a single option (like a checkbox or radio buttons) or to select from among 2 or more options (like a select dropdown), the state (such as checked/unchecked or selected/not selected) is not conveyed to assistive technology, so people who are blind and/or use a screen reader or other assistive technology may not be able to understand the purpose of each element, the options available, and whether the element or an option is currently checked. This occurs on the following pages: Xray; Home - Logged Out; Adjust; Harmonize; Home - Logged In; Selection Tool; Generative Fill; Create: Upload; Body Parser Select.
The content of multiple tooltips cannot be accessed using a screen reader, so people who are blind and others who use a screen reader will not be able to read this content. This occurs on the following pages: Adjust; Create: Upload; Generative Fill; Selection Tool; Retouch.
An element that appears and functions like a list box (which allows the user to select 1 or more options from a list of options) does not have the required attributes in its HTML code needed to provide the programmatic role, name, state, and other properties for the list box and/or its options to assistive technology, so people who are blind and/or use a screen reader or other assistive technology may not be able to understand the name, purpose, or content of the list box and its options or how to interact with them. This occurs on the following page: Type.
An element that appears and functions like a combo box does not have the required attributes in its HTML code needed to provide its programmatic role, name, state, and other properties to assistive technology, so people who are blind and/or use a screen reader or other assistive technology may not be able to understand the name, purpose, or content of the element or how to interact with it. This occurs on the following page: Create: Upload.
The programmatic state of some elements that reveal or hide content ("expanded" or "collapsed") is missing or is used incorrectly, so people who are blind and/or use a screen reader or other assistive technology will not be informed of the current state of each element or the state will be misrepresented. This occurs on the following pages: Home - Logged In; Create: Interface; Generative Fill; Type; Xray; Home - Logged Out; Create: Upload; Adjust; Retouch.
Multiple elements do not have an attribute in their HTML code that will provide its programmatic state (such as "checked"/"not checked") to assistive technology or the state assigned is not correct, so people who are blind and/or use a screen reader or other assistive technology may not be able to understand the current state of the element or how to interact with it. This occurs on the following pages: Xray; Add Image; Type; Selection Tool; Adjust.
Table 2: Success Criteria, Level AA
Notes:
1.2.4 Captions (Live) (Level AA)
Also applies to:
EN 301 549 Criteria
- 9.1.2.4 (Web)
- 10.1.2.4 (Non-web document)
- 11.1.2.4 (Open Functionality Software)
- 11.1.2.4 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
1.2.5 Audio Description (Prerecorded) (Level AA)
Also applies to:
EN 301 549 Criteria
- 9.1.2.5 (Web)
- 10.1.2.5 (Non-web document)
- 11.1.2.5 (Open Functionality Software)
- 11.1.2.5 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
1.3.4 Orientation (Level AA 2.1 and 2.2)
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 and 2.2)
Also applies to:
EN 301 549 Criteria
- 9.1.3.5 (Web)
- 10.1.3.5 (Non-web document)
- 11.1.3.5.1 (Open Functionality Software)
- 11.1.3.5.2 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508 – Does not apply
1.4.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:
The color contrast ratio between text and its background is less than 4.5:1, so people who are colorblind or have low vision may have difficulty reading the text. This occurs on the following pages: Home - Logged In; Generative Fill; Xray; Create: Upload; Type; Home - Logged Out.
The color contrast ratio between placeholder text in an input and the input's background is less than 4.5:1, so people who are colorblind or have low vision may have difficulty reading the placeholder text. This occurs on the following page: Generative Fill.
The color contrast ratio between text placed over an image and that image is less than 4.5:1, so people who are colorblind or have low vision may have difficulty reading the text. This occurs on the following page: Type.
The color contrast ratio on hover or focus between a control's text label and its background is less than 4.5:1, so people who are colorblind or have low vision may have difficulty reading the text label of the control. This occurs on the following page: Type.
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 content is readable and functional when browser zoom is set to 200% of its initial size. Exceptions include:
Content is lost, clipped, or obscured when the page is zoomed to 200%, so people who have low vision and need to enlarge text to read it may not have access to that content. This occurs on the following pages: Lesson: Generative Fill; Type; Home - Logged In; Create: Upload.
Functionality is lost when the page is zoomed to 200%, so people who have low vision and need to enlarge text to read it may not have access to this functionality. This occurs on the following pages: Lesson: Generative Fill; Create: Upload; Create: Interface.
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 and 2.2)
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. Examples include:
When the page is adjusted to an equivalent width of 320 pixels and content reflows to fit within the viewport, some content does not fit horizontally, so it cannot be viewed without scrolling. People with low vision who increase the size of text and other content using the browser zoom may have difficulty accessing the content that can only be seen by horizontal scrolling. This occurs on the following page: Home - Logged Out.
When the page is adjusted to an equivalent width of 320 pixels and content reflows to fit within the viewport, some content or functionality becomes unavailable, so people with low vision who increase the size of text and other content using the browser zoom will not be able to access all of the page's content and/or functionality. This occurs on the following pages: Generative Fill; Retouch; Create: Upload; Type; Adjust; Home - Logged Out; Xray; Home - Logged In; Add Image; Lesson: Generative Fill; Create: Interface.
When the page is adjusted to an equivalent width of 320 pixels and content reflows to fit within the viewport, some content overlaps and cannot be seen or understood, so the overlapping content is not available to people with low vision who increase the size of text and other content using the browser zoom. This occurs on the following pages: Type; Add Image; Selection Tool; Adjust; Create: Upload.
1.4.11 Non-text Contrast (Level AA 2.1 and 2.2)
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 of the boundaries and indicators of the visual states of each active user component and any graphics required to understand content have a 3:1 color contrast ratio with adjacent colors or their background. Examples include:
Some icons (or parts of an icon required to understand its content) do not have a 3:1 color contrast ratio with the background or adjacent colors, so people who are colorblind or have low vision may not be able to understand the information presented by each icon. This occurs on the following pages: Type; Selection Tool; Harmonize; Adjust; Create: Interface; Add Image; Generative Fill; Xray; Lesson: Generative Fill.
The focus indicators of some interactive elements (like buttons or input fields) do not have a 3:1 color contrast ratio with the background, so people who are colorblind or have low vision may have difficulty perceiving when each interactive element is receiving focus. This occurs on the following pages: Home - Logged Out; Home - Logged In; Type; Create: Upload.
Some images or graphics (like a chart) or parts of the image/graphic required to understand its content do not have a 3:1 color contrast ratio with the background or adjacent colors, so people who are colorblind or have low vision may not be able to understand the information presented by the image/graphic. This occurs on the following page: Xray.
The indicators for the state of some interactive elements (like checkboxes or radio buttons) do not have a 3:1 color contrast ratio with the background, so people who are colorblind or have low vision may have difficulty in perceiving the state of the interactive elements. This occurs on the following pages: Xray; Create: Upload; Create: Interface; Type.
The visual boundaries of some interactive elements (like a radio button or input fields) do not have a 3:1 color contrast ratio with the background, so people who are colorblind or have low vision may have difficulty in perceiving the boundaries of the interactive element. This occurs on the following pages: Type; Selection Tool; Xray; Adjust; Retouch; Body Parser Select; Generative Fill.
1.4.12 Text Spacing (Level AA 2.1 and 2.2)
Also applies to:
EN 301 549 Criteria
- 9.1.4.12 (Web)
- 10.1.4.12 (Non-web document)
- 11.1.4.12 (Open Functionality Software)
- 11.1.4.12 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508 – Does not apply
Web: Most functions of the product support the required text style properties without loss of content or functionality. Exceptions include:
When text spacing is adjusted to help people with vision, reading, and/or cognitive disabilities, some content cannot be seen because it is cut off. This occurs on the following pages: Home - Logged Out; Xray; Adjust.
1.4.13 Content on Hover or Focus (Level AA 2.1 and 2.2)
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: Most product functions, content does not become visible and then hidden in response to pointer hover or keyboard focus. Examples include:
Content that appears on mouse hover or keyboard focus (such as tooltips, drop-down menus, or popups) is not dismissible, so it obscures all or part of the original content on the page. This occurs on the following pages: Adjust; Add Image; Retouch; Type; Body Parser Select; Xray; Generative Fill; Create: Interface; Harmonize; Lesson: Generative Fill; Selection Tool; Home - Logged Out; Home - Logged In.
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/or labels for form and interactive controls are not informative. Examples include:
Multiple buttons have identical programmatic labels but different functionality, and there is no programmatic context, so people who are blind and/or use a screen reader will not know or may be confused or misled about what each button does. This occurs on the following pages: Add Image; Home - Logged In; Home - Logged Out; Create: Interface.
Multiple programmatic labels for controls or form input fields do not convey the purpose of the control or input, so people who are blind and/or use a screen reader may not understand what a control does or what data to enter. This occurs in the following component: Footer and following pages: Adjust; Xray; Selection Tool; Type; Retouch; Body Parser Select; Home - Logged Out; Create: Upload; Home - Logged In; Create: Interface; Generative Fill; Lesson: Generative Fill.
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:
Multiple interactive elements (such as links, buttons, or form inputs) do not have a visual focus indicator, so sighted people who use a keyboard to navigate content will not know when those elements are receiving focus. This occurs on the following pages: Create: Interface; Xray; Selection Tool.
2.4.11 Focus Not Obscured (Minimum) (Level AA 2.2 only)
EN 301 549 Criteria – Does not apply
Revised Section 508 – Does not apply
Web: When most user interface components receive keyboard focus, each component is not entirely hidden due to author-created content. Exceptions include:
Multiple focused elements are completely covered by other author-created content, which may cause people who use the keyboard to navigate content to become disoriented. This occurs on the following pages: Create: Upload; Add Image.
2.5.7 Dragging Movements (Level AA 2.2 only)
EN 301 549 Criteria – Does not apply
Revised Section 508 – Does not apply
Web: Most functionality that uses a dragging movement can be achieved by a single pointer without dragging, unless dragging is essential or the functionality is determined by the user agent and not modified by the author. Examples include:
Some functionality relies on a dragging movement with no single-pointer, single-touch alternative, making it difficult or impossible for persons with motor difficulties and users of assistive technology to perform the gesture. This occurs on the following pages: Harmonize; Add Image; Retouch; Lesson: Generative Fill; Adjust; Type; Selection Tool; Generative Fill.
2.5.8 Target Size (Minimum) (Level AA 2.2 only)
EN 301 549 Criteria – Does not apply
Revised Section 508 – Does not apply
Web: The size of the target for most clickable controls is at least 24 by 24 CSS pixels, except where the target size is determined by the user agent; there is a different control with equivalent functionality; the target is in line with text; the presentation of the target is essential to the function or otherwise exempted under the rule; or each control is spaced such that a 24-pixel circle placed around the bounding box of the control will not intersect any similar circle for another control. Exceptions include:
A target's hit area does not meet a minimum 24x24 pixel size or spacing. making it difficult for users with hand tremors and those who have difficulty with fine motor movement to activate them accurately. This occurs on the following page: Create: Interface.
3.1.2 Language of Parts (Level AA)
Also applies to:
EN 301 549 Criteria
- 9.3.1.2 (Web)
- 10.3.1.2 (Non-web document)
- 11.3.1.2 (Open Functionality Software) – Does not apply
- 11.3.1.2 (Closed Software) – Does not apply
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
Web: On most pages, the language of each section of content that is different from the default language of the page is correctly identified and can be determined programmatically. Exceptions include:
A portion of content on a page that is in a different language from the rest of the content on the page is not programmatically assigned the language for that portion of content, so screen readers may mispronounce that part of the content. This occurs in the following component: Footer.
3.2.3 Consistent Navigation (Level AA)
Also applies to:
EN 301 549 Criteria
- 9.3.2.3 (Web)
- 10.3.2.3 (Non-web document) – Does not apply
- 11.3.2.3 (Open Functionality Software) – Does not apply
- 11.3.2.3 (Closed Software) – Does not apply
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software) – Does not apply to non-web software
- 504.2 (Authoring Tool)
- 602.3 (Support Docs) – Does not apply to non-web docs
3.2.4 Consistent Identification (Level AA)
Also applies to:
EN 301 549 Criteria
- 9.3.2.4 (Web)
- 10.3.2.4 (Non-web document) – Does not apply
- 11.3.2.4 (Open Functionality Software) – Does not apply
- 11.3.2.4 (Closed Software) – Does not apply
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software) – Does not apply to non-web software
- 504.2 (Authoring Tool)
- 602.3 (Support Docs) – Does not apply to non-web docs
3.3.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)
3.3.8 Accessible Authentication (Minimum) (Level AA 2.2 only)
EN 301 549 Criteria – Does not apply
Revised Section 508 – Does not apply
4.1.3 Status Messages (Level AA 2.1 and 2.2)
Also applies to:
EN 301 549 Criteria
- 9.4.1.3 (Web)
- 10.4.1.3 (Non-web document)
- 11.4.1.3 (Open Functionality Software)
- 11.4.1.3 (Closed Software) – Does not apply
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508 – Does not apply
Web: When status messages do not receive focus, the product does not provide the update to assistive technology. Examples include:
Some status messages are not automatically announced by the screen reader, so people who are blind and/or use a screen reader or other assistive technology may completely miss the status messages, or they may not hear them in a timely fashion. This occurs on the following pages: Selection Tool; Retouch; Add Image; Type; Body Parser Select; Harmonize; Create: Upload; Create: Interface; Generative Fill; Lesson: Generative Fill.
Table 3: Success Criteria, Level AAA
Notes: Not Applicable
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
As noted in 1.3.1 Info and Relationships
As noted in 1.3.2 Meaningful Sequence
As noted in 1.3.3 Sensory Characteristics
As noted in 1.4.1 Use of Color
As noted in 2.1.1 Keyboard
As noted in 2.4.3 Focus Order
As noted in 2.4.6 Headings and Labels
As noted in 3.1.2 Language of Parts
As noted in 3.2.1 On Focus
As noted in 4.1.2 Name, Role, Value
Web: Most functions of the product are usable with limited vision. Exceptions include:
As noted in 1.1.1 Non-text Content
As noted in 1.3.1 Info and Relationships
As noted in 1.3.2 Meaningful Sequence
As noted in 1.3.3 Sensory Characteristics
As noted in 1.4.1 Use of Color
As noted in 1.4.3 Contrast (Minimum)
As noted in 1.4.4 Resize text
As noted in 2.1.1 Keyboard
As noted in 2.4.3 Focus Order
As noted in 2.4.6 Headings and Labels
As noted in 2.4.7 Focus Visible
As noted in 3.1.2 Language of Parts
As noted in 3.2.1 On Focus
As noted in 3.3.2 Labels or Instructions
As noted in 4.1.2 Name, Role, Value
Web: Most functions of the product are usable without perception of color. Exceptions include:
As noted in 1.4.1 Use of Color
As noted in 1.4.3 Contrast (Minimum)
Web: Most functions of the product are usable without hearing. Exceptions include:
As noted in 1.3.3 Sensory Characteristics
As noted in 3.1.2 Language of Parts
Web: Most functions of the product are usable with limited hearing. Exceptions include:
As noted in 1.3.3 Sensory Characteristics
As noted in 3.1.2 Language of Parts
Web: Most functions of the product are usable with limited manipulation and does not require fine motor control or simultaneous manual operations. Exceptions include:
As noted in 2.1.1 Keyboard
As noted in 2.4.3 Focus Order
As noted in 2.4.6 Headings and Labels
As noted in 2.4.7 Focus Visible
As noted in 3.2.1 On Focus
As noted in 4.1.2 Name, Role, Value
Web: Most functions of the product are usable 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 or accessibility features of the platform. The product provides descriptive labels, instructions, and error identification and suggestions for most user input. Exceptions include:
As noted in 1.1.1 Non-text Content
As noted in 1.3.1 Info and Relationships
As noted in 1.3.2 Meaningful Sequence
As noted in 1.3.3 Sensory Characteristics
As noted in 1.4.1 Use of Color
As noted in 2.1.1 Keyboard
As noted in 2.2.2 Pause, Stop, Hide
As noted in 2.4.3 Focus Order
As noted in 2.4.6 Headings and Labels
As noted in 2.4.7 Focus Visible
As noted in 3.1.2 Language of Parts
As noted in 3.2.1 On Focus
As noted in 3.3.2 Labels or Instructions
As noted in 4.1.2 Name, Role, Value
The role, state(s), properties, boundary, name, and description of most objects can be programmatically determined, so those attributes can be perceived and conveyed by assistive technology. Exceptions include:
As noted in 4.1.2 Name, Role, Value
For most objects that allow the user to set their respective properties and/or state, the act of setting a property or state is available programmatically, so that it can be perceived and performed using assistive technology. Exceptions include:
As noted in 4.1.2 Name, Role, Value
In most instances, when a data table is present, all information in the data cells and the row and/or column headers associated with each data cell are available programmatically, so they can be perceived and conveyed by assistive technology. Exceptions include:
As noted in 1.3.1 Info and Relationships
For most objects that have a current value or have a set or range of values associated with the object, the value(s) are available programmatically, so they can be perceived and conveyed by assistive technology. Exceptions include:
As noted in 4.1.2 Name, Role, Value
For most objects that allow the user to set or modify their value, the act of setting a value is available programmatically, so that it can be perceived and performed using assistive technology. Exceptions include:
As noted in 4.1.2 Name, Role, Value
For most elements that act as a label for another element and elements that are labeled by another element, the labeling relationship is programmatically determinable, so it can be perceived and conveyed by assistive technology. Exceptions include:
As noted in 1.3.1 Info and Relationships
As noted in 4.1.2 Name, Role, Value
For most elements that have a parent-child relationship, those relationships are programmatically determinable, so they can be perceived by assistive technology. Exceptions include:
As noted in 1.3.1 Info and Relationships
Most text, text attributes (such as whether text is static or editable), and text boundaries are programmatically determinable, so they can be perceived and conveyed by assistive technology. Exceptions include:
As noted in 1.3.1 Info and Relationships
For most of the elements on which one or more actions may be performed, all of those actions are programmatically determinable, so that each action can be perceived and conveyed by assistive technology. Exceptions include:
As noted in 4.1.2 Name, Role, Value
For most of the elements on which one or more actions may be performed, all of those actions are available programmatically, so that each action can be performed using assistive technology. Exceptions include:
As noted in 2.1.1 Keyboard
On most pages, the position and content of the focus indicator, text insertion point, and/or text selector are programmatically determinable, so that focus position and content can be perceived and conveyed by assistive technology. Exceptions include:
As noted in 2.4.7 Focus Visible
In most cases, status messages relevant to user interactions are available to, and presented by, assistive technology. Exceptions include:
As noted in 4.1.3 Status Messages
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
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
As noted in 1.3.1 Info and Relationships
As noted in 1.3.2 Meaningful Sequence
As noted in 1.3.3 Sensory Characteristics
As noted in 1.4.1 Use of Color
As noted in 2.1.1 Keyboard
As noted in 2.4.3 Focus Order
As noted in 2.4.6 Headings and Labels
As noted in 3.1.2 Language of Parts
As noted in 3.2.1 On Focus
As noted in 4.1.2 Name, Role, Value
As noted in 4.1.3 Status Messages
Web: Most functions of the product are usable with limited vision. Exceptions include:
As noted in 1.1.1 Non-text Content
As noted in 1.3.1 Info and Relationships
As noted in 1.3.2 Meaningful Sequence
As noted in 1.3.3 Sensory Characteristics
As noted in 1.4.1 Use of Color
As noted in 1.4.3 Contrast (Minimum)
As noted in 1.4.4 Resize text
As noted in 1.4.10 Reflow
As noted in 1.4.11 Non-text Contrast
As noted in 1.4.12 Text Spacing
As noted in 1.4.13 Content on Hover or Focus
As noted in 2.1.1 Keyboard
As noted in 2.4.3 Focus Order
As noted in 2.4.6 Headings and Labels
As noted in 2.4.7 Focus Visible
As noted in 3.1.2 Language of Parts
As noted in 3.2.1 On Focus
As noted in 3.3.2 Labels or Instructions
As noted in 4.1.2 Name, Role, Value
Web: Most functions of the product are usable without perception of color. Exceptions include:
As noted in 1.4.1 Use of Color
As noted in 1.4.3 Contrast (Minimum)
As noted in 1.4.11 Non-Text Contrast
Web: Most functions of the product are usable without hearing. Exceptions include:
As noted in 1.1.1 Non-text Content
As noted in 1.3.3 Sensory Characteristics
As noted in 3.1.2 Language of Parts
Web: Most functions of the product are usable with limited hearing. Exceptions include:
As noted in 1.1.1 Non-text Content
As noted in 1.3.3 Sensory Characteristics
As noted in 3.1.2 Language of Parts
Web: Most functions of the product are usable by people with limited manipulation and does not require manipulation, simultaneous action, or hand strength. Exceptions include:
As noted in 1.4.13 Content on Hover or Focus
As noted in 2.1.1 Keyboard
As noted in 2.4.3 Focus Order
As noted in 2.4.6 Headings and Labels
As noted in 2.4.7 Focus Visible
As noted in 2.5.3 Label in Name
As noted in 3.2.1 On Focus
As noted in 4.1.2 Name, Role, Value
Web: Most functions of the product are usable by people with limited reach. Exceptions are noted in:
As noted in 1.4.13 Content on Hover or Focus
As noted in 2.5.3 Label in Name
Web: Most functions of the product are usable by people with limited language, cognitive, and learning abilities. People with cognitive disabilities have varying needs for features that allow them to adapt content and work with assistive technology. Exceptions are noted in:
As noted in 1.1.1 Non-text Content
As noted in 1.3.1 Info and Relationships
As noted in 1.3.2 Meaningful Sequence
As noted in 1.3.3 Sensory Characteristics
As noted in 1.4.1 Use of Color
As noted in 1.4.10 Reflow
As noted in 1.4.12 Text Spacing
As noted in 1.4.13 Content on Hover or Focus
As noted in 2.1.1 Keyboard
As noted in 2.2.2 Pause, Stop, Hide
As noted in 2.4.3 Focus Order
As noted in 2.4.6 Headings and Labels
As noted in 2.4.7 Focus Visible
As noted in 2.5.3 Label in Name
As noted in 3.1.2 Language of Parts
As noted in 3.2.1 On Focus
As noted in 3.3.2 Labels or Instructions
As noted in 4.1.2 Name, Role, Value
As noted in 4.1.3 Status Messages
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 (see WCAG 2.2 section)
Notes :
Chapter 10: Non-Web Documents
Notes : Not Applicable
Chapter 11: Software
Notes: Not Applicable
The product exposes the name, role and state or value of most objects to assistive technology. Exceptions include:
As noted in 4.1.2 Name, Role, Value
The product exposes the row, column, and headers of table cells to assistive technology. Exceptions include:
As noted in 1.3.1 Info and Relationships
For most objects that have a current value or have a set or range of values associated with the object, the value(s) is available programmatically, so it can be perceived and conveyed by assistive technology. Exceptions include:
As noted in 4.1.2 Name, Role, Value
The product UI exposes most label relationships to assistive technologies. Exceptions include:
As noted in 1.3.1 Info and Relationships
As noted in 4.1.2 Name, Role, Value
When a page contains elements that have a parent-child relationship, those relationships are programmatically determinable, so they can be perceived by assistive technology. Exceptions include:
As noted in 1.3.1 Info and Relationships
The product exposes most text content and text values to assistive technology. Exceptions include:
As noted in 1.3.1 Info and Relationships
Most controls in the product expose programmatic role information and actions which can be taken on objects to assistive technology. Exceptions include:
As noted in 4.1.2 Name, Role, Value
The product allows assistive technology to perform all actions on objects. Exceptions include:
As noted in 2.1.1 Keyboard
The product exposes focus location, text insertion point, and object selection state for most user interface components. Exceptions include:
As noted in 2.4.7 Focus Visible
The product notifies assistive technology to most user interaction events. Exceptions include:
As noted in 4.1.3 Status Messages
The product allows assistive technology to modify states and properties of some controls and inputs. Exceptions include:
As noted in 4.1.2 Name, Role, Value
For most objects that allow the user to set or modify its value, the act of setting a value is available programmatically, so that it can be perceived and performed using assistive technology. Exceptions include:
As noted in 4.1.2 Name, Role, Value
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 on the Adobe Accessibility Compliance website.
Chapter 13: ICT Providing Relay or Emergency Service Access
Notes: Not Applicable