Adobe Scan iOS
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
- 16
- Partially supports
- 8
- Does not support
- 1
- Not applicable
- 7
- Not evaluated
- 0
Level AA — 24 criteria
- Supports
- 6
- Partially supports
- 6
- Does not support
- 1
- Not applicable
- 11
- 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 the application. Exceptions include: An informative image does 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 the image. This occurs on the following page: Actions: Move. An image that acts as a link or control does not have a text alternative, so people who are blind and/or use a screen reader will not understand the function performed by the image. This occurs on the following page: View All Scans. |
| 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: A block of text is marked up as a heading but is not a heading, so the structure of the content is misrepresented to assistive technologies and people who are blind and/or use a screen reader. This occurs on the following page: Search. Text that visually functions as a heading is not marked up as a heading, so the structure of the content is not properly conveyed to assistive technologies and people who are blind and/or use a screen reader. This occu |
| 1.3.2 | Meaningful Sequence | A | Partially Supports | Software: The product presents most content in a meaningful sequence. Exceptions include: Some visually hidden content is announced by a screen reader, so people who are blind and/or use a screen reader may be misled or confused when hearing content that is not intended to be part of the reading order on the page. This occurs on the following page: Search. 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 |
| 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: Edit: Clean Up; Edit: Mark Up; Preview Document; Actions: Edit 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 ab |
| 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: Edit: Retake - Adjust; Actions: Edit Text; Text Actions. An action cannot be performed when using voice control, so people who rely on voice control to navigate and operate content cannot perform that action. This occurs on the following pages: Edit: Retake - Adjust; Edit: Resize; Actions |
| 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 iOS application. |
| 2.2.1 | Timing Adjustable | A | Supports | Software: The product supports the adjustment or cancellation of time-based limits. |
| 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 | Supports | Software: Components receive focus in a meaningful order. |
| 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: View Recent Scans; Scan Document; Edi |
| 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: 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: Scan Document; Edit: Retake - Adjust. An interactive element (such as a link, button, or form input) does not have an accessible name because its visible label is not programmatically associated with the element |
| 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 | Supports | Software: Where input errors are automatically, items in error are identified and error messages are provided as and conveyed to assistive technologies. |
| 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: Search; Organize Scans. The label for a form field is missing, so the field's purpose is not clear. This occurs on the following page: Actions: Edit Text. Some visible Instructions for a form input field are not available for people who use assistive technology. This occurs on the following pages: Actions: Combine Files; Reorder Pages. |
| 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: Examples include: A button does not have a programmatic role, so its role (usually button, but sometimes link or something else) 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: Free to Paid User Subscription; Search; Reorder Pages; View All Scans; Actions: Export PDF; Actions: Move; Import from photos. The expand/collapse state of a toggle-type element is mi |
| 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 | Does Not Support | 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: App Wide. |
| 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 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: Actions: Copy to Device; Search; Organize Scans. 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: View Recent Scans; Free to Paid |
| 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 | Supports | Software: The product uses text instead of images of text. |
| 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: Preferences; Actions: Set Password; Free to Paid User Subscription; Edit: Retake - Adjust; Edit: Clean Up; Actions: Copy to Device; Edit: Mark Up; Actions: Combine Files; Actions: Print; Organize Sca |
| 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 iOS 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 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: Edit: Mark Up; Search; Actions: Print; Actions: Edit Text. 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 n |
| 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 | Not Applicable | Software: This criterion does not apply to non-web software. |
| 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: Edit: Retake - Adjust; Reorder Pages; Actions: Edit Text; Text Actions. |
| 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: Sign In; Actions: Set Password; Search; Actions: Move; Actions: Delete. |
| 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 | - | 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 | The product UI exposes most label relationships to assistive technologies. Exceptions include: 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.e Headings |
| 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 | - | Not Applicable | The product is not an authoring tool. |
| 504.2.2 | PDF Export | - | Not Applicable | The product is not an authoring tool. |
| 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.4.6 Headings and Labels 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.11 Non-Text Contrast 2.1.1 Keyboard 2.4.6 Headings and Labels 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.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 2.1.1 Keyboard 2.4.6 Headings and Labels 2.5.1 Pointer Gestures 2.5.3 Label in Name 3.3.2 Labels or Instructions 4.1.2 Name, Role, Value 4.1.3 Status Messages |
| 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 isn’t 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 | - | Not Applicable | The product is not an authoring tool. |
| 11.8.4 | Repair assistance | - | Not Applicable | The product is not an Authoring Tool. |
| 11.8.5 | Templates | - | Not Applicable | The product is not an Authoring Tool. |
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 June 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.