American Express is rolling out a new travel service for its business customers. As is customary for today’s web services, there’s are terms and conditions that the new user needs to agree to when they sign up.

Now, these are often implemented with a checkbox that says something like “I have read and agree to the terms and conditions.” Most of us know that hardly anybody reads and everybody just checks off the box. (Once, I watched my dad, a lawyer, check the box without reading. “It’s probably unenforceable,” he told me.)

But on this new Amex site, there’s a different implementation of this control. Sure, there’s a checkbox, but it’s grayed out. The only way to enable it for checking is to scroll to the bottom of the agreement.

The Amex Biz Travel site greys out the checkbox until the user scrolls to the bottom.

Now, as is also standard, the agreement is presented in a tiny little scrolling text box that shows about 200 words at a time. And, as is also standard, the agreement is a whopping 7,243 words (13 pages in a standard document) long.

Therefore, scrolling through this box takes a fair amount of effort. It’s unlikely that scrolling will encourage anyone to read the document. It’s just an extra hoop to jump through to continue the farce of pretending that the user has “read” whatever it is their agreeing to.

Apparently, the lawyers at Amex think that by having me scroll to the bottom, they can claim that I had every opportunity to read and agree to the terms. Therefore, if there’s something down the road I want to sue them about, I gave up that right with my scrolling action. (It’s unlikely any sensible judge will buy this argument, but it’s just as unlikely that any suit against them will get in front of a judge.)

Of course, the best way to do this would be to be honest with your users and treat them with respect. Amex could write the terms in simple language and give users a chance to really understand what they are agreeing to.

The problem with a design solution like the “scroll to agree” implementation is that it won’t be good enough. What happens when some other lawyer at Amex (or whereever) discovers that users don’t read it when they scroll to the bottom and therefore don’t understand what they are agreeing to? They’ll put in some other ridiculous control, where you’ll have to enter a secret code or recite poetry or something.

At some point, we, as designers, have to stand up and say, “This isn’t really doing what you think it’s doing. It’s just making our relationship with our users worse.” When do we do that?

I’d like to start now.