#9 Consentful Interface

Asking your permission

You can view my code here:)

Images taken with Kruger Cam

.
.

.
.

.
.

.
.

.
.

.
.

Description

Using the F.R.I.E.S model outlined in : Consentful Tech Zine, I iterated on the interface I had worked on last week when users try accessing the Kruger Cam.

When users click on the camera page, the browser immediately asks for permission to access the user's camera and the user is 'forced' to give permission even before seeing what the camera or project is about. This was definitely what I wanted to work around by informing users about the camera before asking them for permission.

As there was no way to toggle the browser asking for permission on or off, I decided to have a welcome interface introducing the camera to users and informing them that if they want to check out the camera, they would be required to give access to their camera. Only if they are comfortable with this will they be redirected to the camera in a new browser page. This is where the browser asks them for permission to access their camera. Once they agree, the camera opens and they can use it. If they change their mind and choose not to share their camera anymore, they can simple click on the close button on the top left which will close the entire tab altogether, cutting access to their camera and automaticlly taking them back to the welcome interface tab.

F.R.I.E.S model

  • Freely Given: Users are not misled, manipulated or pressured into giving access to their camera in any way. The users are free to choose depending on whether they are comfortable or not.
  • Reversible: At every stage the users can change their mind and go to the previous step. When the camera is open, suers are free to click on the close button on the top left, which closes the entire tab itself. They needn't worry about their camera, indicated by the green light, still being on.
  • Informed: The language is easy to comprehend, accessible and to the point. Users are free to make an informed decision regarding their choice based on the text provided in the welcome interface. For example, where the images captured will be saved.
  • Enthusiastic: Users are asked on multiple levels if they are 'really' okay with sharing their webcam since this can be highly sensitive, At no point are they led into giving access for the sake of it, like in the earlier interface (in the experimental camera assignment) where they choose to give access just to be able to open the webpage.
  • Specific: The first question that the users come across is if they are inerested in looking at the camera. If they are not, why ask them for permission when it is not yet needed at this stage? When they choose 'yes', they are interested, they are informed that to view the camera they will be required to give access. By checking their specific intentions, they are exposed to only what they have consented to and nothing more.