Tag Info

New answers tagged

0

Like other people said, inline errors is more user friendly. To add to this, pop-ups should be used (if anything) on finished tasks, success messages, etc, but user has to be able to see what errors has he/she made in order to make the appropriate corrections. And for this, you need some kind of inline display. Now, in this scenario (and based on your ...


0

There is a third possibility, which is do both! Have a pop-up that has the missing/invalid fields fillable. You might want to fall back to inPage errors if there are more than 2-3 invalid fields, or only present the user with 2-3 fields at a time. If there are only a couple of invalid items and you have a long form just showing the missing information AND ...


1

Pop up errors Drawbacks: The pop-up goes away in order to correct the form => I have to remember the errors. Their just plain data, "unlinked" with the particular error source => I have to locate the source of the errors if I can remember them. (unless you also want to color the input or showing some other clue, but I will harder anyway compared with ...


1

As per your edit, I am assuming InPage rather than InLine. I think it depends on the length of your form. I have seen many times where Users have to click the Submit button way down at the bottom, the In Page validation kicks in but Users are not scrolled back up to the inpage validation message. So they have no idea why the form is not submitting! Either ...


0

I think the simplest answer is how much time are you willing to devote to this one portion of your website? The second question is about the clientele that you're serving. The answer to those two questions will be a starting point. If you have lots of time and your clientele is not savvy then do separate pages. If your time is short and your clientele is ...


3

I'm going to answer this from the perspective of a webmaster who is familiar with the error codes that your web app should produce. A 404 Not found error is a very general error for the case when a URL was entered that cannot be parsed. You may not know what area of the site the user was looking for. There may even be nonsense in the URL like ...


-2

No. It can be a security risk to do so, and for the example you give isn't really appropriate anyway. If I try to find a particular meeting - even from a direct link - and it doesn't exist, why throw an error in my face? I'd much prefer a site that displayed a basic "This meeting doesn't exist" message, and then displayed a list of other meetings, for ...


27

The first problem with having multiple 404 pages, each dedicated to a particular area is that you assume users were in the right part of the website at the point when they fell on to the 404. Bearing in mind that many links come from search engines and not necessarily from within the website, then I don't think you can guarantee that a dedicated 404 is ...


2

I agree with Vitaly, the 404 page shouldn't be an end to the users route it should give them help on why this page might not be here and relevent ways to procceed. In your example, suggesting things like "Is this the meeting you are looking for?" then listing relevent results helps the using keep moving forward rather than backtracking


4

I designed a 404 page sometime back with a function you might find interesting. it was using a recommendation engine module suggesting products the user might like and what they previously viewed. not sure what kind of website you are asking this in context to, but a golden rule i stick to is never to bring the user to a dead end.


10

Treat a 404 page like an error message, which it basically is. A good error message offers the users way to overcome the problem. In your example, a 404 for meetings could offer possible matches for meetings, a 404 for recordings could offer recordings, and the same for documents. The possible solutions are different for each type of entity, and the reasons ...


2

I would suggest the clearer "No package with tracking code XYZ was found." It's tempting to suggest a few possible causes as well, such as "Make sure you've typed the code correctly" and the like, but those might be misleading, and most of the time aren't all that helpful anyway: if you see the error message and it mentions the number you typed, a quick ...


5

Tracking code is invalid Is it? Is it really? Is there no possibility that the code is actually valid, but not in the system for some reason. Tracking Code was not recognized Not recognized? Did I get the case wrong? Why was it not recognized? Was it my fault or the computer's fault or the company's fault? Neither of these messages really help me ...


1

Your most common are likely to be: Full stop at end of address Commas instead of full stops Semi-colon or apostrophe instead of @ Spaces in middle or at end of address Bracketed note in field – eg. (office) Double periods.. Some common misspellings: Googlemail – Gogglemail, googlmail, goglemail Hotmail – Hotmial, Hotmal, Hoitmail, Homail, ...



Top 50 recent answers are included