Forms

Many of us who create, manage or use forms probably have some experience with fillable PDF forms. While there are tools for automatically converting PDFs into fillable forms, too often, the results are inaccessible to many assistive technology users. They are also frequently difficult to fill out unless you have a paid version of Adobe.

Use HTML for Forms

Whenever possible, provide forms in HTML format rather than PDF. HTML forms are more accessible and easier to update and edit than PDF forms. Rice has options available to the community through Google Forms, Microsoft Forms, and Qualtrics that, with some attention, can create accessible options. Look for the Google Forms within your Google Workspace and Microsoft Forms within 365. The OIE department can provide access to Qualtrics.

• Google Forms
• Microsoft Forms
• Qualtrics Surveys are more advanced and offer more detailed options

Creating Forms in HTML Editors

If you decide to create your forms in HTML, be aware that there are certain requirements to make them usable and accessible.

Techniques for Forms and Labels in HTML

• Using label elements to associate text labels with form controls

• Using HTML form controls and links

• Providing descriptive labels

• Including the text of the visible label as part of the accessible name

• Matching the accessible name to the visible label

• Using labels, names, and text alternatives consistently for content that has the same functionality

• Providing text instructions at the beginning of a form or set of fields that describes the necessary input

WCAG Success Criteria Forms and Labels

• 1.3.1 Information and Relationships (A)

• 2.1.1. Keyboard (A)

• 2.4.6. Describe Headings and Labels (AA)

• 2.5.3. Label In Name (A)

• 3.2.4 Consistent Identification (AA)

• 3.3.2 Labels or Instructions (A)

Resources

• W3C, Form Concepts (article)

• WebAIM Form Accessibility (article)