[Sigia-l] most understandable phrasing

[Pabini Gabriel-Petit]

Hi Stephanie

Stephanie Berger asked:
> 1.  My cohorts are not sure whether to use "cell phone" or "mobile phone".
> Any evidence that one is better than the other, or one is used more often
> than the other?

Cell phone is more prevalent is the U.S.; mobile, abroad.

> 2.  I am looking for information regarding how best to describe/phrase a
> request to users for their credit card security code found on the back of
> the credit card (or on front in case of AmEx), as my colleagues fear that
> users will impart a pin number accidentally. They'd prefer to avoid using
an
> image description showing where this number resides.

If they're serious about preventing users from typing their pin numbers, you
should include an image that shows an example number on a card. These
numbers aren't labeled on credit cards, so there's no reason to expect that
people will know what they're called.

I just googled the term you're using. "Card security code" seems to be the
term in common use. Here's a good example of how to present this
information. As you can see, a couple of pictures are worth a thousand
words. Too bad that not all credit cards put this code in the same place.

So, use the term--consider it a pedagogical opportunity--but show people
what it means.

> 3. What phrasing do you use for "html email" and "plain text email"?   We
> will be asking the user to select one or the other.

It is best not to use technical terms. However, I think it's important that
users be able to map the terms used on your Web site to those used in the
most common email applications--Outlook and Outlook Express--that is, Rich
text (HTML) and Plain text.

This is one of those cases where I think it is best to follow Microsoft's
lead. Though you might add descriptive phrases, for example:

Your preferred email format:
Rich text (HTML with graphics)
Plain text (Text only, for faster download)

> 4. Where do you go when you are unsure how to phrase something on the web
> and you need it ASAP?

Microsoft Manual of Style for Technical Publications
Google
Competitive companies' Web sites

Pabini Gabriel-Petit
________________________________________

Pabini Gabriel-Petit
Principal & User Experience Architect
Spirit Softworks
www.spiritsoftworks.com