Adobe Firefly
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
- 9
- Partially supports
- 10
- Does not support
- 4
- Not applicable
- 7
- Not evaluated
- 0
Level AA — 20 criteria
- Supports
- 4
- Partially supports
- 10
- Does not support
- 0
- Not applicable
- 6
- 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 (71)
| Criterion | Name | Level | Conformance | Remarks from vendor |
|---|---|---|---|---|
| 1.1.1 | Non-text Content | A | Does Not Support | Web: Some images in the product have meaningful descriptions. However, the product does not provide sufficient text alternatives for most images, such as: Text to image generated content and related editing tools such as reference images. Generative fill functions including image edited, sample images and generated content. Other image content including community images. |
| 1.2.1 | Audio-only and Video-only (Prerecorded) | A | Does Not Support | Web: The product does not contain audio-only media. However, the product contains video-only media and does not provide audio description or transcripts, such as: Video-only animations on cards do not provide transcripts or audio descriptions. Video-only animations on some cards only provide partial transcripts. |
| 1.2.2 | Captions (Prerecorded) | A | Not Applicable | Web: The product does not contain prerecorded synchronized media. |
| 1.2.3 | Audio Description or Media Alternative (Prerecorded) | A | Not Applicable | Web: The product does not contain prerecorded synchronized media that would require audio description or a media alternative. |
| 1.2.4 | Captions (Live) | AA | Not Applicable | Web: The product does not contain live synchronized media. |
| 1.2.5 | Audio Description (Prerecorded) | AA | Not Applicable | Web: The product does not contain prerecorded synchronized media that would require audio description. |
| 1.3.1 | Info and Relationships | A | Partially Supports | Web: Most visual structure and relationship information, such as form controls, landmarks, headings and lists is provided through element semantics, object information or in text. Exceptions include: Some headings do not use semantic heading elements, use heading elements when they should not, or the heading levels used do not fit within the page heading hierarchy. Some content such as tooltips cannot be reached using assistive technologies such as screen readers. Landmarks are used incorrectly Labels are not associated with form controls or group names with their group of form controls. Disab |
| 1.3.2 | Meaningful Sequence | A | Supports | Web: The product presents most content in a meaningful sequence. |
| 1.3.3 | Sensory Characteristics | A | Supports | Web: Instructions do not rely solely on sensory characteristics. |
| 1.3.4 | Orientation | AA | Partially Supports | Web: Content does not restrict its view and operation to a single display orientation on desktop devices. However, on mobile devices, the product restricts its view to portrait orientation. |
| 1.3.5 | Identify Input Purpose | AA | Not Applicable | Web: The product does not contain input fields that collect information about the user. |
| 1.4.1 | Use of Color | A | Supports | Web: The product does not convey information through color alone. |
| 1.4.2 | Audio Control | A | Not Applicable | Web: The product does not contain audio that plays automatically. |
| 1.4.3 | Contrast (Minimum) | AA | Partially Supports | Web: Most text meets minimum contrast requirements. Exceptions include: Try Generative Fill in Photoshop banner link. Saved to favorites toast button in focus or hover state. Some text on the Home page community cards when navigated to behind the fade out overlay. |
| 1.4.4 | Resize text | AA | Partially Supports | Web: Most of the product allows browser zoom to resize text up to 200 percent without loss of content or functionality. Exceptions include: On the home page, the 'Try Generative Fill in Photoshop' banner is missing when the browser is zoomed to 200%. |
| 1.4.5 | Images of Text | AA | Supports | Web: The product uses text instead of images of text, except for branding elements that are considered essential. |
| 1.4.10 | Reflow | AA | Partially Supports | Web: At the required width of 320 CSS pixels, most content is presented without loss of information or functionality, and without requiring scrolling in two dimensions. Exceptions include: On some pages content or functionality is cut off or overruns causing it to be difficult or impossible to read or interact with. The 'Try Generative Fill in Photoshop' banner is missing on pages that have this banner. On the style kits the ‘No mobile support’ message is triggered and no content can be viewed. |
| 1.4.11 | Non-text Contrast | AA | Partially Supports | Web: Most meaningful non-text content elements, such as form controls, states or icons, have sufficient contrast. Exceptions include: Selected states for menu controls. Focus indicators for buttons against inconsistent backgrounds (such as image card backgrounds). Focus indicators for some buttons. Prompt text input fields. Some form controls including drop-down boxes. |
| 1.4.12 | Text Spacing | AA | Partially Supports | Web: Most functions of the product support the required text style properties without loss of content or functionality. Exceptions include: In the text to image editor, the effect labels become truncated. |
| 1.4.13 | Content on Hover or Focus | AA | Partially Supports | Web: Exceptions include: Some tooltip contents are not persistent on touch devices. Tooltip content appears on hover and requires moving the mouse to dismiss it. |
| 2.1.1 | Keyboard | A | Does Not Support | Web: Most product functionality cannot be operated through a keyboard interface. Exceptions include: Functions within the Generative Fill editor including, panning, zooming, moving expansion area and painting/brush. Some tooltip content does not display using the keyboard. Functions within the text to image editor including effect options, links and buttons. Card animations on the home page only display on mouse hover. Focus is not managed for some modal dialogs or toast messages. Focus is not managed for some menus including in the header or text to image editor controls. |
| 2.1.2 | No Keyboard Trap | A | Partially Supports | Web: Most of the product does not include keyboard traps. Exceptions include: Using mobile screen reader software, the feedback menu causes a keyboard trap. |
| 2.1.4 | Character Key Shortcuts | A | Not Applicable | Web: The product does not provide character key shortcuts. |
| 2.2.1 | Timing Adjustable | A | Partially Supports | Web: Most of the product does not include time limits. Exceptions include: Saved to favorites toast message disappears without user action after ~6 seconds. |
| 2.2.2 | Pause, Stop, Hide | A | Partially Supports | Web: Most of the product does not include elements which move, blink, scroll, or auto-update. Exceptions include: Within the Text to Image editor, the button blinks. The homepage animations play automatically without user input on mobile. There are no controls to pause or stop animations on the homepage including the image slideshow and animating placeholder text. |
| 2.3.1 | Three Flashes or Below Threshold | A | Not Applicable | Web: The product does not contain flashing content. |
| 2.4.1 | Bypass Blocks | A | Partially Supports | Web: The product provides heading markup, which allows assistive technology users to bypass repeated blocks such as the main header. However, for users without assistive technology, a bypass mechanism is not provided. |
| 2.4.2 | Page Titled | A | Partially Supports | Web: Exceptions include: The product displays a page title however it is the same for every page and does not describe the page purpose. |
| 2.4.3 | Focus Order | A | Partially Supports | Web: Most components receive focus in a meaningful order. Exceptions include: The generative fill prompt field receives focus when hidden. View favorites toast button receives focus twice. Homepage hero slideshow images are available when visually hidden. |
| 2.4.4 | Link Purpose (In Context) | A | Supports | Web: The purpose of links in the product can be determined from the link text alone or from the programmatic context of the link. |
| 2.4.5 | Multiple Ways | AA | Supports | Web : Users can locate web pages in the product through the home page, where processes/tasks are started. |
| 2.4.6 | Headings and Labels | AA | Partially Supports | Web: Most headings and labels are descriptive. Exceptions include: Some buttons or form fields do not have a meaningful label. |
| 2.4.7 | Focus Visible | AA | Partially Supports | Web: Most focusable elements have a visible keyboard focus indicator. Exceptions include: The homepage prompt field The image canvas within the Generative fill editor. |
| 2.5.1 | Pointer Gestures | A | Supports | Web: Path based gestures have a single pointer alternative. |
| 2.5.2 | Pointer Cancellation | A | Partially Supports | Web: Most product functions that use a single pointer are completed when the user releases the pointer. Exceptions include: The brush/painting selection feature within the Generative fill editor. |
| 2.5.3 | Label in Name | A | Partially Supports | Web: In most product functions, accessible names of controls contain the text of their visible labels. Exceptions include: Some buttons and links have different accessible names from their visible labels. |
| 2.5.4 | Motion Actuation | A | Not Applicable | Web: The product does not have functionality operated by device motion or user motion. |
| 3.1.1 | Language of Page | A | Supports | Web: The language is programmatically determinable within the product. |
| 3.1.2 | Language of Parts | AA | Not Applicable | Web: Content is only presented in one language at a time. |
| 3.2.1 | On Focus | A | Supports | Web: Components do not initiate a change of context when focused. |
| 3.2.2 | On Input | A | Supports | Web: Changes of context do not occur automatically on user input. |
| 3.2.3 | Consistent Navigation | AA | Supports | Web: When navigational mechanisms are repeated in the product they occur in a consistent relative order. |
| 3.2.4 | Consistent Identification | AA | Supports | Web: Components with the same functionality are identified consistently. |
| 3.3.1 | Error Identification | A | Not Applicable | Web: The product does not detect input errors. |
| 3.3.2 | Labels or Instructions | A | Partially Supports | Web: Labels are provided for most input fields. Exceptions include: The Save style kit modal has fields that use placeholder text for their visible label. |
| 3.3.3 | Error Suggestion | AA | Not Applicable | Web: The product does not detect input errors that are displayed to users. |
| 3.3.4 | Error Prevention (Legal, Financial, Data) | AA | Not Applicable | Web: The product does not process legal commitments or financial transactions and does not modify user-controllable data. |
| 4.1.1 | Parsing | A | Supports | Web: This criterion has been removed from WCAG 2.2. In WCAG 2.1 and 2.0 this Success Criterion should be considered as always satisfied for any content using HTML or XML. |
| 4.1.2 | Name, Role, Value | A | Does Not Support | Web: User interface components in most product functions do not provide programmatic name, role, state and value information. Examples include: Some controls do not have an accessible name. Some controls do not have the required state or have an incorrectly used state. Some controls do not have the required roles |
| 4.1.3 | Status Messages | AA | Partially Supports | Web: When status messages are visible, the product provides the update to assistive technology as live regions. However, there are some exceptions. Examples include: When images are generating. When the image background selection is loading. |
| 4.2.1 | Usage without vision | - | Does Not Support | Web: Most functions of the product are not usable without vision. Examples include: As noted in 1.1.1 Non-text Content , some meaningful images do not have text alternatives or text alternatives are not meaningful. As noted in 1.2.1 Audio-only and Video-only (Prerecorded) , video-only media does not have transcripts or audio description. As noted in 1.3.1 Information and Relationships , some information provided visually is not available through markup or text. As noted in 2.1.1 Keyboard , some interactive elements are not operable using a keyboard including, focus management, generative fill |
| 4.2.2 | Usage with limited vision | - | Partially Supports | Web: Most of the functions of the product are usable with limited vision. Exceptions include: As noted in 1.4.3 Contrast (minimum) , some text does not meet color contrast requirements. As noted in 1.4.4 Resize Text , some content is cut off or overruns the viewport/other text or is missing. As noted in 1.4.10 Reflow , some content is missing, cut off or overruns causing it to be difficult to read. The style kits page is not supported at all at this resolution. As noted in 1.4.11 Non-text Contrast , some user interface components such as form fields, selected states or focus styles do not meet |
| 4.2.3 | Usage without perception of colour | - | Partially Supports | Web: Most of the functions of the product are usable without perception of color. Exceptions include: As noted in 1.4.3 Contrast (minimum) , some text does not meet color contrast requirements. As noted in 1.4.11 Non-text Contrast , some user interface components such as form fields, selected states or focus styles do not meet the color contrast |
| 4.2.4 | Usage without hearing | - | Not Applicable | Web: The product does not require the use of hearing. |
| 4.2.5 | Usage with limited hearing | - | Not Applicable | Web: The product does not require the use of hearing. |
| 4.2.6 | Usage without vocal capability | - | Not Applicable | Web: The product does not require the use of speech. |
| 4.2.7 | Usage with limited manipulation or strength | - | Does Not Support | Web: Most of the functions of the product are not usable with limited manipulation and strength. Examples include: As noted in 2.1.1 Keyboard , some interactive elements are not operable using a keyboard including, focus management, generative fill editor functionality, editor menu controls and tooltips. As noted in 2.4.1 Bypass Blocks , pages do not have skip links. As noted in 2.4.3 Focus Order , some visually hidden user interface components receive focus using the tab key. As noted in 2.4.7 Focus Visible , some interactive elements do not display a visible focus indicator. As noted in 2.5. |
| 4.2.8 | Usage with limited reach | - | Supports | Web: The functions of the product are usable with limited reach. |
| 4.2.9 | Minimize photosensitive seizure triggers | - | Not Applicable | Web: The product does not contain flashing content. |
| 4.2.10 | Usage with limited cognition, language or learning | - | Partially Supports | Web: Most of the functions of the product are usable with limited language, cognitive and learning abilities. Exceptions include: As noted in 2.2.1 Timing Adjustable , toast messages disappear quickly. As noted in 2.2.2 Pause, Stop, Hide , some animations cannot be paused, stopped or hidden. As noted in 2.4.2 Page Titled , page tiles are not descriptive. As noted in 3.3.2 Labels or Instructions , some form fields do not have a permanently visible label. As noted in 1.4.12 Text Spacing , some functions do not fully support increased text spacing. As noted in 2.4.6 Headings and Labels , some for |
| 4.2.11 | Privacy | - | Not Applicable | Web: The product does not ask for or display legal, financial, or personal data . |
| 5.1.4 | Functionality closed to text enlargement | - | Not Applicable | |
| 5.1.5 | Visual output for auditory information | - | Not Applicable | |
| 5.1.7 | Access without speech | - | Not Applicable | |
| 5.5.1 | Means of operation | - | Not Applicable | |
| 5.5.2 | Operable parts discernibility | - | Not Applicable | |
| 5.6.1 | Tactile or auditory status | - | Not Applicable | |
| 5.6.2 | Visual status | - | Not Applicable | |
| 12.1.1 | Accessibility and compatibility features | - | Not Evaluated | |
| 12.2.2 | Information on accessibility and compatibility features | - | Not Evaluated | |
| 12.2.3 | Effective communication | - | Not Evaluated |
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 September 2024. 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.