Forms must be accessible, intuitive, and WCAG-compliant, enabling users to complete key actions easily and consistently across devices.

Required Form Elements

All forms must include:

• Clear, descriptive field labels: Tell users exactly what information is needed
• Required fields marked both visually and in text: Use asterisks (*) and "required" text
• Simple, field-level instructions where needed: Provide format examples and constraints
• Helpful, accessible error messages: Explain how to correct mistakes
• WCAG-compliant validation and keyboard navigation: Ensure full keyboard accessibility
• Required privacy and data-use statements: Inform users how their data will be used
• Approved formatting and consistent layout: Follow university design patterns

Form Design Requirements

Forms must:

• Be fully fillable and easy to submit: Test across devices and browsers
• Use plain language: Avoid jargon or long paragraphs
• Follow a logical, linear flow: Group related fields together
• Minimize unnecessary fields: Reduce user burden by only asking for essential information
• Integrate cleanly with systems: Work with Slate, Qualtrics, Microsoft Forms, or other approved platforms

Accessibility Standards

• Label association: Every input must have a properly associated label element
• Error identification: Clearly identify fields with errors using color AND text/icons
• Focus indicators: Visible keyboard focus with 3:1 contrast ratio
• Tab order: Logical navigation order matching visual layout
• Screen reader support: Use ARIA labels when visual labels aren't sufficient
• Touch targets: Minimum 44x44px for mobile accessibility

Error Handling

• Inline validation: Provide immediate feedback when possible
• Clear error messages: Explain what went wrong and how to fix it
• Error summary: List all errors at the top of the form with links to problem fields
• Preserve user input: Don't clear correctly filled fields when errors occur
• Success confirmation: Clearly indicate when form submission is successful

Form Field Best Practices

Text Inputs

• Use appropriate input types (email, tel, number)
• Set reasonable character limits
• Provide format examples for complex inputs
• Enable autocomplete where appropriate

Radio Buttons & Checkboxes

• Use radio buttons for single selection from 2-5 options
• Use checkboxes for multiple selections or single yes/no choices
• Ensure adequate spacing between options (minimum 44px height)
• Group related options with fieldset and legend elements

Dropdown Menus

• Use for 6+ mutually exclusive options
• Provide a meaningful default option ("Select one...")
• Order options logically (alphabetical, chronological, or by frequency)
• Avoid very long lists (consider alternatives for 20+ items)

Privacy and Consent

• Data collection notice: Explain why information is being collected
• Privacy policy link: Provide easy access to the university's privacy policy
• Consent checkboxes: Use for opt-in communications (not pre-checked)
• FERPA compliance: Ensure student data handling meets federal requirements

Approved Platforms

• Slate: Primary platform for admissions and recruitment forms
• Qualtrics: Surveys and research data collection
• Microsoft Forms: Internal forms and simple data collection
• Custom forms: Must be reviewed by Digital Communications for compliance