Adobe Accessibility Conformance Report
VPAT® Version 2.2 – July 2018
Product Information
Name of Product/Version:
- Adobe Acrobat Pro Continuous (purchased as a subscription license)
- Adobe Acrobat Pro Classic (purchased as a one-time perpetual license)
- Adobe Acrobat Standard Continuous (purchased as a subscription license)
- Adobe Acrobat Standard Classic (purchased as a one-time perpetual license)
- Acrobat Reader
Product Description: Acrobat Pro is designed for creating, editing, collaborating, and distributing PDF documents and forms.
Date: January 5, 2020
Contact information: access@adobe.com
Notes: Tested using the most common user journeys. The following tools were used: Create PDF; Export PDF; Prepare Form; Accessibility; Action List; Edit PDF; Enhance Scans; Organize; Comment; Fill & Sign; Send & Track; Protect.
The information contained in this report applies to the product itself. Information about product help and support documentation related to 602.3 (Support Docs) for Section 508 as published in 2017 is located at: http://www.adobe.com/accessibility/compliance.html.
Evaluation Methods Used: Testing Adobe Acrobat Pro 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 of Accessibility API output.
Applicable Standards/Guidelines
This report covers the degree of conformance for the following accessibility standard/guidelines:
Standard/Guideline |
Included in Report |
---|---|
Web Content Accessibility Guidelines 2.0, at http://www.w3.org/TR/2008/REC-WCAG20-20081211/ |
Level A: Yes |
Revised Section 508 standards as published by the U.S. Access Board in the Federal Register on January 18, 2017 |
Yes |
EN 301 549 Accessibility requirements suitable for public procurement of ICT products and services in Europe, V1.1.2 (2015-04) at http://mandate376.standards.eu/standard |
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.0 Report
All WCAG Sections below also document conformance with:
- EN 301 549: Chapter 9 - Web, Chapter 10 - Non-Web documents, Section 11.2.1- Non-Web Software (excluding closed functionality), and Section 11.2.2 - Non-Web Software (closed functionality).
- 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.0 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)
2017 Section 508
|
Software: Supports Authored Content (PDF): Supports |
Software: The product provides text alternatives for non-text content. Authored Content (PDF): Authors can ensure that content meets this criterion. |
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) Also applies to:
2017 Section 508
|
Software: Supports Authored Content (PDF): Supports |
Software: The product does not contain prerecorded audio-only or video-only media. Authored Content (PDF): Authors can ensure that content meets this criterion. |
1.2.2 Captions (Prerecorded) (Level A) Also applies to:
2017 Section 508
|
Software: Supports Authored Content (PDF): Supports |
Software: The product does not contain prerecorded synchronized media. Authored Content (PDF): Authors can ensure that content meets this criterion. |
1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A) Also applies to:
2017 Section 508
|
Software: Supports Authored Content (PDF): Supports |
Software: The product does not contain prerecorded video content that would require audio description or a media alternative. Authored Content (PDF): Authors can ensure that content meets this criterion. |
1.2.4 Captions (Live) (Level AA)
2017 Section 508
|
Software: Supports Authored Content (PDF): Supports
|
Software: The product does not contain live synchronized media. Authored Content (PDF): Authored content does not contain live synchronized media. |
1.2.5 Audio Description (Prerecorded) (Level AA)
2017 Section 508
|
Software: Supports Authored Content (PDF): Supports |
Software: The product does not contain prerecorded video content that would require audio description. Authored Content (PDF): Authors can ensure that content meets this criterion. |
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) Also applies to:
2017 Section 508
|
Software: Partially Supports Authored Content (PDF): Supports |
Software: Most visual structure and relationship information such as the purpose of a button is provided through object information or in text. Exceptions include:
Authored Content (PDF): Authors can ensure that content meets this criterion. |
1.3.2 Meaningful Sequence (Level A) Also applies to:
2017 Section 508
|
Software: Supports Authored Content (PDF): Supports |
Software: The product presents content in a meaningful sequence. Authored Content (PDF): Authors can ensure that content meets this criterion. |
1.3.3 Sensory Characteristics (Level A) Also applies to:
2017 Section 508
|
Software: Partially Supports Authored Content (PDF): Supports |
Software: Most elements do not rely on the use of one sense to use them. Exceptions include:
Authored Content (PDF): Authors can ensure that content meets this criterion. |
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) Also applies to:
2017 Section 508
|
Software: Supports Authored Content (PDF): Supports |
Software: The application does not rely on the use of color to infer information. Authored Content (PDF): Authors can ensure that content meets this criterion.
|
1.4.2 Audio Control (Level A) Also applies to:
2017 Section 508
|
Software: Supports Authored Content (PDF): Supports |
Software: The product does not contain audio that plays automatically. Authored Content (PDF): Authored content does not contain audio that plays automatically. |
1.4.3 Contrast (Minimum) (Level AA)
2017 Section 508
|
Software: Partially Supports Authored Content (PDF): Supports |
Software: Most text meets minimum contrast requirements. Exceptions include:
Authored Content (PDF): Authors can ensure that content meets this criterion. |
1.4.4 Resize Text (Level AA)
2017 Section 508
|
Software: Supports Authored Content (PDF): Supports |
Software: The product allows the user to zoom PDF content to resize text up to 200 percent without loss of content or functionality. The user can also change text size in the operating system and it will reflect without issues in the application. Authored Content (PDF): As a function of a PDF viewer application, the authored content can be zoomed up to 200 percent without loss of content or functionality. |
1.4.5 Images of Text (Level AA)
2017 Section 508
|
Software: Supports Authored Content (PDF): Supports |
Software: The product uses text instead of images of text. Authored Content (PDF): Authors can ensure that content meets this criterion. |
Guideline 2.1 Keyboard Accessible:
Make all functionality available from a keyboard.
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
2.1.1 Keyboard (Level A) Also applies to:
2017 Section 508
|
Software: Partially Supports Authored Content (PDF): Supports |
Software: Most product functionality can be operated through a keyboard interface if the shortcuts are known to the user. Despite this, there are several items that rely on mouse only interactions. These functions are integral to being able to edit PDFs successfully. These failures include:
Authored Content (PDF): Authors can ensure that content meets this criterion. |
2.1.2 No Keyboard Trap (Level A) Also applies to:
2017 Section 508
|
Software: Partially Supports Authored Content (PDF): Supports |
Software: Most of the product functionality will not trap the keyboard focus. Exceptions include:
Authored Content (PDF): Authors can ensure that content meets this criterion. |
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) Also applies to:
2017 Section 508
|
Software: Supports Authored Content (PDF): Supports |
Software: The product does not contain controls or forms which require precise or minimum timing for operation. Authored Content (PDF): Authors can ensure that content meets this criterion. |
2.2.2 Pause, Stop, Hide (Level A) Also applies to:
2017 Section 508
|
Software: Supports Authored Content (PDF): Supports |
Software: The product does not include elements which move, blink, scroll, or auto-update. Authored Content (PDF): Authors can ensure that content meets this criterion. |
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) Also applies to:
2017 Section 508
|
Software: Supports Authored Content (PDF): Supports |
Software: The product does not contain flashing or blinking animated content. Authored Content (PDF): Authors can ensure that content meets this criterion. |
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) Also applies to:
2017 Section 508
|
Software: Supports Authored Content (PDF): Supports |
Software: This criterion does not apply to non-web software. Authored Content (PDF): This criterion does not apply to non-web documents. |
2.4.2 Page Titled (Level A) Also applies to:
2017 Section 508
|
Software: Supports Authored Content (PDF): Supports |
Software: The titles of the software areas describe their purpose. Authored Content (PDF): Authors can ensure that content meets this criterion. |
2.4.3 Focus Order (Level A) Also applies to:
2017 Section 508
|
Software: Partially Supports Authored Content (PDF): Supports |
Software: Most components receive focus in a meaningful order. Exceptions include:
Authored Content (PDF): Authors can ensure that content meets this criterion. |
2.4.4 Link Purpose (In Context) (Level A) Also applies to:
2017 Section 508
|
Software: Supports Authored Content (PDF): Supports |
Software: The purpose of link text can be determined in context. Authored Content (PDF): Authors can ensure that content meets this criterion. |
2.4.5 Multiple Ways (Level AA)
2017 Section 508
|
Software: Supports Authored Content (PDF): Supports |
Software: This criterion does not apply to non-web software. Authored Content (PDF): This criterion does not apply to non-web documents. |
2.4.6 Headings and Labels (Level AA)
2017 Section 508
|
Software: Supports Authored Content (PDF): Supports |
Software: Headings and labels are descriptive. Authored Content (PDF): Authors can ensure that content meets this criterion. |
2.4.7 Focus Visible (Level AA)
2017 Section 508
|
Software: Partially Supports Authored Content (PDF): Supports |
Software: Most focusable elements have a visible keyboard focus indicator. Exceptions include:
Authored Content (PDF): Authors can ensure that content meets this criterion. |
Guideline 3.1 Readable:
Make text content readable and understandable.
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
3.1.1 Language of Page (Level A)
2017 Section 508
|
Software: Supports Authored Content (PDF): Supports |
Software: The language is programmatically determinable within the product. The language can be set by the user in “Preferences”. Authored Content (PDF): Authors can ensure that content meets this criterion. |
3.1.2 Language of Parts (Level AA)
2017 Section 508
|
Software: Supports Authored Content (PDF): Supports |
Software: Content is only presented in one language at a time. Authored Content (PDF): Authors can ensure that content meets this criterion. |
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) Also applies to:
2017 Section 508
|
Software: Supports Authored Content (PDF): Supports |
Software: Components do not initiate a change of context when focused. Authored Content (PDF): Authors can ensure that content meets this criterion. |
3.2.2 On Input (Level A) Also applies to:
2017 Section 508
|
Software: Supports Authored Content (PDF): Supports |
Software: Changes of context that occur automatically on user input are clearly indicated to the user before invoking them. Authored Content (PDF): Authors can ensure that content meets this criterion. |
3.2.3 Consistent Navigation (Level AA)
2017 Section 508
|
Software: Supports Authored Content (PDF): Supports |
Software: This criterion does not apply to non-web software. Authored Content (PDF): This criterion does not apply to non-web documents. |
3.2.4 Consistent Identification (Level AA)
2017 Section 508
|
Software: Supports Authored Content (PDF): Supports |
Software: This criterion does not apply to non-web software. Authored Content (PDF): This criterion does not apply to non-web documents. |
Guideline 3.3 Input Assistance:
Help users avoid and correct mistakes.
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
3.3.1 Error Identification (Level A) Also applies to:
2017 Section 508
|
Software: Supports Authored Content (PDF): Supports |
Software: Where input errors are automatically detected, such as an invalid date, items in error are identified, error messages are provided as text, and the error(s) are associated with the field for assistive technology to convey to the user. Authored Content (PDF): Authors can ensure that content meets this criterion. |
3.3.2 Labels or Instructions (Level A) Also applies to:
2017 Section 508
|
Software: Partially Supports Authored Content (PDF): Supports |
Software: Most form controls have appropriate labels and help in the product. Exceptions include:
Authored Content (PDF): Authors can ensure that content meets this criterion. |
3.3.3 Error Suggestion (Level AA)
2017 Section 508
|
Software: Supports Authored Content (PDF): Supports |
Software: Where input errors are automatically detected, such as not entering a value that is required in the “Advance Settings” for “Create PDF”, suggestions are provided to the user. Authored Content (PDF): Authors can ensure that content meets this criterion. |
3.3.4 Error Prevention (Legal, Financial, Data) (Level AA)
2017 Section 508
|
Software: Supports Authored Content (PDF): Supports |
Software: The product does not process legal commitments or financial transactions, or modify user-controllable data. Authored Content (PDF): Authors can ensure that content meets this criterion. |
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) Also applies to:
2017 Section 508
|
Software: Supports Authored Content (PDF): Supports |
Software: The software is not implemented using markup languages. Authored Content (PDF): The authored content is not implemented using markup languages. |
4.1.2 Name, Role, Value (Level A) Also applies to:
2017 Section 508
|
Software: Partially Supports Authored Content (PDF): Supports |
Software: Name, role, and value can be programmatically determined for most controls in the Software. Exceptions include:
Authored Content (PDF): Authors can ensure that content meets this criterion. |
Criteria |
Conformance Level |
Remarks and Explanations |
||
---|---|---|---|---|
302.1 Without Vision |
Software: Partially Supports Authored Content (PDF): Supports |
Software: Basic workflows in the product are functional for users without vision. However, as highlighted in 1.3.1 Info and Relationships, 2.1.1 Keyboard, 3.3.2 Labels or Instructions and 4.1.2 Name, Role, Value, there are several elements that are not labelled well.
Authored Content (PDF): Authors can create content which is functional without vision. |
||
302.2 With Limited Vision |
Software: Partially Supports Authored Content (PDF): Supports |
Software: Most content is easy to use with limited vision. Exceptions are listed in 1.4.3 Contrast (Minimum), and 1.3.3 Sensory Characteristics.
Authored Content (PDF): Authors can create content which is functional with limited vision.
|
||
|
Software: Partially Supports Authored Content (PDF): Supports |
|
||
302.4 Without Hearing |
Software: Supports Authored Content (PDF): Supports |
|
||
302.5 With Limited Hearing |
Software: Supports Authored Content (PDF): Supports |
|
||
302.6 Without Speech |
Software: Supports Authored Content (PDF): Supports |
Software: The product does not require user speech. Authored Content (PDF): Authors can create content which is functional without speech. |
||
302.7 With Limited Manipulation |
Software: Partially Supports Authored Content (PDF): Supports |
Software: Most functions of the product are functional for users with limited manipulation who rely on keyboard access. The exceptions are noted in 2.1.1 Keyboard. Authored Content (PDF): Authors can create content which is functional with limited manipulation. |
||
302.8 With Limited Reach and Strength |
Software: Partially Supports Authored Content (PDF): Supports |
|
||
302.9 With Limited Language, Cognitive, and Learning Abilities |
Software: Supports Authored Content (PDF): Supports |
Software: The product provides features for simpler, easier use by individuals with limited cognitive, language, and learning abilities. The product provides icons and supplements these with text. Authored Content (PDF): Authors can create content which is functional with limited cognition. |
Criteria |
Conformance Level |
Remarks and Explanations |
|
---|---|---|---|
501.1 Scope – Incorporation of WCAG 2.0 AA |
See WCAG 2.0 section |
See information in the WCAG 2.0 section. |
|
502.2.1 User Control of Accessibility Features |
Supports |
Accessibility features are included in the product and can be amended to suit the user needs. |
|
502.2.2 No Disruption of Accessibility Features |
Partially Supports |
Keyboard shortcuts used in the application conflict with those used by assistive technology. |
|
502.3.1 Object Information |
Partially Supports |
|
|
502.3.2 Modification of Object Information |
Partially Supports |
|
|
502.3.3 Row, Column, and Headers |
Supports |
Tables used in the application use valid descriptions. |
|
502.3.4 Values |
Supports |
|
|
502.3.5 Modification of Values |
Partially Supports |
|
|
502.3.6 Label Relationships |
Supports |
Labels are associated to the item they refer to. |
|
502.3.7 Hierarchical Relationships |
Supports |
|
|
502.3.8 Text |
Supports |
|
|
502.3.9 Modification of Text |
Partially Supports |
|
|
502.3.10 List of Actions |
Partially Supports |
|
|
502.3.11 Actions on Objects |
Partially Supports |
|
|
502.3.12 Focus Cursor |
Partially Supports |
|
|
502.3.13 Modification of Focus Cursor |
Partially Supports |
|
|
502.3.14 Event Notification |
Does Not Support |
Events are not communicated to assistive technology as noted in 1.3.1 Info and Relationships. |
|
502.4 Platform Accessibility Features |
Partially Supports |
Accessibility features are not wholly supported as shown in the WCAG 2.0 section. |
|
503.2 User Preferences |
Supports |
User preferences are included in the product and can be amended to suit the user needs. |
|
503.3 Alternative User Interfaces |
Does Not Support |
The user can amend preferences but cannot amend the user interface. |
|
503.4.1 Caption Controls |
Not Applicable |
No media is present in the application. |
|
503.4.2 Audio Description Controls |
Not Applicable |
|
|
504.2 Content Creation or Editing |
See WCAG 2.0 section |
|
|
504.2.1 Preservation of Information Provided for Accessibility in Format Conversion |
Supports |
|
|
504.2.2 PDF Export |
Supports |
|
|
504.3 Prompts |
Supports |
|
|
504.4 Templates |
Not Applicable |
|
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.
EN 301 549 Report
Notes:
Chapter 4: 4.2 Functional Performance Statements (FPS)
Notes: According to C.4 Functional Performance, this section is informative only.
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
4.2.1 Usage without vision |
Software: Partially Supports Authored Content (PDF): Supports |
Software: Basic workflows in the product are functional for users without vision. However, as highlighted in 1.3.1 Info and Relationships, 2.1.1 Keyboard, 3.3.2 Labels or Instructions and 4.1.2 Name, Role, Value, there are several elements that are not labelled well. Authored Content (PDF): Authors can create content which is functional without vision. |
4.2.2 Usage with limited vision |
Software: Partially Supports Authored Content (PDF): Supports |
Software: Most content is easy to use with limited vision. Exceptions are listed in 1.4.3 Contrast (Minimum), and 1.3.3 Sensory Characteristics. Authored Content (PDF): Authors can create content which is functional with limited vision. |
4.2.3 Usage without perception of colour |
Software: Partially Supports Authored Content (PDF): Supports |
Software: Most content in the product will be functional for users without perception of color. As noted in 1.4.3 Contrast (Minimum), some exceptions exist. Authored Content (PDF): Authors can create content which is functional without perception of color. |
4.2.4 Usage without hearing |
Software: Supports Authored Content (PDF): Supports |
Software: No functionality within the product requires hearing. Authored Content (PDF): Authors can create content which is functional without hearing. |
4.2.5 Usage with limited hearing |
Software: Supports Authored Content (PDF): Supports |
Software: No functionality within the product requires hearing. Authored Content (PDF): Authors can create content which is functional without hearing. |
4.2.6 Usage without vocal capability |
Software: Supports Authored Content (PDF): Supports |
Software: The product does not require the use of speech. Authored Content (PDF): Authors can create content which is functional without speech. |
4.2.7 Usage with limited manipulation or strength |
Software: Partially Supports Authored Content (PDF): Supports |
Software: Most functions of the product are functional for users with limited manipulation who rely on keyboard access. The exceptions are noted in 2.1.1 Keyboard. Authored Content (PDF): Authors can create content which is functional with limited manipulation. |
4.2.8 Usage with limited reach |
Software: Partially Supports Authored Content (PDF): Supports |
Software: 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. Authored Content (PDF): Authors can create content which is functional with limited reach and strength. |
4.2.9 Minimize photosensitive seizure triggers |
Software: Supports Authored Content (PDF): Supports |
Software: The product provides features for simpler, easier use by individuals with limited cognitive, language, and learning abilities. The product provides icons and supplements these with text. Authored Content (PDF): Authors can create content which is functional with limited cognition. |
4.2.10 Usage with limited cognition |
Software: Partially Supports Authored Content (PDF): Supports |
Software: Basic workflows in the product are functional for users without vision. However, as highlighted in 1.3.1 Info and Relationships, 2.1.1 Keyboard, 3.3.2 Labels or Instructions and 4.1.2 Name, Role, Value, there are several elements that are not labelled well. Authored Content (PDF): Authors can create content which is functional without vision. |
4.2.11 Privacy |
Software: Supports Authored Content (PDF): Supports |
Software: The product does not contain accessibility components that compromise the privacy of the user. Authored Content (PDF): Authored content 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 |
See WCAG 2.0 section |
See information in WCAG 2.0 section. |
5.1.3.2 Auditory output delivery including speech |
Not Applicable |
Auditory output is not included in the application. |
5.1.3.3 Auditory output correlation |
Not Applicable |
Auditory output is not included in the application. |
5.1.3.4 Speech output user control |
Not Applicable |
Speech output is not included in the application. |
5.1.3.5 Speech output automatic interruption |
Not Applicable |
Speech output is not included in the application. |
5.1.3.6 Speech output for non-text content |
Not Applicable |
Speech output is not included in the application. |
5.1.3.7 Speech output for video information |
Not Applicable |
Speech output is not included in the application. |
5.1.3.8 Masked entry |
Supports |
Passwords are masked if set to be masked. |
5.1.3.9 Private access to personal data |
Supports |
Personal data is secure in the application once signed in. |
5.1.3.10 Non-interfering audio output |
Not Applicable |
No audio is part of the application. |
5.1.3.11 Private listening |
Not Applicable |
No audio is part of the application. |
5.1.3.12 Speaker volume |
Not Applicable |
No audio is part of the application. |
5.1.3.13 Volume reset |
Not Applicable |
No audio is part of the application. |
5.1.3.14 Spoken languages |
Not Applicable |
No audio is part of the application. |
5.1.3.15 Non-visual error identification |
Supports |
Errors are defined for assistive technology. |
5.1.3.16 Receipts, tickets, and transactional outputs |
Not Applicable |
No transactions are included in scope. |
5.1.4 Functionality closed to text enlargement |
Supports |
Functionality is not affected by text enlargement. |
5.1.5 Visual output for auditory information |
Not Applicable |
No audio is part of the application. |
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 |
Focus of input elements is shown as expected when not using the keyboard. |
5.2 Activation of accessibility features |
Supports |
The application allows preferences to be set for accessibility. |
5.3 Biometrics |
Not Applicable |
Biometrics are not included in the application. |
5.4 Preservation of accessibility information during conversion |
Authored Content (PDF): Supports |
Authored Content (PDF): Accessibility information is preserved upon conversion. |
5.5.1 Means of operation |
Partially Supports |
Most functions of the product are operable. The exceptions are noted in 2.1.1 Keyboard. |
5.5.2 Operable parts discernibility |
Partially Supports |
Most operable parts are shown as focusable. However, visual focus is not always shown with the keyboard as noted in 2.4.7 Focus Visible. |
5.6.1 Tactile or auditory status |
Not Applicable |
Tactile or auditory status is not included in the application. |
5.6.2 Visual status |
Supports |
Visual status of controls is discernable in the application. |
5.7 Key repeat |
Not Applicable |
No key repeat is found in the application. |
5.8 Double-strike key acceptance |
Not Applicable |
No double-strike key acceptance is found in the application. |
5.9 Simultaneous user actions |
Not Applicable |
Simultaneous user actions are not in the application. |
Chapter 6: ICT with Two-Way Voice Communication
Notes: Not Applicable
Chapter 7: ICT with Video Capabilities
Notes: Not Applicable
Chapter 8: Hardware
Notes: Not Applicable
Chapter 9: Web (see WCAG 2.0 section)
Chapter 10: Non-web Documents
Notes:
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
10.2.1 through 10.2.38 |
See WCAG 2.0 section |
See information in WCAG 2.0 section. |
10.2.39 Caption positioning |
Not Applicable |
|
10.2.40 Audio description timing |
Not Applicable |
|
Chapter 11: Software
Notes:
Criteria |
Conformance Level |
Remarks and Explanations |
---|---|---|
11.2.1 Software success criteria (excluding closed functionality) |
See WCAG 2.0 section |
See information in the WCAG section |
11.2.2 Software success criteria (closed functionality) |
See WCAG 2.0 section |
See information in the WCAG section |
11.3.2.1 Platform accessibility service support for software that provides a user interface |
See 11.3.2.5 through 11.3.2.17 |
See information in 11.3.2.5 through 11.3.2.17 |
11.3.2.2 Platform accessibility service support for assistive technologies |
See 11.3.2.5 through 11.3.2.17
|
See information in 11.3.2.5 through 11.3.2.17
|
11.3.2.3 Use of accessibility services |
Not Applicable |
The accessibility services are not in scope for this audit. |
11.3.2.4 Assistive technology |
Not Applicable |
The ICT is not assistive technology. |
11.3.2.5 Object information |
Partially Supports |
Most objects within the application are defined correctly. However, objects are not always defined correctly as outlined in 1.3.1 Info and Relationships and 4.1.2 Name, Role, Value. |
11.3.2.6 Row, column, and headers |
Supports |
Tables are defined in an accessible way. |
11.3.2.7 Values |
Supports |
Values have a meaningful description. |
11.3.2.8 Label relationships |
Partially Supports |
Most elements are associated with their labels correctly. However, as highlighted in 1.3.1 Info and Relationships, 3.3.2 Labels or Instructions and 4.1.2 Name, Role, Value, there are elements that are not labelled well. |
11.3.2.9 Parent-child relationships |
Partially Supports |
Basic workflows in the product are functional for users without vision. However, as highlighted in 1.3.1 Info and Relationships, 2.1.1 Keyboard, 3.3.2 Labels or Instructions and 4.1.2 Name, Role, Value, there are several elements that are not labelled well and rely on sight to use the tools. |
11.3.2.10 Text |
Supports |
Text is used throughout the application to allow users to understand context. |
11.3.2.11 List of available actions |
Supports |
Menus will provide all available actions within the application and help is available. |
11.3.2.12 Execution of available actions |
Does Not Support |
Most product functionality can be operated with a mouse and some for the keyboard. There are several items that rely on mouse only interactions as outlined in 2.1.1 Keyboard. |
11.3.2.13 Tracking of focus and selection attributes |
Partially Supports |
Most items in the application will show focus or selection. However, visual focus is not always shown with the keyboard as noted in 2.4.7 Focus Visible. |
11.3.2.14 Modification of focus and selection attributes |
Supports |
It is possible to change focus and selection preferences in the application. |
11.3.2.15 Change notification |
Does Not Support |
Visually notifications are catered for. Notifications are not announced to blind users as highlighted in 1.3.1 Info and Relationships. |
11.3.2.16 Modifications of states and properties |
Partially Supports |
Almost every item can be amended. Inbuilt settings cannot be changed and other items outlined in 2.1.1 Keyboard. |
11.3.2.17 Modifications of values and text |
Partially Supports |
Almost every item can be amended. Inbuilt settings cannot be changed and other items outlined in 2.1.1 Keyboard. |
11.4.1 User control of accessibility features |
Supports |
The accessibility features can be amended as required. |
11.4.2 No disruption of accessibility features |
Partially Supports |
The application has lots of keyboard shortcuts that work well. However, single key shortcuts can conflict with assistive technology but the user can amend them. |
11.5 User preferences |
Supports |
Users can change their preferences within the application. |
11.6.2 Accessible content creation (if not authoring tool, enter “not applicable”) |
See WCAG 2.0 section |
See information in the WCAG 2.0 section |
11.6.3 Preservation of accessibility information in transformations |
Does Not Support |
Notifications are not announced to blind users as highlighted in 1.3.1 Info and Relationships. |
11.6.4 Repair assistance |
Supports |
Users can contact the helpdesk or use the inbuilt options to change the application. |
11.6.5 Templates |
Supports |
Templates are used within the application or can be imported. |
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.
Chapter 12: 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)