Why Your Form Buttons Should Never Say Submit – UX Movement

In may cases Submit buttons are “calls to action”. You’re asking a visitor/user to do something.

Instead of the default “Submit”, consider what’s actually happening from your user’s perspective. Is there a better way to word that button?

When users fill out a form, they are engag­ing in a task. The action but­ton should affirm what that task is, so that users know exactly what hap­pens when they click that but­ton. A but­ton that describes the user’s task tells users that the form focuses on car­ry­ing out that spe­cific task. The more focused your form is, the more likely you’ll get users to com­plete your form.

via Why Your Form Buttons Should Never Say Submit – UX Movement.

The Email Standards Project

Many years ago the Web Standards Project (or WASP) fought the fine fight to pressure browser manufacturers into complying with some sort of standard version of HTML. Prior to that we almost had to build separate sites for Netscape and Internet Explorer – it was horrible.

We have come so far with browsers, but unfortunately most email clients are, well, a long way behind. If you have ever tested an HTML email in a few different clients you’ll know the frustration.
Yesterday’s launch of the Email Standards Project hopes to remedy this situation. Some people love it, some hate it, but HTML email is here to stay. And if we could have the proper standards support in email clients then it’s probably fair to say that a lot of those opposed would change their mind.

We have a long way to go, but at least now we have a vehicle!