Checkpoint 23: Digital Signatures

Digital signature fields in PDF documents are a type of form field and must meet the same accessibility requirements as other form fields. This checkpoint acknowledges that digital signatures have no unique accessibility failures beyond general form field requirements.

What This Means

Digital signatures in PDFs serve to:

• Authenticate documents: Verify the signer's identity
• Ensure integrity: Confirm the document hasn't been altered
• Provide non-repudiation: The signer cannot deny signing
• Meet legal requirements: Satisfy electronic signature regulations

From a PDF structure perspective, digital signature fields are implemented as a type of interactive form field. They share the same technical foundation as text fields, checkboxes, and other form elements.

The Matterhorn Protocol recognizes that digital signatures do not introduce unique accessibility challenges beyond those already addressed by form field requirements. Therefore:

1. Checkpoint 23 exists to acknowledge digital signatures as a category
2. It defers to other form-related checkpoints for actual requirements
3. No specific testing unique to digital signatures is required
4. Standard form field accessibility rules apply

Why It Matters

While this checkpoint has no unique testing requirements, understanding digital signature accessibility matters:

User interaction:

• Users must be able to locate and activate signature fields
• The purpose of the field must be clear
• Instructions for signing should be accessible
• Status of signed/unsigned should be determinable

Assistive technology compatibility:

• Screen readers must announce signature fields
• Users must be able to navigate to signature fields via forms mode
• Signing workflows should be operable with keyboard and assistive technology

Form field context:

• Signature fields exist within the broader form context
• All form accessibility principles apply
• Labels, tab order, and tooltips are relevant

Legal accessibility:

• Documents requiring signatures often have legal implications
• Inaccessible signature processes may exclude people with disabilities
• Accessibility supports equal access to legal transactions

Common Violations

The Matterhorn Protocol defines one failure condition for digital signatures.

23-001: Other Provisions Apply (Form Fields)

What's Defined: This failure condition explicitly states that digital signatures are subject to the same accessibility requirements as other form fields. There are no unique digital signature failures defined.

Implications:

• Check digital signature fields against all form field checkpoints
• Ensure signature fields have proper labels/tooltips
• Verify tab order includes signature fields appropriately
• Confirm signature fields are keyboard accessible

No Specific Testing Required:

• This checkpoint does not require unique tests
• Apply standard form field testing to signature fields
• Review related checkpoints for form accessibility requirements

Related Checkpoints: While Checkpoint 23 itself has no unique tests, digital signature fields should comply with general form accessibility principles, which may be covered in other checkpoints or WCAG requirements:

• Form fields should have labels or tooltips
• Tab order should be logical
• Instructions should be provided where needed
• Status changes should be communicated

How to Ensure Accessibility

Although no unique testing exists, ensure digital signature fields follow best practices.

Labeling Signature Fields

1. Open your PDF in Adobe Acrobat Pro
2. Go to Tools > Prepare Form
3. Click on the digital signature field
4. In the Properties dialog:
   • Provide a clear Name (internal identifier)
   • Add a Tooltip describing the field's purpose
   • Example tooltip: "Sign here to acknowledge receipt"
5. Click Close

Verifying Tab Order

1. In Prepare Form mode, go to View > Navigation Panels > Fields
2. Check the field order in the Fields panel
3. Ensure signature fields appear in logical sequence
4. Reorder by dragging fields if needed

Providing Instructions

1. Add clear text near signature fields explaining:
   • What the signature acknowledges
   • Who should sign
   • Any relevant instructions
2. Tag this text properly as form instructions
3. Ensure it's read before the signature field in reading order

Testing Keyboard Access

1. Press Tab to navigate through the form
2. Confirm you can reach the signature field
3. Test activating the signature with Enter or Space
4. Ensure the signing dialog is accessible

How to Create Accessible Signature Fields

Adobe Acrobat

Creating new signature fields:

