Skip to main content

Form (Fillable or Static)

informationalclassification scope
Document Class: CLASS-2Form (Fillable or Static)
Remediation: full
Complexity: medium

Forms in PDFs or documents can't be filled out by people using screen readers or keyboard navigation. Citizens with disabilities may be unable to submit applications, permits, or other required government forms, creating ADA Title II compliance issues.

Who Is Affected

Screen reader users, people with motor disabilities who rely on keyboard navigation, users with cognitive disabilities who need clear form instructions, and anyone using assistive technology to complete government forms.

What This Means

Forms are interactive documents that collect information from the public. When forms aren't properly structured, people using assistive technology encounter several barriers:

  • Form fields appear as unlabeled blank spaces to screen readers
  • Tab navigation jumps erratically between fields
  • Required field indicators aren't announced
  • Error messages don't connect to specific fields
  • Instructions are separated from the fields they describe

This affects critical government services like permit applications, benefit enrollment, complaint forms, and voter registration.

Fix: Document

Forms require comprehensive remediation to ensure all interactive elements work with assistive technology. The complexity depends on whether you're working with a fillable PDF or creating accessible alternatives.

For Fillable PDFs (Adobe Acrobat Pro Required)

  1. Run the Accessibility Checker

    • Open the form in Adobe Acrobat Pro
    • Go to Tools → Accessibility → Full Check
    • Review all form-related failures
  2. Add Form Field Labels

    • Right-click each form field → Properties
    • On the General tab, enter a descriptive name in the "Tooltip" field
    • For checkboxes and radio buttons, ensure the label describes the choice
  3. Set Tab Order

    • Go to Tools → Accessibility → Set Tab Order
    • Arrange fields in logical reading sequence
    • Test navigation using only the Tab key
  4. Mark Required Fields

    • In form field Properties → General tab
    • Check "Required" if the field is mandatory
    • Add visual indicators (* or "Required") near field labels
  5. Group Related Fields

    • For radio button groups, ensure they share the same name
    • Use fieldsets for related form sections (address, contact info)
  6. Add Form Instructions

    • Place instructions directly before relevant form sections
    • Use proper heading structure for form sections
    • Include format requirements (date format, phone number style)

For Static Forms (Scanned or Image-Based)

Static forms require conversion to accessible formats:

  1. Convert to Fillable PDF

    • Use Adobe Acrobat Pro's "Prepare Form" tool
    • Manually add form fields over the static image
    • Follow the fillable PDF steps above
  2. Create Web-Based Alternative

    • Build the form using HTML with proper labels and structure
    • Provide a link to the web form alongside the PDF
    • Ensure the web version collects identical information
  3. Provide Alternative Formats

    • Create a Word document version with form fields
    • Offer the form in plain text format
    • Include contact information for phone-based completion

Quality Assurance

  1. Test with Screen Reader

    • Use NVDA (free) or JAWS to navigate the entire form
    • Verify all fields are properly announced
    • Confirm instructions are read in context
  2. Test Keyboard Navigation

    • Navigate using only Tab, Shift+Tab, and arrow keys
    • Ensure no fields are skipped or unreachable
    • Verify form submission works via keyboard
  3. Validate with Accessibility Checker

    • Run PAC 3 or Adobe's checker after remediation
    • Address any remaining form-related issues
    • Document any manual checks required

Standard Reference

This document class addresses multiple WCAG 2.1 criteria related to form accessibility:

  • 1.3.1 Info and Relationships — Form fields must have programmatic labels
  • 1.3.5 Identify Input Purpose — Fields should identify their expected input type
  • 3.3.1 Error Identification — Form errors must be clearly identified
  • 3.3.2 Labels or Instructions — Form fields require clear labels and instructions
  • 4.1.2 Name, Role, Value — Form controls must expose their properties to assistive technology

Relevant PDF Techniques:

  • PDF5 — Indicating required form controls in PDF forms
  • PDF10 — Providing labels for interactive form controls in PDF documents
  • PDF12 — Providing name, role, value information for form fields in PDF documents
  • PDF15 — Providing submit buttons with the submit-form action in PDF forms
  • PDF22 — Indicating when user input is required or input formats in PDF forms
  • PDF23 — Providing interactive form controls in PDF documents

Check if your government website has this issue

OctoComply scans your website and documents for WCAG 2.1 AA violations. The free tier covers up to 10 pages.

Run a Free Scan