Enable Acrobat Sign to tag uploaded PDFs for accessibility - New

Last updated on Nov 18, 2026
Alert

This article contains prerelease information. Release dates, features, and other information are subject to change without notice.

Improve screen reader navigation by automatically adding document structure to eligible PDFs when agreements are sent

Adobe Acrobat Sign can automatically add basic accessibility tags to eligible untagged PDFs, helping recipients who use screen readers navigate document content more effectively. The feature identifies structural elements such as headings and reading order, providing a more organized reading experience without requiring senders to tag every document manually.

Administrators can enable automatic tagging for their account or individual groups. Once enabled, Acrobat Sign attempts to tag eligible documents during the sending process. The feature is best suited to text-based PDFs that don't already contain accessibility tags.

Automatic PDF tagging configuration

Availability

  • Environments: Commercial, Sandbox

  • Access: Available to eligible accounts with administrator access to Send Settings.

  • Permissions: Account and group administrators can configure the feature.

Configuration scope

  • Account: Configure automatic tagging for the account.

  • Group: Configure automatic tagging for an individual group.

Default value

  • Disabled: Automatic PDF accessibility tagging is turned off by default.

  • Enabled: Acrobat Sign attempts to tag eligible untagged PDFs when agreements are sent.

In-flight impact

  • Automatic tagging occurs during agreement sending, before recipients access the document.

  • Changing the configuration does not retroactively add accessibility tags to agreements that have already been sent.

Enable automatic PDF tagging

Go to Account Settings > Send Settings > Improve accessibility of PDF agreements.

Send Settings showing the enabled Auto tag non-tagged PDFs option under Improve accessibility of PDF agreements.
Enable automatic accessibility tagging for eligible untagged PDFs at the account or group level.

What the setting controls

Option

Behavior

Enabled

Acrobat Sign checks eligible PDFs for existing accessibility tags and attempts to add structural tags when none are present.

Disabled

Acrobat Sign does not automatically add structural tags through this feature. Documents proceed through the normal sending process.

Automatic tagging applies at send time, rather than when a document is uploaded or saved as a library template. Senders don't need to select an additional option when preparing an agreement.

How automatic tagging works

When a sender initiates an agreement, Acrobat Sign checks whether automatic tagging is enabled and whether the agreement PDF is eligible.

If the PDF has no existing tag tree and meets the eligibility requirements, Acrobat Sign attempts to add structural tags before making the agreement available to recipients. These tags provide basic document organization, including headings and reading structure, that can help assistive technologies interpret the content.

The feature supports agreements created through:

  • Request Signature

  • Library templates used to create agreements

  • Web forms

  • Custom sending workflows

  • API-created agreements

Library templates themselves aren't automatically tagged when created or saved. Eligible agreements generated from those templates can be tagged during sending.

Automatic tagging can increase processing time before recipients receive the agreement. Senders don't see a separate tagging indicator or receive a notification confirming whether tagging succeeded.

Document eligibility and limitations

Automatic tagging applies to untagged, text-based PDFs that meet the processing requirements.

Document condition

Automatic tagging behavior

Untagged, text-based PDF

Eligible for structural tagging

Combined agreement PDF exceeds 10 MB

Tagging is skipped

Combined agreement PDF exceeds 25 pages

Tagging is skipped

PDF already contains a tag tree

Existing tags are left unchanged

Partially tagged PDF

Tagging is skipped because a tag tree already exists

Scanned or image-only PDF

OCR and image tagging aren't supported

PDF contains form fields

The feature doesn't add accessibility tags to form fields

Document contains an existing digital signature and digital signature preservation is enabled

Tagging is skipped

Agreement uses document reflow processing

Tagging is skipped

Automatic tagging provides basic structural improvements. It does not add alternative text to images, perform OCR, or guarantee that documents meet accessibility standards.

Documents requiring full accessibility support should be prepared and validated before they're sent. See Create accessible PDFs for guidance.

Processing failures and skipped documents

Automatic tagging uses a best-effort process designed to avoid blocking agreements.

When tagging cannot complete, fails, or exceeds the allowed processing time, Acrobat Sign continues sending the agreement using the original untagged PDF. The sender receives no separate failure notification.

Documents that don't meet the eligibility requirements are sent without automatic structural tagging.

Verify that accessibility tags were added

To confirm whether tagging succeeded, download the agreement PDF from the Manage page and open it in Adobe Acrobat.

Inspect the PDF's accessibility tag structure to determine whether a tag tree is present. The presence of tags confirms that the PDF contains structural information, but it does not establish full accessibility compliance.

For the agreement download procedure, see Download the PDF of an agreement

Relationship to tagged-PDF generation

Acrobat Sign also provides an independent setting named Enable Tagged PDF Generation, under Global Settings > Accessible PDFs.

These settings address different parts of document accessibility:

Setting

Purpose

Auto tag non-tagged PDFs

Attempts to add basic structural tags to eligible PDFs that have no existing tag tree.

Enable Tagged PDF Generation

Preserves existing source-document tags and supports appropriate tagging of content entered into agreement form fields.

The settings operate independently. Enabling one does not require enabling the other.

Organizations that prepare fully accessible source documents should continue using established document-authoring and accessibility-validation practices. Automatic structural tagging is an additional capability for eligible untagged PDFs, not a replacement for those practices.