Checkpoint 24: Non-Interactive Forms

Non-interactive forms (designed to be printed and filled out by hand) must include the PrintField attribute to identify form field locations. This enables assistive technology users to understand where to write information when completing printed forms.

What This Means

PDF forms come in two types:

Interactive forms: Have digital form fields that users can type into
Non-interactive forms: Designed to be printed and completed with pen/pencil

Non-interactive forms present accessibility challenges because:

There are no interactive form fields to navigate
Visual cues (lines, boxes) indicate where to write
Screen readers cannot see these visual indicators
Users need to know what information goes where

PDF/UA requires the PrintField attribute on non-interactive form elements. This attribute marks areas where users should write when the form is printed, making the form structure accessible to assistive technology users.

The PrintField attribute identifies:

Text entry lines (name, address, etc.)
Checkboxes to be marked manually
Date fields
Signature lines
Any area where handwritten input is expected

Why It Matters

Non-interactive forms remain common in many contexts:

Government forms: Applications, tax documents, permits
Medical forms: Patient intake, consent forms
Legal documents: Contracts, affidavits, declarations
Educational materials: Worksheets, exams, registration forms
Business forms: Order forms, surveys, feedback sheets

For users who rely on assistive technology:

They need to know what information each blank requires
Screen readers must identify form field locations
Users may fill forms with assistance or use alternative methods
Understanding form structure is essential for completion

Without PrintField markup:

Screen readers encounter blank spaces without context
Users cannot determine what information is requested
Form completion becomes guesswork
Assistive technology cannot provide guidance

Consider a job application form with 20 blank fields. A sighted user sees labels next to each blank. Without PrintField markup, a screen reader user only hears the labels with no indication of where the corresponding blanks are located.

Common Violations

The Matterhorn Protocol defines one failure condition for non-interactive forms.

24-001: Non-Interactive Forms Not Tagged with PrintField Attribute (Human Testing)

What's Wrong: A PDF contains non-interactive form elements (blank lines, boxes, checkboxes for manual marking) but these elements are not tagged with the PrintField attribute.

How to Identify:

Determine if the form is non-interactive:
- Try clicking on blank areas; if nothing happens (no cursor appears), it is non-interactive
- Check for the absence of form fields in Acrobat's Prepare Form tool
- Look for visual cues (lines, boxes) that indicate handwritten entry
Check for PrintField attributes:
- Open the Tags panel
- Find elements that represent form blanks
- Check their properties for the PrintField attribute
- PrintField should be present on elements representing fill-in areas

Common Scenarios:

