Adobe Accessibility Conformance Report International Edition
(Based on VPAT® Version 2.5)
Product Information
- Name of Product/Version: Adobe Acrobat Android
- Product Description: Adobe Acrobat is the global standard for reliably viewing, signing, and commenting on PDF documents
- Date: July 2025
- Contact information: access@adobe.com
- Notes: This report was created by Deque Systems Inc. upon completion of an accessibility evaluation performed in June 2025.
- Evaluation Methods Used: Testing Adobe Acrobat Android involved extensive use of leading assistive technology such as screen readers, screen magnifiers, and speech recognition software. 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
Level A (Yes)
Level AA (Yes)
Level AAA (No )
Level A (Yes)
Level AA (Yes)
Level AAA (No )
Level A (Yes)
Level AA (Yes)
Level AAA (No )
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 only be used in WCAG Level AAA criteria.
WCAG 2.2 Report
Tables 1 and 2 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.2 Success Criteria, they are scoped for full pages, complete processes, and accessibility-supported ways of using technology as documented in the WCAG 2.2 Conformance Requirements.
Table 1: Success Criteria, Level A
Notes:
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.
1.1.1 Non-text Content (Level A)
Also applies to:
EN 301 549 Criteria
- 9.1.1.1 (Web)
- 10.1.1.1 (Non-web document)
- 11.1.1.1.1 (Open Functionality Software)
- 11.1.1.1.2 (Closed Functionality Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
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: Combine a PDF; Help; Home Screen; In App Purchase: Payment Methods & Google Play; Viewer: Go to Page; Viewer: Print.
An informative image that contains text does not have a text alternative that includes essential text present in the image, so people who are blind and/or use a screen reader will not understand the information conveyed by the image. This occurs on the following page: Help.
Some decorative images are not hidden from screen readers, so people who are blind and/or use a screen reader will have to navigate through unnecessary and duplicative text. This occurs on the following pages: Create a PDF; Files; Onboarding; Select a File.
Guideline 1.2 Time-based Media:
Provide alternatives for time-based media.
1.2.1 Audio-only and Video-only (Prerecorded) (Level A)
Also applies to:
EN 301 549 Criteria
- 9.1.2.1 (Web)
- 10.1.2.1 (Non-web document)
- 11.1.2.1.1 (Open Functionality Software)
- 11.1.2.1.2.1 and 11.1.2.1.2.2 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
1.2.2 Captions (Prerecorded) (Level A)
Also applies to:
EN 301 549 Criteria
- 9.1.2.2 (Web)
- 10.1.2.2 (Non-web document)
- 11.1.2.2 (Open Functionality Software)
- 11.1.2.2 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A)
Also applies to:
EN 301 549 Criteria
- 9.1.2.3 (Web)
- 10.1.2.3 (Non-web document)
- 11.1.2.3.1 (Open Functionality Software)
- 11.1.2.3.2 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
Guideline 1.3 Adaptable:
Create content that can be presented in different ways (for example simpler layout) without losing information or structure.
1.3.1 Info and Relationships (Level A)
Also applies to:
EN 301 549 Criteria
- 9.1.3.1 (Web)
- 10.1.3.1 (Non-web document)
- 11.1.3.1.1 (Open Functionality Software)
- 11.1.3.1.2 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
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 correctly conveyed to assistive technologies and people who are blind and/or use a screen reader. This occurs on the following pages: Home: Search; PDF View Settings; About Adobe Acrobat; Account Settings; Adobe Cloud Storage; AI Assistant; Create a PDF; Files; Help; Open a PDF.
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 occurs on the following pages: Home: Search; Share PDF Workflow; AI Assistant; Combine a PDF; Compress PDF; Create a PDF; Export PDF; Get Adobe Scan; Home Screen; In App Purchase: Payment Methods & Google Play; Onboarding; Share PDF Invite.
Content that does not visually function as a list is marked up as a list, so the structure of the page is misrepresented to and people who are blind and/or use a screen reader or other assistive technology. This occurs on the following pages: Combine a PDF; Get Adobe Scan; Preferences.
Some information, structure, and/or relationships are only presented visually but not conveyed programmatically, so context provided to sighted users is not available to people who are blind. This occurs on the following pages: Comment Thread; Highlight.
A block of content has incorrect semantic markup, so its meaning, structure, or relationships is not conveyed to people who are blind and/or use a screen reader. This occurs on the following page: Help.
A block of text visually styled as deleted or inserted does not have semantic markup or text to indicate programmatically that the text is deleted or inserted, so people who are blind and/or use a screen reader may not be aware that the text is deleted or inserted. This occurs on the following page: Highlight.
1.3.2 Meaningful Sequence (Level A)
Also applies to:
EN 301 549 Criteria
- 9.1.3.2 (Web)
- 10.1.3.2 (Non-web document)
- 11.1.3.2.1 (Open Functionality Software)
- 11.1.3.2.2 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
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 the reading order on a page or have no content/functionality. This occurs on the following pages: Add Mobile number; Comment; Comment Thread; Compress PDF; Help; Liquid Mode View PDF; Open a PDF; Share PDF Workflow; Share via Link.
Screen reader focus does not follow the visual focus order or does not move to the intended target, so the reading order for people who are blind and/or use a screen reader may not follow the visual organization of the page. This occurs on the following page: AI Assistant.
Screen reader focus is lost or misplaced due to user interaction or content update, making navigation difficult or impossible for people who are blind and/or use a screen reader or other assistive technology. This occurs on the following pages: AI Assistant; Comment Thread.
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 pages: Combine a PDF; Get Adobe Scan; Viewer: Bookmarks & Table of Contents.
The order that the screen reader announces static content does not match the visual order of the content and changes the meaning of that content, so the intended meaning of the content will be lost or changed for people who are blind and/or use a screen reader. This occurs on the following pages: Comment Thread; Draw; Fill and Sign; Highlight; Text.
Screen readers can read content outside some modal dialogs, so people who are blind and/or use a screen reader may become disoriented or confused. This occurs on the following pages: Edit PDF - Add Text; Viewer: Print.
When a modal is closed, screen reader focus is not returned to the control that opened the modal or to another logical location, making navigation difficult for people who are blind and/or use a screen reader. This occurs on the following page: Search for Text in PDF.
1.3.3 Sensory Characteristics (Level A)
Also applies to:
EN 301 549 Criteria
- 9.1.3.3 (Web)
- 10.1.3.3 (Non-web document)
- 11.1.3.3 (Open Functionality Software)
- 11.1.3.3 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
Guideline 1.4 Distinguishable:
Make it easier for users to see and hear content including separating foreground from background.
1.4.1 Use of Color (Level A)
Also applies to:
EN 301 549 Criteria
- 9.1.4.1 (Web)
- 10.1.4.1 (Non-web document)
- 11.1.4.1 (Open Functionality Software)
- 11.1.4.1 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
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. This occurs on the following pages: Sign In; Google Drive; Home: Gmail Connector Account; In App Purchase: Payment Methods & Google Play; Preferences.
Color is used as the only method to convey the state (such as "checked," "pressed," or "selected") of some controls, 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: Comment; Draw; Edit PDF - Add Image; Edit PDF - Add Text; Fill and Sign; Highlight; Liquid Mode View PDF; Text.
1.4.2 Audio Control (Level A)
Also applies to:
EN 301 549 Criteria
- 9.1.4.2 (Web)
- 10.1.4.2 (Non-web document)
- 11.1.4.2 (Open Functionality Software)
- 11.1.4.2 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
Guideline 2.1 Keyboard Accessible:
Make all functionality available from a keyboard.
2.1.1 Keyboard (Level A)
Also applies to:
EN 301 549 Criteria
- 9.2.1.1 (Web)
- 10.2.1.1 (Non-web document)
- 11.2.1.1.1 (Open Functionality Software)
- 11.2.1.1.2 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
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 action. This occurs on the following pages: Combine a PDF; Comment; Crop Pages; Edit PDF - Add Image; Edit PDF - Add Text; Fill and Sign; Generative Summary; Highlight; In App Purchase: Payment Methods & Google Play; Organize Page; Protect a PDF; Text; Text Context and Blank Context Menu; Viewer: Thumbnails.
2.1.2 No Keyboard Trap (Level A)
Also applies to:
EN 301 549 Criteria
- 9.2.1.2 (Web)
- 10.2.1.2 (Non-web document)
- 11.2.1.2 (Open Functionality Software)
- 11.2.1.2 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
Software: This product does not include
keyboard trap.
2.1.4 Character Key Shortcuts (Level A 2.1 and 2.2)
Also applies to:
EN 301 549 Criteria
- 9.2.1.4 (Web)
- 10.2.1.4 (Non-web document)
- 11.2.1.4.1 (Open Functionality Software)
- 11.2.1.4.2 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508 – Does not apply
Software: Supports (Not
Applicable
Guideline 2.2 Enough Time:
Provide users enough time to read and use content.
2.2.1 Timing Adjustable (Level A)
Also applies to:
EN 301 549 Criteria
- 9.2.2.1 (Web)
- 10.2.2.1 (Non-web document)
- 11.2.2.1 (Open Functionality Software)
- 11.2.2.1 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
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 (Level A)
Also applies to:
EN 301 549 Criteria
- 9.2.2.2 (Web)
- 10.2.2.2 (Non-web document)
- 11.2.2.2 (Open Functionality Software)
- 11.2.2.2 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
Guideline 2.3 Seizures:
Do not design content in a way that is known to cause seizures.
2.3.1 Three Flashes or Below Threshold (Level A)
Also applies to:
EN 301 549 Criteria
- 9.2.3.1 (Web)
- 10.2.3.1 (Non-web document)
- 11.2.3.1 (Open Functionality Software)
- 11.2.3.1 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
Guideline 2.4 Navigable:
Provide ways to help users navigate, find content, and determine where they are.
2.4.1 Bypass Blocks (Level A)
Also applies to:
EN 301 549 Criteria
- 9.2.4.1 (Web)
- 10.2.4.1 (Non-web document) – Does not apply
- 11.2.4.1 (Open Functionality Software) – Does not apply
- 11.2.4.1 (Closed Software) – Does not apply
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software) – Does not apply to non-web software
- 504.2 (Authoring Tool)
- 602.3 (Support Docs) – Does not apply to non-web docs
2.4.2 Page Titled (Level A)
Also applies to:
EN 301 549 Criteria
- 9.2.4.2 (Web)
- 10.2.4.2 (Non-web document)
- 11.2.4.2 (Open Functionality Software) - Does not apply
- 11.2.4.2 (Closed Software) – Does not apply
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
2.4.3 Focus Order (Level A)
Also applies to:
EN 301 549 Criteria
- 9.2.4.3 (Web)
- 10.2.4.3 (Non-web document)
- 11.2.4.3 (Open Functionality Software)
- 11.2.4.3 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
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 cause them to become disoriented. This occurs on the following pages: Edit PDF - Add Text; Read Aloud PDF; Viewer: Print.
2.4.4 Link Purpose (In Context) (Level A)
Also applies to:
EN 301 549 Criteria
- 9.2.4.4 (Web)
- 10.2.4.4 (Non-web document)
- 11.2.4.4 (Open Functionality Software)
- 11.2.4.4 (Closed Software
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
Guideline 2.5 Input Modalities:
Make it easier for users to operate functionality through various inputs beyond keyboard.
2.5.1 Pointer Gestures (Level A 2.1 and 2.2)
Also applies to:
EN 301 549 Criteria
- 9.2.5.1 (Web)
- 10.2.5.1 (Non-web document)
- 11.2.5.1 (Open Functionality Software)
- 11.2.5.1 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508 – Does not apply
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; Home Scree; Share PDF Workflow.
2.5.2 Pointer Cancellation (Level A 2.1 and 2.2)
Also applies to:
EN 301 549 Criteria
- 9.2.5.2 (Web)
- 10.2.5.2 (Non-web document)
- 11.2.5.2 (Open Functionality Software)
- 11.2.5.2 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508 – Does not apply
2.5.3 Label in Name (Level A 2.1 and 2.2)
Also applies to:
EN 301 549 Criteria
- 9.2.5.3 (Web)
- 10.2.5.3 (Non-web document)
- 11.2.5.3.1 (Open Functionality Software)
- 11.2.5.3.2 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508 – Does not apply
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 accessible name of an interactive element (such as a link, button, or form input) includes the visible label but has other words interspersed, so people who use speech input to navigate and operate content will not be able to access the element. This occurs on the following page: Fill and Sign.
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, 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: AI Assistant; Combine a PDF; Create Folder Modal; Fill and Sign; Protect a PDF; Share PDF Workflow; Text.
2.5.4 Motion Actuation (Level A 2.1 and 2.2)
Also applies to:
EN 301 549 Criteria
- 9.2.5.4 (Web)
- 10.2.5.4 (Non-web document)
- 11.2.5.4 (Open Functionality Software)
- 11.2.5.4 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508 – Does not apply
Guideline 3.1 Readable:
Make text content readable and understandable.
3.1.1 Language of Page (Level A)
Also applies to:
EN 301 549 Criteria
- 9.3.1.1 (Web)
- 10.3.1.1 (Non-web document)
- 11.3.1.1.1 (Open Functionality Software)
- 11.3.1.1.2 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
Guideline 3.2 Predictable:
Make Web pages appear and operate in predictable ways.
3.2.1 On Focus (Level A)
Also applies to:
EN 301 549 Criteria
- 9.3.2.1 (Web)
- 10.3.2.1 (Non-web document)
- 11.3.2.1 (Open Functionality Software)
- 11.3.2.1 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
3.2.2 On Input (Level A)
Also applies to:
EN 301 549 Criteria
- 9.3.2.2 (Web)
- 10.3.2.2 (Non-web document)
- 11.3.2.2 (Open Functionality Software)
- 11.3.2.2 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
3.2.6 Consistent Help (Level A 2.2 only)
EN 301 549 Criteria – Does not apply
Revised Section 508 – Does not apply
Guideline 3.3 Input Assistance:
Help users avoid and correct mistakes.
3.3.1 Error Identification (Level A)
Also applies to:
EN 301 549 Criteria
- 9.3.3.1 (Web)
- 10.3.3.1 (Non-web document)
- 11.3.3.1.1 (Open Functionality Software)
- 11.3.3.1.2 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
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 (Level A)
Also applies to:
EN 301 549 Criteria
- 9.3.3.2 (Web)
- 10.3.3.2 (Non-web document)
- 11.3.3.2 (Open Functionality Software)
- 11.3.3.2 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
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 (Level A 2.2 only)
EN 301 549 Criteria – Does not apply
Revised Section 508 – Does not apply
Guideline 4.1 Compatible:
Maximize compatibility with current and future user agents, including assistive technologies.
4.1.1 Parsing (Level A)
Applies to:
WCAG 2.0 and 2.1 – Always answer ‘Supports’
WCAG 2.2 (obsolete and removed) - Does not apply
EN 301 549 Criteria
- 9.4.1.1 (Web)
- 10.4.1.1 (Non-web document)
- 11.4.1.1.1 (Open Functionality Software)
- 11.4.1.1.2 (Closed Software) – Does not apply
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
4.1.2 Name, Role, Value (Level A)
Also applies to:
EN 301 549 Criteria
- 9.4.1.2 (Web)
- 10.4.1.2 (Non-web document)
- 11.4.1.2.1 (Open Functionality Software)
- 11.4.1.2.2 (Closed Software) – Does not apply
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
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 people who are blind and/or use a screen reader or other assistive technology may not be able to understand the purpose of each form control or what input it requires. 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 programmatic state of some elements that reveal or hide content ("expanded" or "collapsed") is missing or is used incorrectly, so people who are blind and/or use a screen reader or other assistive technology will not be informed of the current state of each element or the state will be misrepresented. This occurs on the following pages: Share PDF Workflow; AI Assistant; Comment; Liquid Mode View PDF; Share via Link; Subscriptions.
Multiple buttons do not have a programmatic name, so each button's name (such as "Submit" or "Cancel") is not conveyed to screen readers and other assistive technologies and will not be available to people who use those technologies. This occurs on the following pages: Sign In; Add Mobile number; Adobe Scan.
Multiple controls have an incorrect programmatic state, so each control's state (like "checked"/"unchecked" or "expanded"/"collapsed") conveyed to screen readers and other assistive technologies is incorrect and misrepresents that control's state and functionality to people who use those technologies. This occurs on the following pages: Home: Gmail Connector Access; Add Mobile number.
Multiple controls do not have a programmatic state, so each control's state (like "checked"/"unchecked" or "expanded"/"collapsed") is not conveyed to screen readers and other assistive technologies and the control's state and functionality is not available to people who use those technologies. This occurs on the following pages: AI Assistant; Generative Summary.
Some informative static text is assigned an interactive role that is announced by a screen reader, so people who are blind and/or use a screen reader may be confused. This occurs on the following pages: Comment Thread; Compress PDF; PDF from Emails; Save a copy.
A control has an incorrect programmatic role, so the role (like "button" or "link") conveyed to screen readers and other assistive technologies is incorrect and misrepresents the control's function to people who use those technologies. This occurs on the following page: Subscriptions.
Multiple buttons do not have a programmatic role, so each button's 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: Create a PDF; Crop Pages; Open a PDF; Select a File; Files.
When a control (such as a button) is disabled, its disabled 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 control is disabled. This occurs on the following page: Crop Pages.
An element that looks like a 2-state toggle switch does not behave like one, so people who are blind and/or use a screen reader may not be able to understand the purpose of the element or how to use it. This occurs on the following screen: Share PDF Workflow.
An element that looks like a radio button does not behave like one, so people who are blind and/or use a screen reader may not be able to understand the purpose of the element or how to use it. This occurs on the following screen: In App Purchase.
An element that looks like a text input field (EditText) does not behave like one, so people who are blind and/or use a screen reader may not be able to understand the purpose of the element or how to use it. This occurs on the following screen: Edit PDF - Add Text.
Multiple controls do not have a programmatic role, so each control's 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: Create a PDF; Generative Summary.
Table 2: Success Criteria, Level AA
Notes:
1.2.4 Captions (Live) (Level AA)
Also applies to:
EN 301 549 Criteria
- 9.1.2.4 (Web)
- 10.1.2.4 (Non-web document)
- 11.1.2.4 (Open Functionality Software)
- 11.1.2.4 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
1.2.5 Audio Description (Prerecorded) (Level AA)
Also applies to:
EN 301 549 Criteria
- 9.1.2.5 (Web)
- 10.1.2.5 (Non-web document)
- 11.1.2.5 (Open Functionality Software)
- 11.1.2.5 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
1.3.4 Orientation (Level AA 2.1 and 2.2)
Also applies to:
EN 301 549 Criteria
- 9.1.3.4 (Web)
- 10.1.3.4 (Non-web document)
- 11.1.3.4 (Open Functionality Software)
- 11.1.3.4 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508 – Does not apply
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 (Level AA 2.1 and 2.2)
Also applies to:
EN 301 549 Criteria
- 9.1.3.5 (Web)
- 10.1.3.5 (Non-web document)
- 11.1.3.5.1 (Open Functionality Software)
- 11.1.3.5.2 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508 – Does not apply
1.4.3 Contrast (Minimum) (Level AA)
Also applies to:
EN 301 549 Criteria
- 9.1.4.3 (Web)
- 10.1.4.3 (Non-web document)
- 11.1.4.3 (Open Functionality Software)
- 11.1.4.3 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
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: Viewer: Print.
The color contrast ratio between placeholder text in multiple inputs and each 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: Home: Search; Comment Thread; Search for Text in PDF; Share PDF Invite.
1.4.4 Resize text (Level AA)
Also applies to:
EN 301 549 Criteria
- 9.1.4.4 (Web)
- 10.1.4.4 (Non-web document)
- 11.1.4.4.1 (Open Functionality Software)
- 11.1.4.4.2 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
1.4.5 Images of Text (Level AA)
Also applies to:
EN 301 549 Criteria
- 9.1.4.5 (Web)
- 10.1.4.5 (Non-web document)
- 11.1.4.5.1 (Open Functionality Software)
- 11.1.4.5.2 (Closed Software) – Does not apply
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
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 (Level AA 2.1 and 2.2)
Also applies to:
EN 301 549 Criteria
- 9.1.4.10 (Web)
- 10.1.4.10 (Non-web document)
- 11.1.4.10 (Open Functionality Software)
- 11.1.4.10 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508 – Does not apply
1.4.11 Non-text Contrast (Level AA 2.1 and 2.2)
Also applies to:
EN 301 549 Criteria
- 9.1.4.11 (Web)
- 10.1.4.11 (Non-web document)
- 11.1.4.11 (Open Functionality Software)
- 11.1.4.11 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508 – Does not apply
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 Connector Access; Preferences; Share PDF Invite; Share PDF Workflow; Text; Viewer: Print.
The indicators for the state of some interactive elements (like checkboxes or radio buttons) do 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 state of the interactive elements. This occurs on the following pages: Comment Thread; Preferences; Viewer: Print.
Some icons (or parts of an icon required to understand its content) do not have a 3:1 color contrast ratio with the background or adjacent colors, so people who are colorblind or have low vision may not be able understand the information presented by each icon. This occurs on the following pages: Comment; Comment Thread; Crop Pages; Help; Home Screen; Viewer: Go to Page; Viewer: Print.
Some images or graphics (like a chart) or parts of the image/graphic required to understand its content do not have a 3:1 color contrast ratio with the background or adjacent colors, so people who are colorblind or have low vision may not be able understand the information presented by the image/graphic. This occurs on the following pages: AI Assistant; Read Aloud PDF; Search for Text in PDF; Text Context and Blank Context Menu.
1.4.12 Text Spacing (Level AA 2.1 and 2.2)
Also applies to:
EN 301 549 Criteria
- 9.1.4.12 (Web)
- 10.1.4.12 (Non-web document)
- 11.1.4.12 (Open Functionality Software)
- 11.1.4.12 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508 – Does not apply
1.4.13 Content on Hover or Focus (Level AA 2.1 and 2.2)
Also applies to:
EN 301 549 Criteria
- 9.1.4.13 (Web)
- 10.1.4.13 (Non-web document)
- 11.1.4.13 (Open Functionality Software)
- 11.1.4.13 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508 – Does not apply
2.4.5 Multiple Ways (Level AA)
Also applies to:
EN 301 549 Criteria
- 9.2.4.5 (Web)
- 10.2.4.5 (Non-web document) – Does not apply
- 11.2.4.5 (Open Functionality Software) – Does not apply
- 11.2.4.5 (Closed Software) – Does not apply
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software) – Does not apply to non-web software
- 504.2 (Authoring Tool)
- 602.3 (Support Docs) – Does not apply to non-web docs
software.
2.4.6 Headings and Labels (Level AA)
Also applies to:
EN 301 549 Criteria
- 9.2.4.6 (Web)
- 10.2.4.6 (Non-web document)
- 11.2.4.6 (Open Functionality Software)
- 11.2.4.6 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
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 understand what a control does or what data to enter. This occurs on the following pages: Adobe Cloud Storage; Combine a PDF; Comment Thread; Edit PDF - Add Image; Edit PDF - Add Text; In App Purchase; In App Purchase: Payment Methods & Google Play; Organize Page; PDF from Emails; Protect a PDF; Viewer: Bookmarks and Table of Content.
Multiple buttons have identical programmatic labels but different functionality, and there is no programmatic context, so people who are blind and/or use a screen reader will not know or may be confused or misled about what each button does. This occurs on the following pages: Home: Search; Adobe Cloud Storage; Combine a PDF; Crop Pages; Home Screen; Home: Shared; Share PDF Invite.
2.4.7 Focus Visible (Level AA)
Also applies to:
EN 301 549 Criteria
- 9.2.4.7 (Web)
- 10.2.4.7 (Non-web document)
- 11.2.4.7 (Open Functionality Software)
- 11.2.4.7 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
software.
2.4.11 Focus Not Obscured (Minimum) (Level AA 2.2 only)
EN 301 549 Criteria – Does not apply
Revised Section 508 – Does not apply
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 (Level AA 2.2 only)
EN 301 549 Criteria – Does not apply
Revised Section 508 – Does not apply
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) (Level AA 2.2 only)
EN 301 549 Criteria – Does not apply
Revised Section 508 – Does not apply
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. making it difficult for users with hand tremors and those who have difficulty with fine motor movement to activate them accurately. This occurs on the following page: Protect a PDF.
3.1.2 Language of Parts (Level AA)
Also applies to:
EN 301 549 Criteria
- 9.3.1.2 (Web)
- 10.3.1.2 (Non-web document)
- 11.3.1.2 (Open Functionality Software) – Does not apply
- 11.3.1.2 (Closed Software) – Does not apply
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
3.2.3 Consistent Navigation (Level AA)
Also applies to:
EN 301 549 Criteria
- 9.3.2.3 (Web)
- 10.3.2.3 (Non-web document) – Does not apply
- 11.3.2.3 (Open Functionality Software) – Does not apply
- 11.3.2.3 (Closed Software) – Does not apply
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software) – Does not apply to non-web software
- 504.2 (Authoring Tool)
- 602.3 (Support Docs) – Does not apply to non-web docs
3.2.4 Consistent Identification (Level AA)
Also applies to:
EN 301 549 Criteria
- 9.3.2.4 (Web)
- 10.3.2.4 (Non-web document) – Does not apply
- 11.3.2.4 (Open Functionality Software) – Does not apply
- 11.3.2.4 (Closed Software) – Does not apply
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software) – Does not apply to non-web software
- 504.2 (Authoring Tool)
- 602.3 (Support Docs) – Does not apply to non-web docs
3.3.3 Error Suggestion (Level AA)
Also applies to:
EN 301 549 Criteria
- 9.3.3.3 (Web)
- 10.3.3.3 (Non-web document)
- 11.3.3.3 (Open Functionality Software)
- 11.3.3.3 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
3.3.4 Error Prevention (Legal, Financial, Data) (Level AA)
Also applies to:
EN 301 549 Criteria
- 9.3.3.4 (Web)
- 10.3.3.4 (Non-web document)
- 11.3.3.4 (Open Functionality Software)
- 11.3.3.4 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508
- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)
3.3.8 Accessible Authentication (Minimum) (Level AA 2.2 only)
EN 301 549 Criteria – Does not apply
Revised Section 508 – Does not apply
4.1.3 Status Messages (Level AA 2.1 and 2.2)
Also applies to:
EN 301 549 Criteria
- 9.4.1.3 (Web)
- 10.4.1.3 (Non-web document)
- 11.4.1.3 (Open Functionality Software)
- 11.4.1.3 (Closed Software) – Does not apply
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508 – Does not apply
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.
Table 3: Success Criteria, Level AAA
Notes: Not Applicable
Revised Section 508 Report
Notes:
Chapter 3: Functional Performance Criteria (FPC)
Notes:
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
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.4.1 Use of Color
1.4.3 Contrast (minimum)
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
3.3.1 Error Identification
3.3.2 Labels or Instructions
4.1.2 Name, Role, Value
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)
Software: Most functionality is usable with limited manipulation and does not require fine motor control or simultaneous manual operations. Exceptions include:
2.1.1 Keyboard
2.2.1 Timing Adjustable
2.4.3 Focus Order
2.4.6 Headings and Labels
4.1.2 Name, Role, Value
Software: Most functions of the product are usable 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.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
3.3.1 Error Identification
3.3.2 Labels or Instructions
4.1.2 Name, Role, Value
The product exposes the name, role and state or value of most objects to assistive technology. Exceptions include:
4.1.2 Name, Role, Value
The product allows assistive technology to modify states and properties of some controls and inputs. Exceptions include:
4.1.2.a Name, Role, Value
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
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
The product UI exposes most label relationships to assistive technologies. Exceptions include:
4.1.2 Name, Role, Value
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
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
The product allows assistive technology to perform all actions on objects. Exceptions include:
2.1.1 Keyboard
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
The product notifies assistive technology to most user interaction events. Exceptions include:
4.1.3.a Status Messages
The product does not provide authoring features that support or require prompting for accessible content creation.Chapter 6: Support Documentation and Services
Notes:
EN 301 549 Report
Chapter 4: Functional Performance Statements (FPS)
Notes:
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
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
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
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
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
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 Identification
3.3.2 Labels or Instructions
4.1.2 Name, Role, Value
4.1.3 Status Messages
Chapter 5: Generic Requirements
Notes:
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.
Chapter 6: ICT with Two-Way Voice Communication
Notes: Not Applicable
Chapter 7: ICT with Video Capabilities
Notes: Not Applicable
Chapter 8: Hardware
Notes: The ICT covered by this report is not hardware. As such, the requirements of this chapter do not apply.
Chapter 9: Web (see WCAG 2.2 section)
Notes:
Chapter 10: Non-Web Documents
Notes: Not Applicable
Chapter 11: Software
Notes:
The product exposes the name, role and state or value of most objects to assistive technology. Exceptions include:
4.1.2 Name, Role, Value
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
The product UI exposes most label relationships to assistive technologies. Exceptions include:
4.1.2 Name, Role, Value
For most objects the product exposes hierarchical parent-child relationships to assistive technology. Exceptions include:
1.3.1 Info and Relationships.
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
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
The product allows assistive technology to perform all actions on objects. Exceptions include:
2.1.1 Keyboard
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
The product notifies assistive technology to most user interaction events. Exceptions include:
4.1.3.a Status Messages
The product allows assistive technology to modify states and properties of some controls and inputs. Exceptions include:
4.1.2.a Name, Role, Value
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
The product does not provide authoring features that support or require prompting for accessible content creation.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 13: ICT Providing Relay or Emergency Service Access
Notes: Not Applicable