User Experience Designer
smartmockups_jmb28ui9.jpg

Copy of Human Services Agreements Concept

Brief:
The Human Services Agreement (HSA) is intended to be a become framework for future End-user License Agreements. This came about from my detest to lengthy EULA's sometimes entire books long e.g. Apple's or use such large words and vagueness that it no longer serves a purpose except to confuse the reader into submission to avoid further counterproductive efforts. The final version is intended to be deployed using Twitter Bootstrap and function as an open-source GNU script.

In short, bring a humanistic approach to something that has become almost robotic.

Research:
The following is a mixture of research in human to computer interaction, local and universal psychology, cognitive science, ideology dependent on users place of birth and current living location, and personal observations of differing age/sex/race groups attempting to understand EULA's.

Step 1: Gather preliminary user information

  1. This section serves as a pre-signature validating the users intent to ‘sign’ said agreement, prior to it being finalized.

  2. Text translation is auto-generated via IP but still manually selectable as an IP trace isn't always accurate.

  3. We globalize the name by removing the traditional “first” and “last” name approach. Henceforth users names are stored with an ID number, thus no actually need for name, other that for user visibility.

  4. Step 1-2 helps to auto-generate colors used for each section e.g. Step 2-2.

  5. Age is asked and checked via step 1-2 to conform to the users local age restriction on signing documents.


Step 2: Easily digestible information

  1. The terms are broken-up into its own self contained section.

  2. Each section is color coded to distinguish it apart. The colors are auto generated based on the users location to prevent misunderstand e.g. ‘red’ in China represents luck, whereas in the United States it is for danger.

  3. Technical verbiage is kept to a minimum. Any used is italicized and a hover-text-box will show with the definition when highlighted.

  4. A variety of psychology techniques is employed to prevent skimming and assist in better understanding of said section.

  5. Any information on the sections typic is available under the ‘Additional info’ button, should the user require it. Step 2b-1.


Step 2b-1: Offer the user addition assistance

  1. Rather than simply not bothering with users that disagree with said agreement, perhaps from misunderstanding it, we give the option to quickly send an email for assistance after clicking the ‘Additional Info’ button then ‘Contact us. This is used to help further build trust between end-user and admin.


Step 3: Checked confirmation

  1. As the user begins to scroll to the bottom of each section, a light-box will appear informing them to ‘Continue scrolling to agree’. This tracks with the pages scroll bar and will only appear as they progress downwards e.g. it is almost universally understood that Top = Start and Bottom = End, for websites.

  2. As they scroll, the next section will come into view. Once the next section is completely in view, the ‘Continue scrolling to agree’ light-box will fade away.


Step 5: Final review

  1. In the final review, the service agreement is populated with their name.

  2. We give the option to change their name at this step to help validate the legitimacy of this forum.

  3. An option to have said agreement emailed as a PDF is given.

  4. Once the user clicks submit, ‘What’s Up CAPTCHA?’ will display to validate the human behind the screen. Step 6-1.


Step 6: Confirmation

  1. ‘What’s Up CAPTCHA?’ is used in-place of word-Captcha systems for better legibility.

  2. Moving the slider from left to right will rotate the image

  3. Clicking done will check that the image is correctly aligned and submit the forum.