Fillable lines tagged as artifacts or figures without PrintField
Checkbox squares not identified as PrintField
Signature lines without PrintField marking
Table cells for handwritten entry lacking PrintField
Date blanks (//____) without PrintField

How to Fix in Adobe Acrobat

Identifying Non-Interactive Form Elements

Open the PDF in Adobe Acrobat Pro
Look for visual form elements:
- Horizontal lines for text entry
- Square boxes for checkboxes
- Rectangular areas for longer responses
- Signature lines
Go to Tools > Prepare Form
If Acrobat detects no form fields, confirm the form is non-interactive

Adding PrintField Attribute

Open View > Show/Hide > Navigation Panes > Tags
Locate the tag containing the form blank element
If the blank is untagged or tagged as Artifact:
- First create or assign an appropriate tag (Form, P, or appropriate structure)
Right-click the tag > Properties
Click the Tag tab
Click Edit Attribute Objects
Add a new attribute:
- Key: PrintField
- Value: true (or appropriate value for the type)
Click OK to save

Tagging Form Elements Properly

For each type of form element:

Text entry lines:

<P PrintField="true">
  Name: ____________________
</P>

Checkboxes:

<Form PrintField="Checkbox">
  [ ] Option A
</Form>

Signature areas:

<P PrintField="true">
  Signature: _________________ Date: ________
</P>

Using the Reading Order Tool

Go to Tools > Accessibility > Reading Order
Draw regions around form areas
Tag appropriately (Form or Text as needed)
After tagging, add PrintField attributes via Tag Properties

Creating Proper Form Structure

For complex forms, create a logical structure:

Document
├── Sect "Personal Information"
│   ├── P "Name:" + PrintField (for blank)
│   ├── P "Address:" + PrintField (for blank)
│   └── P "Phone:" + PrintField (for blank)
├── Sect "Preferences"
│   ├── P "Option A" + PrintField="Checkbox"
│   ├── P "Option B" + PrintField="Checkbox"
│   └── P "Option C" + PrintField="Checkbox"
└── Sect "Signature"
    └── P "Signature:" + PrintField + "Date:" + PrintField

Associating Labels with PrintFields

Ensure each PrintField has an associated label:

The label text should precede or clearly relate to the PrintField
Consider using the /TU (tooltip/alternate text) attribute for additional description
Structure should make the label-field relationship clear

How to Fix in Source Documents

Microsoft Word

When creating forms intended for print:

Use form controls symbolically:
- Do not use Word's interactive form fields for print forms
- Use underscores, boxes, or lines as visual indicators
Ensure proper labeling:
- Place labels immediately before or above blanks
- Use consistent formatting
After PDF export:
- Open in Acrobat
- Add PrintField attributes manually
- Word does not automatically create PrintField attributes

Creating Print Forms in Word

For text entry:

Name: _______________________
Address: ____________________

For checkboxes:

[ ] Option A
[ ] Option B

For signature lines:

Signature: __________________ Date: __________

Adobe InDesign

Design the form layout with clear visual indicators
Ensure labels are properly positioned
Export to PDF with tagging enabled
Post-process in Acrobat to add PrintField attributes

Best Practices for Print Form Design

Clear visual structure: Use lines, boxes, and spacing
Explicit labels: Every blank should have an associated label
Sufficient space: Allow adequate room for handwritten responses
Logical grouping: Group related fields (e.g., address fields together)
Instructions: Include clear instructions for completing the form

Alternative: Converting to Interactive Forms

Consider whether the form should be interactive instead:

Benefits of Interactive Forms

Users can type directly into the PDF
Form fields are inherently accessible
Data can be saved and processed electronically
Better experience for all users

When to Use Interactive Forms

Forms will primarily be completed digitally
Data collection and processing benefits from digital entry
Audience has access to PDF readers that support forms
Accessibility is a high priority

When to Keep Non-Interactive

Forms must be signed by hand
Primary use is print-and-mail
Legal requirements mandate paper submission
Users prefer or require paper forms

Converting to Interactive

In Adobe Acrobat:

Go to Tools > Prepare Form
Let Acrobat auto-detect form fields, or add manually
Configure each field with proper labels and tooltips
Test form field navigation and accessibility

Testing Your Fix

Manual Inspection

Open the Tags panel
Find each form element (blank line, checkbox, etc.)
Verify PrintField attribute is present
Check attribute value is appropriate
Ensure labels are associated with fields

Screen Reader Testing

Open PDF with NVDA, JAWS, or VoiceOver
Navigate through the form
Verify:
- Form fields are announced
- Labels are associated with fields
- The purpose of each blank is clear
- Navigation through the form is logical
Compare what the screen reader announces to the visual form

Content Review

Print the form
Compare printed output to accessibility structure
Verify every fill-in area has corresponding PrintField
Check that labels make sense without visual context

Validation Checklist

All text entry blanks have PrintField attribute
All checkbox areas have PrintField attribute
Signature lines have PrintField attribute
Each PrintField has an associated label
Labels clearly describe what information is needed
Screen reader properly announces form structure
Form navigation is logical and complete
Tab/arrow key navigation follows visual order

Special Considerations

Multi-Page Forms

For forms spanning multiple pages:

Maintain consistent structure across pages
Use section headings to organize content
Ensure page breaks do not separate labels from fields
Test navigation across page boundaries

Tables as Forms

When forms use table layouts:

Tag the table structure properly (Table, TR, TD)
Add PrintField to cells that require input
Use header cells (TH) for column/row labels
Ensure reading order flows logically through the table

Conditional Fields

For fields that apply only in certain situations:

Mark conditional instructions clearly
Still include PrintField on all potential entry areas
Use structure to group related conditional fields
Labels should indicate when fields apply

International Forms

For multilingual or international forms:

Ensure labels are in the appropriate language
Consider right-to-left reading order where applicable
Date and number format fields should indicate expected format
Address fields may need country-specific structure

Additional Resources

Official Standards and Guidelines

Form Accessibility

Tools

PAC (PDF Accessibility Checker) - Free PDF/UA validation
NVDA Screen Reader - Free screen reader for testing
CommonLook PDF Validator - Professional PDF validation

This documentation is based on the Matterhorn Protocol 1.02, the definitive reference for PDF/UA validation. Non-interactive form violations require human testing because automated tools cannot determine which visual elements represent form fields. For the most current information, consult the PDF Association and W3C WCAG guidelines.