Adobe Accessibility Conformance Report International Edition
(Based on VPAT® Version 2.5)
Product Information
-
Name of Product/Version: Adobe Acrobat Studio Continuous
Adobe Acrobat Standard Continuous -
Report Dated: May 2026
-
Product Description: Acrobat Studio is an AI-powered PDF and design solution that includes Acrobat Pro, Acrobat AI Assistant, PDF Spaces, and Adobe Express Premium. It gives individuals and teams the tools to work with PDFs, get quick insights, share information, and create on-brand content. Included in this ACR are:
- Adobe Acrobat Pro with Adobe Document Cloud services is the most complete PDF solution for today's multi-device world. Connect with your documents, access essential PDF and e-signature tools, and make collaboration on PDF reviews easy from any device. Work from your computer, mobile device, web browser – or even inside your favorite Microsoft Office apps.
- Acrobat Studio which allows users to turn static files into conversational knowledge hubs, with a personalized AI Assistant for deeper insights.
- PDF Spaces which turns static files into conversational knowledge hubs, with a personalized AI Assistant for deeper insights.
-
Contact information: access@adobe.com
-
Notes: The information contained in this report applies to the product itself. Information about product help and support documentation is located at: http://www.adobe.com/accessibility/compliance.html.
-
Evaluation Methods Used: This ACR has been created by Deque Systems based on the audit conducted by Deque Systems and Deque Software Private Limited?
Testing Adobe Acrobat Pro involved extensive use of leading assistive technology such as screen readers, screen magnifiers, and speech recognition software, as well exclusive use of the keyboard. Native platform accessibility features were also used to assist with testing. These were supplemented with techniques such as manual inspection of Accessibility API output.
Applicable Standards/Guidelines
This report covers the degree of conformance for the following accessibility standard/guidelines:
Standard/Guideline
Included In Report
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 be used only 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, the criteria are scoped for full screens, 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: Partially Supports
Software: The product provides sufficient text alternatives for most instances of non-text content. Exceptions include:
Some 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 available in the image, and if it is an active image, will not understand its function. This occurs on the following screens: Create PDF; Use a Certificate: Sign with a Digital ID; Generative Summaries; Studio Home; Acrobat Tools pane; Express Touchpoints SDK - Generate Image.
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 screens: Share; Adobe Sign / Send for Signatures; Create PDF.
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)
Software: Supports (Not Applicable)
Software: The product does not contain prerecorded audio-only or video-only media.
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)
Software: Supports (Not Applicable)
Software: The product does not contain prerecorded synchronized media.
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)
Software: Supports (Not Applicable)
Software: The product does not contain prerecorded video content that would require audio description or a media alternative.
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: Partially Supports
Software: Most visual structure and relationship information is provided through element semantics. 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 screen: Adobe Sign / Send for Signatures.
Some groups of form controls are not programmatically associated with their group label, so the purpose of individual controls in each group cannot be understood by people who are blind and/or use a screen reader. This occurs on the following screens: Edit - Links; Express Touchpoints SDK - Generate Image; Accessibility - Use guided actions: Accessibility Checker.
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 screen: Adobe Sign / Send for Signatures.
A set of radio buttons is not programmatically grouped, so the group label for the set of radio buttons will not be conveyed to people who are blind and/or use a screen reader, and they will not understand the purpose of the individual radio buttons. This occurs on the following screen: Protect with a Password.
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: Partially Supports
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 screens: PDF Spaces - First Time; Create Studio View; Create PDF.
The screen reader announcement of static text does not match the visual text displayed, so the intended meaning of the text will be lost or changed for people who are blind and/or use a screen reader. This occurs on the following screens: Acrobat Tools pane; Acrobat Home.
A hidden or empty interactive element receives screen reader focus, so people who are blind and/or use a screen reader will navigate to an element that is not intended to be part of the reading order on the page or has no content/functionality. This occurs on the following screen: Prepare Form.
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)
Software: Supports
Software: Instructions do not rely solely on sensory characteristics.
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: Partially Supports
Software: Most functions of the product do not convey information through color alone. Exceptions include:
Color is used as the only method to convey 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 screens: Combine Files / Organize during Combine; Edit - Organize; Comment on PDF; Quick Tools in Document.
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: Edit - Links; Quick Tools in Document.
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)
Software: Supports (Not Applicable)
Software: The product does not contain audio that plays automatically.
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: Does Not Support
Software: Most product functionality cannot be operated through a keyboard interface. Examples include:
Multiple functions cannot be performed using only the keyboard, so people who use the keyboard alone to navigate and operate content cannot use these functions. This occurs on all pages evaluated.
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 screen: Adobe Sign / Send for Signatures.
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: Partially Supports
Software: In most cases, keyboard focus is not locked or trapped in a particular area, and the user can navigate to and from all navigable elements using only a keyboard. Exception includes:
There is a keyboard trap, so people who use a keyboard to navigate content will get stuck in one place on the page. This occurs on the following screen: Comment on PDF.
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)
Software: The product does not provide character key shortcuts.
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: Supports
Software: The product supports the adjustment or cancellation of time-based limits.
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: Supports (Not Applicable)
Software: The product does not include elements which move, blink, scroll, or auto-update.
Guideline 2.3 Seizures:
Do not design content in a way that is known to cause seizures.
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)
Software: Supports (Not Applicable)
Software: The product does not contain flashing content.
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
Software: Supports
Software: A method is provided to skip navigation and other page elements that are repeated across web pages.
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)
Software: Supports
Software: The title of the software describes its purpose.
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: Partially Support
Software: Most components receive focus in a meaningful order. Exceptions include:
Keyboard focus is lost or misplaced as a result of user interaction or content update, or refresh, so people who use the keyboard to navigate content (including screen reader users) will become disoriented. This occurs on the following screens: This occurs on all pages evaluated.
Keyboard focus or touch screen swiping goes to multiple elements that are hidden or empty, so people who use the keyboard to navigate content (including screen reader users) may become disoriented or confused. This occurs on the following screen: Prepare Form.
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)
Software: Partially Supports
Software: The purpose of most links can be determined from the link text alone or from the link text and its programmatic context. Exception includes:
The purpose of the link is not made clear by its text or the context provided by the content that immediately surrounds it, so people who are blind and/or use a screen reader will not know where the link goes. This occurs on the following screen: Edit PDF.
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: Supports
Software: All functionality that can be operated with a pointer can be operated with single-point actions.
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
Software: Supports
Software: Product functions that use a single pointer are completed when the user releases the pointer and allow the user to cancel the pointer action before completing the pointer click.
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 (Open Functionality Software)
- 11.2.5.3 (Closed Software)
- 11.8.2 (Authoring Tool)
- 12.1.2 (Product Docs)
- 12.2.4 (Support Docs)
Revised Section 508 – Does not apply
Software: Partially Supports
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 screens: Accessibility - Use guided actions: Accessibility Checker; Express Touchpoints SDK - Edit Image; Prepare Form; Create Studio View.
The accessible name of multiple interactive elements (such as links, buttons, or form inputs) does not contain the visible label, so people who use speech input to navigate and operate content will not be able to access those elements. This occurs on the following screens: Acrobat Tools pane; Fill and Sign; Redact; Express Touchpoints SDK - Generate Image; Enhance Scan; Protect with a Password; Use a Certificate: Digitally Sign; Comment on PDF; Prepare for Accessibility: Accessibility Tags.
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
Software: Supports (Not Applicable)
Software: The product does not have functionality operated by device motion or user motion.
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)
Software: Supports
Software: The product relies on the features of the underlying operating system to set and indicate the language of the user interface.
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)
Software: Supports
Software: Components do not initiate a change of context when focused.
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)
Software: Partially Supports
Software: In most cases, when a user inputs information or interacts with a control, it does not result in a substantial change to the page that could disorient the user, or the user is informed about the change ahead of time. Exception includes:
When a user enters text in an input field or selects a checkbox or radio button, a new window unexpectedly opens, so people who have cognitive disabilities and others may be confused or disoriented. This occurs on the following screen: Edit PDF.
3.2.6 Consistent Help (Level A 2.2 only)
EN 301 549 Criteria - Does not apply
Revised Section 508 – Does not apply
Software: Supports
Software: On web pages that contain help features (including human or automated contact options or self-help options), those features occur in the same order relative to other page content unless the user changes that order.
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: Supports
Software: Where input errors are automatically detected items in error are identified and error messages are provided as text.
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: Partially Supports
Software: Labels are provided for most input fields. Exceptions include:
The labels for some form fields are missing, so each field's purpose is not clear. This occurs on the following screens: Adobe Sign / Send for Signatures; View PDF - Navigate & View; View PDF - Bookmarks; Acrobat Home; Studio Home; View PDF - Thumbnails.
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 screen: Comment on PDF.
Some visible Instructions for a form input field are not available for people who use assistive technology. This occurs on the following screens: Studio Home; Acrobat Home.
A required field is not identified as required by its label, in the form's general instructions, or by an error message that indicates that the field is not completed, so people cannot determine that the field is required. This occurs on the following screen: Protect with a Password.
3.3.7 Redundant Entry (Level A 2.2 only)
EN 301 549 Criteria - Does not apply
Revised Section 508 – Does not apply
Software: Supports
Software: If information previously entered by, or provided to, the user is required to be entered again in the same process, that information is either automatically populated or available for the user to select unless the previously entered information is no longer valid or re-entering the information is essential or required to ensure security.
Guideline 4.1 Compatible:
Maximize compatibility with current and future user agents, including assistive technologies.
4.1.1 Parsing (Level A)
Also applies to:
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)
Software: Does Not Apply
Software: This criterion was removed from WCAG 2.2
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: Does Not Support
Software: User interface components in most product functions do not provide programmatic name, role, state, or value information. Examples include:
Multiple controls (such as a button or link) do not have a programmatic role, so each controls’ 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: Quick Tools in Document; Acrobat Home; Studio Home; Edit - Organize; Adobe Sign / Send for Signatures; View PDF - Attachments; Create Studio View; View PDF - Navigate & View; Acrobat Tools pane; PDF Spaces - Create Space.
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 all pages evaluated.
Multiple controls have an incorrect programmatic role, so the role (like "button" or "link") for each control conveyed to screen readers and other assistive technologies is incorrect and misrepresents that control's function to people who use those technologies. This occurs on the following screens: Prepare Form; Comment on PDF; PDF Spaces - Create Space.
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 screens: Edit PDF; Fill and Sign; Studio Home; Protect with a Password; Edit - Organize; View PDF - Navigate & View; Adobe Sign / Send for Signatures; Enhance Scan; Export PDF; Podcast; Compress; Use a Certificate: Digitally Sign; Create PDF; Add a stamp; Prepare Form; Accessibility - Use guided actions: Make Accessible; Redact; Prepare for Accessibility: Accessibility Tags.
Multiple controls (such as a button or link) 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 screens: Acrobat Tools pane; PDF Spaces - Create Space; View PDF - Bookmarks; Accessibility - Use guided actions: Accessibility Checker; View PDF - Thumbnails; Adobe Sign / Send for Signatures; Express Touchpoints SDK - Edit Image; Prepare Form; Create Studio View.
Multiple controls do not have a programmatic role and name, so each controls’ role (usually button, but sometimes link or something else) and its name (such as "Submit" or "Cancel") are 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: AI Assistant; Generative Summaries; View PDF - Thumbnails; Protect with a Password; View PDF - Attachments.
A custom select does not have a role and/or a state (such as which options are available and/or which option is currently selected) that are conveyed to assistive technology, 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 element, the available options, and which option is selected. This occurs on the following screen: Adobe Sign / Send for Signatures.
For some elements that allow a user either to select or not select a single option (like a checkbox or radio buttons) or to select from among 2 or more options (like a select dropdown), the state (such as checked/unchecked or selected/not selected) is not conveyed to assistive technology, 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 element, the options available, and whether the element or an option is currently checked. This occurs on the following screens: Read Aloud; View PDF - Bookmarks; Studio Home; PDF Spaces - Create Space; Prepare Form; Create PDF; Create From a Template.
In a table that can be sorted by column the sorted state (ascending/descending) of the table's columns is not conveyed to assistive technology or the state conveyed is incorrect, so people who are blind and/or use a screen reader or other assistive technology may not be able to understand the order in which the table's content is presents and whether that order is meaningful when interpreting the data's meaning. This occurs on the following screen: View PDF - Attachments.
The content of multiple tooltips is not accessible to screen readers. This occurs on the following screens: Share; Edit PDF; AI Assistant; Generative Summaries; View PDF - Navigate & View; Acrobat Tools pane
Some elements that appear and function like a modal dialog do not have the required attributes in its HTML code needed to provide its programmatic role, name, state, and other properties to assistive technology, 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 each element or how to interact with it. This occurs on the following screens: Redact; PDF Spaces - Add Files; PDF Spaces - First Time; Protect with a Password; PDF Spaces with Monetization; Use a Certificate: Digitally Sign; Use a Certificate: Sign with a Digital ID.
Multiple elements that appear and function like a combobox do not have the required attributes in its HTML code needed to provide its programmatic role, name, state, and other properties to assistive technology, 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 each element or how to interact with it. This occurs on the following screens: Comment on PDF; Adobe Sign / Send for Signatures
The conversation between the user and the AI assistant is not clearly differentiated. This occurs on the following screen: AI Assistant
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)
Software: Supports (Not Applicable)
Software: The product does not contain live synchronized media.
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)
Software: Supports (Not Applicable)
Software: The product does not contain prerecorded video content that would require audio description.
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: Supports
Software: Content does not restrict its view and operation to a single display orientation.
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 (Open Functionality Software)
- 11.1.3.5 (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)
Software: The product’s technology does not have support for programmatic identification of input purpose.
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: Partially Support
Software: Most texts meet minimum contrast requirements. Examples 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 screens: Export PDF; Studio Home; Adobe Sign / Send for Signatures; Protect with a Password; Comment on PDF; Fill and Sign; Combine Files / Organize during Combine.
The color contrast ratios on hover or focus between the text labels of some controls and their background are less than 4.5:1, so people who are colorblind or have low vision may have difficulty reading the text label of each control. This occurs on all pages evaluated.
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 screen: Express Touchpoints SDK - Generate Image.
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 screens: Acrobat Tools pane; Adobe Sign / Send for Signatures.
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)
Software: Supports
Software: The product allows operating system display scaling to resize text up to 200 percent without loss of content or functionality.
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: Supports
Software: The product uses text instead of images of text, except for branding elements that are considered essential.
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.1 (Open Functionality Software)
- 11.1.4.10.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: Does Not Support
Software: At the required width of 320 CSS pixels, most functions of the product do not meet this criterion. Example includes:
When the page is adjusted to an equivalent width of 320 pixels and content reflows to fit within the viewport, some content or functionality becomes unavailable, so people with low vision who increase the size of text and other content using the browser zoom will not be able to access all of the page's content and/or functionality. This occurs on all pages evaluated.
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: Partially Support
Software: Most meaningful non-text content elements have sufficient contrast. Examples include:
The visual boundaries of some interactive elements (like a radio button or input fields) do not have a 3:1 color contrast ratio with the background, so people who are colorblind or have low vision may have difficulty in perceiving the boundaries of the interactive element. This occurs on the following screens: Create Studio View; Quick Tools in Document; View PDF - Thumbnails; View PDF - Navigate & View; Acrobat Tools pane; AI Assistant; Protect with a Password; Adobe Sign / Send for Signatures; Redact; Comment on PDF.
The focus indicators of some interactive elements (like buttons or input fields) 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 when each interactive element is receiving focus. This occurs on the following screens: Create Studio View; Edit - Links; Adobe Sign / Send for Signatures; Prepare Form; Redact.
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 in perceiving the state of the interactive elements. This occurs on the following screens: Studio Home; PDF Spaces - Add Files; View PDF - Bookmarks.
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 to understand the information presented by each icon. This occurs on all pages evaluated.
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
Software: Supports
Software: The spacing between letters, words, lines of text, and paragraphs can be adjusted with no loss of content or functionality.
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
Software: Does Not Support
Software: In most, if not all, cases when additional content is triggered by pointer hover or keyboard focus, that additional content cannot be dismissed and hovered over, and the content does not persist until the user dismisses it. Examples include:
Content that appears on mouse hover or keyboard focus (such as tooltips, drop-down menus, or popups) is not dismissible, so it obscures all or part of the original content on the page. This occurs on all pages evaluated.
Content that appears on mouse hover (such as tooltips, drop-down menus, or popups) disappears when the mouse pointer is moved over that content, meaning people with disabilities, especially people with low vision who need to magnify text, may not be able to read the additional content. This occurs on all pages evaluated.
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: Supports
Software: Multiple ways are available to find other pages on the site.
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: Partially Supports
Software: Most headings and labels for form and interactive controls are informative. Exceptions include:
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: Accessibility - Use guided actions: Make Accessible; Acrobat Home; Studio Home; Express Touchpoints SDK - Generate Image; Edit - Organize; Create From a Template; View PDF - Thumbnails; AI Assistant.
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 screens: Prepare for Accessibility: Accessibility Tags; Add a stamp; View PDF - Navigate & View; Acrobat Home; Studio Home; Compress; Fill and Sign; View PDF - Attachments; Create Studio View; Comment on PDF; Express Touchpoints SDK - Edit Image; Acrobat Tools pane; Export PDF; Combine Files / Organize during Combine; PDF Spaces - Create Space; PDF Spaces with Monetization; Edit PDF; Quick Tools in Document; Accessibility - Use guided actions: Make Accessible; Edit - Links.
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: Partially Supports
Software: Most focusable elements have a visible keyboard focus indicator. Exception includes:
Multiple interactive elements (such as links, buttons, or form inputs) do not have a visual focus indicator, so sighted people who use a keyboard to navigate content will not know when those elements are receiving focus. This occurs on the following screens: PDF Spaces - Create Space; Express Touchpoints SDK - Edit Image.
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: Supports
Software: When a user interface component receives keyboard focus, the component is not entirely hidden due to author-created content.
2.5.7 Dragging Movements (Level AA 2.2 only)
EN 301 549 Criteria - Does not apply
Revised Section 508 – Does not apply
Software: Does Not Support
Software: Most, if not all, functionality that uses a dragging movement cannot be achieved by a single pointer without dragging, except for functions for which dragging is essential or the functionality is determined by the user agent and not modified by the author. Example includes:
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. This occurs on all pages evaluated.
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: Supports
Software: The size of the target for each clickable control 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.
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: Supports
Software: Changes of language for passages or phrases can be programmatically determined.
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
Software: Supports
Software: Navigation patterns that are repeated on web pages are presented in the same relative order each time they appear and do not change order when navigating through the site.
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
Software: Supports
Software: Labels, names, and/or text alternatives for content that have the same functionality across multiple web pages are consistently identified.
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: Supports
Software: Where input errors are automatically detected, suggestions for correction are provided to the user.
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)
Software: Supports
Software: The product does not process legal commitments or financial transactions. When editing files, changes to user-controllable data are reversible or can be confirmed before finalizing.
3.3.8 Accessible Authentication (Minimum) (Level AA 2.2 only)
EN 301 549 Criteria - Does not apply
Revised Section 508 – Does not apply
Software: Supports
Software: A cognitive function test (such as remembering a password or solving a puzzle) is not required for any step in an authentication process unless either another method is available that does not rely on a cognitive function test; help is available to assist the user in completing the test; or the test is to recognize objects or identify non-text content the user provided to the website.
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) - Does not apply
- 11.4.1.3 (Open Functionality Software) - Does not apply
- 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: Partially Supports
Software: In most cases, status messages can be programmatically determined and presented by assistive technologies without receiving focus. Exception include:
Some status messages are 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 messages, or they may not hear them in a timely fashion. This occurs on the following screens: Combine Files / Organize during Combine; Acrobat Tools pane; Comment on PDF; View PDF - Navigate & View; Create PDF; Generative Summaries; Protect with a Password; Edit PDF; AI Assistant; Adobe Sign / Send for Signatures.
Table 3: Success Criteria, Level AAA
Notes: Not Applicable
Revised Section 508 Report
Notes:
Chapter 3: Functional Performance Criteria (FPC)
Notes:
Software: Partially Supports
Software: Most functions of the product are usable without vision. Exceptions include:
As noted in 1.1.1 Non-text Content
As noted in 1.3.1 Info and Relationships
As noted in 1.3.2 Meaningful Sequence
As noted in 1.4.1 Use of Color
As noted in 2.1.1 Keyboard
As noted in 2.1.2 No Keyboard Trap
As noted in 2.4.3 Focus Order
As noted in 2.4.4 Link Purpose (In Context)
As noted in 2.4.6 Headings and Labels
As noted in 3.2.2 On Input
As noted in 4.1.2 Name, Role, Value
Software: Partially Supports
Software: Most functionality is usable with limited vision. Exceptions include:
As noted in 1.1.1 Non-text Content
As noted in 1.3.1 Info and Relationships
As noted in 1.3.2 Meaningful Sequence
As noted in 1.4.1 Use of Color
As noted in 1.4.3 Contrast (Minimum)
As noted in 2.1.1 Keyboard
As noted in 2.1.2 No Keyboard Trap
As noted in 2.4.3 Focus Order
As noted in 2.4.4 Link Purpose (In Context)
As noted in 2.4.6 Headings and Labels
As noted in 2.4.7 Focus Visible
As noted in 3.2.2 On Input
As noted in 3.3.2 Labels or Instructions
As noted in 4.1.2 Name, Role, Value
Software: Partially Supports
Software: Most functions of the product are usable without perception of color. Exceptions include:
As noted in 1.4.1 Use of Color
As noted in 1.4.3 Contrast (Minimum)
Software: Supports
Software: The product is functional for users without hearing
Software: Supports
Software: The product is functional for users with limited hearing.
Software: Supports (not applicable)
Software: The product does not require the use of speech
Software: Partially Supports
Software: Most functionality is usable with limited manipulation and does not require fine motor control or simultaneous manual operations. Exceptions include:
As noted in 2.1.1 Keyboard
As noted in 2.1.2 No Keyboard Trap
As noted in 2.4.3 Focus Order
As noted in 2.4.4 Link Purpose (In Context)
As noted in 2.4.6 Headings and Labels
As noted in 2.4.7 Focus Visible
As noted in 4.1.2 Name, Role, Value
Software: Supports
Software: The product is functional with limited reach and strength.
Software: Partially Supports
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 or accessibility features of the platform. The product provides descriptive labels, instructions, and error identification and suggestions for most user input. Exceptions include:
As noted in 1.1.1 Non-text Content
As noted in 1.3.1 Info and Relationships
As noted in 1.3.2 Meaningful Sequence
As noted in 1.4.1 Use of Color
As noted in 2.1.1 Keyboard
As noted in 2.4.3 Focus Order
As noted in 2.4.4 Link Purpose (In Context)
As noted in 2.4.6 Headings and Labels
As noted in 2.4.7 Focus Visible
As noted in 3.2.2 On Input
As noted in 3.3.2 Labels or Instructions
As noted in 4.1.2 Name, Role, Value
The role, state(s), properties, boundary, name, and description of most objects can be programmatically determined, so those attributes can be perceived and conveyed by assistive technology. Exceptions include:
As noted in 4.1.2 Name, Role, Value
For most objects that allow the user to set their respective properties and/or state, the act of setting a property or state is available programmatically, so that it can be perceived and performed using assistive technology. Exceptions include:
As noted in 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) are available programmatically, so they can be perceived and conveyed by assistive technology. Exceptions include:
As noted in 4.1.2 Name, Role, Value
For most objects that allow the user to set or modify their value, the act of setting a value is available programmatically, so that it can be perceived and performed using assistive technology. Exceptions include:
As noted in 4.1.2 Name, Role, Value
For most elements that act as a label for another element and elements that are labeled by another element, the labeling relationship is programmatically determinable, so it can be perceived and conveyed by assistive technology. Exceptions include:
As noted in 1.3.1 Info and Relationships
As noted in 4.1.2 Name, Role, Value
For most of the elements on which one or more actions may be performed, all of those actions are available programmatically, so that each action can be performed using assistive technology. Exceptions include:
As noted in 2.1.1 Keyboard
On most pages, the position and content of the focus indicator, text insertion point, and/or text selector are programmatically determinable, so that focus position and content can be perceived and conveyed by assistive technology. Exceptions include:
As noted in 2.4.7 Focus Visible
In most cases, status messages relevant to user interactions are available to, and presented by, assistive technology. Exceptions include:
As noted in 4.1.3 Status Messages
In most instances, in its capacity as an authoring tool, the product preserves accessibility information when converting content from one format to another, so information in the original format necessary to make portions of the content accessible is provided in the new format, and this content will be available to people with disabilities. Exception includes:
During the PDF to Word conversion, some headings and table markup are not preserved.
Chapter 6: Support Documentation and Services
Notes: Information regarding Support Documentation and Services is available in the Accessibility Conformance Report for the Adobe Help Center on the Adobe Accessibility Compliance website.
EN 301 549 Report
Notes:
Chapter 4: Functional Performance Statements (FPS)
Notes:
Software: Partially Supports
Software: Most functions of the product are usable without vision. Exceptions include:
As noted in 1.1.1 Non-text Content
As noted in 1.3.1 Info and Relationships
As noted in 1.3.2 Meaningful Sequence
As noted in 1.4.1 Use of Color
As noted in 2.1.1 Keyboard
As noted in 2.1.2 No Keyboard Trap
As noted in 2.4.3 Focus Order
As noted in 2.4.4 Link Purpose (In Context)
As noted in 2.4.6 Headings and Labels
As noted in 3.2.2 On Input
As noted in 4.1.2 Name, Role, Value
As noted in 4.1.3 Status Messages
Software: Partially Supports
Software: Most functionality is usable with limited vision. Exceptions include:
As noted in 1.1.1 Non-text Content
As noted in 1.4.1 Use of Color
As noted in 1.4.3 Contrast (Minimum)
As noted in 1.4.10 Reflow
As noted in 1.4.11 Non-text Contrast
As noted in 1.4.13 Content on Hover or Focus
As noted in 2.1.1 Keyboard
As noted in 2.1.2 No Keyboard Trap
As noted in 2.4.3 Focus Order
As noted in 2.4.4 Link Purpose (In Context)
As noted in 2.4.6 Headings and Labels
As noted in 2.4.7 Focus Visible
As noted in 3.2.2 On Input
As noted in 3.3.2 Labels or Instructions
As noted in 4.1.2 Name, Role, Value
Software: Partially Supports
Software: Most functions of the product are usable without perception of color. Exceptions include:
As noted in 1.4.1 Use of Color
As noted in 1.4.3 Contrast (Minimum)
As noted in 1.4.11 Non-Text Contrast
Software: Supports
Software: The product is functional for users without hearing.
Software: Supports
Software: The product is functional for users with limited hearing.
Software: Supports
Software: All functionality is usable without speech.
Software: Partially Supports
Software: Most functionality is usable by people with limited manipulation and does not require manipulation, simultaneous action, or hand strength. Exceptions include:
As noted in 2.1.1 Keyboard
As noted in 2.1.2 No Keyboard Trap
As noted in 2.4.3 Focus Order
As noted in 2.4.4 Link Purpose (In Context)
As noted in 2.4.6 Headings and Labels
As noted in 2.4.7 Focus Visible
As noted in 2.5.3 Label in Name
As noted in 3.2.2 On Input
As noted in 4.1.2 Name, Role, Value
Software: Partially Supports
Software: Most functionality is usable by people with limited reach. Exceptions include:
As noted in 2.5.3 Label in Name
Software: Supports
Software: The product does not contain flashing content.
Software: Partially Supports
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 or accessibility features of the platform. The product provides descriptive labels, instructions, and error identification and suggestions for most user input. Exceptions include:
As noted in 1.4.13 Content on Hover or Focus
As noted in 2.4.3 Focus Order
As noted in 2.4.4 Link Purpose (In Context)
As noted in 2.4.6 Headings and Labels
As noted in 2.4.7 Focus Visible
As noted in 3.2.2 On Input
As noted in 3.3.2 Labels or Instructions
As noted in 4.1.3 Status Messages
Software: Supports
Software: Where the product provides features for accessibility, it maintains the privacy of people who use these features at the same level as other user.
Chapter 5: Generic Requirements
Notes:
In most instances, in its capacity as an authoring tool, the product preserves accessibility information when converting content from one format to another, so information in the original format necessary to make portions of the content accessible is provided in the new format, and this content will be available to people with disabilities. Exception includes:
During the PDF to Word conversion, some headings and table markup are not preserved.
Chapter 6: ICT with Two-Way Voice Communication
Notes: Not Applicable
Chapter 7: ICT with Video Capabilities
Notes: Not Applicable
Clause 8: Hardware
Notes: The ICT covered by this report is not hardware. As such, the requirements of this clause do not apply.
Clause 9: Web (see WCAG 2.2 section)
Notes:
Chapter 10: Non-Web Documents
Notes: Not Applicable
Chapter 11: Software
Notes:
Most objects in the product do not expose name, role, state, boundary, or description information to assistive technology. Example includes:
As noted in 4.1.2 Name, Role, Value
The product exposes the values of most [input] controls to assistive technology. Exceptions include:
As noted in 4.1.2 Name, Role, Value
For most elements that act as a label for another element and elements that are labeled by another element, the labeling relationship is programmatically determinable, so it can be perceived and conveyed by assistive technology. Exceptions include:
As noted in 1.3.1 Info and Relationships
As noted in 4.1.2 Name, Role, Value
For most elements that act as a label for another element and elements that are labeled by another element, the labeling relationship is programmatically determinable, so it can be perceived and conveyed by assistive technology. Exception includes:
As noted in 2.1.1 Keyboard
On most pages, the position and content of the focus indicator, text insertion point, and/or text selector are programmatically determinable, so that focus position and content can be perceived and conveyed by assistive technology. Exception includes:
As noted in 2.4.7 Focus Visible
In most cases, status messages relevant to user interactions are available to, and presented by, assistive technology. Exceptions include:
As noted in 4.1.3 Status Messages
For most objects that allow the user to set their respective properties and/or state, the act of setting a property or state is available programmatically, so that it can be perceived and performed using assistive technology. Exceptions include:
As noted in 4.1.2 Name, Role, Value
For most objects that allow the user to set their respective properties and/or state, the act of setting a property or state is available programmatically, so that it can be perceived and performed using assistive technology. Exceptions include:
As noted in 4.1.2 Name, Role, Value
In most instances, in its capacity as an authoring tool, the product preserves accessibility information when converting content from one format to another, so information in the original format necessary to make portions of the content accessible is provided in the new format, and this content will be available to people with disabilities. Exceptions include:
During the PDF to Word conversion, some headings and table markup are not preserved.
Chapter 12: Documentation and Support Services
Notes: Information regarding Support Documentation and Services is available in the Accessibility Conformance Report for the Adobe Help Center on the Adobe Accessibility Compliance website.
Chapter 13: ICT Providing Relay or Emergency Service Access
Notes: Not Applicable
