Building Inclusive Applications

In today's digital age, it's common for applications to collect personal information from users for identification or authentication purposes. This article outlines best practices for building inclusive and accessible applications that meet the diverse needs of different users.

Provide alternative options for information collection

Not all users will feel comfortable providing certain types of personal information. Offer alternative options for verifying a user's identity whenever possible.

For example, allow users to establish a relationship with their name, email, and phone but collect and verify the individual's DOB, SSN, and address once the account is available for deposit or withdrawal activities.

Allow flexible data entry

Allowing your users to enter data flexibly can improve their experience with your application or service. Below are some tips:

• Give users freeform text fields instead of drop down menus for entering information such as names and addresses. This allows for cultural naming conventions and accommodates those with non-standard information.
• Provide clear and concise instructions on how to enter data into the system. Use simple language and provide examples to help users understand what is required.
• Allow users to enter data in multiple formats. For example, allow users to enter phone numbers with or without dashes or enter dates in different formats.
• Validate the information with inclusive regular expressions.

Be transparent about how data is used

To help users feel more comfortable sharing their personal information and build trust with your application, consider implementing the following:

• Clearly communicate the purpose of data collection and how users' personal information will be used and protected.
• Allow users to review your application's privacy policy.
• If possible, allow users to opt out of certain types of data usage.

Consider localization

When building applications intended for international users, it's important to properly localize the language and components used for collecting and validating personal information. Personal information, such as names, addresses, and identity documents, can vary significantly between countries and cultures.

Accommodate those with limited access to information

Some users may have limited access to official identification documents or other traditional verification forms, or only have access a basic feature phone or low-bandwidth connectivity.

It's important to accommodate these users when building your application, such as:

• Provide alternative means of verification. This can include allowing users to verify their identity through email or phone, or by providing alternative forms of identification, such as a passport or driver's license from their home country.
• Simplify the user interface, reduce the number of graphics or animations, and optimize images and other media to reduce their file size.
• Provide alternative means of access to the application. This can include providing a text-based interface or allowing users to access the application through SMS or voice commands.

Build with a trauma-informed approach

Some users may feel distressed at providing personal information due to past negative experiences. To accommodate these users, consider implementing the following:

• Minimize requests for information to only what is strictly necessary.
• Provide a clear explanation for why the information is needed and allow users to opt out of non-critical requests.
• Allow users to save their progress and return to the process later if necessary.