Perform usability testing for the mobile security slider
= Background =
Tor is broadly aiming to 1) prioritize mobile users and 2) make the desktop version of Tor browser and Tor browser mobile (currently orfox, but will be rebranded) consistent. The security slider allows the user to choose their security level while using tor browser. Since this is not on the mobile application yet, adding this feature accomplishes both of the aforementioned goals. While adding the feature to the mobile version, we made some changes from the desktop version to improve the interface and make the UI more mobile-appropriate. If you are curious about how and why we made the changes to the security slider you can look at the project page.
The purpose of this test is to see if the security slider is usable. Specifically, the metrics for success are:
- Control: the user understands how to change their settings.
- Communication: the user understands what each setting does (literally understand--“to make the setting from safe to safer, I slide this button over”, not that they understand what each setting means or how it is technically implemented).
- Comprehension: the user knows how the settings will affect their browsing (again, this along the lines of “this is what I want,” “this makes this feature go away and I do/don’t like that” not that they understand how JS is a vector for exploits or even is aware of the difference between http and https websites).
- Decision: the user is able to make the decision that they want.
We are not testing: if the Tor browser mobile is easy to find on the app store, if people are able to install it on their phone, if it is easy to use, or if the security slider is easy to find in the menu.
We are running a small-scale, short, qualitative, open-ended, qualitative user test.
- Small-scale: we are testing with 5 users. Read about when it is appropriate if you are curious.
- Open-ended: users are free to answer the question in their own words. This is to allow the users to speak more freely and to communicate naturally. (the opposite would be closed ended, and would involve asking the user to rank/rate/label the interface, “how hard is it from 1 to 10?. This works better for larger groups, but not small groups.)
- Qualitative: we are focusing on user attitude and comprehension (do they like it, will they use it, are they able to use it). We are not concerned with user behavior (how many people use which setting, how many clicks, how many seconds) for this phase in testing.
= Materials =
What we will give to our partners as background and instructions: https://drive.google.com/open?id=1aE1txcRdJ9u5Der2-k9i-eq8mzvyPyAdmrPGlVKyPxo
Interview questions and feedback form: https://drive.google.com/open?id=1yYCLZtZuvK_0EICCiXbxQTHFJUhRHJ_rJgdMO5AR-uA