Adobe Accessibility Conformance Report International Edition
(Based on VPAT® Version 2.5)
Product Information
- Name of Product/Version: Adobe Acrobat iOS
- 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 iOS 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:
A decorative image is 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 screens: Create Account 2.
An informative image does not have a text alternative, so people who are blind and/or use a screen reader will not be able to access the information conveyed the image. This occurs on the following screens: Home Screen; Social Sign in: Google; Create Account 1.
An image that acts as a link or control does not have a text alternative, so people who are blind and/or use a screen reader will not understand the function performed by the image. This occurs on the following screens: Subscriptions; Help and Support.
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:
A block of text is marked up as a heading but is not a heading, so the structure of the content is misrepresented to assistive technologies and people who are blind and/or use a screen reader. This occurs on the following screens: Home Screen; Home: Search; In App Purchase: Payment Methods & Google Play; Liquid Mode View 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 screens: AI Assistant; Fill and Sign; Read comment; Home Screen; Protect a PDF; Subscriptions; Social Sign in: Google; Save a Copy; Export PDF; Compress PDF; Share via Link; Open a PDF; Adobe Cloud Storage; Combine a PDF; Local Acrobat; In App Purchase: Payment Methods & Google Play; User Profile; Preferences; PDF from Emails; Adobe Scan; Create a PDF; Provide Feedback on Acrobat; About Adobe Acrobat; Select Items.
Content that is visually presented as a list is not marked up as a list, so the presence and structure of the list are not conveyed to assistive technologies and people who are blind and/or use a screen reader. This occurs on the following screen: Create Account 1.
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 screen: Highlight.
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 screens: Read comment; Comment; 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:
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 screen: Create Account 2.
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 screens: Read comment; Comment; Combine a PDF.
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 screens: Text; AI Assistant; Edit PDF - Add Text; Adobe Cloud Storage; Local Acrobat; In App Purchase: Payment Methods & Google Play; Adobe Scan; Organize Page; PDF View Settings.
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 screens: AI Assistant; Fill and Sign; Home Screen; Protect a PDF; Print; Share via Link; Open a PDF; Files: Recent; Highlight; Files: Shared; Create Folder Modal; Files; Account Settings; One Drive Connector
The correct reading order of dynamically changing content is not programmatically determinable by screen readers, so people who are blind and/or use a screen reader may not be made aware of new or changed content that is dynamically added to a page. This occurs on the following screens: Edit PDF - Add Text; Fill and Sign.
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 screens: Fill and Sign; Edit PDF - Add Text; Files: Recent; Draw; Highlight.
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 screens: Sign In; Social Sign in: Google; Create Account 2; Create Account 1; One Drive Connector.
Color is used as the only method to convey the state (such as "checked," "pressed," or "selected”) of a control, 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 screens: Text; Fill and Sign; Edit PDF - Add Text; Export PDF; Open a PDF; Draw; Highlight; Edit PDF - Add Image.
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 screens: AI Assistant; Home Screen; Adobe Cloud Storage; Home: Search; Local Acrobat; Preferences; Adobe Scan; Organize Page; Files: Shared.
An action cannot be performed when using voice control, so people who rely on voice control to navigate and operate content cannot perform that action. This occurs on the following screens: AI Assistant; Home Screen; Save a Copy; Onboarding; Open a PDF; Adobe Cloud Storage; Home: Search; Comment; Combine a PDF; Highlight; Local Acrobat; Files: Shared; Preferences; PDF from Emails; Adobe Scan; Files; Create a PDF; Provide Feedback on Acrobat; Generative Summary; AI Assistant.
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 screens: Text; Fill and Sign; Comment; Highlight.
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)
Software: On most pages where moving, blinking, scrolling, or auto-updating information is present, that information can be paused, stopped, hidden, or otherwise controlled by the user.
Exceptions include:
The user cannot pause, stop, or hide moving or blinking content, so people who cannot read text quickly or track moving objects, have attention deficit disorders or other cognitive disabilities, or use a screen reader may not be able to read or understand the content. This occurs on the following screen: Onboarding.
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)
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 screens: AI Assistant; Home Screen; Send a Copy; Print; Open a PDF; Crop Pages.
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:
The accessible name of an interactive element (such as a link, button, or form input) does not contain the visible label, so people who use speech input to navigate and operate content will not be able to access the element. This occurs on the following screens: Create Folder Modal; Provide Feedback on Acrobat; Liquid Mode View PDF.
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 screens: Text; Go to Page; Edit PDF - Add Text; Print; Combine a PDF.
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:
An error for a form input (such as a text input field, radio button, select dropdown, or checkbox) is 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 screen: Create Account 2.
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:
The label of an element is not persistent (always visible on the page), so the element's purpose may be difficult to discover. This occurs on the following screens: Social Sign in: Facebook; One Drive Connector; Invite People.
The label for a form field is missing, so the field's purpose is not clear. This occurs on the following screens: Edit PDF - Add Text; Social Sign in: Google; 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 some product functions do not provide programmatic [name, role, state, or value] information.
Examples include:
A button does not have a programmatic name, so its 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 screen: Generative Summary.
A button does not have a programmatic role, so its role (usually button, but sometimes link or something else) is not conveyed to screen readers and other assistive technologies and will not be available to people who use those technologies. This occurs on the following screens: Home Screen; Edit PDF - Add Text; Print; Export PDF; Home: Search; Comment; Highlight; Select Items; Organize Page; Invite People; Pages.
An element that looks like a modal dialog (UIAlertController) 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 interact with it. This occurs on the following screen(s): Protect a PDF; Save a Copy; Export PDF; Compress PDF; Onboarding; Combine a PDF; Recognize Text; In App Purchase: Payment Methods & Google Play; Onboarding Trial; Provide Feedback on Acrobat.
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 screens: AI Assistant; Print.
A control (such as a button or link) does not have a programmatic name, so its 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 screen: Edit PDF - Add Text.
A form control (such as a text input field or checkbox) is not programmatically associated with its visible label, so people who are blind and/or use a screen reader or other assistive technology may not be able to understand the purpose of the form control or what input it requires. This occurs on the following screens: Text; Go to Page; Edit PDF - Add Text; Print; Combine a PDF; Invite People.
When a button is selected, its 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 button is selected. This occurs on the following screens: AI Assistant; Edit PDF - Add Text; Open a PDF.
A control does not have a programmatic state, so the 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 screens: Files: Recent; Generative Summary.
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 screen: Invite People.
A control has an incorrect programmatic state, so the control's state (like "checked"/"unchecked" or "expanded"/"collapsed") conveyed to screen readers and other assistive technologies is incorrect and misrepresents the control's state and functionality to people who use those technologies. This occurs on the following screen: Subscriptions.
Multiple elements do not have an attribute in their code that will provide its programmatic role to assistive technology or the role assigned is not correct (like assigning a button the role of "checkbox"), so people who are blind and/or use a screen reader or other assistive technology may not be able to understand the name, purpose, or content of the element or how to interact with it. This occurs on the following screens: Bell Notification; Save a Copy; Combine a PDF; Files: Shared; Files; 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
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 placeholder text in an input and the input's background is less than 4.5:1, so people who are colorblind or have low vision may have difficulty reading the placeholder text. This occurs on the following screens: AI Assistant; Social Sign in: Facebook; Files: Recent; Preferences; Create Folder Modal; Invite People.
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 screens: Search for Text in PDF; Read comment; Bell Notification; Go to Page; Social Sign in: Facebook; Send a Copy; Edit PDF - Add Text; Print; Files: Recent; In App Purchase: Payment Methods & Google Play; Photos; Create Folder Modal; Files: Recent.
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)
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 screens: Text; AI Assistant; Fill and Sign; Protect a PDF; Social Sign in: Facebook; Edit PDF - Add Text; Print; Files: Recent; Home: Search; Highlight; One Drive Connector; In App Purchase: Payment Methods & Google Play; Photos; Preferences; Onboarding Trial; Read Aloud Feedback; PDF View Settings; Crop Pages.
An icon (or part of the icon required to understand its content) does 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 icon. This occurs on the following screens: Bookmarks; Text; Home Screen; Share via Link; Open a PDF; Adobe Cloud Storage; Comment; Combine a PDF; Highlight; Local Acrobat; In App Purchase: Payment Methods & Google Play; Files: Shared; Photos; Adobe Scan; Files; Invite People; Liquid Mode View PDF; PDF View Settings.
The indicator for the state of an interactive element (like a checkbox or radio button) 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 state of the interactive element. This occurs on the following screens: Search for Text in PDF; AI Assistant; Read comment; Print; Export PDF; Open a PDF; Adobe Cloud Storage; Adobe Scan; Read Aloud Feedback; Local Acrobat; Photos.
An image or graphic (like a chart) or part of the image/graphic required to understand its content does 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 screen: AI Assistant.
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 programmatic label for a control or form input field does not convey the purpose of the control or input, so people who are blind and/or use a screen reader may not understand what the control does or what data to enter. This occurs on the following screens: Bell Notification; Home Screen; Subscriptions; Edit PDF - Add Text; Print; Create Account 2; Adobe Cloud Storage; Combine a PDF; Local Acrobat; In App Purchase: Payment Methods & Google Play; Photos; Select Items; Adobe Scan; Organize Page; Onboarding Trial; Provide Feedback on Acrobat; Home: Search.
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 screens: Read comment; Home Screen; Comment.
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.
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 screens: Edit PDF - Add Text; Combine a PDF; 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 in line 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 screens: Protect a PDF; Social Sign in: Facebook.
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)
Software: On most pages, the language of each section of content that is different from the default language of the page is correctly identified and can be determined programmatically.
Exceptions include:
A portion of content on a page that is in a different language from the rest of the content on the page is not programmatically assigned the language for that portion of content, so screen readers may mispronounce that part of the content. This occurs on the following screens: Social Sign in: Facebook; Social Sign in: Google.
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)
Software: Where input errors are automatically detected, suggestions for correction are provided to the user in most cases.
Exceptions include
A form field's error message does not suggest how to correct the error, so users may have difficulty determining how to complete the form successfully. This occurs on the following screen: Create Account 2.
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 screens: Sign In; AI Assistant; Fill and Sign; Subscriptions; Social Sign in: Facebook; Create Account 2; Open a PDF; Files: Recent; Comment; Create Account 1; Draw; Highlight; Photos; Select Items; Adobe Scan; Organize Page; Text; Home: Search.
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.6 Headings and Labels
3.1.2 Language of Parts
3.3.1 Error Identification
3.3.3 Error Suggestion
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)
2.1.1 Keyboard
2.2.1 Timing Adjustable
2.4.6 Headings and Labels
3.1.2 Language of Parts
3.3.1 Error Identification
3.3.2 Labels or Instructions
3.3.3 Error Suggestion
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)
3.3.1 Error Identification
Software: Most functions of the product 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.6 Headings and Labels
3.3.3 Error Suggestion
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
2.1.1 Keyboard
2.2.1 Timing Adjustable
2.2.2 Pause, Stop, Hide
2.4.6 Headings and Labels
3.1.2 Language of Parts
3.3.1 Error Identification
3.3.2 Labels or Instructions
3.3.3 Error Suggestion
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.
Exception includes:
4.1.2 Name, Role, Value
The product UI exposes most label relationships to assistive technologies. Exceptions include:
4.1.2 Name, Role, Value
When a page contains elements that have a parent-child relationship, those relationships are programmatically determinable, so they can be perceived by assistive technology.
Exceptions include:
1.3.1 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.1 Info and Relationships
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
Most controls in the product expose programmatic role information and actions which can be taken on objects to assistive technology.
Exceptions include:
1.3.1 Info and Relationships
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 Status Messages
Chapter 6: Support Documentation and Services
Notes: 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: 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.6 Headings and Labels
3.1.2 Language of Parts
3.3.1 Error Identification
3.3.3 Error Suggestion
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.4.1 Use of Color
1.4.3 Contrast (minimum)
1.4.11 Non-Text Contrast
2.1.1 Keyboard
2.2.1 Timing Adjustable
2.4.6 Headings and Labels
3.1.2 Language of Parts
3.3.1 Error Identification
3.3.2 Labels or Instructions
3.3.3 Error Suggestion
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
3.3.1 Error Identification
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:
2.1.1 Keyboard
2.2.1 Timing Adjustable
2.4.6 Headings and Labels
2.5.1 Pointer Gestures
2.5.3 Label in Name
3.3.3 Error Suggestion
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:
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.4.1 Use of Color
2.1.1 Keyboard
2.2.1 Timing Adjustable
2.2.2 Pause, Stop, Hide
2.4.6 Headings and Labels
2.5.1 Pointer Gestures
2.5.3 Label in Name
3.1.2 Language of Parts
3.3.1 Error Identification
3.3.2 Labels or Instructions
3.3.3 Error Suggestion
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:
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
When a page contains elements that have a parent-child relationship, those relationships are programmatically determinable, so they can be perceived by assistive technology. Exceptions include:
1.3.1 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.1 Info and Relationships
Most controls in the product expose programmatic role information and actions which can be taken on objects to assistive technology.
Exceptions include:
1.3.1 Info and Relationships
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 Status Messages
The product allows assistive technology to modify states and properties of some controls and inputs. 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
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