Acrobat-web-2025
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
- 12
- Partially supports
- 10
- Does not support
- 2
- Not applicable
- 8
- Not evaluated
- 0
Level AA — 24 criteria
- Supports
- 9
- Partially supports
- 11
- Does not support
- 0
- Not applicable
- 4
- 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 (102)
| Criterion | Name | Level | Conformance | Remarks from vendor |
|---|---|---|---|---|
| 1.1.1 | Non-text Content | A | Partially Supports | Web: The product provides sufficient text alternatives for most instances of images | non-text content, such as informative images. Exceptions include: Some images do not have a text alternative, so people who are blind and/or use a screen reader will not be able to access the information available in the image and if it is an active image, will not understand its function. This occurs on the following pages: Anonymous Modern Viewer; File Viewer: PDF; Request eSignatures – Send; Acrobat Web Paywall; Welcome Page. Some decorative images are not hidden from screen readers, so people who are blin |
| 1.2.1 | Audio-only and Video-only (Prerecorded) | A | Not Applicable | Web: The product does not contain prerecorded audio-only or video-only media. |
| 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 video content that would require audio description or a media alternative. |
| 1.3.1 | Info and Relationships | A | Does Not Support | Web: Most structure and relationship information are not provided programmatically or in text. 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 page: Acrobat Web Paywall. A group of form controls is not programmatically associated with their group label, so the purpose of individual controls in the group cannot be understood by people who are blind and/or use a screen reader. This occ |
| 1.3.2 | Meaningful Sequence | A | Partially Supports | Web: The product presents 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 page: Welcome Page. The order that the screen reader announces static content does not match the visual order of the content and changes the meaning of that content, so the intended meaning of the content will be lost or changed for people who are blind and/or use a screen read |
| 1.3.3 | Sensory Characteristics | A | Supports | Web: Instructions do not rely solely on sensory characteristics. |
| 1.4.1 | Use of Color | A | Partially Supports | Web: Most functions of the product do not convey information through color alone. Exceptions include: Color is the only visual method used to identify a link, and a link text's contrast ratio with the color of the surrounding text is less than 3:1, so people who are colorblind or have low vision may not be able to identify the link. This occurs on the following page: Acrobat Web Paywall. 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 and people who are blind |
| 1.4.2 | Audio Control | A | Not Applicable | Web: The product does not contain audio that plays automatically. |
| 2.1.1 | Keyboard | A | Partially Supports | Web: Most product functionality can be operated through a keyboard interface. Examples include: An action cannot be performed when using a screen reader, so people who are blind and others who use a screen reader cannot perform this action. This occurs on the following page: Request e-signatures - Send. 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: Request e-signatures - Send; Request e-signatures - Prepare; Acrobat Web Paywall; Welcome Page and on the co |
| 2.1.2 | No Keyboard Trap | A | Supports | Web: The product does not include keyboard traps. |
| 2.1.4 | Character Key Shortcuts | A | Supports | Web: The product provides character key shortcuts. Users can active when the relevant user interface component is in focus. |
| 2.2.1 | Timing Adjustable | A | Not Applicable | Web: The product does not include time limits. |
| 2.2.2 | Pause, Stop, Hide | A | Partially Supports | Web: On most pages where moving, blinking, scrolling, or auto-updating information is present, that information can be paused, stopped, hidden, or otherwise controlled by the user. Exceptions include: The user cannot pause, stop, or hide content that automatically moves, blinks, or scrolls, so people who cannot read text quickly, have attention deficit disorders or other cognitive disabilities, or use a screen reader may not be able to read or understand the content. This occurs on the following page: Request e-signatures - Send. |
| 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 | Supports | Web: The product provides headings to bypass repeated blocks. |
| 2.4.2 | Page Titled | A | Partially Supports | Web: Most pages have descriptive and informative titles. Exceptions include: The page does not have a programmatic title, so people who use a screen reader will not be able to identify the purpose of the page without reading the page content. This occurs on the following pages: Anonymous Modern Viewer; File Viewer: PDF. |
| 2.4.3 | Focus Order | A | Partially Supports | Web: Most components receive focus in a meaningful order. Exceptions include: Keyboard focus is lost or misplaced as a result of user interaction or content update or refresh, so people who use the keyboard to navigate content (including screen reader users) will become disoriented. This occurs on the following page: Request e-signatures - Send. Keyboard focus is not confined within a modal, so people who use the keyboard to navigate content (including screen reader users) will be able to navigate outside of the modal, which may cause them to become disoriented. This occurs on the following co |
| 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.5.1 | Pointer Gestures | A | Not Applicable | Web: The product does not rely on multipoint or path-based gestures. |
| 2.5.2 | Pointer Cancellation | A | Supports | Web: 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 | Web: 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: Home Page – Responsive Tablet and Mobile View only; Request e-signatures - Send; Gen AI: AI Assistant Floating banner; File Viewer: Header. An interactive element (such as a link, button, or form input) does not have |
| 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 | Partially Supports | Web: On most pages, the language of the page is correct and can be determined programmatically. Exceptions include: No language is programmatically assigned to a page, so screen readers may mispronounce content. This occurs on the following pages: Anonymous Modern Viewer; File Viewer: PDF. |
| 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.6 | Consistent Help | A | Supports | Web: 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 | Supports | Web: Where input errors are automatically detected, a text message or alert is provided that identifies the field/control where the error was detected and describes the error. |
| 3.3.2 | Labels or Instructions | A | Partially Supports | Web: Labels are provided for most input fields. Exceptions include: The label for a form field is missing, so the field's purpose is not clear. This occurs on the following pages: Home Page; File Viewer: PDF; Gen AI: Select File Modal and the component Header, found on multiple pages. |
| 3.3.7 | Redundant Entry | A | Supports | Web: If information previously entered by, or provided to, the user is required to be entered again in the same process, that information is either automatically populated or available for the user to select unless the previously entered information is no longer valid or re-entering the information is essential or required to ensure security. |
| 4.1.1 | Parsing | A | Supports | For WCAG 2.0, 2.1, EN 301 549, and Revised 508 Standards, the September 2023 errata update indicates this criterion is always supported. See the WCAG 2.0 Editorial Errata and the WCAG 2.1 Editorial Errata . |
| 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, or value] information. Examples include: A button does not have a programmatic name, so its name (such as "Submit" or "Cancel") is not conveyed to screen readers and other assistive technologies and will not be available to people who use those technologies. This occurs on the following pages: Home Page; Request e-signatures - Send; Gen AI: AI Assistant Floating banner; File Viewer: Header. A button does not have a programmatic role, so its role (usually button, but sometimes link or someth |
| 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 video content that would require audio description. |
| 1.3.4 | Orientation | AA | Supports | Web: Content does not restrict its view and operation to a single display 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.3 | Contrast (Minimum) | AA | Partially Supports | Web: 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 Gen AI: AI Assistant Panel; File Viewer: Right Panel, and the component Header which appears on multiple pages. The color contrast ratio between text and its background is less than 4.5:1, so people who are colorblind or have low vision may have difficulty reading the text. This occurs |
| 1.4.4 | Resize text | AA | Partially Supports | Web: Using browser zoom, text can be resized up to 200 percent without loss of content or functionality for most content. Exceptions 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: Gen AI: AI Assistant Panel; Acrobat Web Paywall. Functionality is lost 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 this functionality. This occurs on the following page: |
| 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: 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: Request e-signatures - Send; Gen AI: AI A |
| 1.4.11 | Non-text Contrast | AA | Partially Supports | Web: 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: Home Page; Request e-signatures - Send; Gen AI: AI Assistant Panel; Gen AI: AI Assistant Floating banner; File Viewer: Right Panel; File Viewer: PDF and the component Header which appears on multiple page |
| 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: When text spacing is adjusted to help people with vision, reading and cognitive disabilities, some content cannot be seen because it is cut off. This occurs on the following pages: Home Page; Request e-signatures - Send. When text spacing is adjusted to help people with vision, reading, and/or cognitive disabilities, some or all of the content cannot be read because it overlaps with other content. This occurs on the following page: Acrobat Web Paywall. |
| 1.4.13 | Content on Hover or Focus | AA | Partially Supports | Web: In most cases when additional content is triggered by pointer hover or keyboard focus, that additional content can be dismissed and hovered over, and the content persists until the user dismisses it. Exceptions include: Content that appears on mouse hover (such as tooltips, drop-down menus, or popups) disappears when the mouse pointer is moved over that content, meaning people with disabilities, especially people with low vision who need to magnify text, may not be able to read the additional content. This occurs on the following page: Home Page and the component Header which appears on m |
| 2.4.5 | Multiple Ways | AA | Supports | Web: Users can locate web pages in the product through search. |
| 2.4.6 | Headings and Labels | AA | Partially Supports | Web: Most headings and labels are descriptive. Exceptions include: A programmatic label for a control or form input field does not convey the purpose of the control or input, so people who are blind and/or use a screen reader may not understand what the control does or what data to enter. This occurs on the following pages: Request e-signatures - Send; Request e-signatures - Prepare; Acrobat Web Paywall. Multiple buttons have identical programmatic labels but different functionality, and there is no programmatic context, so people who are blind and/or use a screen reader will not know or may b |
| 2.4.7 | Focus Visible | AA | Supports | Web: The keyboard focus indicator is visible by default. |
| 2.4.11 | Focus Not Obscured (Minimum) | AA | Partially Supports | Web: When most user interface components receive keyboard focus, each component is not entirely hidden due to author-created content. Exceptions include: A focused element is completely covered by other author-created content, which may cause people who use the keyboard to navigate content to become disoriented. This occurs on the following component which appears on multiple pages: Header – Responsive Tablet and Mobile View only. |
| 2.5.7 | Dragging Movements | AA | Partially Supports | Web: Most functionality that uses a dragging movement can be achieved by a single pointer without dragging, unless 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: Request e-signatures - Send; Request e-signatures - Prepare. |
| 2.5.8 | Target Size (Minimum) | AA | Supports | Web: The size of the target for each clickable control 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 |
| 3.1.2 | Language of Parts | AA | Partially Supports | Web: On most pages, the language of each section of content that is different from the default language of the page is correctly identified and can be determined programmatically. Exceptions exist: A portion of content on a page that is in a different language from the rest of the content on the page is not programmatically assigned the language for that portion of content, so screen readers may mispronounce that part of the content. This occurs on the following page: Welcome Page. |
| 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.3 | Error Suggestion | AA | Supports | Web: 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 | Web: The product does not process legal commitments or financial transactions and does not modify user-controllable data. |
| 3.3.8 | Accessible Authentication (Minimum) | AA | Supports | Web: A cognitive function test (such as remembering a password or solving a puzzle) is not required for any step in an authentication process unless either another method is available that does not rely on a cognitive function test; help is available to assist the user in completing the test; or the test is to recognize objects or identify non-text content the user provided to the Web site. |
| 4.1.3 | Status Messages | AA | Partially Supports | Web: 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: Home Page; Request e-signatures - Send; Gen AI: AI Assistant Panel; Gen AI: Select File Modal. |
| 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 | - | Partially Supports | The role, state(s), properties, boundary, name, and description of most objects can be programmatically determined, so those attributes can be perceived and conveyed by assistive technology. Exceptions include: 4.1.2. Name, Role, Value |
| 502.3.2 | Modification of Object Information | - | Partially Supports | For most objects that allow the user to set their respective properties and/or state, the act of setting a property or state is available programmatically, so that it can be perceived and performed using assistive technology. Exceptions include: 4.1.2. Name, Role, Value |
| 502.3.3 | Row, Column, and Headers | - | Partially Supports | In most instances when a data table is present, all information in the data cells and the row and/or column headers associated with each data cell are available programmatically, so they can be perceived and conveyed by assistive technology Exceptions include: 1.3.1. Info and Relationships |
| 502.3.4 | Values | - | Partially Supports | For most objects that have a current value or have a set or range of values associated with the object, the value(s) is available programmatically, so it can be perceived and conveyed by assistive technology. Exceptions include: 4.1.2. Name, Role, Value |
| 502.3.5 | Modification of Values | - | Partially Supports | For most objects that allow the user to set or modify its value, the act of setting a value is available programmatically, so that it can be perceived and performed using assistive technology. Exceptions include: 4.1.2. Name, Role, Value |
| 502.3.6 | Label Relationships | - | Partially Supports | Web: For most elements that act as a label for another element and elements that are labeled by another element, the labeling relationship is programmatically determinable, so it can be perceived and conveyed by assistive technology. Exceptions include: 1.3.1 Info and Relationships 4.1.2. Name, Role, Value |
| 502.3.7 | Hierarchical Relationships | - | Partially Supports | When a page contains elements that have a parent-child relationship, those relationships are programmatically determinable, so they can be perceived by assistive technology. Exceptions include: 1.3.1. Info and Relationships |
| 502.3.8 | Text | - | Partially Supports | The content of text objects, text attributes, and the boundary of text rendered to the screen, shall be programmatically determinable. Exceptions are noted in: 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 | - | Partially Supports | For most of the elements on which one or more actions may be performed, all of those actions are available programmatically, so that each action can be performed using assistive technology. Exceptions include: 2.1.1 Keyboard Navigation |
| 502.3.12 | Focus Cursor | - | Supports | The product exposes focus location, text insertion point, and object selection state for user interface components |
| 502.3.13 | Modification of Focus Cursor | - | Supports | When a user can set focus, set the text insertion point, or change selection state of an object in the product, then the focus or selection state can also be changed programmatically. |
| 502.3.14 | Event Notification | - | Partially Supports | In most cases, status messages relevant to user interactions are available to, and presented by, assistive technology. Exceptions include: 4.1.3. Status Messages |
| 503.4.1 | Caption Controls | - | Not Applicable | The product does not display video. |
| 503.4.2 | Audio Description Controls | - | Not Applicable | The product does not provide prerecorded media that requires audio description. |
| 504.2.1 | Preservation of Information Provided for Accessibility in Format Conversion | - | Does Not Support | Upon upload and download of PDF content, accessibility information from the PDF is not retained. Specifically: Document language is not retained in the downloaded file. Image properties are not retained in the downloaded file. Content is missing semantic markup |
| 504.2.2 | PDF Export | - | Does Not Support | Upon upload and download of PDF content, accessibility information from the PDF is not retained. Specifically: Document language is not retained in the downloaded file. Image properties are not retained in the downloaded file. Content is missing semantic markup |
| 4.2.1 | Usage without vision | - | Partially Supports | Web: Most functionality is usable without vision. Exceptions 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.2 Page Titled 2.4.3 Focus Order 2.4.6 Headings and Labels 3.1.1 Language of Page 3.1.2 Language of Parts 4.1.2 Name, Role, Value 4.1.3 Status Messages |
| 4.2.2 | Usage with limited vision | - | Partially Supports | Web: Most functionality is usable with limited vision. Exceptions 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 Reflow 1.4.11 Non-Text Contrast 1.4.12 Text Spacing 1.4.13 Content on Hover or Focus 2.1.1 Keyboard 2.4.2 Page Titled 2.4.3 Focus Order 2.4.6 Headings and Labels 3.1.1 Language of Page 3.1.2 Language of Parts 3.3.2 Labels or Instructions 4.1.2 Name, Role, Value |
| 4.2.3 | Usage without perception of colour | - | Partially Supports | Web: Most functionality is usable without perception of color. Exceptions include: 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 | 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 with no or limited vocal capability | - | Not Applicable | Web: The product does not require the use of speech. |
| 4.2.7 | Usage with limited manipulation or strength | - | Partially Supports | Web: Most functionality is usable by people with limited manipulation and does not require manipulation, simultaneous action, or hand strength. Exceptions include: 1.4.13 Content on Hover or Focus 2.1.1 Keyboard 2.4.2 Page Titled 2.4.3 Focus Order 2.4.6 Headings and Labels 2.5.3 Label in Name 4.1.2 Name, Role, Value |
| 4.2.8 | Usage with limited reach | - | Supports | Web: All functionality is usable with limited reach and strength. |
| 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 functionality is 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. Exceptions include: 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 Reflow 1.4.12 Text Spacing 1.4.13 Content on Hover or Focus 2.1.1 Keyboard 2.2.2 Pause, Stop, Hide 2.4.2 Page Titled 2.4.3 Focus Order 2.4.6 Headings and Labels 2.5.3 Label in Name 3.1.1 Language of Page 3.1.2 Language of Parts 3.3.2 Labe |
| 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 | 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 | - | Not Applicable | 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. Exception includes: 4.1.2 Name, Role, Value. |
| 5.6.1 | Tactile or auditory status | - | Not Applicable | Tactile or auditory status is not included in the product. |
| 5.6.2 | Visual status | - | Not Applicable | The 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 | Upon upload and download of PDF content, accessibility information from the PDF is not retained. Specifically: Document language is not retained in the downloaded file. Image properties are not retained in the downloaded file. Content is missing semantic markup |
| 11.8.4 | Repair assistance | - | Supports | The product provides functionality for authors to run reports to identify accessibility issues. Authors can ensure the WCAG 2.0 level A and AA requirements are satisfied. |
| 11.8.5 | Templates | - | Not Applicable | The product does not provide templates for authored content. |
| 12.1.1 | Accessibility and compatibility features | - | Not Applicable | The product does not have an accessibility and compatibility features |
| 12.2.2 | Information on accessibility and compatibility features | - | Not Applicable | Information on accessibility and compatibility features are not provided. |
| 12.2.3 | Effective communication | - | Not Applicable | The web pages do not contain effective communication. |
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.