Are Documents Signed With Adobe Acrobat Sign Accessible?

E-signatures are crucial for streamlining workflows, allowing users to sign documents quickly and securely. However, maintaining accessibility for all users, including those with disabilities, is just as important. This article explores how Adobe Acrobat Pro DC Sign handles document accessibility before and after e-signing, identifies common accessibility issues, and suggests potential improvements.

Video Guide

Preparing a Document for Accessibility

Before applying an e-signature, it’s essential to ensure that the document is properly tagged for accessibility. Key elements include:

• Figure tags: Used to identify images or visual elements.
• Heading tags: Organize content with proper headings like H1 for titles.
• Form fields: Tagged as fillable, making them interactive and accessible for users with assistive technologies.

Steps to Ensure Accessibility Before E-Signing:

1. Tag all content: Apply appropriate tags to headings, figures, and form fields.
2. Check form fields: Ensure that form fields are fillable and accessible.
3. Run an accessibility check: Use Adobe Acrobat’s built-in accessibility checker to verify that all content is accessible before sending the document for e-signature.

E-Signing a Document in Adobe Acrobat Pro DC

Once the document is prepared and verified for accessibility, the next step is to send it for e-signature using Adobe Acrobat Pro DC’s “Request e-signature” feature.

Steps for E-Signing:

1. Select the Fill & Sign tool: Choose “Request e-signature” to send the document.
2. Send the document: Specify the recipient’s email and where the signature should be placed.
3. Sign the document: After the recipient fills out the form and adds a signature, Adobe Acrobat certifies the document, locking it to prevent further edits.

Once the document is locked, its accessibility may be compromised.

Testing Accessibility After E-Signing

After signing, an accessibility test using a screen reader (such as JAWS) can help determine if the content remains accessible. Initial tests show that while screen readers can read the document’s structure, such as headings and form labels, they often fail to read the actual content entered in the form fields, including the signature.

Key Findings from the Screen Reader Test:

• Structural elements: Headings and form labels remain accessible.
• Missing form content: Screen readers may not read the filled-in data, such as names and signatures.
• Signature metadata: Instead of reading the user’s signature, screen readers may only read metadata generated by Adobe, such as timestamps and certification information.

These results indicate that although the document’s structure remains accessible, the content entered during the signing process becomes inaccessible to assistive technologies.

Accessibility Issues with E-Signed Documents

The main issue with accessibility in e-signed documents arises from Adobe Acrobat’s process of locking the document after signing. Once the document is locked, users cannot make any changes, including accessibility-related adjustments. This limitation poses significant challenges for individuals who rely on assistive technologies.

Common Accessibility Issues Post-Signing:

1. Untagged content: Newly added content, such as signatures and timestamps, is not tagged for accessibility.
2. Inaccessible form data: The content entered in form fields during signing is often unreadable for screen readers.
3. Annotations not tagged: Any annotations added post-signing are not properly tagged for accessibility.
4. Tab order issues: Signed documents may experience tab order problems, affecting navigation for users relying on keyboards.
5. Missing alternate text: Elements lacking appropriate alternate text contribute to accessibility failures.

Although validating signatures ensures document authenticity, these accessibility issues persist after signing.

Read how Docusign compares with Adobe Sign in terms of accessibility.

Limitations and Future Improvements

Adobe Acrobat Pro DC’s current approach to e-signature accessibility presents notable limitations. Locking the document after signing prevents any further changes, including accessibility improvements. This highlights the need for future updates that prioritize accessibility.

Potential Future Improvements:

1. Tagging signed content: Adobe should ensure that signatures and form data added during the signing process are tagged for accessibility.
2. Allowing post-signing adjustments: Users should have the option to make accessibility changes after a document is signed.
3. Enhancing e-signature accessibility: Adobe could develop more robust tools that maintain accessibility throughout the e-signature process.

Adobe Acrobat Pro DC struggles to maintain document accessibility after an e-signature is applied. While the document’s structure remains intact, content added during the signing process—such as form data and signatures—becomes inaccessible to screen readers and other assistive technologies. Common issues include untagged content, failed tab orders, and missing alternate text.

To ensure that e-signed documents remain usable for all individuals, Adobe must prioritize accessibility in future software updates. Until these improvements are made, users should be aware of the limitations surrounding the accessibility of e-signed documents.

Let me be your champion for inclusion. I offer tailored solutions (and self-paced courses!) to ensure your documents meet and exceed compliance expectations. For more detailed insights, tutorials, and in-depth discussions on accessibility and related topics, don’t forget to check out my YouTube channel: The Accessibility Guy on YouTube. Subscribe for regular updates!