Adobe Acrobat Android
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
- 13
- Partially supports
- 11
- Does not support
- 1
- Not applicable
- 7
- Not evaluated
- 0
Level AA — 24 criteria
- Supports
- 5
- Partially supports
- 9
- Does not support
- 0
- 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 (102)
| 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 the application. Exceptions include: 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 each image. This occurs on the following pages: Adobe Cloud Storage; AI Assistant; Subscriptions. Some informative 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 conveyed by the image. This occurs on the following pages: Com |
| 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 object information or are available in text. Exceptions include: Some content that is visually presented as multiple lists is not marked up as a list, so the presence and structure of each list are not conveyed to assistive technologies and people who are blind and/or use a screen reader. This occurs on the following pages: Comment Thread; In App Purchase: Payment Methods & Google Play. Some content that is visually presented as a list is not properly marked up as a list, so the structures of those lists are not c |
| 1.3.2 | Meaningful Sequence | A | Partially Supports | Software: 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 pages: PDF View Settings; Comment; Liquid Mode View PDF; Save a copy; Share PDF Invite. Some hidden or empty interactive elements receive screen reader focus, so people who are blind and/or use a screen reader will navigate to elements that are not intended to be part of t |
| 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: Draw; Edit PDF - Add Text; Highlight; Text. 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. |
| 1.4.2 | Audio Control | A | Not Applicable | Software: The product does not contain audio that plays automatically. |
| 2.1.1 | Keyboard | A | Partially Supports | Software: Most product functionality can be operated through alternative input methods or keyboard interface. Exceptions 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 pages: Combine a PDF; Fill and Sign; Generative Summary; Help; Highlight; Preferences; Protect a PDF; Text Context and Blank Context Menu. An action cannot be performed using only a switch control, so people who use a switch control alone to navigate and operate content cannot perform this actio |
| 2.1.2 | No Keyboard Trap | A | Supports | Software: This product does not include keyboard trap. |
| 2.1.4 | Character Key Shortcuts | A | Supports | Software: This success criterion technically doesn't apply to Native Android application. |
| 2.2.1 | Timing Adjustable | A | Partially Supports | Software: In most cases when a time limit exists, the user is given an option to turn off, adjust, or extend the time limit. Exceptions include: Some content visually appears and disappears with no ability to adjust how long the content is visible, potentially preventing people who are blind, have low vision, or have mobility or cognitive disabilities from locating or reading the content. This occurs on the following pages: Comment; Comment Thread; Create PDF - Web to PDF; Draw; Edit PDF - Add Image; Edit PDF - Add Text; Fill and Sign; Highlight; Recognize Text; Text. |
| 2.2.2 | Pause, Stop, Hide | A | Supports | Software: Moving, blinking, scrolling, and auto-updating information can be paused, stopped or hidden by the user. |
| 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: Switch control or touch screen swiping goes to multiple elements that are hidden or empty, so people who use a switch control to navigate content may become disoriented or confused. This occurs on the following pages: Comment; Comment Thread; Compress PDF; Liquid Mode View PDF; Open a PDF; Share PDF Workflow; Share via Link. Focus is not confined within multiple modals when using a switch control, so people who use a switch control to navigate content will be able to navigate outside of the modal, which may caus |
| 2.4.4 | Link Purpose (In Context) | A | Supports | Software: 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 | Partially Supports | Software: Most functionality that can be operated with a pointer can be operated with single-point actions. Exceptions include: Functionality (excluding operating system, user agents [like a browser], or assistive technology functions) relies on path-based gestures that require the user to move the finger or pointer in a specific path or sequence, so people with motor disabilities or limited dexterity and people who use certain assistive technology to interact with the page will not be able to operate this functionality. This occurs on the following pages: Crop Pages; Adobe Scan; AI Assistant; |
| 2.5.2 | Pointer Cancellation | A | Supports | Software: Product functions that use a single pointer are completed when the user releases the pointer. |
| 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: Multiple interactive elements (such as links, buttons, or form inputs) do not have an accessible name because their visible labels are not programmatically associated with the elements, so people who use speech input to navigate and operate content will not be able to access those elements. This occurs on the following pages: PDF View Settings; Sign In; Add Mobile number; Compress PDF; Edit PDF - Add Text; Export PDF; Fill and Sign; Home Screen; Preferences. The acces |
| 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 product relies on the features of the underlying operating system to set and indicate the language of the user interface. |
| 3.2.1 | On Focus | A | Supports | Software: Components do not initiate a change of context when focused. |
| 3.2.2 | On Input | A | Supports | Software: Changes of context do not occur automatically on user input. |
| 3.2.6 | Consistent Help | A | Supports | Software: On screens that contain help features (including human or automated contact options or self-help options), those features occur in the same order relative to other screen 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. Exceptions include: Errors for some form inputs (such as text input fields, radio buttons, select dropdowns, or checkboxes) are 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 pages: Viewer: Go to Page; Viewer: Print. . |
| 3.3.2 | Labels or Instructions | A | Partially Supports | Software: Labels are provided for most input fields. Exceptions include: Some labels of elements are not persistent (always visible on the page), so each element's purpose may be difficult to discover. This occurs on the following page: Home: Search; Comment Thread; Search for Text in PDF; Share PDF Invite; Viewer: Go to Page. The labels for some form fields are missing, so each field's purpose is not clear. This occurs on the following pages: Draw; Highlight. |
| 3.3.7 | Redundant Entry | A | Supports | Software: 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 | 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 information. Examples include: When some buttons are selected, their selected state is not conveyed programmatically, so people who are blind and/or use a screen reader or other assistive technology will not be informed that the buttons are selected. This occurs on the following pages: Viewer: Thumbnails; AI Assistant; Adobe Cloud Storage; PDF View Settings; Home: Search. Multiple form controls (such as text input fields or checkboxes) are not programmatically associated with their visible labels, so peop |
| 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 | Partially Supports | Software: On most screens, The product restricts its view either landscape or portrait orientation. Exceptions include: When the display orientation is changed (from portrait to landscape or vice versa), the content does not adjust to the new orientation, so people who require a particular display orientation may not be able to access some of that content or functionality. This occurs on the following page: Adobe Scan. |
| 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 | Partially Supports | Software: Most text meets minimum contrast requirements. Exceptions include: 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 on the following pages: Account Settings; Add Mobile number; Adobe Scan; Crop Pages; Export PDF; Help; Protect a PDF; Viewer: Print. The color contrast ratio between text placed over an image and that image is less than 4.5:1, so people who are colorblind or have low vision may have difficulty reading the text. This occurs on the following page: |
| 1.4.4 | Resize text | AA | Not Applicable | Software: This success criterion technically doesn't apply to Native Android application. |
| 1.4.5 | Images of Text | AA | Partially Supports | Software: The product uses text instead of images of text. Exceptions include: Text on the page is text embedded in an image instead of actual text. An image of text is difficult to zoom or otherwise modify, so people who have low vision and need to enlarge text to read it may not be able to read the text. People with other disabilities that need to otherwise modify text to read it also may not be able to read this text. This occurs on the following page: Viewer: Print. |
| 1.4.10 | Reflow | AA | Not Applicable | Software: This success criterion technically doesn't apply to Native Android application. |
| 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: Edit PDF - Add Text; PDF View Settings; Add Mobile number; Combine a PDF; Comment Thread; Compress PDF; Crop Pages; Draw; Export PDF; Fill and Sign; Google Drive; Highlight; Home Screen; Home: Gmail |
| 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 | Not Applicable | Software: This success criterion technically doesn't apply to Native Android application. |
| 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 for form and interactive controls are informative. 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 page: Help. Multiple programmatic labels for controls or form input fields do not convey the purpose of the control or input, so people who are blind and/or use a screen reader may not u |
| 2.4.7 | Focus Visible | AA | Not Applicable | Software: This criterion does not apply to non-web software. |
| 2.4.11 | Focus Not Obscured (Minimum) | AA | Partially Supports | Software: When most user interface components receive keyboard focus, each component is not entirely hidden due to author-created content. Exceptions include: Multiple focused elements are 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 pages: Viewer: Print; Share via Link; Comment; Liquid Mode View PDF; Read Aloud PDF; Open a PDF; Share PDF Workflow. |
| 2.5.7 | Dragging Movements | AA | Partially Supports | Software: 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: Combine a PDF; Viewer: Thumbnails; Text; Organize Page. |
| 2.5.8 | Target Size (Minimum) | AA | Partially Supports | 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: A target's hit area does not meet minimum 24x24 pixel size or spacing. maki |
| 3.1.2 | Language of Parts | AA | Supports | Software: Changes of language for passages or phrases can be programmatically determined. |
| 3.2.3 | Consistent Navigation | AA | Supports | Software: When navigational mechanisms are repeated in the product they occur in a consistent relative order. |
| 3.2.4 | Consistent Identification | AA | Supports | Software: Components with the same functionality are identified consistently. |
| 3.3.3 | Error Suggestion | AA | Supports | Software: 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 | Supports | Software: 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 | 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: AI Assistant; Viewer: Go to Page; Sign In; Protect a PDF; Export PDF; Liquid Mode View PDF; Combine a PDF; Organize Page. |
| 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 product exposes 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 states and properties of some controls and inputs. Exceptions include: 4.1.2.a Name, Role, Value |
| 502.3.3 | Row, Column, and Headers | - | Not Applicable | The product does not use data tables. |
| 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 | The product UI exposes most label relationships to assistive technologies. Exceptions include: 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 | - | Partially Supports | The product allows assistive technology to perform all actions on objects. Exceptions include: 2.1.1 Keyboard |
| 502.3.12 | Focus Cursor | - | Supports | The product exposes focus location, text insertion point, and object selection state for most user interface components. |
| 502.3.13 | Modification of Focus Cursor | - | Partially 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. Exceptions include: 1.3.2 Meaningful Sequence |
| 502.3.14 | Event Notification | - | Partially Supports | The product notifies assistive technology to most user interaction events. Exceptions include: 4.1.3.a 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 | - | Supports | The product preserves the accessibility information during conversion. |
| 504.2.2 | PDF Export | - | Supports | The product preserves the accessibility information during conversion. |
| 4.2.1 | Usage without vision | - | Partially Supports | Software: Most functions of the product are usable without vision. 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 2.1.1 Keyboard 2.2.1 Timing Adjustable 2.4.3 Focus Order 2.4.6 Headings and Labels 3.3.1 Error Identification 4.1.2 Name, Role, Value 4.1.3 Status Messages |
| 4.2.2 | Usage with limited vision | - | Partially Supports | Software: Most functionality is usable with limited vision. Exceptions include: 1.1.1 Non-Text Content 1.3.1 Info and Relationships 1.3.2 Meaningful Sequence 1.3.4 Device Orientation 1.4.1 Use of Color 1.4.3 Contrast (minimum) 1.4.5 Images of Text 1.4.11 Non-Text Contrast 2.1.1 Keyboard 2.2.1 Timing Adjustable 2.4.3 Focus Order 2.4.6 Headings and Labels 3.3.1 Error Identification 3.3.2 Labels or Instructions 4.1.2 Name, Role, Value |
| 4.2.3 | Usage without perception of colour | - | Partially Supports | Software: Most functions of the product are 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 | 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.3.4 Device Orientation 2.1.1 Keyboard 2.2.1 Timing Adjustable 2.4.3 Focus Order 2.4.6 Headings and Labels 2.5.1 Pointer Gestures 2.5.3 Label in Name 4.1.2 Name, Role, Value |
| 4.2.8 | Usage with limited reach | - | Partially Supports | Software: Users with limited reach and strength will not have difficulty navigating to most of the controls. Exceptions include: 1.3.4 Device Orientation 2.5.1 Pointer Gestures 2.5.3 Label in Name |
| 4.2.9 | Minimize photosensitive seizure triggers | - | Not Applicable | Software: The product does not contain flashing content or media. |
| 4.2.10 | Usage with limited cognition, language or learning | - | Partially Supports | Software: The product is functional for users 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. The product provides labeling for most controls. Exceptions include: 1.1.1 Non-Text Content 1.3.1 Info and Relationships 1.3.2 Meaningful Sequence 1.3.4 Device Orientation 1.4.1 Use of Color 1.4.5 Images of Text 2.1.1 Keyboard 2.2.1 Timing Adjustable 2.4.3 Focus Order 2.4.6 Headings and Labels 2.5.1 Pointer Gestures 2.5.3 Label in Name 3.3.1 Error Identificat |
| 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: 1.3.1 Info and Relationships 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 | - | 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 | - | Supports | The product preserves the accessibility information during conversion. |
| 11.8.4 | Repair assistance | - | Not Applicable | The product does not provide authoring features that support or require prompting for accessible content creation. |
| 11.8.5 | Templates | - | Not Applicable | The product does not provide templates for authored content. |
| 12.1.1 | Accessibility and compatibility features | - | Partially Supports | The provided product documentation does not explain how to use the accessibility and compatibility features of the content. This occurs on the following page: Help. |
| 12.2.2 | Information on accessibility and compatibility features | - | Not Applicable | The product does not have Information on accessibility and compatibility features. |
| 12.2.3 | Effective communication | - | Not Applicable | Support services are not provided for the product. |
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 July 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.