Adobe Accessibility Conformance Report
VPAT® Version 2.3 (Revised) – April 2019
Product Information
Name of Product/Version: Adobe Scan iOS 20.03.16
Product Description: The free Adobe Scan PDF scanner app turns your device into a powerful portable PDF scanner that recognizes text automatically (OCR). Use this mobile document scanner to turn anything — receipts, notes, documents, photos, business cards, whiteboards — into an Adobe PDF with text you can reuse from each PDF and photo scan. Capture, enhance, cleanup, reuse, and share your documents using Adobe Scan.
Date: April 22, 2020
Contact information: access@adobe.com
Notes: The information contained in this report applies to the product itself. Information about product help and support documentation is located at: http://www.adobe.com/accessibility/compliance.html.
Evaluation Methods Used: Testing Adobe Scan Mobile (iOS) involved extensive use of leading assistive technology such as screen readers, and screen magnifiers, as well exclusive use of the keyboard. Native platform accessibility features were also used to assist with testing. These were supplemented with techniques such as manual inspection.
Applicable Standards/Guidelines
This report covers the degree of conformance for the following accessibility standard/guidelines:
Standard/Guideline |
Included in Report |
---|---|
Level A: Yes |
|
Level A: Yes |
|
Yes |
|
Yes |
Terms
The terms used in the Conformance Level information are defined as follows:
- Supports: The functionality of the product has at least one method that meets the criterion without known defects or meets with equivalent facilitation.
- Partially Supports: Some functionality of the product does not meet the criterion.
- Does Not Support: The majority of product functionality does not meet the criterion.
- Not Applicable: The criterion is not relevant to the product.
- Not Evaluated: The product has not been evaluated against the criterion. This can be used only in WCAG 2.0 Level AAA.
WCAG 2.x Report
All WCAG sections also document conformance with:
- EN 301 549: Chapter 9 - Web, Sections 10.1-10.4 of Chapter 10 - Non-Web documents, and Sections 11.1-11.4 and 11.8.2 of Chapter 11 - Non-Web Software (open and closed functionality), and Sections 12.1.2 and 12.2.4 of Chapter 12 – Documentation
- Revised Section 508: Chapter 5 – 501.1 Scope, 504.2 Content Creation or Editing, and Chapter 6 – 602.3 Electronic Support Documentation.
Note: When reporting on conformance with the WCAG 2.x Success Criteria, they are scoped for full pages, complete processes, and accessibility-supported ways of using technology as documented in the WCAG 2.0 Conformance Requirements.
Guideline 1.1 Text Alternatives:
Provide text alternatives for any non-text content so that it can be changed into other forms people need, such as large print, braille, speech, symbols or simpler language.
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
1.1.1 Non-text Content (Level A)
Revised Section 508
|
Partially Supports |
The product provides sufficient text alternatives for most instances of images and non-text content. Exceptions include:
|
Guideline 1.2 Time-based Media:
Provide alternatives for time-based media.
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
1.2.1 Audio-only and Video-only (Prerecorded) (Level A)
Revised Section 508
|
Supports |
The product does not contain prerecorded audio-only or video-only media. |
1.2.2 Captions (Prerecorded) (Level A)
Revised Section 508
|
Supports |
The product does not contain any content that requires captions. |
1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A)
Revised Section 508
|
Supports |
The product does not contain prerecorded video content that would require audio description or a media alternative. |
1.2.4 Captions (Live) (Level AA)
Revised Section 508
|
Supports |
The product does not contain live synchronized media. |
1.2.5 Audio Description (Prerecorded) (Level AA)
Revised Section 508
|
Supports |
The product does not contain prerecorded video content that would require audio description. |
Guideline 1.3 Adaptable:
Create content that can be presented in different ways (for example simpler layout) without losing information or structure.
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
1.3.1 Info and Relationships (Level A)
Revised Section 508
|
Does Not Support |
The product does not provide appropriate programmatic or textual equivalents for most visual structure and relationship. Some exceptions include:
|
1.3.2 Meaningful Sequence (Level A)
Revised Section 508
|
Supports |
The product presents content in a meaningful sequence. |
1.3.3 Sensory Characteristics (Level A)
Revised Section 508
|
Supports |
Instructions provided for understanding and operating content do not rely solely on sensory characteristics. |
1.3.4 Orientation (Level AA 2.1 only)
Revised Section 508 – Does not apply |
Supports |
Content does not restrict its view and operation to a single display orientation and responds appropriately to screen orientation changes. |
1.3.5 Identify Input Purpose (Level AA 2.1 only)
Revised Section 508 – Does not apply |
Supports |
The purpose of each input field collecting information about the user can be programmatically determined. |
Guideline 1.4 Distinguishable:
Make it easier for users to see and hear content including separating foreground from background.
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
1.4.1 Use of Color (Level A)
Revised Section 508
|
Partially Supports |
Throughout the product, color is not used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element, except:
|
1.4.2 Audio Control (Level A)
Revised Section 508
|
Supports |
The product does not contain audio that plays automatically. |
1.4.3 Contrast (Minimum) (Level AA)
Revised Section 508
|
Does Not Support |
Several components on the product do not meet the minimum contrast requirements. Exceptions include:
|
1.4.4 Resize text (Level AA)
Revised Section 508
|
Does Not Support |
Throughout the product, when resizing text up to system maximum, text is no longer contained within its containers and overlaps with elements, causing it to be difficult to read. |
1.4.5 Images of Text (Level AA)
Revised Section 508
|
Supports |
The product uses text instead of images of text. |
1.4.10 Reflow (Level AA 2.1 only)
Revised Section 508 – Does not apply |
Supports |
Content responds and reflows as necessary when zoomed and does not require scrolling in two dimensions |
1.4.11 Non-text Contrast (Level AA 2.1 only)
Revised Section 508 – Does not apply |
Supports |
User interface components and meaningful graphics have sufficient contrast with the surrounding background. |
1.4.12 Text Spacing (Level AA 2.1 only)
Revised Section 508 – Does not apply |
Supports |
There is no loss of content or functionality when users override author specified text styles. |
1.4.13 Content on Hover or Focus (Level AA 2.1 only)
Revised Section 508 – Does not apply |
Supports |
Throughout the product, content is not made visible via hover or focus or, when it is, it is dismissable, hoverable, and persistent. |
Guideline 2.1 Keyboard Accessible:
Make all functionality available from a keyboard.
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
2.1.1 Keyboard (Level A)
Revised Section 508
|
Partially Supports |
Most basic product functionality can be operated through a keyboard interface. Exceptions include:
|
2.1.2 No Keyboard Trap (Level A)
Revised Section 508
|
Supports |
The product does not feature any content or controls that cause a keyboard trap. |
2.1.4 Character Key Shortcuts (Level A 2.1 only)
Revised Section 508 – Does not apply |
Supports |
No Shortcuts are used in the product. |
Guideline 2.2 Enough Time:
Provide users enough time to read and use content.
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
2.2.1 Timing Adjustable (Level A)
Revised Section 508
|
Supports |
The product does not include time limits. |
2.2.2 Pause, Stop, Hide (Level A)
Revised Section 508
|
Supports |
The product does not include elements which move, blink, scroll, or auto-update. |
Guideline 2.3 Seizures:
Do not design content in a way that is known to cause seizures.
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
2.3.1 Three Flashes or Below Threshold (Level A)
Revised Section 508
|
Supports |
The product does not contain flashing content. |
Guideline 2.4 Navigable:
Provide ways to help users navigate, find content, and determine where they are.
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
2.4.1 Bypass Blocks (Level A)
Revised Section 508
|
Supports |
This criterion does not apply to non-web software. |
2.4.2 Page Titled (Level A)
Revised Section 508
|
Does Not Support |
Throughout the application, screen titles are either not present or are not announced to VoiceOver users on screen load. |
2.4.3 Focus Order (Level A)
Revised Section 508
|
Partially Supports |
Most components receive focus in a meaningful order. Exceptions include:
|
2.4.4 Link Purpose (In Context) (Level A)
Revised Section 508
|
Supports |
Links within the product make sense within their context of use. |
2.4.5 Multiple Ways (Level AA)
Revised Section 508
|
Supports |
This criterion does not apply to non-web software. |
2.4.6 Headings and Labels (Level AA)
Revised Section 508
|
Supports |
Headings and labels are descriptive. |
2.4.7 Focus Visible (Level AA)
Revised Section 508
|
Partially Supports |
Most focusable elements have a visible keyboard focus indicator. Exceptions include:
|
Guideline 2.5 Input Modalities:
Make it easier for users to operate functionality through various inputs beyond keyboard.
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
2.5.1 Pointer Gestures (Level A 2.1 only)
Revised Section 508 – Does not apply |
Supports |
Elements in the product can be used with required pointer gestures. |
2.5.2 Pointer Cancellation (Level A 2.1 only)
Revised Section 508 – Does not apply |
Supports |
The product contains only functionality that can be activated on the up event of a single pointer. |
2.5.3 Label in Name (Level A 2.1 only)
Revised Section 508 – Does not apply |
Supports |
For components that have visible text labels, that text exists in the component's accessible name. |
2.5.4 Motion Actuation (Level A 2.1 only)
Revised Section 508 – Does not apply |
Supports |
The product does not contain any functionality that can be operated by device motion or user motion. |
Guideline 3.1 Readable:
Make text content readable and understandable.
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
3.1.1 Language of Page (Level A)
Revised Section 508
|
Supports |
The language is programmatically determinable within the product. |
3.1.2 Language of Parts (Level AA)
Revised Section 508
|
Supports |
Content is only presented in one language at a time. |
Guideline 3.2 Predictable:
Make Web pages appear and operate in predictable ways.
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
3.2.1 On Focus (Level A)
Revised Section 508
|
Supports |
Components do not initiate a change of context when focused. |
3.2.2 On Input (Level A)
Revised Section 508
|
Supports |
Changes of context do not occur automatically on user input. |
3.2.3 Consistent Navigation (Level AA)
Revised Section 508
|
Supports |
When navigational mechanisms are repeated in the product, they occur in a consistent relative order and appearance. |
3.2.4 Consistent Identification (Level AA)
Revised Section 508
|
Supports |
Components with the same functionality, such as form controls with the same purpose are identified consistently. |
Guideline 3.3 Input Assistance:
Help users avoid and correct mistakes.
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
3.3.1 Error Identification (Level A)
Revised Section 508
|
Supports |
Where input errors are automatically detected, items in error are identified and error messages are conveyed to assistive technologies. |
3.3.2 Labels or Instructions (Level A)
Revised Section 508
|
Supports |
Labels and instructions (where necessary) are provided when content requires user input. |
3.3.3 Error Suggestion (Level AA)
Revised Section 508
|
Supports |
The product provides suggestions to the user when input errors are automatically detected. |
3.3.4 Error Prevention (Legal, Financial, Data) (Level AA)
Revised Section 508
|
Supports |
The product does not process legal commitments or financial transactions. Changes to user-controllable data are reversible or can be confirmed before finalizing. |
Guideline 4.1 Compatible:
Maximize compatibility with current and future user agents, including assistive technologies.
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
4.1.1 Parsing (Level A)
Revised Section 508
|
Supports |
The product is not implemented using markup languages. |
4.1.2 Name, Role, Value (Level A)
Revised Section 508
|
Does Not Support |
Many user interface components do not convey their name, role or value to assistive technology, such as:
|
4.1.3 Status Messages (Level AA 2.1 only)
Revised Section 508 – Does not apply |
Supports |
Status messages, when provided, are presented in a way that can be programmatically determined and do not require that they receive focus. |
Criteria |
Conformance Level |
Remarks and Explanations |
|
---|---|---|---|
302.1 Without Vision |
Does Not Support |
Several pieces of functionality within the product are inaccessible to users without vision, as shown in 1.1.1 Non-Text Content, 1.3.1 Info and Relationships, 2.1.1 Keyboard, 2.4.3 Focus Order and 4.1.2 Name, Role, Value. |
|
302.2 With Limited Vision |
Partially Supports |
Some pieces of functionality within the product are inaccessible to users with low vision, as shown in 1.4.3 Contrast (Minimum). |
|
|
Partially Supports |
Users who cannot perceive color will be able to use most of the product, notwithstanding the exceptions listed in 1.4.1 Use of Color and 1.4.3 Contrast (Minimum). |
|
302.4 Without Hearing |
Supports |
No functionality within the product requires hearing. |
|
302.5 With Limited Hearing |
Supports |
No functionality within the product requires hearing. |
|
302.6 Without Speech |
Supports |
The product does not require user speech. |
|
302.7 With Limited Manipulation |
Partially Supports |
Most of the product can be used by users with limited manipulation. Exceptions are listed in 2.1.1 Keyboard and 2.4.3 Focus Order. |
|
302.8 With Limited Reach and Strength |
Partially Supports |
Most functions of the product are functional for users with limited reach or strength who rely on keyboard access. The exceptions are noted in 2.1.1 Keyboard. |
|
302.9 With Limited Language, Cognitive, and Learning Abilities |
Partially Supports |
Some features of the product will present challenges for users with cognitive impairments, as noted in 2.4.3 Focus Order. |
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
501.1 Scope – Incorporation of WCAG 2.0 AA |
See WCAG 2.x section |
See information in WCAG 2.x section. |
502.2.1 User Control of Accessibility Features |
Supports |
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 |
Some features of the product lack role, state, and/or accessible name information for a number of functional components as described in 1.3.1 Info and Relationships, 3.3.2 Labels or Instructions, and 4.1.2 Name, Role, Value. |
502.3.2 Modification of Object Information |
Partially Supports |
In some features of the product, the users cannot modify states and properties of an object using assistive technologies when those states and properties of an object in the product can be modified by users in general as noted in 2.1.1 Keyboard and 4.1.2 Name, Role, Value. |
502.3.3 Row, Column, and Headers |
Supports |
The product does not contain data tables. |
502.3.4 Values |
Partially Supports |
The values of some input controls in the product are not programmatically determinable, as described in 4.1.2 Name, Role, Value. |
502.3.5 Modification of Values |
Partially Supports |
Most basic product functionality can be operated through a keyboard interface, notwithstanding the exceptions noted in 2.1.1 Keyboard. |
502.3.6 Label Relationships |
Partially Supports |
The product conveys an accessible name for most interactive elements to assistive technology, notwithstanding the exceptions noted in 1.3.1 Info and Relationships and 4.1.2 Name, Role, Value. |
502.3.7 Hierarchical Relationships |
Partially Supports |
Most of the product has clear hierarchical relationships, notwithstanding the exceptions noted in 1.3.1 Info and Relationships. |
502.3.8 Text |
Supports |
Text content, text attributes, and text boundaries are programmatically determinable. |
502.3.9 Modification of Text |
Supports |
The product allows assistive technology to modify text. |
502.3.10 List of Actions |
Partially Supports |
Actions that an object can perform are exposed, notwithstanding exceptions noted in 1.3.1 Info and Relationships and 4.1.2 Name, Role, Value. |
502.3.11 Actions on Objects |
Partially Supports |
The product allows assistive technology to programmatically execute actions on objects, subject to exceptions as described in 1.3.1 Info and Relationships, 2.1.1 Keyboard and 4.1.2 Name, Role, Value. |
502.3.12 Focus Cursor |
Partially Supports |
Most focusable elements have a visible keyboard focus indicator. Exceptions include:
|
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 |
Supports |
When components in the product change their programmatic states and values, the changes are available to assistive technology. |
502.4 Platform Accessibility Features |
Supports |
This product is not platform software. |
503.2 User Preferences |
Supports |
The product honors platform settings for color, contrast, font type, font size, and focus cursor. |
503.3 Alternative User Interfaces |
Supports |
The product does not provide an alternative user interface that functions as assistive technology. |
503.4.1 Caption Controls |
Supports |
The product does not contain video content with audio that would require being described through captions. |
503.4.2 Audio Description Controls |
Supports |
The product does not contain video content with audio that would require being described with Audio Description. |
504.2 Content Creation or Editing |
See WCAG 2.x section |
See information in WCAG 2.x section |
504.2.1 Preservation of Information Provided for Accessibility in Format Conversion |
Supports |
The content of an exported PDF is announced in the same order as in the application. |
504.2.2 PDF Export |
Supports |
The content of an exported PDF is announced in the same order as in the application. |
504.3 Prompts |
Does Not support |
The product does not prompt the user to create accessible content. |
504.4 Templates |
Does Not support |
The product does not provide templates that allow for the creation of content that conforms to Level A and Level AA Success Criteria and Conformance Requirements in WCAG 2.1. |
Chapter 6: Support Documentation and Services
Notes: Information regarding Support Documentation and Services is available in the Accessibility Conformance Report for the Adobe Help Center on the Adobe Accessibility Compliance website..
EN 301 549 Report
Notes:
Chapter 4: Functional Performance Statements (FPS)
Notes:
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
4.2.1 Usage without vision |
Partially Supports |
Several pieces of functionality within the product are inaccessible to users without vision, as shown in 1.1.1 Non-text content, 1.3.1 Info and Relationships, 2.1.1 Keyboard, 2.4.3 Focus Order and 4.1.2 Name, Role, Value. |
4.2.2 Usage with limited vision |
Partially Supports |
Some pieces of functionality within the product are inaccessible to users with low vision, as shown 1.4.3 Contrast (Minimum), 1.4.4 Resize Text and 2.4.3 Focus Order. |
4.2.3 Usage without perception of colour |
Partially Supports |
Users who cannot perceive color will be able to use most of the product, notwithstanding the exceptions listed in 1.4.1 Use of Color and 1.4.3 Contrast (Minimum). |
4.2.4 Usage without hearing |
Supports |
The product does not contain any audio content that requires hearing. |
4.2.5 Usage with limited hearing |
Supports |
The product does not contain any audio content that requires hearing. |
4.2.6 Usage without vocal capability |
Supports |
The product does not require user speech. |
4.2.7 Usage with limited manipulation or strength |
Partially Supports |
Some functionality within the product is inaccessible to users with limited manipulation or strength, as shown in 2.1.1 Keyboard and 2.4.3 Focus Order. |
4.2.8 Usage with limited reach |
Partially Supports |
Some functionality within the product is inaccessible to users with limited reach, as shown in 2.1.1 Keyboard. |
4.2.9 Minimize photosensitive seizure triggers |
Supports |
The product does not contain any flashing content. |
4.2.10 Usage with limited cognition |
Partially Supports |
Some features of the product will present challenges for users with cognitive impairments, as noted in 2.4.3 Focus Order. |
4.2.11 Privacy |
Supports |
The product does not contain accessibility components that compromise the privacy of the user. |
Chapter 5: Generic Requirements
Notes:
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
5.1.3.1 General |
Supports |
The product does not have closed functionality. |
5.1.3.2 Auditory output delivery including speech |
Supports |
The product does not have closed functionality. |
5.1.3.3 Auditory output correlation |
Supports |
The product does not have closed functionality. |
5.1.3.4 Speech output user control |
Supports |
The product does not have closed functionality. |
5.1.3.5 Speech output automatic interruption |
Supports |
The product does not have closed functionality. |
5.1.3.6 Speech output for non-text content |
Supports |
The product does not have closed functionality. |
5.1.3.7 Speech output for video information |
Supports |
The product does not have closed functionality. |
5.1.3.8 Masked entry |
Supports |
The product does not have closed functionality. |
5.1.3.9 Private access to personal data |
Supports |
The product does not have closed functionality. |
5.1.3.10 Non-interfering audio output |
Supports |
The product does not have closed functionality. |
5.1.3.11 Private listening |
Supports |
The product does not have closed functionality. |
5.1.3.12 Speaker volume |
Supports |
The product does not have closed functionality. |
5.1.3.13 Volume reset |
Supports |
The product does not have closed functionality. |
5.1.3.14 Spoken languages |
Supports |
The product does not have closed functionality. |
5.1.3.15 Non-visual error identification |
Supports |
The product does not have closed functionality. |
5.1.3.16 Receipts, tickets, and transactional outputs |
Supports |
The product does not have closed functionality. |
5.1.4 Functionality closed to text enlargement |
Supports |
The product does not have closed functionality. |
5.1.6.1 Closed functionality |
See 5.1.3.1 through 5.1.3.16 |
See information in 5.1.3.1 through 5.1.3.16 |
5.1.6.2 Input focus |
Supports |
The product does not have functionality that is closed to keyboards. |
5.2 Activation of accessibility features |
Supports |
The product does not have accessibility features requiring activation. |
5.3 Biometrics |
Supports |
The product does not rely on biological characteristics. |
5.4 Preservation of accessibility information during conversion |
Supports |
The product does not convert information or communication. |
5.5.1 Means of operation |
Supports |
This product does not have operable parts. |
5.5.2 Operable parts discernibility |
Supports |
This product does not have operable parts. |
5.6.1 Tactile or auditory status |
Supports |
This product does not have locking or toggle controls. |
5.6.2 Visual status |
Supports |
This product does not have locking or toggle controls. |
5.7 Key repeat |
Supports |
The product relies on platform software to supply key repeat functionality. |
5.8 Double-strike key acceptance |
Supports |
The product does not, by itself, supply a keyboard or keypad. |
5.9 Simultaneous user actions |
Supports |
Simultaneous user actions are not required to operate the product. |
Chapter 6: ICT with Two-Way Voice Communication
Notes: Not Applicable
Chapter 7: ICT with Video Capabilities
Notes:
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
7.1.1 Captioning playback |
Supports |
The product does not contain any audio content within video content that would require captions. |
7.1.2 Captioning synchronization |
Supports |
The product does not contain any audio content within video content that would require captions. |
7.1.3 Preservation of captioning |
Supports |
The product does not contain any audio content within video content that would require captions. |
7.2.1 Audio description playback |
Supports |
The product does not contain video content with audio that would require being described with Audio Description. |
7.2.2 Audio description synchronization |
Supports |
The product does not contain video content with audio that would require being described with Audio Description. |
7.2.3 Preservation of audio description |
Supports |
The product does not contain video content with audio that would require being described with Audio Description. |
7.3 User controls for captions and audio description |
Supports |
The product does not contain audio or video content with audio that would require captions or Audio Description. |
Chapter 8: Hardware
Notes: Not Applicable
Chapter 9: Web (see WCAG 2.x section)
Notes:
Chapter 10: Non-web Documents
Notes: Not Applicable
Chapter 11: Software
Notes:
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
11.1.1.1 through 11.4.1.3 |
See WCAG 2.x section |
See information in WCAG 2.x section. |
11.5.2.3 Use of accessibility services |
Supports |
The product uses the native platform accessibility APIs to expose content to assistive technologies. |
11.5.2.4 Assistive technology |
Not Applicable |
This product is not assistive technology. |
11.5.2.5 Object information |
Partially Supports |
The product lacks role, state, and/or accessible name information for many functional components as described in 1.3.1 Info and Relationships and 4.1.2 Name, Role, Value. |
11.5.2.6 Row, column, and headers |
Supports |
The product does not contain data tables. |
11.5.2.7 Values |
Partially Supports |
The role, name or values of many input controls in the product are not programmatically determinable, as noted in 4.1.2 Name, Role, Value. |
11.5.2.8 Label relationships |
Supports |
The product exposes label relationships to assistive technology. |
11.5.2.9 Parent-child relationships |
Partially Supports |
The product includes some hierarchical relationships that are misidentified, as noted in 1.3.1 Info and Relationships. |
11.5.2.10 Text |
Supports |
Text content, text attributes, and text boundaries are programmatically determinable. |
11.5.2.11 List of available actions |
Supports |
Actions that an object can perform are exposed. |
11.5.2.12 Execution of available actions |
Partially Supports |
The product allows assistive technology to programmatically execute actions on objects, subject to exceptions as described in 1.3.1 Info and Relationships, 2.1.1 Keyboard and 4.1.2 Name, Role, Value. |
11.5.2.13 Tracking of focus and selection attributes |
Partially Supports |
The keyboard focus indicator is visible on most interactive components. Exceptions are described in 2.4.7 Focus Visible. |
11.5.2.14 Modification of focus and selection attributes |
Partially Supports |
Most components receive focus in a meaningful order. Exceptions are described in 2.4.3 Focus Order. |
11.5.2.15 Change notification |
Supports |
When components in the product change their programmatic states and values, the changes are available to assistive technology. |
11.5.2.16 Modifications of states and properties |
Supports |
The product does allow users to modify states or properties of an object using assistive technologies. |
11.5.2.17 Modifications of values and text |
Supports |
The product does allow users to modify values or text of an object using assistive technologies. |
11.6.1 User control of accessibility features |
Supports |
The product is not platform software. |
11.6.2 No disruption of accessibility features |
Supports |
The product does not disrupt platform accessibility features. |
11.7 User preferences |
Partially Supports |
The product honors platform settings for color, contrast, font type and focus cursor but does not honor platform settings for font size as noted in 1.4.4 Resize text. |
11.8.2 Accessible content creation |
See WCAG 2.x section |
See information in WCAG 2.x section. |
11.8.3 Preservation of accessibility information in transformations |
Supports |
The content of an exported PDF is announced in the same order as in the application. |
11.8.4 Repair assistance |
Does Not Support |
The product does not prompt the user to create accessible content. |
11.8.5 Templates |
Does Not Support |
The product does not provide templates that allow for the creation of content that conforms to Level A and Level AA Success Criteria and Conformance Requirements in WCAG 2.1. |
Chapter 12: Documentation and Support Services
Notes: Information regarding Support Documentation and Services is available in the Accessibility Conformance Report for the Adobe Help Center on the Adobe Accessibility Compliance website.
Chapter 13: ICT Providing Relay or Emergency Service Access
Notes: Not Applicable
Voluntary Product Accessibility Template® and VPAT® are a registered trademark of Information Technology Industry Council (ITI)