Lightroom Classic (Windows)
Accessibility Conformance Report published by Adobe
Partial extraction. We read 30 of 31 Level A and 20 of 24 Level AA criteria from this document (91% coverage). The remainder are missing from our extraction, not necessarily from Adobe's report — their table layout defeated our parser. Treat the figures below as incomplete and read the source document for the full picture.
Conformance by level
Reported by the vendor. WCAG Level AA is the benchmark referenced by ADA Title II, Section 508 and the European Accessibility Act; Level AAA is optional and often left unevaluated.
Level A — 30 criteria
- Supports
- 20
- Partially supports
- 5
- Does not support
- 5
- Not applicable
- 0
- Not evaluated
- 0
Level AA — 20 criteria
- Supports
- 16
- Partially supports
- 3
- Does not support
- 1
- Not applicable
- 0
- Not evaluated
- 0
Source: View the original report published by Adobe.
These figures are extracted from that document. They are the vendor's own statements, not an independent assessment, and automated extraction can misread a table.
All reported criteria (96)
| Criterion | Name | Level | Conformance | Remarks from vendor |
|---|---|---|---|---|
| 1.1.1 | Non-text Content | A | Does Not Support | 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. |
| 1.2.1 | Audio-only and Video-only (Prerecorded) | A | Supports | Software: The product does not contain prerecorded audio-only or video-only content. Authored Content (HTML): Authored content does not contain prerecorded audio-only or video-only media. |
| 1.2.2 | Captions (Prerecorded) | A | 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) | A | 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) | AA | 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) | AA | 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. |
| 1.3.1 | Info and Relationships | A | Supports | Software: Structure and relationship information is provided. Authored Content (HTML): Authors can provide appropriate semantics for most visual structure and relationship information. Exceptions include: Implicit headings in most templates. In the Classic template, there is a heading level that does not match its visual importance. |
| 1.3.2 | Meaningful Sequence | A | Supports | Software: Where the content of the product is exposed to assistive technology, the content is presented in a meaningful sequence. Examples include: A meaningful sequence can be determined within the main menu Authored Content (HTML): The product allows authors to present content in a meaningful sequence. |
| 1.3.3 | Sensory Characteristics | A | 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 | AA | 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 | AA | 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. |
| 1.4.1 | Use of Color | A | Partially Supports | Software: Most functions of the product do not convey information through color alone. Exceptions include: Currently selected module in module picker Map pins. Authored Content (HTML): Authors can ensure that content meets this criterion. |
| 1.4.2 | Audio Control | A | 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) | AA | Partially Supports | Software: Most text meets minimum contrast requirements. Exceptions include: Gray text used for some labels and unselected options. Red text used for errors or warnings. Orange text used for notifications. Authored Content (HTML): Authors can ensure that content meets this criterion. |
| 1.4.4 | Resize text | AA | 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 | AA | 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 | AA | Partially Supports | Software: 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. When text is increased to the maximum size allowed by the product, some loss of content and functionality occurs. Examples include: Filters in Filmstrip are obscured. Text in the Book module overlaps other content. 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 | AA | Partially Supports | Software: Some active user interface controls do not meet minimum contrast requirements. Examples include: Some icon buttons. Checkboxes. 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 | AA | 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 | AA | Does Not Support | Software: In most product functions, content that becomes visible on hover is hidden in a manner which does not meet this criterion. Examples include: Contextual help popovers and plain text tooltips that cannot be moved over with a pointer. Authored Content (HTML): Authors can ensure that content meets this criterion. |
| 2.1.1 | Keyboard | A | Does Not Support | 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 the keyboard alone and most controls do not receive keyboard focus. Examples include: Folders and files in the Source panel cannot be navigated or activated with keyboard. Some dialogs cannot be dismissed with keyboard. Slider editing controls can be used with a keyboard only after being clicked or hovered with a mouse. The keyboard cannot be used to se |
| 2.1.2 | No Keyboard Trap | A | Partially Supports | Software : Most content that receives keyboard focus within the product does not contain a keyboard trap. Exceptions include: Some dialogs cannot be dismissed with the keyboard and the user is unable to perform other keyboard actions. Authored Content (HTML): Authored content does not include keyboard traps. |
| 2.1.4 | Character Key Shortcuts | A | Does Not Support | Software: The product provides unmodified character key shortcuts and does not provide a mechanism to disable or remap these shortcuts. Authored Content (HTML): Authored content does not provide character key shortcuts. |
| 2.2.1 | Timing Adjustable | A | 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 | A | 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. |
| 2.3.1 | Three Flashes or Below Threshold | A | Supports | Software: The product does not contain flashing content. Authored Content (HTML): Authors can ensure that content does not flash. |
| 2.4.1 | Bypass Blocks | A | 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 | A | Does Not Support | 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 | A | 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) | A | Supports | Software: The purpose of link text 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: Content generated with the Classic template contains multiple links with identical textual content but different destinations. |
| 2.4.5 | Multiple Ways | AA | 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 | AA | Supports | Software: Software: Headings and labels are descriptive. Authored Content (HTML): Authors can ensure that content meets this criterion. |
| 2.4.7 | Focus Visible | AA | 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. |
| 2.5.1 | Pointer Gestures | A | 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 | A | Partially Supports | Software: Some product functions that use a single pointer are completed before the user releases the pointer. Examples include: Elements in the Module selector. Buttons to activate color picker popovers. Buttons in the Attributes filters. Authored Content (HTML): Authors can ensure that content meets this criterion. |
| 2.5.3 | Label in Name | A | Partially Supports | Software: In some product functions, accessible names of controls do not contain the text of their visible labels or include the text of the visible label with other words and special characters interspersed. For most of these controls, the accessible name is “(Bridge View)”. Examples include: Module picker. Photos in Filmstrip. Authored Content (HTML): For most authored content, accessible names of controls do not contain the text of their visible labels. Examples include: Visible numbers for linked gallery items in the Classic template are not represented in the accessible names of the links |
| 2.5.4 | Motion Actuation | A | 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. |
| 3.1.1 | Language of Page | A | Partially Supports | Software: The product is available in 12 languages. Most users configure software to match their operating system language. However, the product does not automatically follow the operating system language setting to render its user interface, and the product does not identify its language to assistive technology. Authored Content (HTML): The product does not allow authors to set the language of the page. |
| 3.1.2 | Language of Parts | AA | Supports | 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. |
| 3.2.1 | On Focus | A | 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 | A | 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 | AA | 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 | AA | 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. |
| 3.3.1 | Error Identification | A | 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 | A | 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 | AA | 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) | AA | 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. |
| 4.1.1 | Parsing | A | 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 | A | Does Not Support | Software: User interface components in most product functions do not provide programmatic name, role, value, or state information. Examples include: Most text values are not exposed to assistive technology. Icon buttons with rollover textual labels lack programmatically associated text. Editable text inputs, such as metadata fields, lack programmatic labels. Buttons in Filmstrip lack programmatic names or have name of “(Bridge View)”. The selected state of images is not conveyed programmatically. Modules in Module picker and photos in Filmstrip have a role of “pane”. Authored Content (HTML) : |
| 4.1.3 | Status Messages | AA | Supports | Software: This criterion does not apply to non-web software. Authored Content (HTML): Authored content does not include status messages. |
| 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 expose their values to assistive technology, for those controls that can receive focus. |
| 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 | - | Partially 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, changes in values of slider controls. |
| 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.1 | Preservation of Information Provided for Accessibility in Format Conversion | - | Not Applicable | Imported image files do not provide accessibility information for format conversion. |
| 504.2.2 | PDF Export | - | Does Not Support | The product exports PDF 1.7 files that do not conform to PDF/UA-1. |
| 4.2.1 | Usage without vision | - | 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 , most non-text controls provide no textual alternative for use by screen readers. As noted in 2.1.1 Keyboard , most actions cannot be performed using the keyboard alone. As noted in 2.1.2 No Keyboard Trap , some dialogs cause a keyboard trap. As noted in 4.1.2 Name, Role, Value , most controls do not provide useful name and role value. As noted in 7.2.1 Audio description playback , the product does not provide a mechanism to select and play available audio description tr |
| 4.2.2 | Usage with limited vision | - | Partially Supports | Software: Most functions of the product are usable with limited vision. Exceptions include: As noted in 1.4.3 Contrast (Minimum) , most elements in the product provide sufficient contrast, but some elements such as certain labels, errors, and notifications do not meet the minimum requirement. As noted in 1.4.10 Reflow , text size cannot be increased to 400%, but at the maximum text size some loss of content and functionality occurs. As noted in 1.4.11 Non-text Contrast , most non-text elements provide adequate color contrast, but some controls such as checkboxes do not meet the minimum contras |
| 4.2.3 | Usage without perception of colour | - | Partially Supports | Software: Most functions of the product are usable without perception of colour. Exceptions include: As noted in 1.4.1 Use of Color , colour alone is used to communicate some information. Authored Content (HTML): Authors can create content which is functional for users without perception of color. |
| 4.2.4 | Usage without hearing | - | Partially Supports | Software: Most functions of the product are usable without hearing. Exceptions include: As noted in 7.1.1 Captioning playback and 7.3 User controls for captions and audio description , the product does not provide caption playback functionality. Authored Content (HTML): Authors can create content which is functional for users without hearing. |
| 4.2.5 | Usage with limited hearing | - | Partially Supports | Software: Most functions of the product are usable with limited hearing. Exceptions include: As noted in 7.1.1 Captioning playback and 7.3 User controls for captions and audio description , the product does not provide caption playback functionality. Authored Content (HTML): Authors can create content which is functional for users with limited hearing. |
| 4.2.6 | Usage without vocal capability | - | 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 | - | Does Not Support | Software: Most functions of the product are not usable with limited manipulation or strength. Examples include: As noted in 1.4.13 Content on Hover or Focus , most content that becomes visible on hover cannot be moved over with a pointer. As noted in 2.1.1 Keyboard , although the main menu and keyboard shortcuts provide access to some content and functionality, most actions cannot be performed using keyboard alone. As noted in 2.1.2 No Keyboard Trap , some dialogs cause a keyboard trap. As noted in 2.1.4 Character Key Shortcuts , no mechanism is provided to disable or remap single character ke |
| 4.2.8 | Usage with limited reach | - | 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 | - | 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 | - | Partially 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: As noted in 2.4.2 Page Titled , the visible page title is not announced correctly by assistive technology. As noted in 2.5.3 Label in Name , many controls do not have accessible names that contain the text of their visible labels. Au |
| 4.2.11 | Privacy | - | 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. |
| 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. Some 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 contain locking or toggle controls. |
| 5.6.2 | Visual status | - | Not Applicable | The product does not contain locking or toggle controls. |
| 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 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. |
| 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.8.3 | Preservation of accessibility information in transformations | - | Not Applicable | Imported image files do not provide accessibility information for format conversion. |
| 11.8.4 | Repair assistance | - | Not Applicable | The product does not have accessibility checking functionality. |
| 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: As noted in 1.1.1 Non-text Content , 1.3.1 Info and Relationships , 2.1.1 Keyboard , 2.4.1 Bypass Blocks , 2.4.4 Link Purpose (In Context) , 2.5.3 Label in Name , 3.1.1 Language of Page , and 3.1.2 Language of Parts , Grid, Track, and Square templates do not allow authors to create WCAG conformant HTML content; Classic template allows authors to create partially WCAG conformant HTML content. |
Is this your product? If this report is out of date or misrepresented, we will correct or remove it. Contact us to claim this listing.
Get told when this changes
This report is dated August 2023. An ACR can be quietly replaced at any time, and the published date is the only signal a buyer gets. We will email you when this one is updated.
Double opt-in — we email you once to confirm, and send nothing until you do. One-click unsubscribe on every message. We store your address and what you are watching, nothing else. Privacy.