User Guide Cancel

Create and verify PDF accessibility (Acrobat Pro)

Search
Adobe Acrobat

Adobe Acrobat

Open on web
  1. Acrobat User Guide
  2. Introduction to Acrobat
    1. Access Acrobat from desktop, mobile, web
    2. Introducing the new Acrobat experience
    3. What's new in Acrobat
    4. Keyboard shortcuts
    5. System Requirements
  3. Workspace
    1. Workspace basics
    2. Opening and viewing PDFs
      1. Opening PDFs
      2. Navigating PDF pages
      3. Viewing PDF preferences
      4. Adjusting PDF views
      5. Enable thumbnail preview of PDFs
      6. Display PDF in browser
    3. Working with online storage accounts
      1. Access files from Box
      2. Access files from Dropbox
      3. Access files from OneDrive
      4. Access files from SharePoint
      5. Access files from Google Drive
    4. Acrobat and macOS
    5. Acrobat notifications
    6. Grids, guides, and measurements in PDFs
    7. Asian, Cyrillic, and right-to-left text in PDFs
  4. Creating PDFs
    1. Overview of PDF creation
    2. Create PDFs with Acrobat
    3. Create PDFs with PDFMaker
    4. Using the Adobe PDF printer
    5. Converting web pages to PDF
    6. Creating PDFs with Acrobat Distiller
    7. Adobe PDF conversion settings
    8. PDF fonts
  5. Editing PDFs
    1. Edit text in PDFs
    2. Edit images or objects in a PDF
    3. Rotate, move, delete, and renumber PDF pages
    4. Edit scanned PDFs
    5. Enhance document photos captured using a mobile camera
    6. Optimizing PDFs
    7. PDF properties and metadata
    8. Links and attachments in PDFs
    9. PDF layers
    10. Page thumbnails and bookmarks in PDFs
    11. PDFs converted to web pages
    12. Setting up PDFs for a presentation
    13. PDF articles
    14. Geospatial PDFs
    15. Applying actions and scripts to PDFs
    16. Change the default font for adding text
    17. Delete pages from a PDF
  6. Scan and OCR
    1. Scan documents to PDF
    2. Enhance document photos
    3. Troubleshoot scanner issues when scanning using Acrobat
  7. Forms
    1. PDF forms basics
    2. Create a form from scratch in Acrobat
    3. Create and distribute PDF forms
    4. Fill in PDF forms
    5. PDF form field properties
    6. Fill and sign PDF forms
    7. Setting action buttons in PDF forms
    8. Publishing interactive PDF web forms
    9. PDF form field basics
    10. PDF barcode form fields
    11. Collect and manage PDF form data
    12. About forms tracker
    13. PDF forms help
    14. Send PDF forms to recipients using email or an internal server
  8. Combining files
    1. Combine or merge files into single PDF
    2. Rotate, move, delete, and renumber PDF pages
    3. Add headers, footers, and Bates numbering to PDFs
    4. Crop PDF pages
    5. Add watermarks to PDFs
    6. Add backgrounds to PDFs
    7. Working with component files in a PDF Portfolio
    8. Publish and share PDF Portfolios
    9. Overview of PDF Portfolios
    10. Create and customize PDF Portfolios
  9. Sharing, reviews, and commenting
    1. Share and track PDFs online
    2. Mark up text with edits
    3. Preparing for a PDF review
    4. Starting a PDF review
    5. Hosting shared reviews on SharePoint or Office 365 sites
    6. Participating in a PDF review
    7. Add comments to PDFs
    8. Adding a stamp to a PDF
    9. Approval workflows
    10. Managing comments | view, reply, print
    11. Importing and exporting comments
    12. Tracking and managing PDF reviews
  10. Saving and exporting PDFs
    1. Saving PDFs
    2. Convert PDF to Word
    3. Convert PDF to PPTX
    4. Convert PDF to XLSX or XML
    5. Convert PDF to JPG
    6. Convert PDF to PNG
    7. Convert or export PDFs to other file formats
    8. File format options for PDF export
    9. Reusing PDF content
  11. Security
    1. Enhanced security setting for PDFs
    2. Securing PDFs with passwords
    3. Manage Digital IDs
    4. Securing PDFs with certificates
    5. Opening secured PDFs
    6. Removing sensitive content from PDFs
    7. Setting up security policies for PDFs
    8. Choosing a security method for PDFs
    9. Security warnings when a PDF opens
    10. Securing PDFs with Adobe Experience Manager
    11. Protected View feature for PDFs
    12. Overview of security in Acrobat and PDFs
    13. JavaScripts in PDFs as a security risk
    14. Attachments as security risks
    15. Allow or block links in PDFs
  12. Electronic signatures
    1. Sign PDF documents
    2. Capture your signature on mobile and use it everywhere
    3. Send documents for e-signatures
    4. Create a web form
    5. Request e-signatures in bulk
    6. Collect online payments
    7. Brand your account
    8. About certificate signatures
    9. Certificate-based signatures
    10. Validating digital signatures
    11. Adobe Approved Trust List
    12. Manage trusted identities
  13. Printing
    1. Basic PDF printing tasks
    2. Print Booklets and PDF Portfolios
    3. Advanced PDF print settings
    4. Print to PDF
    5. Printing color PDFs (Acrobat Pro)
    6. Printing PDFs in custom sizes
  14. Accessibility, tags, and reflow
    1. Create and verify PDF accessibility
    2. Accessibility features in PDFs
    3. Reading Order tool for PDFs
    4. Reading PDFs with reflow and accessibility features
    5. Edit document structure with the Content and Tags panels
    6. Creating accessible PDFs
    7. Cloud-based auto-tagging
  15. Searching and indexing
    1. Creating PDF indexes
    2. Searching PDFs
  16. Multimedia and 3D models
    1. Add audio, video, and interactive objects to PDFs
    2. Adding 3D models to PDFs (Acrobat Pro)
    3. Displaying 3D models in PDFs
    4. Interacting with 3D models
    5. Measuring 3D objects in PDFs
    6. Setting 3D views in PDFs
    7. Enable 3D content in PDF
    8. Adding multimedia to PDFs
    9. Commenting on 3D designs in PDFs
    10. Playing video, audio, and multimedia formats in PDFs
    11. Add comments to videos
  17. Print production tools (Acrobat Pro)
    1. Print production tools overview
    2. Printer marks and hairlines
    3. Previewing output
    4. Transparency flattening
    5. Color conversion and ink management
    6. Trapping color
  18. Preflight (Acrobat Pro)
    1. PDF/X-, PDF/A-, and PDF/E-compliant files
    2. Preflight profiles
    3. Advanced preflight inspections
    4. Preflight reports
    5. Viewing preflight results, objects, and resources
    6. Output intents in PDFs
    7. Correcting problem areas with the Preflight tool
    8. Automating document analysis with droplets or preflight actions
    9. Analyzing documents with the Preflight tool
    10. Additional checks in the Preflight tool
    11. Preflight libraries
    12. Preflight variables
  19. Color management
    1. Keeping colors consistent
    2. Color settings
    3. Color-managing documents
    4. Working with color profiles
    5. Understanding color management

