Adobe Accessibility Conformance Report
VPAT® Version 2.3 (Revised) – April 2019
Product Information
Name of Product/Version: Lightroom Classic - MacOS
Product Description: The desktop-focused app for editing and organizing your photos.
Date: August 2023
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 Lightroom Classic 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:
Standard/Guideline |
Included in Report |
---|---|
Level A: Yes |
|
Level A: Yes |
|
Yes |
|
Yes |
Terms
The terms used in the Conformance Level information are defined as follows:
- Supports: The functionality of the product has at least one method that meets the criterion without known defects or meets with equivalent facilitation.
- Partially Supports: Some functionality of the product does not meet the criterion.
- Does Not Support: The majority of product functionality does not meet the criterion.
- Not Applicable: The criterion is not relevant to the product.
- Not Evaluated: The product has not been evaluated against the criterion. This can be used only in WCAG 2.0 Level AAA.
WCAG 2.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.
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
1.1.1 Non-text Content (Level A)
Revised Section 508
|
Software: Does Not Support Authored Content (HTML): Partially Supports |
Software: Most non-text controls in the product are identified by text that appears on mouse hover. However, this text is not announced by screen readers. Authored Content (HTML): The Classic template uses the value of the image metadata Title field as alt text on detail pages but does not provide appropriate alt text on the index page. Most templates in the product do not allow authors to provide sufficient text alternatives for images. |
Guideline 1.2 Time-based Media:
Provide alternatives for time-based media.
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
1.2.1 Audio-only and Video-only (Prerecorded) (Level A)
Revised Section 508
|
Software: Supports Authored Content (HTML): Supports |
Software: The product does not contain prerecorded audio-only or video-only content. Authored Content (HTML): Authored Content (HTML): The Classic template uses the value of the image metadata Title field as alt text on detail pages but does not provide appropriate alt text on the index page. Most templates in the product do not allow authors to provide sufficient text alternatives for images. |
1.2.2 Captions (Prerecorded) (Level A)
Revised Section 508
|
Software: Supports Authored Content (HTML): Supports |
Software: The product does not contain prerecorded synchronized media. Authored Content (HTML): Authored content does not contain prerecorded synchronized media. |
1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A)
Revised Section 508
|
Software: Supports Authored Content (HTML): Supports |
Software: The product does not contain prerecorded synchronized media. Authored Content (HTML): Authored content does not contain prerecorded synchronized media. |
1.2.4 Captions (Live) (Level AA)
Revised Section 508
|
Software: Supports Authored Content (HTML): Supports |
Software: The product does not contain live synchronized media. Authored Content (HTML): Authored content does not contain live synchronized media. |
1.2.5 Audio Description (Prerecorded) (Level AA)
Revised Section 508
|
Software: Supports Authored Content (HTML): Supports |
Software: The product does not provide prerecorded media that requires audio description. Authored Content (HTML): Authored content does not contain video content that would require audio description. |
Guideline 1.3 Adaptable:
Create content that can be presented in different ways (for example simpler layout) without losing information or structure.
Criteria |
Conformance Level |
Remarks and Explanations |
|
---|---|---|---|
1.3.1 Info and Relationships (Level A)
Revised Section 508
|
|
Software: Structure and relationship information is provided. Authored Content (HTML): Authors can provide appropriate semantics for most visual structure and relationship information. Exceptions include:
|
|
1.3.2 Meaningful Sequence (Level A)
Revised Section 508
|
Software: Supports Authored Content (HTML): Supports |
|
|
1.3.3 Sensory Characteristics (Level A)
Revised Section 508
|
Software: Supports Authored Content (HTML): Supports |
Software: Instructions do not rely solely on sensory characteristics. Authored Content (HTML): Authors can ensure that content meets this criterion. |
|
1.3.4 Orientation (Level AA 2.1 only)
Revised Section 508 – Does not apply |
Software: Supports Authored Content (HTML): Supports |
Software: Content does not restrict its view and operation to a single display orientation. Authored Content (HTML): Authored content does not restrict its view and operation to a single display orientation. |
|
1.3.5 Identify Input Purpose (Level AA 2.1 only)
Revised Section 508 – Does not apply |
Software: Supports Authored Content (HTML): Supports |
Software: The product’s technology does not have support for programmatic identification of input purpose. Authored Content (HTML): Authored content does not contain user input controls which would require identification of input purpose. |
Guideline 1.4 Distinguishable:
Make it easier for users to see and hear content including separating foreground from background.
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
1.4.1 Use of Color (Level A)
Revised Section 508
|
Software: Partially Supports Authored Content (HTML): Supports |
Software: Most functions of the product do not convey information through color alone. Exceptions include:
Authored Content (HTML): Authors can ensure that content meets this criterion. |
1.4.2 Audio Control (Level A)
Revised Section 508
|
Software: Supports Authored Content (HTML): Supports |
Software: The product does not contain audio that plays automatically. Authored Content (HTML): Authored content does not contain audio that plays automatically. |
1.4.3 Contrast (Minimum) (Level AA)
Revised Section 508
|
Software: Partially Supports Authored Content (HTML): Supports |
Software: Most text meets minimum contrast requirements. Exceptions include:
Authored Content (HTML): Authors can ensure that content meets this criterion. |
1.4.4 Resize text (Level AA)
Revised Section 508
|
Software: Supports Authored Content (HTML): Supports |
Software: The product provides a text resizing function and allows operating system display scaling to resize text up to 200 percent without loss of content or functionality. Authored Content (HTML): Using browser zoom, text in authored content can be resized up to 200 percent without loss of content or functionality. |
1.4.5 Images of Text (Level AA)
Revised Section 508
|
Software: Supports Authored Content (HTML): Supports |
Software: The product uses text instead of images of text. Authored Content (HTML): Authors can ensure that content meets this criterion. |
1.4.10 Reflow (Level AA 2.1 only)
Revised Section 508 – Does not apply |
Software: Partially Supports Authored Content (HTML): Supports |
Software: When text is increased to the maximum size allowed by the combination of platform and application settings, no loss of content or functionality occurs, and scrolling in two directions is not required. However, the product viewport cannot be reduced to 320 CSS pixels, and text size cannot be increased to 400% at a viewport width of 1280 CSS pixels. Authored Content (HTML): At the required width of 320 CSS pixels, authored content is presented without loss of information or functionality, and without requiring scrolling in two dimensions. |
1.4.11 Non-text Contrast (Level AA 2.1 only)
Revised Section 508 – Does not apply |
Software: Partially Supports Authored Content (HTML): Supports |
Software: Some active user interface controls do not meet minimum contrast requirements. Examples include:
Authored Content (HTML): Authors can ensure that content meets this criterion by using the Classic template and selecting colors with adequate contrast |
1.4.12 Text Spacing (Level AA 2.1 only)
Revised Section 508 – Does not apply |
Software: Supports Authored Content (HTML): Supports |
Software: The product is not implemented using markup languages. Authored Content (HTML): Authored content supports the required text style properties without loss of content or functionality. |
1.4.13 Content on Hover or Focus (Level AA 2.1 only)
Revised Section 508 – Does not apply |
Software: Does Not Support Authored Content (HTML): Supports |
Software: In most product functions, content that becomes visible on hover is hidden in a manner which does not meet this criterion. Examples include:
Authored Content (HTML): Authors can ensure that content meets this criterion. |
Guideline 2.1 Keyboard Accessible:
Make all functionality available from a keyboard.
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
2.1.1 Keyboard (Level A)
Revised Section 508
|
Software: Does Not Support Authored Content (HTML): Supports |
Software: Most content within the product cannot be operated through a keyboard interface. Although the main menu provides access to some functionality and keyboard shortcuts are available for some actions, many actions cannot be performed with a keyboard alone and most controls do not receive keyboard focus. Examples include:
Authored Content (HTML): Authors can ensure that content meets this criterion by using the Classic template. However, most authored content produced with other templates cannot be operated with a keyboard. |
2.1.2 No Keyboard Trap (Level A)
Revised Section 508
|
Software: Partially Supports Authored Content (HTML): Supports |
Software: Most content that receives keyboard focus within the product does not contain a keyboard trap. Exceptions include:
Authored Content (HTML): Authored content does not include keyboard traps. |
2.1.4 Character Key Shortcuts (Level A 2.1 only)
Revised Section 508 – Does not apply |
Software: Supports Authored Content (HTML): Supports |
Software: The product provides unmodified character key shortcuts, but the shortcuts can be remapped using platform tools. Authored Content (HTML): Authored content does not provide character key shortcuts. |
Guideline 2.2 Enough Time:
Provide users enough time to read and use content.
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
2.2.1 Timing Adjustable (Level A)
Revised Section 508
|
Software: Supports Authored Content (HTML): Supports |
Software: The product does not include time limits. Authored Content (HTML): Authored content does not include time limits. |
2.2.2 Pause, Stop, Hide (Level A)
Revised Section 508
|
Software: Supports Authored Content (HTML): Supports |
Software: The product does not include elements which move, blink, scroll, or auto-update. Authored Content (HTML): Authors can ensure that content meets this criterion. |
Guideline 2.3 Seizures:
Do not design content in a way that is known to cause seizures.
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
2.3.1 Three Flashes or Below Threshold (Level A)
Revised Section 508
|
Software: Supports Authored Content (HTML): Supports |
Software: The product does not contain flashing content. Authored Content (HTML): Authors can ensure that content does not flash. |
Guideline 2.4 Navigable:
Provide ways to help users navigate, find content, and determine where they are.
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
2.4.1 Bypass Blocks (Level A)
Revised Section 508
|
Software: Supports Authored Content (HTML): Supports |
Software: This criterion does not apply to non-web software. Authored Content (HTML): Authors can ensure content meets this criterion by using the Classic template. However, most templates in the product do not allow authors to create content which meets this criterion. |
2.4.2 Page Titled (Level A)
Revised Section 508
|
Software: Does Not Support Authored Content (HTML): Supports |
Software: The main product window has a visible title which changes as modules change, but this title is not announced correctly by assistive technology. Authored Content (HTML): Authors can ensure that content meets this criterion. |
2.4.3 Focus Order (Level A)
Revised Section 508
|
Software: Supports Authored Content (HTML): Supports |
Software: Where components receive focus, focus is received in a meaningful order. Authored Content (HTML): Authors can ensure that content meets this criterion. |
2.4.4 Link Purpose (In Context) (Level A)
Revised Section 508
|
Software: Supports Authored Content (HTML): Does Not Support |
Software: The purpose of link text in the product can be determined in context. Authored Content (HTML): Authors cannot provide the purpose of most links through link text alone or through programmatic context. Examples include:
|
2.4.5 Multiple Ways (Level AA)
Revised Section 508
|
Software: Supports Authored Content (HTML): Supports |
Software: This criterion does not apply to non-web software. Authored Content (HTML): Authors can ensure that content meets this criterion. |
2.4.6 Headings and Labels (Level AA)
Revised Section 508
|
Software: Supports Authored Content (HTML): Supports |
Software: Headings and labels are descriptive. Authored Content (HTML): Authors can ensure that content meets this criterion. |
2.4.7 Focus Visible (Level AA)
Revised Section 508
|
Software: Supports Authored Content (HTML): Supports |
Software: In those elements that can receive keyboard focus, focus is indicated visually. Authored Content (HTML): Authors can ensure that content meets this criterion. |
Guideline 2.5 Input Modalities:
Make it easier for users to operate functionality through various inputs beyond keyboard.
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
2.5.1 Pointer Gestures (Level A 2.1 only)
Revised Section 508 – Does not apply |
Software: Supports Authored Content (HTML): Supports |
Software: The product does not rely on multipoint or path-based gestures. Authored Content (HTML): Authored content does not rely on multipoint or path-based gestures. |
2.5.2 Pointer Cancellation (Level A 2.1 only)
Revised Section 508 – Does not apply |
Software: Partially Supports Authored Content (HTML): Supports |
Software: Some product functions that use a single pointer are completed before the user releases the pointer. Examples include:
Authored Content (HTML): Authors can ensure that content meets this criterion. |
2.5.3 Label in Name (Level A 2.1 only)
Revised Section 508 – Does not apply |
Software: Partially Supports Authored Content (HTML): Does Not Support |
Software: In some product functions, accessible names of controls do not contain the text of their visible labels. Examples include:
Authored Content (HTML): For most authored content, accessible names of controls do not contain the text of their visible labels. Examples include:
|
2.5.4 Motion Actuation (Level A 2.1 only)
Revised Section 508 – Does not apply |
Software: Supports Authored Content (HTML): Supports |
Software: The product does not include functionality operated by device motion or user motion. Authored Content (HTML): Authored content does not have functionality operated by device motion or user motion. |
Guideline 3.1 Readable:
Make text content readable and understandable.
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
3.1.1 Language of Page (Level A)
Revised Section 508
|
Software: Supports Authored Content (HTML): Does Not Support |
Software: The product responds to operating system settings for language. Authored Content (HTML): The product does not allow authors to set the language of the page. |
3.1.2 Language of Parts (Level AA)
Revised Section 508
|
Software: Supports Authored Content (HTML): Does Not Support |
Software: Content is only presented in one language at a time. Authored Content (HTML): Authors cannot set the language for individual phrases within the content. |
Guideline 3.2 Predictable:
Make Web pages appear and operate in predictable ways.
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
3.2.1 On Focus (Level A)
Revised Section 508
|
Software: Supports Authored Content (HTML): Supports |
Software: Components do not initiate a change of context when focused. Authored Content (HTML): Authored content does not include components that initiate a change of context when focused. |
3.2.2 On Input (Level A)
Revised Section 508
|
Software: Supports Authored Content (HTML): Supports |
Software: Changes of context that occur on user input are clearly indicated to the user before invoking them. Authored Content (HTML): Authored content does not include user interface components with settings that can be changed. |
3.2.3 Consistent Navigation (Level AA)
Revised Section 508
|
Software: Supports Authored Content (HTML): Supports |
Software: This criterion does not apply to non-web software. Authored Content (HTML): Navigational mechanisms are repeated in the same relative order in a set of pages. |
3.2.4 Consistent Identification (Level AA)
Revised Section 508
|
Software: Supports Authored Content (HTML): Supports |
Software: This criterion does not apply to non-web software. Authored Content (HTML): Authors can ensure that components with the same functionality are identified consistently in a set of pages. |
Guideline 3.3 Input Assistance:
Help users avoid and correct mistakes.
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
3.3.1 Error Identification (Level A)
Revised Section 508
|
Software: Supports Authored Content (HTML): Supports |
Software: Where input errors are automatically detected, such as invalid values in text inputs for slider controls, items in error are identified and error messages are provided as text. Authored Content (HTML): Authored content does not contain user input controls which would require error identification. |
3.3.2 Labels or Instructions (Level A)
Revised Section 508
|
Software: Supports Authored Content (HTML): Supports |
Software: Labels are provided for input fields. Authored Content (HTML): Authored content does not contain user input controls that would require labels or instructions. |
3.3.3 Error Suggestion (Level AA)
Revised Section 508
|
Software: Supports Authored Content (HTML): Supports |
Software: Where input errors are automatically detected, such as invalid values in text inputs for slider controls, the value is corrected to the closest suggested value and the user is informed. Authored Content (HTML): Authored content does not contain user input controls which would require error identification or suggestion. |
3.3.4 Error Prevention (Legal, Financial, Data) (Level AA)
Revised Section 508
|
Software: Supports Authored Content (HTML): Supports |
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 (HTML): Authored content does not contain user input controls which would require error identification or prevention. |
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)
Revised Section 508
|
Software: Supports Authored Content (HTML): Supports |
Software: The product is not implemented using markup languages. Authored Content (HTML): 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. |
4.1.2 Name, Role, Value (Level A)
Revised Section 508
|
Software: Does Not Support Authored Content (HTML): Supports |
Software: User interface components in most product functions do not provide programmatic name, role, or state information. Examples include:
Authored Content (HTML): Authors can ensure that content meets this criterion by using the Classic template. However, content generated with other templates does not provide name, role, value, or state information. |
4.1.3 Status Messages (Level AA 2.1 only)
Revised Section 508 – Does not apply |
Software: Supports Authored Content (HTML): Supports |
Software: This criterion does not apply to non-web software. Authored Content (HTML): Authored content does not include status messages. |
Revised Section 508 Report
Notes:
Chapter 3: Functional Performance Criteria (FPC)
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 (HTML): Partially Supports |
Software: Most functions of the product are not usable without vision. Examples include:
Authored Content (HTML): One of four templates in the product allow users to create content that is partially usable without vision. Examples include:
|
|
302.2 With Limited Vision |
Software: Partially Supports Authored Content (HTML): Partially Supports |
Software: Most functions of the product are usable with limited vision. Exceptions include:
Authored Content (HTML): One of four templates in the product allow users to create content that is partially usable with limited vision. Examples include:
|
|
|
Software: Partially Supports Authored Content (HTML): Supports |
Software: Most functions of the product are usable without perception of color. Exceptions include:
Authored Content (HTML): Authors can create content which is functional for users without perception of color. |
|
302.4 Without Hearing |
Software: Partially Supports Authored Content (HTML): Supports |
Software: Most functions of the product are usable without hearing. Exceptions include:
Authored Content (HTML): Authors can create content which is functional for users without hearing. |
|
302.5 With Limited Hearing |
Software: Supports Authored Content (HTML): Supports |
Software: Most functions of the product are usable with limited hearing. Exceptions include:
Authored Content (HTML): Authors can create content which is functional for users with limited hearing. |
|
302.6 Without Speech |
Software: Supports Authored Content (HTML): Supports |
Software: The product does not require the use of speech. Authored Content (HTML): Authors can create content which is functional for users without speech. |
|
302.7 With Limited Manipulation |
Software: Does Not Support Authored Content (HTML): Supports |
Software: Most functions of the product are not usable with limited manipulation. Examples include:
Authored Content (HTML): Authors can create content which is usable with limited manipulation by using the Classic template. However, most templates in the product do not allow authors to create content which meets this criterion. Examples include:
|
|
302.8 With Limited Reach and Strength |
Software: Supports Authored Content (HTML): Supports |
Software: The product is functional with limited reach and strength. Authored Content (HTML): 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 (HTML): Supports |
Software: 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 and contextual help. Exceptions include:
Authored Content (HTML): Authors can create content which is functional for users with limited language, cognitive, and learning abilities. |
Criteria |
Conformance Level |
Remarks and Explanations |
|
---|---|---|---|
501.1 Scope – Incorporation of WCAG 2.0 AA |
See WCAG 2.x section |
See information in WCAG 2.x section. |
|
502.2.1 User Control of Accessibility Features |
Not Applicable |
The product is not platform software. |
|
502.2.2 No Disruption of Accessibility Features |
Supports |
The product does not disrupt platform accessibility features. |
|
502.3.1 Object Information |
Does Not Support |
Most objects in the product do not expose accurate name, role, state, boundary, or description information to assistive technology. |
|
502.3.2 Modification of Object Information |
Partially Supports |
States and properties of controls and inputs in the product can be set by assistive technology, for those controls that can receive focus. |
|
502.3.3 Row, Column, and Headers |
Not Applicable |
The product does not use data tables. |
|
502.3.4 Values |
Partially Supports |
Most controls that can receive focus expose their values to assistive technology. |
|
502.3.5 Modification of Values |
Partially Supports |
Values of controls and inputs in the product can be set by assistive technology, for those controls that can receive focus. |
|
502.3.6 Label Relationships |
Does Not Support |
The product does not expose most label relationships to assistive technology. |
|
502.3.7 Hierarchical Relationships |
Does Not Support |
The product does not expose most hierarchical parent-child relationships to assistive technology. |
|
502.3.8 Text |
Supports |
The product exposes text content and text values to assistive technology. |
|
502.3.9 Modification of Text |
Partially Supports |
Text of controls and inputs in the product can be set by assistive technology, for those controls that can receive focus. |
|
502.3.10 List of Actions |
Does Not Support |
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 |
Supports |
The product allows assistive technology to perform actions on objects. |
|
502.3.12 Focus Cursor |
Supports |
The product exposes information to track focus, insertion point, and selection to assistive technology, for those controls that can receive focus. |
|
502.3.13 Modification of Focus Cursor |
Does Not Support |
The product does not allow assistive technology to move or modify focus, insertion point, and selection for most controls. |
|
502.3.14 Event Notification |
Partially Supports |
The product notifies assistive technology of some user interaction events. Exceptions include changes in state when content is expanded and changes in values of slider controls. |
|
502.4 Platform Accessibility Features |
Not Applicable |
The product is not platform software. |
|
503.2 User Preferences |
Supports |
The product adapts to platform settings for contrast and font size. |
|
503.3 Alternative User Interfaces |
Not Applicable |
The product does not provide an alternative user interface that functions as assistive technology. |
|
503.4.1 Caption Controls |
Does Not Support |
The product does not provide user controls for captions. |
|
503.4.2 Audio Description Controls |
Does Not Support |
The product does not provide user controls for audio descriptions. |
|
504.2 Content Creation or Editing |
See WCAG 2.x section |
See information in WCAG 2.x section. |
|
504.2.1 Preservation of Information Provided for Accessibility in Format Conversion |
Not Applicable |
Imported image files do not provide accessibility information for format conversion. |
|
|
Does Not Support |
The product exports PDF 1.7 files that do not conform to PDF/UA-1. |
|
504.3 Prompts |
Does Not Support |
Authoring functions do not prompt authors to create content which conforms to WCAG 2.0 Levels A and AA. |
|
504.4 Templates |
Does Not Support |
Templates in the product do not allow authors to create content which fully conforms to WCAG 2.1 Levels A and AA. Examples include:
|
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:
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
4.2.1 Usage without vision |
Software: Does Not support Authored Content (HTML): Partially Supports |
Software: Most functions of the product are not usable without vision. Examples include:
Authored Content (HTML): One of four templates in the product allow users to create content that is partially usable without vision. Examples include:
|
4.2.2 Usage with limited vision |
Software: Partially Supports Authored Content (HTML): Partially Supports |
Software: Most functions of the product are usable with limited vision. Exceptions include:
Authored Content (HTML): One of four templates in the product allow users to create content that is partially usable with limited vision. Examples include:
|
4.2.3 Usage without perception of colour |
Software: Partially Supports Authored Content (HTML): Supports |
Software: Most functions of the product are usable without perception of colour. Exceptions include:
Authored Content (HTML): Authors can create content which is functional for users without perception of color. |
4.2.4 Usage without hearing |
Software: Partially Supports Authored Content (HTML): Supports |
Software: Most functions of the product are usable without hearing. Exceptions include:
Authored Content (HTML): Authors can create content which is functional for users without hearing. |
4.2.5 Usage with limited hearing |
Software: Partially Supports Authored Content (HTML): Supports |
Software: Partially Supports Authored Content (HTML): Supports |
4.2.6 Usage without vocal capability |
Software: Partially Supports Authored Content (HTML): Supports |
Software: The product does not require the use of speech. Authored Content (HTML): 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 (HTML): Supports |
Software: Most functions of the product are not usable with limited manipulation or strength. Examples include:
Authored Content (HTML): Authors can create content which is usable with limited manipulation or strength by using the Classic template. However, most templates in the product do not allow authors to create content which meets this criterion. Examples include:
|
4.2.8 Usage with limited reach |
Software: Supports Authored Content (HTML): Supports |
Software: The product is functional with limited reach. Authored Content (HTML): Authors can create content which is functional with limited reach. |
4.2.9 Minimize photosensitive seizure triggers |
Software: Supports Authored Content (HTML): Supports |
Software: The product does not contain elements which flash or other features likely to trigger photosensitive seizures. Authored Content (HTML): 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 |
Software: Partially Supports Authored Content (HTML): Supports |
Software: 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 and contextual help. Exceptions include:
Authored Content (HTML): Authors can create content which is functional for users with limited language, cognitive, and learning abilities. |
4.2.11 Privacy |
Software: Supports Authored Content (HTML): Supports |
Software: The product does not ask for legal, financial, or personal data. Authored Content (HTML): Authors can create content which maintains user privacy when accessibility features are used. |
Chapter 5: Generic Requirements
Notes:
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
5.1 Closed Functionality |
Not Applicable |
5.1.2.2-5.1.6.2 are not applicable for this product, which has no closed functionality. |
5.2 Activation of accessibility features |
Supports |
Text size can be increased from within the product. |
5.3 Biometrics |
Not Applicable |
The product does not use biological characteristics for user identification or for control of the product. |
5.4 Preservation of accessibility information during conversion |
Not Applicable |
Imported image files do not provide accessibility information for conversion. |
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 |
Partially Supports |
The product has only non-mechanical operable parts, such as on-screen buttons and sliders. 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 |
The product does not have locking or toggle controls. |
5.6.2 Visual status |
Not Applicable |
The product does not have locking or toggle controls. |
5.7 Key repeat |
Not Applicable |
The product relies on platform software to turn off or adjust key repeat. |
5.8 Double-strike key acceptance |
Not Applicable |
The product does not provide 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. |
Chapter 6: ICT with Two-Way Voice Communication
Notes: Not Applicable
Chapter 7: ICT with Video Capabilities
Notes:
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
7.1.1 Captioning playback |
Does Not Support |
The product does not provide caption playback. |
7.1.2 Captioning synchronization |
Not Applicable |
The product does not display captions. |
7.1.3 Preservation of captioning |
Does Not Support |
Videos imported with captions do not retain their captions when exported. |
7.2.1 Audio description playback |
Does Not Support |
The product does not provide a mechanism to select and play available audio description tracks. |
7.2.2 Audio description synchronization |
Not Applicable |
The product does not have a mechanism to play an audio description. |
7.2.3 Preservation of audio description |
Does Not Support |
Videos imported with audio descriptions do not retain their audio descriptions when exported. |
7.3 User controls for captions and audio description |
Does Not Support |
The product does not provide user controls for captions or audio descriptions. |
Chapter 8: Hardware
Notes: Not Applicable
Chapter 9: Web (see WCAG 2.x section)
Notes:
Chapter 10: Non-web Documents
Notes: Not Applicable
Chapter 11: Software
Notes:
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
11.1.1.1 through 11.4.1.3 |
See WCAG 2.x section |
See information in WCAG 2.x section. |
11.5.2.4 Assistive technology |
Not Applicable |
This product is not assistive technology. |
11.5.2.5 Object information |
Does Not Support |
Most objects in the product do not expose accurate name, role, state, boundary, or description information to assistive technology. |
11.5.2.6 Row, column, and headers |
Not Applicable |
The product does not use data tables. |
11.5.2.7 Values |
Partially Supports |
Most controls expose their values to assistive technology, for those controls that can receive focus. |
11.5.2.8 Label relationships |
Does Not Support |
The product does not expose most label relationships to assistive technology. |
11.5.2.9 Parent-child relationships |
Does Not Support |
The product does not expose most hierarchical parent-child relationships to assistive technology. |
11.5.2.10 Text |
Supports |
The product exposes text content and text values to assistive technology. |
11.5.2.11 List of available actions |
Does Not Support |
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 |
Supports |
The product allows assistive technology to perform actions on objects. |
11.5.2.13 Tracking of focus and selection attributes |
Partially Supports |
The product exposes information to track focus, insertion point, and selection to assistive technology, for those controls that can receive focus. |
11.5.2.14 Modification of focus and selection attributes |
Does Not Support |
The product does not allow assistive technology to move or modify focus, insertion point, and selection for most controls. |
11.5.2.15 Change notification |
Partially Supports |
The product notifies assistive technology of some user interaction events. Exceptions include changes in state when content is expanded, changes in values of slider controls. |
11.5.2.16 Modifications of states and properties |
Partially Supports |
States and properties of controls and inputs in the product can be set by assistive technology, for those controls that can receive focus. |
11.5.2.17 Modifications of values and text |
Partially Supports |
Values and text of controls and inputs in the product can be set by assistive technology, for those controls that can receive focus. |
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 |
The product adapts to platform settings for color, contrast, and font size. |
11.8.2 Accessible content creation |
See WCAG 2.x section |
The product enables authors to create HTML content which partially conforms to WCAG 2.1 Levels A and AA. See details for individual criteria in the WCAG 2.x section. However, most authoring functions in the product do not actively guide authors to create accessible content. |
11.8.5 Templates |
Partially Supports |
Templates in the product allow authors to create content which partially conforms to WCAG 2.1 Levels A and AA. Examples include:
|
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
Voluntary Product Accessibility Template® and VPAT® are a registered trademark of Information Technology Industry Council (ITI)