53 Input Purposes for User Interface Components

Semantic Markup for input fields reminds me of microformats

The purpose for each common input field that collects an individual's personal data MUST be programmatically defined based on the list of 53 Input Purposes for User Interface Components.

The intent of this success criterion is to programmatically provide additional information about form inputs (like address, phone number, and password fields) so that the information can be outputted to different modalities. Assistive technologies can use this information to help the user in various ways, including automatically completing forms, filling in usernames and passwords, and pairing custom icons with form elements for users who prefer using images for communication.

The W3C provides a full list of inputs covered by this criterion opens in a new window which is built on the input purposes included in HTML 5.2 Autofill, so using HTML 5.2 Autofill is a good way to meet this success criterion. This success criterion only applies to text inputs asking for information about the user themselves. It does not apply to text inputs asking for information about anyone other than the user, and it does not apply to any input types that are not text. Success Criterion 1.3.6 “Identify Purpose” is level AAA and builds on this requirement.

Tagged with

← Previous Racial justice and tech Web Accessibility : Form Labels, Instructions, and Validation Next →