Before you begin

We're rolling out a new, more intuitive product experience. If the screen shown here doesn’t match your product interface, select help for your current experience.

In the new experience, the tools appear on the left side of the screen.

Overview

You can use Acrobat to make PDFs meet the common accessibility standards, such as Web Content Accessibility Guidelines (WCAG) 2.0 and PDF/UA (Universal Access, or ISO 14289). Acrobat provides the following accessibility tools:

  • Prepare for accessibility: A predefined action automates many tasks, checks accessibility, and provides instructions for items that require manual fixes. Quickly find and fix problem areas.
  • Check for accessibility: It verifies whether the document conforms to accessibility standards, such as PDF/UA and WCAG 2.0.
  • Open accessibility report: It summarizes the findings of the accessibility check. It contains links to tools and documentation that assist in fixing problems.
  • Reading options: It includes settings for the available reading options. 
  • Fix reading order: You can use the Reading Order tool to examine the structure, reading order, and contents of a PDF.
  • Save as accessible text: It allows you to read the saved text file in a word-processing application. It also enables you to emulate the end-user experience of readers who use a braille printer to read the document.

Check accessibility of PDFs (Acrobat Pro)

You can use the Prepare for accessibility tool to check and make a PDF accessible. It prompts you to address accessibility issues, such as a missing document description or title. It looks for common elements that need further action, such as scanned text, form fields, tables, and images. You can run a Prepare for accessibility action on all PDFs except dynamic forms (XFA documents) or portfolios.

  1. Open the PDF, and then, from the global bar in the upper left, select All tools, select View more, and then select Prepare for accessibility.

    Prepare for accessibility panel with a list of available actions appear on the left panel. 

  2. From the left panel, select Check for accessibility. 

  3. From the Accessibility Checker Options dialog, select the options as required and then select Start Checking.

  4. Once the check is complete, it displays a panel on the right that lists the accessibility issues. Select each issue type drop-down to view the details and make fixes, as suggested.

    Since the Accessibility Check feature does not distinguish between essential and nonessential content types, some reported issues may not affect readability. We suggest that you review all issues to determine the ones that need correction.

    The report displays one of the following statuses for each rule check:

    • Passed: The item is accessible.
    • Skipped By User: Rule was not checked because it wasn't selected in the Accessibility Checker Options dialog box.
    • Needs Manual Check: The Full Check/Accessibility Check feature couldn't check the item automatically. Verify the item manually.
    • Failed: The item didn't pass the accessibility check.

  5. To view a complete report of the check, from the left panel, select Open accessibility report.

    It displays a detailed report in the right panel.

