Overview
The current account creation screen asks for a user's first and last name, but this can be problematic and exclusive as not all individuals have standard western European names. The goal of this issue is to update the screen to use the full name instead.
Note: The current Postgres schema requires First Name & Last Name. This needs to be addressed.
This improvement brought to light the need for an 'Improvement' issue form. The creation of that form is tracked at
Background
The use of full name as the sole identifier in forms is the industry best practice, as demonstrated in the referenced article. This change will make the account creation process more inclusive and user-friendly.
🤠 Hat Tip: @TheETupper for bringing this to light in Slack
References
Does your form have two separate fields for the user's name? If it does, you're making it harder for them to fill out your form. But there's a better way. Split Name Fields Cause Problems Not every user has a first and last name. Their cultural background determines how their name is formed. For example, […]
Acceptance Criteria
Team
🖼️ Front End
Overview
The current account creation screen asks for a user's first and last name, but this can be problematic and exclusive as not all individuals have standard western European names. The goal of this issue is to update the screen to use the full name instead.
Note: The current Postgres schema requires
First Name&Last Name. This needs to be addressed.This improvement brought to light the need for an 'Improvement' issue form. The creation of that form is tracked at
Background
The use of full name as the sole identifier in forms is the industry best practice, as demonstrated in the referenced article. This change will make the account creation process more inclusive and user-friendly.
🤠 Hat Tip: @TheETupper for bringing this to light in Slack
References
Why Your Form Only Needs One Name Field
Acceptance Criteria
Team
🖼️ Front End