Adobe Acrobat Pro
Accessibility Conformance Report published by Adobe
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 — 32 criteria
- Supports
- 8
- Partially supports
- 10
- Does not support
- 3
- Not applicable
- 11
- Not evaluated
- 0
Level AA — 24 criteria
- Supports
- 4
- Partially supports
- 5
- Does not support
- 5
- Not applicable
- 10
- 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 (99)
| Criterion | Name | Level | Conformance | Remarks from vendor |
|---|---|---|---|---|
| 1.1.1 | Non-text Content | A | Partially Supports | Software: The product provides sufficient text alternatives for most instances of non-text content. Exceptions include: Some informative images do not have a text alternative, so people who are blind and/or user a screen reader will not be able to access the information conveyed by the image. This occurs on the following pages: Protect a PDF - Manage security policies; Prepare for Accessibility - Properties; View PDF - Read. Some images that act as a link or control do not have a text alternative, so people who are blind and/or use a screen reader will not understand the function performed by |
| 1.2.1 | Audio-only and Video-only (Prerecorded) | A | Not Applicable | Software: The product does not contain prerecorded audio-only or video-only media. |
| 1.2.2 | Captions (Prerecorded) | A | Not Applicable | Software: The product does not contain prerecorded synchronized media. |
| 1.2.3 | Audio Description or Media Alternative (Prerecorded) | A | Not Applicable | Software: The product does not contain prerecorded video content that would require audio description or a media alternative. |
| 1.3.1 | Info and Relationships | A | Partially Supports | Software: Most visual structure and relationship information is provided through semantics. Exceptions include: Content is arranged visually like a data table, but it is not programmatically marked up as a table, so the table's structure and relationships are not conveyed to people who are blind and/or use a screen reader. This occurs on the following pages: Protect a PDF - Create a Security Envelope; View PDF - Attachments; Protect a PDF - Encrypt with certificate - Select Recipients; Protect a PDF - Manage security policies; Prepare Form - General Properties; Protect a PDF - Set security pro |
| 1.3.2 | Meaningful Sequence | A | Does Not Support | Software: The product does not present most content in a meaningful sequence. Exceptions include: The screen reader skips and does not announce informative static content (text or images), so the intended meaning of that content will be lost or changed for people who are blind and/or use a screen reader. This occurs on the following pages: Combine Files / Organize during Combine; Enhance Scan; Protect a PDF - Create a Security Envelope; Prepare for Accessibility; Create PDF; Comment on PDF; View PDF - Attachments; Use guided actions - Publish Sensitive Information; Use guided actions; Protect |
| 1.3.3 | Sensory Characteristics | A | Supports | Software: Instructions do not rely solely on sensory characteristics. |
| 1.4.1 | Use of Color | A | Partially Supports | Software: Most functions of the product do not convey information through color alone. Exceptions include: Color is used as the only method to convey information, so that information will not be available to people who are colorblind and people who are blind and/or use a screen reader. This occurs on the following pages: Quick Tools in Document; and the component Color palette, which appears on multiple pages. Color is used as the only method to convey the state (such as "checked," "pressed," or "selected") of a control, so that information will not be available to people who are colorblind an |
| 1.4.2 | Audio Control | A | Not Applicable | Software: The product does not contain audio that plays automatically. |
| 2.1.1 | Keyboard | A | Does Not Support | Software: Most product functionality cannot be operated through a keyboard interface. Examples include: A function cannot be performed using only the keyboard, so people who use the keyboard alone to navigate and operate content cannot use this function. This occurs on the following pages: Combine Files / Organize during Combine; Enhance Scan; Protect a PDF - Create a Security Envelope; Prepare for Accessibility; Comment on PDF; View PDF - Attachments; Use guided actions - Publish Sensitive Information; Use guided actions; Protect a PDF; Protect a PDF - Remove hidden information; AI Assistant; |
| 2.1.2 | No Keyboard Trap | A | Supports | Software: The product does not include keyboard traps. |
| 2.1.4 | Character Key Shortcuts | A | Supports | Software: The product provides character key shortcuts. Users can disable or remap the shortcuts to non-printable keys. |
| 2.2.1 | Timing Adjustable | A | Not Applicable | Software: The product does not include time limits. |
| 2.2.2 | Pause, Stop, Hide | A | Not Applicable | Software: The product does not include elements which move, blink, scroll, or auto-update. |
| 2.3.1 | Three Flashes or Below Threshold | A | Not Applicable | Software: The product does not contain flashing content. |
| 2.4.1 | Bypass Blocks | A | Not Applicable | Software: This criterion does not apply to non-web software. |
| 2.4.2 | Page Titled | A | Supports | Software: The title of the software describes its purpose. |
| 2.4.3 | Focus Order | A | Partially Supports | Software: Most components receive focus in a meaningful order. Exceptions include: Keyboard focus or touch screen swiping goes to an element that is hidden or empty, so people who use the keyboard to navigate content (including screen reader users) may become disoriented or confused. This occurs on the following pages: Comment on PDF; Redact a PDF - Sanitize Document; Redact a PDF - Find Text and Redact. The focus order is not logical and presents content in an order that misrepresents its meaning or operability, so people who use a keyboard, switch control, or other assistive technology to na |
| 2.4.4 | Link Purpose (In Context) | A | Partially Supports | Software: The purpose of most links can be determined from the link text alone or from the link text and its programmatic context. Exceptions include: The purpose of the link is not made clear by its text or the context provided by the content that immediately surrounds it, so people who are blind and/or use a screen reader will not know where the link goes. This occurs on the following page: Edit PDF. |
| 2.5.1 | Pointer Gestures | A | Not Applicable | Software: The product does not rely on multipoint or path-based gestures. |
| 2.5.2 | Pointer Cancellation | A | Supports | Software: Product functions that use a single pointer are completed when the user releases the pointer and allow the user to cancel the pointer action before completing the pointer click. |
| 2.5.3 | Label in Name | A | Partially Supports | Software: In most product functions, accessible names of controls contain the text of their visible labels. Exceptions include: The accessible name of an interactive element (such as a link, button, or form input) does not contain the visible label, so people who use speech input to navigate and operate content will not be able to access the element. This occurs on the following pages: Combine Files / Organize during Combine; Enhance Scan; Protect a PDF - Create a Security Envelope; Prepare for Accessibility; Comment on PDF; Protect a PDF; Prepare Form - Image field properties; Prepare Form - |
| 2.5.4 | Motion Actuation | A | Not Applicable | Software: The product does not have functionality operated by device motion or user motion. |
| 3.1.1 | Language of Page | A | Supports | Software: The language is programmatically determinable within the product. |
| 3.2.1 | On Focus | A | Partially Supports | Software: In most product functions, components do not initiate a change of context when focused. Exception includes: When an element receives keyboard focus, it results in a substantial, unanticipated context change (such as a change in the page content that changes the meaning of the page), so people who use a keyboard to navigate content (including screen reader users) may become confused or disoriented. This occurs on the following page: Acrobat Home. |
| 3.2.2 | On Input | A | Partially Supports | Software: In most cases, when a user inputs information or interacts with a control, it does not result in a substantial change to the page that could disorient the user, or the user is informed about the change ahead of time. Exceptions include: When a user changes the setting of a user interface control (such as entering text in an input field or selecting a checkbox or radio button), it results in an unanticipated context change (such as opening a new window, moving focus to another element, or submitting a form), so people who have cognitive disabilities and others may be confused or disor |
| 3.2.6 | Consistent Help | A | Supports | Software: On web pages that contain help features (including human or automated contact options or self-help options), those features occur in the same order relative to other page content unless the user changes that order. |
| 3.3.1 | Error Identification | A | Partially Supports | Software: Most input errors are identified and described to the users in text. Exception includes: An error for a form input (such as a text input field, radio button, select dropdown, or checkbox) is not identified with a text error message or a text alternative for an image, so people who are blind and/or use a screen reader will not be made aware that an error has occurred. This occurs on the following page: Adobe Sign / Send for Signatures. |
| 3.3.2 | Labels or Instructions | A | Partially Supports | Software: Labels are provided for most input fields. Exceptions include: The label of an element is not persistent (always visible on the page), so the element's purpose may be difficult to discover. This occurs on the following pages: Comment on PDF; Use a Certificate - Digitally Sign; Use a Certificate: Certify (invisible signature); Use a Certificate - Certify (visible signatures). The label for a form field is missing, so the field's purpose is not clear. This occurs on the following pages: Protect a PDF - Create a Security Envelope; Compress a PDF - Advanced Optimization; Prepare Form - D |
| 3.3.7 | Redundant Entry | A | Supports | Software: No processes on the site require the user to enter information previously entered as part of the same process. |
| 4.1.1 | Parsing | A | Not Applicable | Software: The product is not implemented using markup languages. |
| 4.1.2 | Name, Role, Value | A | Does Not Support | Software: User interface components in most product functions do not provide programmatic name, role, state, or value information. Examples include: A custom checkbox element does not have a programmatic role and/or its current state (checked or not checked) is not conveyed programmatically, so people who are blind and/or use a screen reader or other assistive technology will not be aware that the element is a checkbox or if the checkbox is checked. This occurs on the following pages: Protect a PDF - Remove hidden information; View PDF - Thumbnails. An element that appears and functions like a |
| 1.2.4 | Captions (Live) | AA | Not Applicable | Software: The product does not contain live synchronized media. |
| 1.2.5 | Audio Description (Prerecorded) | AA | Not Applicable | Software: The product does not contain prerecorded video content that would require audio description. |
| 1.3.4 | Orientation | AA | Supports | Software: Content does not restrict its view and operation to a single display orientation. |
| 1.3.5 | Identify Input Purpose | AA | Not Applicable | Software: The product’s technology does not have support for programmatic identification of input purpose. |
| 1.4.3 | Contrast (Minimum) | AA | Does Not Support | Software: Most text meets minimum contrast requirements. Exceptions include: The color contrast ratio between placeholder text in an input and the input's background is less than 4.5:1, so people who are colorblind or have low vision may have difficulty reading the placeholder text. This occurs on the following pages: AI Assistant; Acrobat Tools pane; Use a Certificate - Digitally Sign; Use a Certificate: Certify (invisible signature); Use a Certificate - Certify (visible signatures). The color contrast ratio between text and its background is less than 4.5:1, so people who are colorblind or h |
| 1.4.4 | Resize text | AA | Does Not Support | Software: The product does not provide its own text resizing function. When text is resized using operating system display scaling content and functionality is lost in most product functions. Examples include: Content is lost, clipped, or obscured when the page is zoomed to 200%, so people who have low vision and need to enlarge text to read it may not have access to that content. This occurs on the following pages: Protect a PDF - Remove hidden information; AI Assistant; Protect a PDF - Protect with a Password & Remove Security; Adobe Sign / Send for Signatures; Use guided actions - Actions; |
| 1.4.5 | Images of Text | AA | Supports | Software: The product uses text instead of images of text. |
| 1.4.10 | Reflow | AA | Does Not Support | Software: At the required width of 320 CSS pixels, most functions of the product do not meet this criterion. Loss of information or functionality occurs. Examples include: When the page is adjusted to an equivalent width of 320 pixels and content reflows to fit within the viewport, some content or functionality becomes unavailable, so people with low vision who increase the size of text and other content using the browser zoom will not be able to access all of the page's content and/or functionality. This occurs on the following pages: Acrobat Home; Acrobat Tools pane; Add a stamp; Adobe Sign |
| 1.4.11 | Non-text Contrast | AA | Partially Supports | Software: Most meaningful non-text content elements have sufficient contrast. Exceptions include: The visual boundary of an interactive element (like a radio button or input field) does not have a 3:1 color contrast ratio with the background, so people who are colorblind or have low vision may have difficulty perceiving the boundaries of the interactive element. This occurs on the following pages: Protect a PDF - Remove hidden information; AI Assistant; Protect a PDF - Protect with a Password & Remove Security; View PDF - Thumbnails; Acrobat Tools pane; Quick Tools in Document; Use a Certifica |
| 1.4.12 | Text Spacing | AA | Not Applicable | Software: The product is not implemented using markup languages. |
| 1.4.13 | Content on Hover or Focus | AA | Partially Supports | Software: Most of the product’s functionality, the additional content that is displayed on hover or focus is dismissible, hoverable or persistent. Exceptions include: Content that appears on mouse hover or keyboard focus (such as tooltips, drop-down menus, or popups) is not dismissible, so it obscures all or part of the original content on the page. This occurs on the following pages: Enhance Scan; Prepare for Accessibility; Comment on PDF; View PDF - Attachments; Use guided actions; Protect a PDF; Protect a PDF - Remove hidden information; AI Assistant; Fill and Sign; Prepare Form - Component |
| 2.4.5 | Multiple Ways | AA | Not Applicable | Software: This criterion does not apply to non-web software. |
| 2.4.6 | Headings and Labels | AA | Partially Supports | Software: Most headings and labels are descriptive. Exceptions include: A label for a control or form input field does not convey the purpose of the control or input, so users may not understand what the control does or what data to enter, especially people with cognitive or learning disabilities and people who are blind and/or use a screen reader. This occurs on the following pages: Comment on PDF; Use guided actions; Use guided actions - Make accessible; Edit - Organize PDF; Edit PDF; and the component Color palette which appears on multiple pages. A programmatic label for a control or form |
| 2.4.7 | Focus Visible | AA | Partially Supports | Software: Most focusable elements have a visible keyboard focus indicator. Exceptions include: An interactive element (such as a link, button, or form input) does not have a visual focus indicator, so sighted people who use a keyboard to navigate content will not know when that element is receiving focus. This occurs on the following pages: Enhance Scan; Create PDF; Comment on PDF; Protect a PDF - Remove hidden information; Protect a PDF - Protect with a Password & Remove Security; Adobe Sign / Send for Signatures; Quick Tools in Document; Prepare Form. |
| 2.4.11 | Focus Not Obscured (Minimum) | AA | Supports | Software: When a user interface component receives keyboard focus, the component is not entirely hidden due to author-created content. |
| 2.5.7 | Dragging Movements | AA | Does Not Support | Software: Most, if not all, functionality that uses a dragging movement cannot be achieved by a single pointer without dragging, excepting functions for which dragging is essential or the functionality is determined by the user agent and not modified by the author. Exceptions include: Some functionality relies on a dragging movement with no single-pointer, single touch alternative, making it difficult or impossible for persons with motor difficulties and users of assistive technology to perform the gesture on the following pages: Acrobat Home; Acrobat Tools pane; Add a stamp; Adobe Sign / Send |
| 2.5.8 | Target Size (Minimum) | AA | Does Not Support | Software: The size of the target for most clickable controls is at least 24 by 24 CSS pixels, except where the target size is determined by the user agent; there is a different control with equivalent functionality; the target is inline with text; the presentation of the target is essential to the function or otherwise exempted under the rule; or each control is spaced such that a 24-pixel circle placed around the bounding box of the control will not intersect any similar circle for another control. Exceptions include: Multiple target hit areas do not meet minimum 24x24 pixel side or spacing m |
| 3.1.2 | Language of Parts | AA | Not Applicable | Software: Content is only presented in one language at a time. |
| 3.2.3 | Consistent Navigation | AA | Not Applicable | Software: This criterion does not apply to non-web software. |
| 3.2.4 | Consistent Identification | AA | Not Applicable | Software: This criterion does not apply to non-web software. |
| 3.3.3 | Error Suggestion | AA | Supports | Where input errors are automatically detected, suggestions for correction are provided to the user. |
| 3.3.4 | Error Prevention (Legal, Financial, Data) | AA | Not Applicable | Software: The product does not process legal commitments or financial transactions and does not modify user-controllable data. |
| 3.3.8 | Accessible Authentication (Minimum) | AA | Not Applicable | Software: No authentication processes are included in the site, or if authentication processes are present, they do not include a cognitive function test. |
| 4.1.3 | Status Messages | AA | Partially Supports | Software: In most cases, status messages can be programmatically determined and presented by assistive technologies without receiving focus. Exceptions include: A status message is not automatically announced by the screen reader, so people who are blind and/or use a screen reader or other assistive technology may completely miss the status message or they may not hear it in a timely fashion. This occurs on the following pages: Combine Files / Organize during Combine; Enhance Scan; Create PDF; Comment on PDF; Protect a PDF - Remove hidden information; AI Assistant; Protect a PDF - Protect with |
| 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 | The product does not expose the name, role and state or value of most objects to assistive technology. Exceptions include: 4.1.2 Name, Role, Value |
| 502.3.2 | Modification of Object Information | - | Partially Supports | The product allows assistive technology to modify most of the states and properties of the controls. Exceptions include: 4.1.2 Name, Role, Value |
| 502.3.3 | Row, Column, and Headers | - | Partially Supports | The product has data tables, and most have programmatically determinable structure, relationships, and content. Exceptions include: 1.3.1 Info and Relationships |
| 502.3.4 | Values | - | Partially Supports | The values of most input controls in the product are programmatically determinable. Exceptions include: 4.1.2 Name, Role, Value |
| 502.3.5 | Modification of Values | - | Partially Supports | The product allows users to modify most values or text of an object using assistive technologies when those states and properties of an object in the product can be modified by users in general. Exceptions include: 4.1.2 Name, Role, Value |
| 502.3.6 | Label Relationships | - | Partially Supports | The product UI exposes most label relationships to assistive technologies. Exceptions include: 1.3.1 Info and Relationships 4.1.2 Name, Role, Value |
| 502.3.7 | Hierarchical Relationships | - | Supports | The product exposes hierarchical parent-child relationships to assistive technology. |
| 502.3.8 | Text | - | Partially Supports | Most of the product’s text objects, text attributes, and on-screen text boundaries are exposed to assistive technology. Exceptions include: 1.3.2 Meaningful Sequence |
| 502.3.9 | Modification of Text | - | Supports | The product allows assistive technology to modify the text. |
| 502.3.10 | List of Actions | - | Partially Supports | Most controls in the product expose programmatic role information and actions which can be taken on objects to assistive technology. Exceptions include: 4.1.2 Name, Role, Value |
| 502.3.11 | Actions on Objects | - | Does Not Support | For most, if not all, elements on which one or more actions may be performed, those actions are not available programmatically determinable, so that each action cannot be performed using assistive technology. Examples include: 2.1.1 Keyboard Navigation |
| 502.3.12 | Focus Cursor | - | Partially Supports | The product exposes focus location, text insertion point, and object selection state for most user interface components. Exceptions include: 2.4.7 Focus Visible |
| 502.3.13 | Modification of Focus Cursor | - | Supports | When a user can focus or change selection state of a control in the product via keyboard, then the focus or selection state can also be changed programmatically. |
| 502.3.14 | Event Notification | - | Partially Supports | The product notifies assistive technology to most user interaction events. Exceptions include: 4.1.3 Status Messages |
| 503.4.1 | Caption Controls | - | Not Applicable | The product does not contain video with synchronized audio that requires captions, and it provides user controls for captions. |
| 503.4.2 | Audio Description Controls | - | Not Applicable | The product does not contain prerecorded video content that would require audio description. |
| 504.2.1 | Preservation of Information Provided for Accessibility in Format Conversion | - | Does Not Support | When converting content, the accessibility information is not preserved upon converting PDF to Word, PowerPoint and Excel. |
| 504.2.2 | PDF Export | - | Does Not Support | The product exports PDF 1.7 files that do not conform to PDF/UA-1. Examples include: Headings lost the markup Images lost text alternatives |
| 4.2.1 | Usage without vision | - | Does Not Support | Software: Most, if not all, functionality is not usable without vision. Examples are noted in: 1.1.1 Non-Text Content 1.3.1 Info and Relationships 1.3.2 Meaningful Sequence 1.4.1 Use of Color 2.1.1 Keyboard 2.4.3 Focus Order 2.4.4 Link Purpose (in context) 2.4.6 Headings and Labels 3.2.1 On Focus 3.2.2 On Input 3.3.1 Error Identification 4.1.2 Name, Role, Value 4.1.3 Status Messages |
| 4.2.2 | Usage with limited vision | - | Does Not Support | Software: Most, if not all, functionality is not usable with limited vision. Examples are noted in: 1.1.1 Non-Text Content 1.3.1 Info and Relationships 1.3.2 Meaningful Sequence 1.4.1 Use of Color 1.4.3 Contrast (minimum) 1.4.4 Resize Text 1.4.10 Use of Color 1.4.11 Non-Text Contrast 1.4.13 Content on Hover or Focus 2.1.1 Keyboard 2.4.3 Focus Order 2.4.4 Link Purpose (in context) 2.4.6 Headings and Labels 2.4.7 Focus Visible 3.2.1 On Focus 3.2.2 On Input 3.3.1 Error Identification 3.3.2 Labels or Instructions 4.1.2 Name, Role, Value |
| 4.2.3 | Usage without perception of colou r | - | Partially Supports | Software: Most functionality is usable without perception of color. Exceptions are noted in: 1.4.1 Use of Color 1.4.3 Contrast (minimum) 1.4.11 Non-text Contrast |
| 4.2.4 | Usage without hearing | - | Not Applicable | Software: The product does not require the use of hearing. |
| 4.2.5 | Usage with limited hearing | - | Not Applicable | Software: The product does not require the use of hearing. |
| 4.2.6 | Usage with no or limited vocal capability | - | Not Applicable | Software: The product does not require the use of speech. |
| 4.2.7 | Usage with limited manipulation or strength | - | Partially Supports | Software: Users with limited manipulation who use speech recognition or switch control software will not have difficulty navigating to most of the controls. Exceptions include: 1.4.13 Content on Hover or Focus 2.1.1 Keyboard 2.4.3 Focus Order 2.4.4 Link Purpose (in context) 2.4.6 Headings and Labels 2.4.7 Focus Visible 2.5.3 Label in Name 3.2.1 On Focus 4.1.2 Name, Role, Value |
| 4.2.8 | Usage with limited reach | - | Supports | Software: All functionality is usable with limited reach and strength. |
| 4.2.9 | Minimize photosensitive seizure triggers | - | Not Applicable | Software: The product does not contain flashing content. |
| 4.2.10 | Usage with limited cognition, language or learning | - | Does Not Support | Software: Most, if not all, functionality is not usable by people with limited language, cognitive, and learning abilities. People with cognitive disabilities have varying needs for features that allow them to adapt content and work with assistive technology. Examples are noted in: 1.1.1 Non-Text Content 1.3.1 Info and Relationships 1.3.2 Meaningful Sequence 1.4.1 Use of Color 1.4.10 Non-Text Contrast 1.4.13 Content on Hover or Focus 2.1.1 Keyboard 2.4.3 Focus Order 2.4.4 Link Purpose (in context) 2.4.6 Headings and Labels 2.4.7 Focus Visible 2.5.3 Label in Name 3.2.1 On Focus 3.2.2 On Input 3 |
| 4.2.11 | Privacy | - | Not Applicable | Software: The product does not provide any privacy features. |
| 5.1.4 | Functionality closed to text enlargement | - | Not Applicable | The product does not have closed functionality. |
| 5.1.5 | Visual output for auditory information | - | Not Applicable | The product does not have closed functionality. |
| 5.1.7 | Access without speech | - | Not Applicable | The product does not have closed functionality. |
| 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. Most operable parts have an accessible name which enables them to be discernible without user vision. Exceptions include: Some graphical on-screen buttons do not have an accessible name. |
| 5.6.1 | Tactile or auditory status | - | Not Applicable | Tactile or auditory status is not included in the product. |
| 5.6.2 | Visual status | - | Supports | Visual status of controls is discernible in the product. |
| 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 | - | Does Not Support | Accessibility information is not preserved upon converting PDF to Word, PowerPoint and Excel. |
| 11.8.4 | Repair assistance | - | Supports | The product provides functionality for authors to run reports on sites to identify accessibility issues. |
| 11.8.5 | Templates | - | Not Applicable | The product does not provide templates for authored 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 April 2025. 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.