Fix accessibility issues (Acrobat Pro)

To fix a failed check after running the Prepare for accessibility check, select ellipsis in the Accessibility Checker panel on the right and select one of the following options from the context menu:

  • Fix: Acrobat either fixes the item automatically or displays a dialog box prompting you to fix the item manually.
  • Skip Rule: Deselects this option in the Accessibility Checker Options dialog box for future checks of this document, and change the item status to Skipped.
  • Explain: Opens the online Help where you can get more details about the accessibility issue.
  • Check Again: Runs the checker again on all items. Choose this option after modifying one or more items.
  • Show Report: Displays a report with links to tips on how to repair failed checks.
  • Options: Opens the Accessibility Checker Options dialog box, so you can select which checks are performed.

Accessibility issues

Document

Prevent security settings from interfering with screen readers

A document author can specify that no part of an accessible PDF is to be copied, printed, extracted, commented on, or edited. This setting could interfere with a screen reader's ability to read the document because screen readers must be able to copy or extract the document's text to convert it to speech.

This flag reports whether it's necessary to turn on the security settings that allow accessibility.

To fix the rule automatically, go to All tools > Prepare for accessibility > Check for accessibility and then ensure that the option Accessibility permission flat is set is selected before running the check. Then, select Open accessibility report, and from the right panel, right-click the Accessibility permission flag and select Fix.

To manually fix the accessibility permissions:

  1. Select the hamburger menu  (Windows) or the File menu (macOS) > Document properties.

  2. In the Document properties dialog:

    1. Select the Security tab.
    2. From the Security Method drop-down, select No Security.
    3. Select OK.

If your assistive technology product is registered with Adobe as a Trusted Agent, you can read PDFs that might be inaccessible to another assistive technology product. Acrobat recognizes when a screen reader or other product is a Trusted Agent and overrides security settings that would typically limit access to the content for accessibility purposes. However, the security settings remain in effect for all other purposes, such as to prevent printing, copying, extracting, commenting, or editing text.

Note:

See the related WCAG section: 1.1.1 Non-text Content. (A), 4.1.2 Name, role, value

Image-only PDF

Reports whether the document contains non-text content that is not accessible. If the document appears to contain text, but doesn't contain fonts, it could be an image-only PDF file.

To fix the rule automatically, go to All tools > Prepare for accessibility > Check for accessibility. Then, ensure that the option Document is not-image only PDF is deselected before running the check.

To fix this rule check manually, use OCR to recognize text in scanned images:

  1. From the All tools menu, select Scan & OCR.

  2. From the Scan & OCR panel, under Recognize Text, select In this file.

  3. From the Pages dialog, select the pages you want to process, the document language, and then select Recognize text.

Note:

See the related WCAG section: 1.1.1. Non-text content (A)

Tagged PDF

If this rule check fails, the document isn't tagged to specify the correct reading order.

To fix the item automatically, go to All tools > Prepare for accessibility > Check for accessibility. Then, ensure that the option Document is tagged PDF is selected before running the check. Acrobat automatically adds tags to the PDF.

To specify tags manually, do one of the following:

  • Enable tagging in the source application and re-create the PDF.
  • Select All tools > Prepare for accessibility > Automatically tag PDF. If there are any issues, the Add Tags Report appears in the navigation pane. It lists potential problems by page, provides a navigational link to each problem, and suggests ways to fix them.
  • Select All tools > Prepare for Accessibility > Fix reading order and create the tags tree. For more information, see Reading Order.
  • Open the Tags panel and create the tags tree manually. To display the Tags panel, select the hamburger menu  (Windows) > View or select the View menu (macOS), and then select Show/Hide > Side panels > Accessibility tags. For more information, see the Edit document structure with the Content and Tags panel.
Note:

See the related WCAG section: 1.3.1 Info and Relationships, 1.3.2, 2.4.1, 2.4.4, 2.4.5, 2.4.6, 3.1.2, 3.3.2, 4.1.2 Name, role, value

Logical reading order

Verify this rule check manually. Make sure that the reading order displayed in the Tags panel coincides with the logical reading order of the document.

Document language

Setting the document language in a PDF enables some screen readers to switch to the appropriate language. This check determines whether the primary text language for the PDF is specified. If the check fails, set the language.

To set the language automatically, select Primary Language in the Accessibility Checker tab and then choose Fix from the Options menu. Choose a language in the Set Reading Language dialog box, and then select OK.