1. Open your PDF in Adobe Acrobat Pro
2. Go to Tools > Prepare Form
3. Click Add a signature field (or select from form tools)
4. Draw the field where signatures should appear
5. Double-click the field to open Properties
6. On the General tab:
   • Enter a clear Name
   • Add a Tooltip explaining the field
7. On the Appearance tab:
   • Configure visual appearance
   • Ensure sufficient size for visibility
8. Click Close

Adobe Sign / Document Cloud

When using Adobe's e-signature services:

1. Place signature fields during document preparation
2. Label each signature field clearly
3. Use recipients' names or roles in field names
4. Add instructions as needed
5. The platform handles much of the accessibility automatically

Other E-Signature Platforms

For DocuSign, HelloSign, and similar services:

1. Follow the platform's accessibility guidelines
2. Place and label fields clearly
3. Test the signing experience with assistive technology
4. Report accessibility issues to the platform provider

Testing Your Implementation

Standard Form Field Tests

Apply these tests to digital signature fields:

1. Label presence: Does the field have a tooltip or associated label?
2. Tab accessibility: Can the field be reached via Tab key?
3. Activation: Can the field be activated with keyboard?
4. Screen reader: Does a screen reader announce the field and its purpose?
5. Visual identification: Is the field visually identifiable?

Screen Reader Testing

1. Open the PDF with NVDA, JAWS, or VoiceOver
2. Navigate to forms mode (usually Insert+F7 in JAWS or NVDA+F7)
3. Find the signature field in the forms list
4. Navigate to the field
5. Verify the screen reader announces:
   • That it's a signature field
   • The tooltip/label text
   • Any associated instructions

Keyboard Navigation

1. Open the PDF and start at the beginning
2. Press Tab repeatedly to navigate form fields
3. Reach the signature field
4. Press Enter or Space to activate
5. Complete or cancel the signing dialog
6. Continue tabbing to verify proper flow

Validation Checklist

• Signature field has a tooltip or label
• Field purpose is clearly described
• Tab order includes the signature field appropriately
• Field is keyboard accessible
• Screen reader announces the field properly
• Instructions near the field are accessible
• Signing dialog/process is accessible
• Signed status is communicated appropriately

Digital Signature Best Practices

Clear Purpose Communication

• Before signing: Explain what the signature acknowledges
• Field labeling: Use descriptive tooltips
• Instructions: Provide clear guidance on signing process
• Confirmation: Confirm successful signature completion

Visual and Non-Visual Access

• Ensure signature fields are visually identifiable
• Provide text alternatives for any signature-related graphics
• Don't rely solely on color to indicate signature status
• Make signed/unsigned status determinable by assistive technology

Process Accessibility

The signing workflow should be accessible:

1. Document opening and navigation
2. Locating signature fields
3. Initiating the signing process
4. Completing authentication (if required)
5. Applying the signature
6. Confirming successful signing

Legal and Compliance Considerations

• Accessible signing processes support legal compliance
• Some jurisdictions require accessible digital signatures
• Document your accessibility measures for compliance records
• Test with actual assistive technology users when possible

Additional Resources

Official Standards and Guidelines

• PDF Association Matterhorn Protocol 1.02
• ISO 32000-2: Digital Signatures in PDF
• W3C WCAG 2.1: Forms

Digital Signature Resources

• Adobe Sign Accessibility
• DocuSign Accessibility
• PDF Association: Digital Signatures

Form Accessibility Resources

• WebAIM: Creating Accessible Forms
• PDF/UA Technical Implementation Guide
• Adobe Acrobat: Creating Accessible PDFs

Tools

• Adobe Acrobat Pro - Signature field creation
• PAC (PDF Accessibility Checker) - General form validation
• NVDA Screen Reader - Free screen reader for testing

This documentation is based on the Matterhorn Protocol 1.02, the definitive reference for PDF/UA validation. Checkpoint 23 acknowledges that digital signatures are form fields subject to general form accessibility requirements, with no unique failures defined. For the most current information, consult the PDF Association and W3C WCAG guidelines.