Accessible account form
Create a signup form whose labels, guidance, and errors work without placeholders.Description
Requirements
Email, password, and terms controls each have a visible label associated through for and id.
The email control uses type email, the password control uses type password, and terms acceptance uses a checkbox.
Email and password controls expose the email and new-password autocomplete tokens.
The password input references the visible 12-character guidance through aria-describedby.
The terms checkbox is required before the form can be submitted.
The form contains a submit button with the accessible name Create account.
Password guidance
Focus the password input with assistive technology
The field label and the 12-character requirement are both announced
Constraints
Associate labels with controls using for and idUse the email and password input types with appropriate autocomplete valuesAssociate password guidance through aria-describedby and make terms acceptance required
Hints
Hint 1
List each control's visible name, native input purpose, and validation requirement before writing the markup.
Hint 2
Connect every label to a unique control id and supply autocomplete values that describe the expected data.
Hint 3
Reference the existing password guidance from its input, and make consent part of native form validation.