To set the language manually, do one of the following:

  • Choose the hamburger menu  (Windows) or the File menu (macOS) > Properties > Advanced, and then select a language from the drop-down list in the Reading Options section. (If the language doesn't appear in the drop-down list, you can enter the ISO 639 code for the language in the Language field.) This setting applies the primary language for the entire PDF.
  • Set the language for all text in a subtree of the tags tree. Open the Tags panel. Expand the Tags root and select an element. Then choose Properties from the Options menu. Choose a language from the Language drop-down list. (To display the Tags panel, select the hamburger menu  (Windows) > View or select the View menu (macOS), and then select Show/Hide > Side panels > Accessibility tags.)
  • Set the language for a block of text by selecting the text element or container element in the Content panel. Then, right-click (Windows) or Ctrl-click (macOS) the text, choose Properties from the context menu, and choose a language from the Language drop-down list. (To display the Content panel, select the hamburger menu  (Windows) > View or select the View menu (macOS), and then select Show/Hide > Side panels > Content.)
Note:

See the related WCAG section: Language of Page (Level A)

Title

Reports whether there is a title in the Acrobat application title bar.

To fix the title automatically, select Title in the Accessibility Checker tab, and choose Fix from the Options menu. Enter the document title in the Description dialog box (deselect Leave As Is, if necessary).

To fix the title manually:

  1. Select the hamburger menu  (Windows) or the File menu (macOS) > Document properties.

  2. In the dialog that opens, under Description, enter a title in the Title text box.

  3. Select Initial View and then from the Show drop-down, select Document Title.

  4. Select OK.

Note:

See the related WCAG section: 2.4 Page Titled (Level A)

Bookmarks

This check fails when the document has 21 or more pages, but doesn't have bookmarks that parallel the document structure.

To add bookmarks to the document, select Bookmarks on the Accessibility Checker panel, and choose Fix from the Options menu. In the Structure Elements dialog box, select the elements that you want to use as bookmarks, and click OK. (You can also access the Structure Elements dialog box by clicking the Options menu on the Bookmark tab and selecting the New Bookmarks From Structure command.)

Note:

See the related WCAG sections: 2.4.1 Bypass Blocks (Level A), 2.4.5 Multiple Ways (Level AA)

Color contrast

When this check fails, it's possible that the document contains content that isn't accessible to people who are color-blind.

To fix this issue, make sure that the document's content adheres to the guidelines outlined in WCAG section 1.4.3. Or, include a recommendation that the PDF viewer use high-contrast colors:

  1. Select the hamburger menu  (Windows) or the Acrobat menu (macOS) > Preferences. 

  2. In the dialog that opens, from the left panel, select Accessibility.

  3. Select Replace Document Colors and then select Use High-Contrast Colors. From the High-contrast color combination, choose the color combination that you want and then select OK.

Page content

Tagged content

This check reports whether all content in the document is tagged. Ensure that all content in the document is either included in the Tags tree, or marked as an artifact.

Do one of the following to fix this rule check:

  • Open the Content panel and right-click (Windows) or Ctrl-click (macOS) the content that you want to mark as an artifact. Then, select Create Artifact from the context menu. (To display the Content tab, select the hamburger menu  (Windows) > View or select the View menu (macOS), and then select Show/Hide > Side panels > Content.)
  • Tag the content by choosing All tools > Prepare for accessibility > Fix reading order. Select the content, and then apply tags as necessary.
  • Assign tags using the Tags panel. Right-click (Windows) or Ctrl-click (Mac OS) the element in the Tags tree, and choose Create Tag From Selection. Items such as comments, links, and annotations don't always appear in the Tags tree. To find these items, choose Find from the Options menu. (To display the Tags panel, select the hamburger menu  (Windows) > View or select the View menu (macOS), and then select Show/Hide > Side panels > Accessibility tags.)
Note:

See the related WCAG sections: 1.1.1 Non-text content (A), 1.3.1 Info and Relationships (Level A), 1.3.2 Meaningful Sequence (Level A), 2.4.4 Link Purpose (In Context) (Level A), 3.1.2 Language of Parts (Level AA), 4.1.2 Name, role, value

Tagged annotations

This rule checks whether all annotations are tagged. Ensure that annotations such as comments and editorial marks (insert and highlight) are either included in the Tags tree or marked as artifacts.

  • Open the Content panel , and right-click (Windows) or Ctrl-click (Mac OS) the content you want to mark as an artifact. Then, select Create Artifact from the context menu. (To display the Content panel, select the hamburger menu  (Windows) > View or select the View menu (macOS), and then select Show/Hide > Side Panels > Content).
  • To tag the content, select All tools > Prepare for accessibility > Fix reading order. Then, select the content and apply the tags as necessary.
  • Assign tags using the Tags panel. (To display the Tags panel, choose select the hamburger menu  (Windows) > View or select the View menu (macOS), and then select Show/Hide
    > Side Panels > Accessibility tags).

To have Acrobat assign tags automatically to annotations as they're created, choose Autotag document from the Options ( . . . ) menu on the Tags panel.

Note:

See the related WCAG section: 1.3.1 Info and Relationships (Level A), 4.1.2 Name, role, value

Tab order

Because tabs are often used to navigate a PDF, it's necessary that the tab order parallels the document structure.

To fix the tab order automatically, select Tab Order on the Accessibility Checker panel, and choose Fix from the Options menu.

To manually fix the tab order for links, form fields, comments, and other annotations:

  1. Click the Page Thumbnails panel on the navigation pane.

  2. Click a page thumbnail, and then choose Page Properties from the Options menu.

  3. In the Page Properties dialog box, choose Tab Order. Then, select Use Document Structure, and select OK.

  4. Repeat these steps for all thumbnails in the document.

Note:

See the related WCAG section: 2.4.3, Focus Order (Level A)

Character encoding

Specifying the encoding helps PDF viewers' present users with readable text. However, some character-encoding issues aren't repairable within Acrobat.

To ensure proper encoding, do the following:

  • Verify that the necessary fonts are installed on your system.
  • Use a different font (preferably OpenType) in the original document, and then re-create the PDF.
  • Re-create the PDF file with a newer version of Acrobat Distiller.
  • Use the latest Adobe Postscript driver to create the PostScript file, and then re-create the PDF.
Note:

The WCAG doesn't address Unicode character mapping.

Tagged multimedia

This rule checks whether all multimedia objects are tagged. Ensure that content is included in the Tags tree or marked as an artifact.

Open the Content panel and right-click (Windows) or Ctrl-click (Mac OS) the content that you want to mark as an artifact. Then, select Create Artifact from the context menu. (To display the Content panel, select the hamburger menu  (Windows) > View or select the View menu (macOS), and then select Show/Hide > Side Panels > Content.)

Tag the content by choosing All tools > Prepare for accessibility > Fix reading order. Select the content, and then apply tags as necessary.

Assign tags using the Tags panel. Right-click (Windows) or Ctrl-click (Mac OS) the element in the Tags tree, and choose Create Tag From Selection. (To display the Tags panel, select the hamburger menu  (Windows) > View or select the View menu (macOS), and then select Show/Hide > Side Panels > Accessibility tags.)

Note:

See the related WCAG sections: 1.1.1 Non-text Content. (A), 1.2.1 Audio- only and Video- only (Prerecorded). (A), 1.2.2 Captions (Prerecorded). (A), 1.2.3 Audio Description or Media Alternative (Prerecorded). (A), 1.2.5 Audio Description (Prerecorded). (AA)

Screen flicker

Elements that make the screen flicker, such as animations and scripts, can cause seizures in individuals who have photosensitive epilepsy. These elements can also be difficult to see when the screen is magnified.

If the Screen Flicker rule fails, manually remove or modify the script or content that causes screen flicker.

Note:

See these related WCAG sections: 1.1.1 Non-text Content. (A), 1.2.1 Audio- only and Video- only (Prerecorded). (A), 1.2.2 Captions (Prerecorded). (A), 1.2.3 Audio Description or Media Alternative (Prerecorded). (A), 2.3.1 Three Flashes or Below Threshold. (Level A)

Scripts

Content cannot be script-dependent unless both content and functionality are accessible to assistive technologies. Make sure that scripting doesn't interfere with keyboard navigation or prevent the use of any input device.

Check the scripts manually. Remove or modify any script or content that compromises accessibility.

Note:

See these related WCAG sections: 1.1.1 Non-text Content. (A), 2.2.2 Pause, Stop, Hide. (Level A), 4.1.2 Name, role, value

Timed responses

This rule check applies to documents that contain forms with JavaScript. If the rule check fails, make sure that the page does not require timed responses. Edit or remove scripts that impose timely user response so that users have enough time to read and use the content.

Note:

See the related WCAG section: 2.2.1 Timing Adjustable. (Level A)

For URLs to be accessible to screen readers, they must be active links that are correctly tagged in the PDF. (The best way to create accessible links is with the Create Link command, which adds all three links that screen readers require to recognize a link.) Make sure that navigation links are not repetitive and that there is a way for users to skip over repetitive links.

If this rule check fails, check navigation links manually and verify that the content does not have too many identical links. Also, provide a way for users to skip over items that appear multiple times. For example, if the same links appear on each page of the document, also include a "Skip navigation" link.

Note:

See the related WCAG section: 2.4.1 Bypass Blocks. (Level A)

Forms

Tagged form fields

In an accessible PDF, all form fields are tagged and part of the document structure. In addition, you can use the tool tip form field property to provide the user with information or instructions.

To tag form fields, choose All tools > Prepare for accessibility > Automatically tag PDF. 

Note:

See the related WCAG sections: 1.3.1 Info and Relationships. (Level A), 4.1.2 Name, role, value

Field descriptions

For accessibility, all form fields need a text description (tool tip).

To add a text description to a form field:

  1. Select one of the Form tools, and then right-click (Windows) or Ctrl-click (Mac OS) the form field.
  2. Choose Properties from the context menu.
  3. Click the General properties tab.
  4. Enter a description of the form field in the Tooltip field.
Note:

See the related WCAG sections: 1.3.1 Info and Relationships. (Level A), 3.3.2 Labels or Instructions (Level A), 4.1.2 Name, role, value

Alternate text

Figures alternate text

Make sure that images in the document either have alternate text or are marked as artifacts.

If this rule check fails, do one of the following:

  • Select Figures Alternate Text in the Accessibility Checker panel, and choose Fix from the Options menu. Add alternate text as prompted in the Set Alternate Text dialog box.
  • Use the Tags panel to add alternate text for images in the PDF.
  • Open the Content panel and right-click (Windows) or Ctrl-click (Mac OS) the content that you want to mark as an artifact. Then, select Create Artifact from the context menu. (To display the Content panel, select the hamburger menu  (Windows) > View or select the View menu (macOS), and then select Show/Hide > Side Panels > Content.)
Note:

See the related WCAG section: 1.1.1 Non-text Content. (A)

Nested alternate text

Screen readers don't read the alternate text for nested elements. Therefore, don't apply alternate text to nested elements.

To remove alternate text from nested elements, do the following:

  1. Select the hamburger menu  (Windows) > View or select the View menu (macOS), and then select Show/Hide > Side Panels > Accessibility tags.
  2. Right-click (Windows) or Ctrl-click (Mac OS) a nested element in the Accessibility tags panel and choose Properties from the context menu.
  3. Remove the Alternate Text and the text to which it's applied from the Object Properties dialog box, then select Close.
Note:

See the related WCAG section: #1.1.1 Non-text Content. (A)

Associated with content

Make sure that alternate text is always an alternate representation of content on the page. If an element has alternate text but does not contain any page content, there is no way to determine which page it is on. If the Screen Reader Option in the Reading preferences is not set to read the entire document, then screen readers never read the alternate text.

  1. Right-click (Windows) or Ctrl-click (Mac OS) an item to check.
  2. Open it in the Accessibility tags panel. (To display the Accessibility tags panel, select the hamburger menu  (Windows) > View or select the View menu (macOS), and then select Show/Hide > Side Panels  > Accessibility tags.)
  3. Remove the Alternate Text from the Tags panel for any nested item that has no page content.
Note:

See the related WCAG section: 1.1.1 Non-text Content. (A)

Hides annotation

Alternate text can't hide an annotation. If an annotation is nested under a parent element with alternate text, then screen readers don't see it.

To remove alternate text from nested elements:

  1. Select the hamburger menu  (Windows) > View or select the View menu (macOS), and then select Show/Hide > Side Panels > Accessibility tags.
  2. Right-click (Windows) or Ctrl-click (Mac OS) a nested element in the Tags panel and choose Properties from the context menu.
  3. Remove the alternate text from the Object Properties dialog box and select OK.
Note:

See the related WCAG sections: 1.3.1 Info and Relationships. (Level A), 4.1.2 Name, role, value

Other elements alternate text

This report checks for content other than figures that require alternate text (such as multimedia, annotation, or 3D model). Make sure that alternate text is always an alternate representation of content on the page. If an element has alternate text but does not contain any page content, there is no way to determine which page it is on. If the Screen Reader Options in the Reading preferences is not set to read the entire document, then screen readers don't read the alternate text.

  1. Select the hamburger menu  (Windows) > View or select the View menu (macOS), and then select Show/Hide > Side Panels > Accessibility tags.
  2. Right-click (Windows) or Ctrl-click (Mac OS) a nested element in the Accessibility tags panel and choose Properties from the context menu.
  3. Remove the alternate text from the Object Properties dialog box and select OK.
Note:

See the related WCAG section: 1.1.1 Non-text Content. (A)

Tables

Because table structure can be complex, it is best practice to check them for accessibility manually.

Rows

This rule checks whether each TR in a table is a child of Table, THead, TBody, or TFoot.

See Correct table tags with the Tags panel.

Note:

Related WCAG section: 1.3.1 Info and Relationships. (Level A)

TH and TD

In a proper table structure, TH and TD are children of TR.

See Correct table tags with the Tags panel.

Note:

See related WCAG section: #1.3.1 Info and Relationships. (Level A)

Headers

For accessibility, it's necessary that all tables in the PDF have a header.

See Correct table tags with the Tags panel.

Note:

See the related WCAG section: 1.3.1 Info and Relationships. (Level A)

Regularity

To be accessible, tables must contain the same number of columns in each row, and rows in each column.

See Correct table tags with the Tags panel.

Note:

See the related WCAG section: 1.3.1 Info and Relationships. (Level A)

Summary

Table summaries are optional, but can improve accessibility.

  1. Select All tools > Prepare for accessibility > Fix reading order.
  2. Select the table by drawing a rectangle around it. 
  3. In the Fix reading order dialog box, select Table.
  4. Right-click (Windows) or Ctrl-click (Mac OS) Table.
  5. Click Edit Table Summary.
  6. Enter a summary and select OK.
Note:

See the related WCAG section: 1.3.1 Info and Relationships. (Level A)

Lists

List items

The check reports whether each List Item (LI) is a child of List (L). When this rule check fails, the structure of this list is incorrect. Lists must have the following structure: A List element must contain List Item Elements. And, List Item Elements can only contain Label Elements and List Item Body Elements.

To fix the list structure:

  1. Find the list in the Accessibility Checker panel by right-clicking (Windows) or Ctrl-clicking (Mac OS) the failed element and choosing Show In Tags Panel.
  2. Create elements, change the types of elements, or rearrange existing elements by dragging them.
Note:

See the related WCAG section: 1.3.1 Info and Relationships. (Level A)

Lbl and LBody

Lists must have the following structure: A List element must contain List Item Elements. And, List Item Elements can only contain Label Elements and List Item Body Elements. When this rule check fails, the structure of this list is incorrect.

To fix the list structure:

  1. Find the list in the Accessibility Checker panel by right-clicking (Windows) or Ctrl-clicking (Mac OS) the failed element and choosing Show In Tags Panel.
  2. Create elements, change the types of elements, or rearrange existing elements by dragging them.
Note:

See the related WCAG section: 1.3.1 Info and Relationships. (Level A)

Headings

Appropriate nesting

This rule checks nested headings. When this check fails, headings are not nested properly.

To fix the list structure:

  1. Find the list in the Accessibility Checker panel by right-clicking (Windows) or Ctrl-clicking (macOS) the failed element and choosing Show in Tags Panel.
  2. Create elements, change the types of elements, or rearrange existing elements by dragging them.
Note:

See the related WCAG section: 2.4.6 Headings and Labels. (Level AA). The order of headings is not required under WCAG, and is only an advisory technique.

WCAG mapping to PDF/UA

WCAG 2.0 ISO 14289 -1 (File) Techniques
1.1.1 Non-text Content. (A)
  • 7.3 addresses content requiring text alteration.
  • 7.18.1 paragraph four addresses control descriptions.
  • 7.18.6.2 addresses time-based media alternatives. Test, Sensory, and CAPTCHA use-cases are addressed via the technical means used.
  • 7.1 paragraph 1, sentence 2 addresses decoration.
1.2.1 Audio- only and Video- only (Prerecorded). (A)
  • 7.18.6.2 addresses time-based media alternatives. Design-specific. It's necessary that authors and developers consider this provision and ensure conformance.
1.2.2 Captions (Prerecorded). (A)
  • 7.18.6.2 addresses time-based media alternatives. Design-specific. It's necessary that authors and developers consider this provision and ensure conformance.
1.2.3 Audio Description or Media Alternative (Prerecorded). (A)
  • 7.18.6.2 addresses time-based media alternatives. Design-specific. It's necessary that authors and developers consider this provision and ensure conformance.
1.2.4 Captions (Live). (AA)
  • Design-specific. It's necessary that authors and developers consider this provision and ensure conformance.
1.2.5 Audio Description (Prerecorded). (AA)
  • 7.18.6.2 addresses time-based media alternatives. Design-specific. It's necessary that authors and developers consider this provision and ensure conformance.
1.2.6 Sign Language (Prerecorded). (AAA)
  • Design-specific. It's necessary that authors and developers consider this provision and ensure conformance.
  
1.2.7 Extended Audio Description (Prerecorded). (AAA)
  • Design-specific. It's necessary that authors and developers consider this provision and ensure conformance
  
1.2.8 Media Alternative (Prerecorded). (AAA)
  • 7.18.6.2 addresses time-based media alternatives. Design-specific. It's necessary that authors and developers consider this provision and ensure conformance.
  
1.2.9 Audio- only (Live). (AAA)
  • Design-specific. It's necessary that authors and developers consider this provision and ensure conformance.
  
1.3.1 Info and Relationships. (Level A)
  • 7.1 - 7.10 and 7.20 address structure and relationships in content.
  • 7.17 and 7.18 address structure and relationships in annotations.
1.3.2 Meaningful Sequence. (Level A)
  • 7.2 paragraph two addresses the meaningful sequence of content.
  • 7.17 addresses navigation features.
  • 7.18.3 addresses tab order in annotations.
1.3.3 Sensory Characteristics. (Level A)
  • 7.1, paragraphs 6 and 7
1.4.1 Use of Color. (Level A)
  • 7.1, paragraph 6
1.4.2 Audio Control. (Level A)
  • Design-specific. It's necessary that authors and developers consider this provision and ensure conformance.
1.4.3 Contrast (Minimum). (Level AA)
  • 7.1, paragraph 6 and note 4
1.4.4 Resize text. (Level AA)
  • Not applicable
1.4.5 Images of Text. (Level AA)
  • 7.3, paragraph 6
1.4.6 Contrast (Enhanced). (Level AAA)
  • 7.1, paragraph 6
  
1.4.7 Low or No Background Audio. (Level AAA)
  • While ISO 14289 does not address this success criterion, conformance in PDF requires ISO 14289 conforming files and readers. The manner in which developers support this success criterion in PDF in not defined in ISO 14289 or ISO 32000.
  
1.4.8 Visual Presentation. (Level AAA)
  • Design-specific. It's necessary that authors and developers consider this provision and ensure conformance.
  
1.4.9 Images of Text (No Exception). (Level AAA)
  • 7.3 paragraph 1
  
2.1.1 Keyboard. (Level A)
  • Not applicable
2.1.2 No Keyboard Trap. (Level A)
  • Design-specific. It's necessary that developers consider this provision and ensure conformance.
2.1.3 Keyboard (No Exception). (Level AAA)
  • 7.19, paragraph 3
  
2.2.1 Timing Adjustable. (Level A)
  • 7.19, paragraph three applies, but generally this rule is design-specific. It's necessary that developers consider this provision and ensure conformance.
2.2.2 Pause, Stop, Hide. (Level A)
  • 7.19
2.2.3 No Timing. (Level AAA)
  • 7.19
  
2.2.4 Interruptions. (Level AAA)
  • 7.19
  
2.2.5 Re- authenticating. (Level AAA)
  • Not applicable
  
2.3.1 Three Flashes or Below Threshold. (Level A)
  • 7.1, paragraph 5
2.3.2 Three Flashes.(Level AAA)
  • 7.1, paragraph 5
  
2.4.1 Bypass Blocks. (Level A)
  • Not applicable, unless the PDF includes repetitive real content. Page content, such as running headers and footers, must conform with 7.8.
2.4.2 Page Titled. (Level A)
  • 7.1, paragraphs 8 and 9
2.4.3 Focus Order. (Level A)
  • 7.1, paragraph 2, 7.18.1; paragraph 2, 7.18.3
2.4.4 Link Purpose (In Context). (Level A)
  • 7.18.5
2.4.5 Multiple Ways. (Level AA)
  • PDFs can conform with this provision in several ways, including outlines (7.17), links (7.18.5), and page labels.
2.4.6 Headings and Labels. (Level AA)
  • 7.4
2.4.7 Focus Visible. (Level AA)
  • Not applicable
2.4.8 Location. (Level AAA)
  • 7.4, 7.17
  
2.4.9 Link Purpose (Link Only). (Level AAA)
  • 7.18.5
  
2.4.10 Section Headings. (Level AAA)
  • 7.4
  
3.1.1 Language of Page. (Level A)
  • 7.2, paragraph 3.
3.1.2 Language of Parts. (Level AA)
  • 7.2, paragraph 3.
3.1.3 Unusual Words. (Level AAA)
  • Not addressed in ISO 14289. See ISO 32000-1, section 14.9.5.
  
3.1.4 Abbreviations. (Level AAA)
  • Not addressed in ISO 14289. See ISO 32000-1, section 14.9.5.
  
3.1.5 Reading Level. (Level AAA)
  • No Accessibility Support impact. This rule is design-specific. It's necessary that application or document authors consider this provision and ensure conformance.
  
3.1.6 Pronunciation. (Level AAA)
  • PDF provides several mechanisms for deploying media and other options for pronunciation assistance. Design-specific. It's necessary that authors and developers consider this provision and ensure conformance.
  
3.2.1 On Focus. (Level A)
  • 7.18, paragraph 2
3.2.2 On Input. (Level A)
  • 7.18, paragraph 2
3.2.3 Consistent Navigation. (Level AA)
  • 7.1, paragraph 1, 7.17
3.2.4 Consistent Identification. (Level AA)
  • 7.1, paragraph 1
3.2.5 Change on Request. (Level AAA)
  • 7.19, paragraph 2
  
3.3.1 Error Identification. (Level A)
  • Design-specific. It's necessary that authors and developers consider this provision and ensure conformance.
3.3.2 Labels or Instructions (Level A)  
4.1.2 Name, role, value  

More like this

 Adobe

Get help faster and easier

New user?

Quick links

View all your plans Manage your plans
View quick links
Hide quick links

Legal Notices    |    Online Privacy Policy