Name of Product/Version: Adobe Photoshop version 21.1.2 (macOS)
Product Description: Photoshop is an industry leading imaging software for digital imagery; compositing, retouching, drawing, illustration, creative imaging and more.
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, screen magnifiers, and speech recognition software, as well exclusive 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:
The terms used in the Conformance Level information are defined as follows:
Supports: The functionality of the product has at least one method that meets the criterion without known defects or meets with equivalent facilitation.
Partially Supports: Some functionality of the product does not meet the criterion.
Does Not Support: The majority of product functionality does not meet the criterion.
Not Applicable: The criterion is not relevant to the product.
Not Evaluated: The product has not been evaluated against the criterion. This can be used only in WCAG 2.0 Level AAA.
WCAG 2.x Report
All WCAG sections 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.x Success Criteria, they are scoped for full pages, complete processes, and accessibility-supported ways of using technology as documented in the WCAG 2.0 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.
Software: The product does not provide sufficient text alternatives for most non-text content, including images that are within the product screens and image buttons.
Authored Content (PDF): The product does not allow authors to provide text alternatives for non-text content.
Software: A clear hierarchy is represented in menus; however, most information and relationships conveyed through presentation in the product cannot be programmatically determined, nor are they available in text.
Authored Content (PDF): The product does not allow authors to provide appropriate programmatic or textual equivalents for most visual structure and relationship information.
Software: The text of interface increases in size appropriately.
Authored Content (PDF): Using the zoom function of a PDF reader application, text can be resized up to 200 percent without loss of content or functionality.
Software: The product uses text instead of images of text.
Authored Content (PDF): All text is exported as an image with no alternative text.
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.1 (Open Functionality Software)
11.1.4.10.2 (Closed Software)
11.8.2 (Authoring Tool)
12.1.2 (Product Docs)
12.2.4 (Support Docs)
Revised Section 508 – Does not apply
Software: Supports
Authored Content (PDF): Supports
Software: At the required width of 320 CSS pixels, content is presented without loss of information or functionality, and without requiring scrolling in two dimensions.
Authored Content (PDF): Authored content requires two-dimensional layout for meaning.
Software: When content is triggered by hover or focus, it becomes visible and then hidden in a manner which meets this criterion.
Authored Content (PDF): Authored content does not contain content elements triggered by hover or focus.
Guideline 2.1 Keyboard Accessible:
Make all functionality available from a keyboard.
Criteria
Conformance Level
Remarks and Explanations
2.1.1 Keyboard (Level A) Also applies to: EN 301 549 Criteria
9.2.1.1 (Web)
10.2.1.1 (Non-web document)
11.2.1.1.1 (Open Functionality Software)
11.2.1.1.2 (Closed Software)
11.8.2 (Authoring Tool)
12.1.2 (Product Docs)
12.2.4 (Support Docs)
Revised Section 508
501 (Web)(Software)
504.2 (Authoring Tool)
602.3 (Support Docs)
Software: Does Not Support
Authored Content (PDF): Supports
Software: The main application menus are keyboard accessible. However, most complete product functions cannot be operated through a keyboard interface. Examples include:
The main tool bar does not have a method of access via the keyboard.
Most controls are not accessible with the keyboard.
Authored Content (PDF): Authored content does not contain controls that would require a keyboard interface.
Software: The product does not process legal commitments or financial transactions. When editing files, changes to user-controllable data are reversible or can be confirmed before finalizing.
Authored Content (PDF): Authored content does not contain legal or financial data and does not modify user-controllable data.
Guideline 4.1 Compatible:
Maximize compatibility with current and future user agents, including assistive technologies.
Criteria
Conformance Level
Remarks and Explanations
4.1.1 Parsing (Level A) Also applies to: EN 301 549 Criteria
9.4.1.1 (Web)
10.4.1.1 (Non-web document)
11.4.1.1.1 (Open Functionality Software)
11.4.1.1.2 (Closed Software) – 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)
Software: Supports
Authored Content (PDF): Supports
Software: This criterion does not apply to non-web software.
Authored Content (PDF): The authored content is not implemented using markup languages.
Software: User interface components in most product functions do not provide programmatic information.
Authored Content (PDF): Authored content does not contain controls that would require programmatically determined name, role, state, property, and value information.
Notes: This table documents instances of equivalent facilitation or instances of functions not addressed by technical requirements. Responses which cite technical requirements are informative only.
Criteria
Conformance Level
Remarks and Explanations
302.1 Without Vision
Software: Does Not Support
Authored Content (PDF): Does Not Support
Software: Most functions of the product are not usable without vision. Examples include:
As noted in 1.1.1 Non-text Content, the product does not provide sufficient text alternatives.
As noted in 1.3.1 Info and Relationships, most information and relationships conveyed through presentation in the product cannot be programmatically determined, nor are they available in text.
As noted in 1.3.2 Meaningful Sequence, the product does not have a meaningful reading sequence that can be programmatically determined.
As noted in 2.1.1 Keyboard, most product functionality cannot be operated using the keyboard alone for navigation.
As noted in 2.1.2 No Keyboard Trap, a keyboard trap is present when creating a new document.
As noted in 4.1.2 Name, Role, Value, user interface components in most product functions do not provide programmatic information.
Authored Content (PDF): The product does not allow authors to create content which is functional for users without vision. Examples include:
As noted in 1.1.1 Non-text Content, authors cannot provide alternative text that is exported.
As noted in 1.3.1 Info and Relationships, the product does not allow authors to provide appropriate programmatic or textual equivalents for most visual structure and relationship information.
As noted in 1.3.2 Meaningful Sequence, the product does not allow authors to present content in a meaningful sequence.
302.2 With Limited Vision
Software: Partially Supports
Authored Content (PDF): Supports
Software: Most functions of the product are usable with limited vision. Exceptions include:
As noted in 1.1.1 Non-text Content, the product does not provide sufficient text alternatives.
Authored Content (PDF): Authors can create content which is functional for users with limited vision.
302.3 Without Perception of Color
302.3 Without Perception of Color
Software: Supports
Authored Content (PDF): Supports
Software: The product is usable by people without perception of color.
Authored Content (PDF): Authors can create content which is functional for users without perception of color.
302.3 Without Perception of Color
302.4 Without Hearing
Software: Supports
Authored Content (PDF): Supports
Software: The product does not require the use of hearing.
Authored Content (PDF): Authors can create content which is functional for users without hearing.
302.5 With Limited Hearing
Software: Supports
Authored Content (PDF): Supports
Software: The product does not require the use of hearing.
Authored Content (PDF): Authors can create content which is functional for users with limited hearing.
302.6 Without Speech
Software: Supports
Authored Content (PDF): Supports
Software: The product does not require the use of speech.
Authored Content (PDF): Authors can create content which is functional for users without speech.
302.7 With Limited Manipulation
Software: Does Not Support
Authored Content (PDF): Supports
Software: Most functions of the product are not usable with limited manipulation. Examples include:
As noted in 2.1.1 Keyboard, most product functionality requires the use of a mouse.
As noted in 2.1.2 No Keyboard Trap, a keyboard trap is present when creating a new document.
Authored Content (PDF): Authors can create content which is functional for users with limited manipulation.
302.8 With Limited Reach and Strength
Software: Supports
Authored Content (PDF): Supports
Software: The product is functional with limited reach and strength.
Authored Content (PDF): Authors can create content which is functional with limited reach and strength.
302.9 With Limited Language, Cognitive, and Learning Abilities
Software: Supports
Authored Content (PDF): Supports
Software: The product is functional for users with limited language, cognitive, and learning abilities.
Authored Content (PDF): Authors can create content which is functional for users with limited language, cognitive, and learning abilities.
The product does not disrupt platform accessibility features.
502.3.1 Object Information
Does Not Support
The product does not provide names and roles for most controls, as noted in 1.3.1 Info and Relationships and 4.1.2 Name, Role, Value.
502.3.2 Modification of Object Information
Does Not Support
Most states and properties of controls cannot be set programmatically through assistive technology.
502.3.3 Row, Column, and Headers
Not Applicable
The product does not contain tables.
502.3.4 Values
Partially Supports
The product exposes the values of most input controls to assistive technology. Exceptions include:
Combo boxes.
502.3.5 Modification of Values
Does Not Support
Most values of controls cannot be set programmatically through assistive technology.
502.3.6 Label Relationships
Does Not Support
As noted in 4.1.2 Name, Role, Value, the product does not expose most label relationships to assistive technology.
502.3.7 Hierarchical Relationships
Does Not Support
As noted in 1.3.1 Info and Relationships, most information on screens is not exposed to assistive technology, which includes hierarchical parent-child relationships.
502.3.8 Text
Does Not Support
As noted in 1.3.1 Info and Relationships, most text information on screens is not exposed to assistive technology.
502.3.9 Modification of Text
Supports
Where text input controls are present, their text values can be set programmatically through assistive technology.
502.3.10 List of Actions
Does Not Support
Some controls, such as menus, provide role information. However, most controls in the product do not expose programmatic role information and actions which can be taken on objects to assistive technology.
502.3.11 Actions on Objects
Does Not Support
Though some actions can be executed on objects through assistive technology, most actions require the use of a mouse.
502.3.12 Focus Cursor
Supports
Where components receive focus, the product exposes focus, text insertion point, and selection attributes to assistive technology.
502.3.13 Modification of Focus Cursor
Partially Supports
Partially Supports
The product allows assistive technology to move or modify focus, insertion point, and selection for most controls. Exceptions include:
As noted in 2.1.2 No Keyboard Trap, focus is trapped at the library search box after creating a new document.
Partially Supports
502.3.14 Event Notification
Does Not Support
The product does not notify assistive technology about most attribute changes in user interface elements. Examples include:
The state change of checkboxes and radio buttons.
502.4 Platform Accessibility Features
Not Applicable
The product is not platform software.
503.2 User Preferences
Supports
System accessibility preferences are supported in the software, such as invert colors, high contrast, and others.
503.3 Alternative User Interfaces
Not Applicable
The product does not provide an alternative user interface that functions as assistive technology.
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.
Software: Most functions of the product are not usable without vision. Examples include:
As noted in 1.1.1 Non-text Content, the product does not provide sufficient text alternatives.
As noted in 1.3.1 Info and Relationships, most information and relationships conveyed through presentation in the product cannot be programmatically determined, nor are they available in text.
As noted in 1.3.2 Meaningful Sequence, the product does not have a meaningful reading sequence that can be programmatically determined.
As noted in 2.1.1 Keyboard, most product functionality cannot be operated using the keyboard alone for navigation.
As noted in 2.1.2 No Keyboard Trap, a keyboard trap is present when creating a new document.
As noted in 4.1.2 Name, Role, Value, user interface components in most product functions do not provide programmatic information.
Authored Content (PDF): The product does not allow authors to create content which is functional for users without vision. Examples include:
As noted in 1.1.1 Non-text Content, authors cannot provide alternative text that is exported.
As noted in 1.3.1 Info and Relationships, the product does not allow authors to provide appropriate programmatic or textual equivalents for most visual structure and relationship information.
As noted in 1.3.2 Meaningful Sequence, the product does not allow authors to present content in a meaningful sequence.
4.2.2 Usage with limited vision
Software: Partially Supports
Authored Content (PDF): Supports
Software: Most functions of the product are usable with limited vision. Exceptions include:
As noted in 1.1.1 Non-text Content, the product does not provide sufficient text alternatives.
As noted in 1.4.11 Non-text Contrast, in some product functions a control has a dark blue outline on a dark gray background.
Authored Content (PDF): Authors can create content which is functional for users with limited vision.
4.2.3 Usage without perception of colour
Software: Supports
Authored Content (PDF): Supports
Software: The product is usable by people without perception of color.
Authored Content (PDF): Authors can create content which is functional for users without perception of color.
4.2.4 Usage without hearing
Software: Supports
Authored Content (PDF): Supports
Software: The product does not require the use of hearing.
Authored Content (PDF): Authors can create content which is functional for users without hearing.
4.2.5 Usage with limited hearing
Software: Supports
Authored Content (PDF): Supports
Software: The product does not require the use of hearing.
Authored Content (PDF): Authors can create content which is functional for users with limited hearing.
4.2.6 Usage with no or limited vocal capability
Software: Supports
Authored Content (PDF): Supports
Software: The product does not require the use of speech.
Authored Content (PDF): Authors can create content which is functional for users without speech.
4.2.7 Usage with limited manipulation or strength
Software: Does Not Support
Authored Content (PDF): Supports
Software: Most functions of the product are not usable with limited manipulation or strength. Examples include:
As noted in 2.1.1 Keyboard, most product functionality requires the use of a mouse.
As noted in 2.1.2 No Keyboard Trap, a keyboard trap is present when creating a new document.
Authored Content (PDF): Authors can create content which is functional for users with limited manipulation or strength.
4.2.8 Usage with limited reach
Software: Supports
Authored Content (PDF): Supports
Software: The product is functional with limited reach.
Authored Content (PDF): Authors can create content which is functional with limited reach.
4.2.9 Minimize photosensitive seizure triggers
Software: Supports
Authored Content (PDF): Supports
Software: The product does not contain flashing content.
Authored Content (PDF): Authors can create content which does not flash, or flashes within an acceptable threshold, in order to minimize the potential for triggering photosensitive seizures.
4.2.10 Usage with limited cognition, language or learning
Software: Supports
Authored Content (PDF): Supports
Software: The product is functional for users with limited language, cognitive, and learning abilities.
Authored Content (PDF): Authors can create content which is functional for users with limited language, cognitive, and learning abilities.
4.2.11 Privacy
Software: Supports
Authored Content (PDF): Supports
Software: The product maintains user privacy when accessibility features are used.
Authored Content (PDF): Authors can create content which maintains user privacy when accessibility features are used.
5.1.3.16 Receipts, tickets, and transactional outputs
Not Applicable
The product does not have closed functionality.
5.1.4 Functionality closed to text enlargement
Not Applicable
The product does not have functionality that is closed to text enlargement.
5.1.5 Visual output for auditory information
Not Applicable
The product does not have closed functionality.
5.1.6.1 Closed functionality
See 5.1.3.1 through 5.1.3.16
See information in 5.1.3.1 through 5.1.3.16.
5.1.6.2 Input focus
Not Applicable
The product does not have functionality that is closed to keyboards.
5.2 Activation of accessibility features
Does Not Support
Text enlargement and interface color change (to increase contrast) rely on the user’s ability to perceive small menu text. Creation of additional keyboard shortcuts requires the mouse.
5.3 Biometrics
Not Applicable
The product does not rely on biological characteristics for user identification or for control of the product.
5.4 Preservation of accessibility information during conversion
Does Not Support
Alternative text information for images is only exported with HTML documents and not PDF.
5.5.1 Means of operation
Not Applicable
The product has only non-mechanical operable parts, such as on-screen buttons, which do not require grasping, pinching, or twisting of the wrist to operate.
5.5.2 Operable parts discernibility
Does Not Support
The product has only non-mechanical operable parts, such as on-screen buttons. As noted in 4.1.2 Name, Role, Value, most operable parts lack an accessible name which would enable them to be discernible without user vision.
5.6.1 Tactile or auditory status
Not Applicable
This product does not have locking or toggle controls.
5.6.2 Visual status
Not Applicable
This product does not have locking or toggle controls.
5.7 Key repeat
Not Applicable
This product relies on platform software to turn off or adjust key repeat.
5.8 Double-strike key acceptance
Not Applicable
This product does not supply a keyboard or keypad.
5.9 Simultaneous user actions
Supports
The product relies on platform software features, such as Sticky Keys, to ensure simultaneous user actions are not required.
11.5.2.1 Platform accessibility service support for software that provides a user interface
See 11.5.2.5 through 11.5.2.17
See information in 11.5.2.5 through 11.5.2.17.
11.5.2.2 Platform accessibility service support for assistive technologies
See 11.5.2.5 through 11.5.2.17
See information in 11.5.2.5 through 11.5.2.17.
11.5.2.3 Use of accessibility services
See 11.5.2.5 through 11.5.2.17
See information in 11.5.2.5 through 11.5.2.17.
11.5.2.4 Assistive technology
Not applicable
The product is not assistive technology.
11.5.2.5 Object information
Does Not Support
The product does not provide names and roles for most controls, as noted in 1.3.1 Info and Relationships and 4.1.2 Name, Role, Value.
11.5.2.6 Row, column, and headers
Not Applicable
The product does not contain tables.
The product does not contain tables.
The product does not contain tables.
11.5.2.7 Values
Partially Supports
The product exposes the values of most input controls to assistive technology. Exceptions include:
Combo boxes.
11.5.2.8 Label relationships
Does Not Support
As noted in 4.1.2 Name, Role, Value, the product does not expose most label relationships to assistive technology.
11.5.2.9 Parent-child relationships
Does Not Support
As noted in 1.3.1 Info and Relationships, most information on screens is not exposed to assistive technology, which includes hierarchical parent-child relationships.
11.5.2.10 Text
Does Not Support
As noted in 1.3.1 Info and Relationships, most text information on screens is not exposed to assistive technology.
11.5.2.11 List of available actions
Does Not Support
Some controls, such as menus, provide role information. However, most controls in the product do not expose programmatic role information and actions which can be taken on objects to assistive technology.
11.5.2.12 Execution of available actions
Does Not Support
Though some actions can be executed on objects through assistive technology, most actions require the use of a mouse.
11.5.2.13 Tracking of focus and selection attributes
Supports
Where components receive focus, the product exposes focus, text insertion point, and selection attributes to assistive technology.
11.5.2.14 Modification of focus and selection attributes
Partially Supports
The product allows assistive technology to move or modify focus, insertion point, and selection for most controls. Exceptions include:
As noted in 2.1.2 No Keyboard Trap, focus is trapped at the library search box after creating a new document.
11.5.2.15 Change notification
Does Not Support
The product does not notify assistive technology about most attribute changes in user interface elements. Examples include:
The state change of checkboxes and radio buttons.
11.5.2.16 Modifications of states and properties
Does Not Support
Most states and properties of controls cannot be set programmatically through assistive technology.
11.5.2.17 Modifications of values and text
Does Not Support
Most values of controls cannot be set programmatically through assistive technology.
11.6.1 User control of accessibility features
Not Applicable
The product is not platform software.
11.6.2 No disruption of accessibility features
Supports
The product does not disrupt platform accessibility features.
11.7 User preferences
Supports
System accessibility preferences are supported in the software, such as invert colors, high contrast, and others.
The product enables authors to create content which partially conforms to WCAG 2.1 Levels A and AA. See details for individual criteria in the WCAG 2.x section. Most authoring functions in the product do not actively guide authors to create accessible content.
11.8.3 Preservation of accessibility information in transformations
Does Not Support
When converting a Photoshop file into PDF format, the product does not preserve the alternative text of images or other textual information.
11.8.4 Repair assistance
Not Applicable
The product does not have accessibility checking functionality.
11.8.5 Templates
Does Not Support
Downloadable templates do not allow authors to create content which conforms to WCAG 2.1 Levels A and AA.
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.
Voluntary Product Accessibility Template® and VPAT® are a registered trademark of Information Technology Industry Council (ITI)
Cookie Settings
General information
You can control how Adobe websites use cookies and similar technologies by making choices below. But note that if you disable cookies and similar technologies entirely, Adobe websites may not function properly.
Cookies are small text files stored by your web browser when you use websites. There are also other technologies that can be used for similar purposes like HTML5 Local Storage and local shared objects, web beacons, and embedded scripts. These technologies help us do things like remembering you and your preferences when you return to our sites, measure how you use the website, conduct market research, and gather information about the ads you see and interact with.
You can make choices in the menu below about what cookies and other technologies you want us to use on Adobe sites when you visit them from this browser. You can always change those choices later by clicking on the Cookie Preferences link at the bottom of the page.
If enabled:
We can improve your experience by tailoring the site and the content to things we think might be of interest
We can better keep track of your preferences — like what language you prefer to use
We will better understand your likely interests so we can provide you more relevant Adobe ads and content on non-Adobe websites and in non-Adobe apps
It will help us improve the performance of our website and those of our partners who use the Adobe Experience Cloud
If disabled:
We won’t be able to remember you from session to session so the experience may not be tailored to your interests
You’ll still have access to the content of the site but certain features that depend on cookies may not function
You’ll still see ads, they just may not be as relevant to you
General information
You can control how Adobe websites use cookies and similar technologies by making choices below. But note that if you disable cookies and similar technologies entirely, Adobe websites may not function properly.
Cookies are small text files stored by your web browser when you use websites. There are also other technologies that can be used for similar purposes like HTML5 Local Storage, web beacons, and embedded scripts. These technologies help us do things like remembering you and your preferences when you return to our sites, measure how you use the website, conduct market research, and gather information about the ads you see and interact with.
You can make choices in the menu below about what cookies and other technologies you want us to use on Adobe sites when you visit them from this browser. You can always change those choices later by clicking on the Cookie Preferences link at the bottom of the page.
If enabled:
We can improve your experience by tailoring the site and the content to things we think might be of interest
We can better keep track of your preferences — like what language you prefer to use
We will better understand your likely interests so we can provide you more relevant Adobe ads and content on non-Adobe websites and in non-Adobe apps
It will help us improve the performance of our website and those of our partners who use the Adobe Experience Cloud
If disabled:
We won’t be able to remember you from session to session so the experience may not be tailored to your interests
We’ll still count your use of our site and services
You’ll still have access to the content of the site but certain features that depend on cookies may not function
You’ll still see ads, they just may not be as relevant to you
Operate the site and core servicesOperate site and measure engagement
Always active
These cookies are required, and they are used to enable the site and related services core functionality. Without them the site could not operate, so they cannot be disabled.
These cookies enable the site and related services’ core functionality and collect statistics about user engagement, such as counting active use to help us understand trends. These cookies cannot be disabled.
Measure performance
These cookies are used to analyze site usage to measure and improve performance. Without them Adobe cannot know what content is most valued and how often unique visitors return to the site, making it hard to improve information we offer to you.
These cookies are used to analyze site usage to measure and improve performance. Without them Adobe cannot know what content is most valued, making it hard to improve information we offer to you.
Extend functionality
These cookies are used to enhance the functionality of Adobe sites such as remembering your settings and preferences to deliver a personalized experience; for example, your username, your repeated visits, preferred language, your country, or any other saved preference.
Personalize advertising
These cookies are used to enable Adobe and our partners to serve ads more relevant to your interests. Without them you will still see ads, but they might not be as relevant to you.
