2. When email address and confirm email address fields have invalid entries, error should be 'enter valid email format', not 'values must match'.
3. If edentiti is targeting Australian market, I would validate state and postcode as well.
4. Regarding 'Add additional address/email/phone' buttons:
4.1 When clicked, error messages dissappear, only error icons are left.
4.2 Do you really need a postback?
4.3 These buttons make the page too 'heavy'. I would make them looking like your 'Cancel' link. Also, I would not put arrow on them. Arrow makes sense when you move between the pages, like 'Back' and 'Next'. For 'Add address, etc.', it does not make sense because you are staying on the same page.
4.4. If you have 'Add' button, I suggest to have 'Remove' as well. Example, GMail "Contacts"
5. I would not use button graphic to show 'creating edentiti progress'. visitor is used that buttons can be clicked. When click does not produce any result it is a bit frustrating.
6. It is more common to use red * or red tick to show which fields are required.
Cheers, Irina.
On 3/3/06, Lachlan Hunt <
[EMAIL PROTECTED]> wrote:
Hi Everyone,
A new site I recently developed the front-end for over the past few
months, called Edentiti [1], has just officially launched and I wanted
to get some feedback about the usability, accessibility and over
functionality in whatever browsers you can get your hands on. I've
tested in various Windows and Mac browsers during development, but as is
always the case, bugs tend to sneak in wherever they can and something
may have been missed.
(I know there are bugs in IE7, but I'd rather wait till MS actually
release something that isn't a joke like both betas 1 and 2 were before
I bother testing/fixing with it - the one to be released after Mix '06
looks slightly more promising)
For all you DOM Scripting fans, if you go to step 2 of the Create an
Edentiti section, there's a funky form validation script you might want
to check out.
http://edentiti.com/create/ (click next, to get to step 2)
[1] http://edentiti.com/
PS. I know the markup is currently XHTML and I'm aware how much of a
hypocrite that makes me :-), but, given the time constraints, it was a
limitation of the back end solution we had to accept, with plans to
convert it to HTML4 later on.
--
Lachlan Hunt
http://lachy.id.au/
******************************************************
The discussion list for http://webstandardsgroup.org/
See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on posting to the list & getting help
******************************************************
