Showing posts with label ux. Show all posts
Showing posts with label ux. Show all posts

2014-03-22

Level Up!: Do Users Need To Click "I Agree" to TOS Button To Give Consent?

(TLDR: No. Courts decide these cases simply by whether the person had reasonable notice of the Terms & Conditions. If you have a website/app and plan on collecting personal info or just have customers in general, the I highly suggest you read more about this topic. Disclaimer: IANYL.)


As a UX designer, I try to make things that are as simple and painless as possible for users to use. One pain (and protection) that almost every product/app needs is a Terms of Service (TOS) agreement, aka Terms of Use (TOU), aka Terms And Conditions (T&C), aka End User License Agreement (EULA).

The current "best practice" for showing TOS to users is by providing a clear link near the "continue to use app" button (which could be a register or purchase button). This is so that most users don't have to go through the extra step of clicking "I Agree" to something that they likely didn't read. Also, having the TOS pop-up interrupts users' flow (and can sometimes be quite scary-looking).

But, unfortunately, before today, I never really thought about the legal consequences of the different methods to show users the terms and conditions. I just used methods that I noticed many other great UX designers and companies using. So, I wasn't able to explain the legal-ness (to my satisfaction) to concerned client.

I took it upon myself to take the time to do some research around this area and organize it into this post, with sources and references cited.

In my research, I have found that the courts also know that most users don't read the TOS, and clicking "I agree" doesn't mean that the user has read it. What the courts look for is mainly that the user has had the easy opportunity to find and read the TOS, if they wanted to.

There are two main ways that users "agree" to TOS:

  • Click-wrap Agreement, aka "click-through agreement": This means that users must take some sort of action that signifies their consent to the TOS. This action could be a button that says "I Agree". Also, near the call to action, it is sufficient to say "By [continuing], you agree to our Terms of Service", with the TOS having a direct link.
  • Browse-wrap Agreement, aka "not a contract": Basically, saying users agree to TOS by browsing website/app, and the link to TOS is not extremely easy to find in regular use. A link at the bottom of the website could be considered hard to find, especially when there are many other links down there too.


My Summary (Just from my research (links below), though more can always be done.)

  • If your app collects or uses personal information, then use the click-through (clickwrap) agreement.
  • Remove any clauses about unilaterally editing contract at any time.
  • Add ability for company to modify terms, with prior notice. [More research needed for exact words to use]
  • Add ability for users to reject TOS, e.g. by terminating account. 



A few sources I read, in order of my recommended readings (Yes, there is a "Good" before "Great", just because of what this post was supposed to be about):
 - Great: How Zappos' User Agreement Failed In Court and Left Zappos Legally Naked (Forbes)
 - Great: The Clicks That Bind: Ways Users "Agree" to Online Terms of Service (EFF)
 - Good: Terms Of Use And Privacy Policy Best Practices (UpCounsel)
 - Great: Website Terms and Conditions: Some Best Practices (JDSupra)
 - Miscellaneous, but good: Terms of Service; Didn't Read (TOSDR)
 - Good: Browse wrap (Wikipedia)
 - Okay: Clickwrap / Browsewrap Agreements: It’s the Notice, Stupid!

Further Reading:
 - Terms of Use and the Digital Millennium Copyright Act (DCMA)
 - Search "Clickwrap vs browsewrap"


Disclaimer: I am not your lawyer (IANYL). This post's only intention is to help point readers in the right direction to learn more about this topic.

~ Danial Goodwin ~


ps - Bonus info! The terms "click-wrap" and "browse-wrap" come from physical goods/software that was "shrink-wrapped". Manufacturers had license agreements that basically said users agree to TOS by removing the shrink-wrap. (Source: Wikipedia)



2013-12-24

Terrible User Experience - There's Only One Major Application I Know That Does This

Perhaps the most terrible example of all user experience (UX) an application/program can give to users, is to shut down the program when the user is in the middle of working. Case study: Windows. I just got auto-updated.

In Windows 7, there is a small window that pops up that says the computer will restart in 15 minutes, in order to install updates. After that message is postponed, it doesn't pop up in the front any more. In my multiple monitor setup, I don't always pay attention to all of them. There is just typically one main monitor I work with. My current work involved having about 20 tabs in a browser open and a few more large RAM-hungry application, so I didn't want to have to re-setup my workspace. So, I was able to postpone the auto-update a few times. But, when I was really into my work on one monitor, the auto-shut-down prompt I assume was ominously counting down on my other monitor, behind everything. In the middle of typing, sudden the document disappears. There goes all the work (if I was working in a program without autosave).

I am a UX designer and have many recommendations to improve this "feature" in Windows 7. I'm glad my biggest recommendation is taken care of in Windows 8: Make the death prompt more visible. Just having that one change would save me from more trouble.

I understand where Microsoft and other companies are coming from. They want to make sure that updates are installed so that users are protected from even worse virus/malware attacks. I'm sure they've done their research to learn that many people unfortunately don't install the updates in a timely manner, if at all. So, in order to protect users from worse troubles, Microsoft has by default decided to be more aggressive in getting the updates installed.
I had to throw in that "by default" in the last sentence because I know there is the option to disable all automatic updates. But, good UX and good customer service wouldn't put the blame on the user/customer. If the user does something "wrong", then it is only because the application allowed the user to do so.

Bonus: Here's a copywriting tip: Never have long chunks of words/paragraphs.

~ Danial Goodwin ~



2013-05-22

Simply Advanced Mobile App Development Website Updated

Hello,

Please check out my new design of Simply Advanced's home page. It's live now. Another surprising discovery is that my website shows first when searching for "Simply Advanced". You can access it by clicking the first result in: https://www.google.com/search?q=simply+advanced

Let me know what you think. =]
~ Simply Advanced ~