GenderMag
Last updated
Last updated
Copyright © 2021 MOSIP. This work is licensed under a Creative Commons Attribution (CC-BY-4.0) International License unless otherwise noted.
The GenderMag Methodology aims to analyze and mitigate gender biases in users’ problem-solving interactions with software. It underscores the importance of accounting for gender differences in human-computer interaction (HCI) during the software design process.
Process
We identified two personas based on their familiarity with technology and their ability to embrace technological progress. The personas are:
Abi, who is either Abigail or Abishek, is 45 years old. She works as a homemaker, is literate, but not very tech- savvy. Her internet connectivity is moderate, and she does not have a personal phone.
Tim, who is either Timothy or Timara, a 24-year-old financial consultant, is literate, tech-savvy, and boasts excellent internet connectivity. Additionally, he owns the latest phone.
Examine the feature, systematically walk through the process, assess their information handling, and pinpoint any problems.
During the walkthrough, we pinpointed inclusivity concerns in the Inji Wallet app’s user interface and experience. Subsequently, we took steps to mitigate these issues, aiming to eliminate digital entry barriers.
As part of Phase1, below P1 items are fixed in the v0.11.0-Inji Wallet release:
| Sl No | Problem statement | Solution | Jira number |
|---|---|---|---|
As part of Phase2, below P1, P2 items are fixed in the v0.12.0 release of Inji Wallet:
| Sl No | Problem Statement | Solution | Jira number |
|---|---|---|---|
1
The term “scan” can be ambiguous because scanning a QR code within an app might result in a money transfer from a bank account. This perception could be influenced by cultural factors. Abi, instead of directly clicking on the “Scan” option, prefers to select her card and then look for a “Share” option. Unless external assistance is available, Abi will avoid using the “Scan” feature.
Without external assistance, unless there are instructions visibly posted on the wall, she might find it challenging to comprehend whether she needs to select the “scan” option.
The Scan Button in the Navigation Bar can now be referred to as “Share”.
2
On the "Retrieve your ID" screen, instead of using "VID auto population," consider using "Download ID." This change will help avoid confusion for Abi, who might expect an explanation of what VID / UIN IDs are.
On the "Home with cards view," Abi might wonder why her card displays "Activation Pending," while the other card shows Activated for online login".
In the FAQ or Help section, provide information about the various types of IDs, their locations, and instructions on how to download them using different ID methods.
Provide additional information related to "Activation Pending," and ensure clear icon translations for "Activation Done" versus "Activation Pending".
3
When the user clicks on the "Add" button, the options "Generate your card" or "Retrieve your ID" might be confusing.
The description should also include an explanation of why the verification process is necessary.
When the user glances at the screen, the "AID" is not immediately evident.
Update main screen name to "Download your card".
Update main screen description to "Select ID type and enter the MOSIP provided UIN or VID you wish to download." (Also, with a reference to upcoming OTP screen).
Enhance the text to provide a heads up about the upcoming step of OTP verification, so that user is prepared to receive and enter the OTP.
Update bottom line text to "Don't have UIN / VID? Get it now using your AID."
1
Screen name: Retrieve your UIN/VID on clicking Get it now using your AID link
It is confusing for Abi as she has to walk through a lot of steps to get her card. Though it is mentioned as AID, she would be happy but may / may not move forward as it is going to get UIN but not a card.
Update screen name to "Get your UIN/VID." instead of Retrieve your UIN/VID
2
The Resend Code is unclear in the OTP screen.
The Resend Code Text can be more descriptive. “Resend OTP” would be more clear than “Resend code”
The Resend code is confusing as to whether it is clickable or not.
Rename “Resend code” as “Resend OTP”
3
Though Tim is tech savvy, Tim will be sort of puzzled why the app needs location access as well despite a lot of other permissions provided. Tim will be unhappy and question why they are required to provide location access in order to scan a QR code.
Description can be more indicative of the specific purpose of seeking location access.
4
Abi is not so familiar with tech, when the app says share a selfie, they might not know, face auth using her photo, is going in the background. she might think it will break her privacy.
Abi might be confused, as she cannot understand what is the next action to be done, from the instruction. it does not mention whether she has to click on the shutter button or it will take a picture automatically although she would perform the subgoal. Will it automatically click the selfie or do Abi need to click on the button?
For problem statement 1:
Provide assurance wrt Privacy
Terminology update: Face Authentication to Face Verification
Acquaint user with text about "Share with selfie" feature, informing user about face authentication - Through FAQs
Avoid usage of slang jargons like selfie → need confirmation from the product team on the alternative <Sasi>: Let us retain the word as that is more relatable to all.
For problem statement 2:
Enhance text: In the Face Verification screen, the text should be enhanced as "Hold the phone steady, keep your face focused in the centre and click on Capture" below the camera placeholder.
5
The description in the camera screen is not explaining about the sharing credential. Text near the scanner can mention about the “Hold the phone steady and scan the QR code to share your credential”.
Enhance text in Share page while scanning QR code. Text near the scanner can mention about the “Hold the phone steady and scan the QR code to share your card."
Change CTA from "Scan" to "Share"
6
Unlock App screen:
Abi would be stressed if she doesn’t remember the passcode. As there is nothing on the screen to get help. She might not know what to do because she is risk averse.
Add text: Tap on the button to unlock you app with the PIN or biometrics - Text to be enhanced in the unlock screen to clearly call out on other options.
“To unlock the app securely, you can set up either biometric authentication, such as fingerprint or facial recognition or opt for a 6-digit Passcode for quick access. Choose 'Use Biometrics' to enable biometric authentication or 'I'll Do Later' to set up a 6-digit passcode.”
CTAs:
Use Biometrics
I’ll Do Later
7
During the VC sharing, the successful transfer screen closes in a split second leaving the user clueless on the action status. The transition was quick, and no document is shown after the successful transfer. hence Abi is not clear if the sharing is successful or not.
Consider having an Error screen with CTA, clearly indicating the next expected action > Retry
8
No Information related to the selfie captured process was not conveyed to the users, even in the end screen. Selfie capture process does not relate back to the ID sharing process. No message regarding what happened with the selfie clicked.
Post face capture and before initiating the sharing process, inform users about successful face verification/match - But without any CTA.