Slashdot Mirror


Top Ten Web-Design Mistakes of 2002

yoey writes "Another famous Nielsen year-end wrapup: "Every year brings new mistakes. In 2002, several of the worst mistakes in Web design related to poor email integration. The number one mistake, however, was lack of pricing information, followed by overly literal search engines.""

17 of 542 comments (clear)

  1. Re:You know what I like? by Mr.+Bad+Example · · Score: 2, Interesting

    You really should wait for the page to load, though. The cartoons there are pretty spiffy...and I'm not just saying that because they were drawn by my wife. Cough.

  2. Javascript in links and Flash animation by phylus · · Score: 5, Interesting

    I think we should be much more worried about the trend in using flash for everything. I've seen sites that have whole link bars, with no special effects that warrant it, done in flash. Isn't that' what an href is for?

    I do a lot of web developing and I've come realize that a lot of things that I want to do cannot be done without having Javascript in the link. While it is sometimes annoying when I'm browsing a site and cannot directly link to a page because they use a POSTed form inside of a Javascript, there are many many positive uses for Javascript, such as history.go(-1).

    1. Re:Javascript in links and Flash animation by Reziac · · Score: 3, Interesting

      But your links that require js lock out everyone who has js turned off -- acto WebTechniques magazine (now NewArchitect), that's some 30% of users and growing -- including folks behind corp firewalls that strip js, so the user has no choice. At the very least, be kind enough to give us plain links somewhere on the same page!!

      Tho the absolute most obnoxious links arrived shortly after DreamweaverMX -- where the entire menu is done as flash buttons. The way they're rigged, you can't even download the .swf and extract the URL by hand, plus there's nothing useful in docsource.

      --
      ~REZ~ #43301. Who'd fake being me anyway?
    2. Re:Javascript in links and Flash animation by Just+Some+Guy · · Score: 3, Interesting

      What's wrong with saying "Click here to go back" instead of saying "Go find the back button which isn't near what you're reading right now and click that."
      What's wrong with doing something like:

      Click <a href="<? echo $HTTP_REFERER ?>">here</a> to go back

      The above example is PHP, but applies equally well to whatever server-side scripting language you're using. Why force your users to enable JavaScript when there's no real need for it?

      --
      Dewey, what part of this looks like authorities should be involved?
    3. Re:Javascript in links and Flash animation by shnarez · · Score: 2, Interesting
      Click <a href="<? echo $HTTP_REFERER ?>">here</a> to go back

      Except if I'm using links or elinks, I just might disable the appropriate $HTTP_REFERRER to be set: set it to something random or the page itself (as links allows) because say I'm not all into the "tracking" by companies of which pages I've been seeing before theirs. And then this magic also fails.

      People, my web browser knows better than your server which page is "back" for me! Don't second-guess me and pretend you're 'leet.

      On top of that, the above "go to referrer" is not equivalent to "go back" if you think about it: if I'm at A, and go to B, then C, my stack of pages is { A, B }. If I "go back", I am at B, with stack {A}. Stack = pages you previously saw. On the other hand, using "referrer" method, with stack { A, B }, being at C, going to referrer (B), my stack is now {A, B, C}, and I am at B. But now if I click "back" I should go to A. But, instead I will go to C!!

      Sorry if it's too complex, but this is just to say that all the external methods to control my "backward browsing" are doomed to fail. My browser is the authority on my history list, not the server. Hacks with javascript are cute, but I prefer to disable javascript.

  3. Re:They missed one... by SilkBD · · Score: 2, Interesting
    I agree, the #2 mistake should be flash (#1 would be auto pop-ups/unders)... use of it in any way other than a brief intro that can be skipped.

    Flash pisses me off because it takes away functionality from my browser...

    --
    00101010
  4. Good stuff but... by ciryon · · Score: 3, Interesting

    a good thing would be to mention cross-platform and browser compatibility. Don't use Microsoft's arbitrary closed extensions. Make sure that the page validates as W3C code, or at least almost does it.

    But many other things in the article were bulls-eye, like the tiny text.

    Ciryon

  5. Web designers competence improves? by varjag · · Score: 4, Interesting

    At least if we take the common design mistakes as the metric.

    'Poor email intergration' sounds pretty sophisticated compared to 'don't use the <blink> tag'.

    --
    Lisp is the Tengwar of programming languages.
  6. browser type by Khopesh · · Score: 5, Interesting

    how about sites that think mozilla can't render something?
    nothing quite as annoying as
    "you need Internet Explorer 5+ or Netscape 6.2.2+ to view this site"
    ...especially when mozilla 1.3a gets blocked but netscape 6.2.2 doesn't!

    solution: some browsers allow you to change the userAgent.
    in mozilla, the prefbar plugin allows this (among other things).

    --
    Use my userscript to add story images to Slashdot. There's no going back.
  7. Re:Fixed text size? Only because M$ broke it by battjt · · Score: 4, Interesting

    Does anyone with a monster graphics card jacked up to max resolution use your site?

    I like using large fonts on high resolution; it looks nice. Small fonts are too small to read on my monitor.

    (I'm 31 and have better than 20/20 eyes.)

    Joe

    --
    Joe Batt Solid Design
  8. Why Frames Suck by igbrown · · Score: 2, Interesting

    These days I find fewer and fewer public and commercial websites that are relying on framesets for layout and navigation. IMHO, this is a good thing. However, I have noticed that a large number of web-based interfaces for commercial, enterprise-oriented applications, as well as many internal enterprise websites/web-applications, tend to rely very heavily on framesets.

    I would like to see Nielsen revisit his 1996 critique of frames, perhaps exploring some of the technologies (PHP, JSP, ASP etc.*) that have provided better solutions to the problems frames initially tried to correct (dynamic navigation/content, rich GUI interface, etc.).

    * While dynamic, server-generated content was around in 1996 (cgi, ssi, and shtml), it was not as widespread, nor was it as readily available to the average web-designer/developer.

  9. Re:They missed one... by fermion · · Score: 2, Interesting
    This is main current gripe with Nielsen. In the past his stance against Flash has made most of his other oversights tolerable. The fact is that Flash is almost always primarily used for 1)useless intros and 2) advertising. While I think his foray into flash usability is commendable, I think his association with Flash is a deal with the force of web unsuitability, and ultimately threatens his credibility.

    I do not run flash on my main browser. I do not like to upgrade browser software because it will generally include flash. I have seen good uses of flash. I have more often seen gratuitous uses that stifle the visitor.

    --
    "She's a scientist and a lesbian. She's not going to let it slide." Orphan Black
  10. All Good, but, but, but by Greyfox · · Score: 3, Interesting
    It seems like most web sites feel like they have to annoy you with their obnoxious design. Corporate internal web sites often seem to be the worst offenders, too. It seems like the last thing a company is going to do is spend a few bucks for a usability person to go over the design of the web pages with them.

    Did you notice the alt tags on the Nielsen site? I've never seen another site put that much effort into a page.

    --

    I'm trying to teach myself to set people on fire with my mind... Is it hot in here?

  11. Re:They missed websites that are just unnavigable by parc · · Score: 5, Interesting

    My wife works for a not-to-be-named textbook company. Their online companion to one of their books was getting incredibly poor remarks. She was in a group working on the problem, so she asked to see the site map. The answer from the web-design group was "site map? We don't have one." So she clarified that she was talking about a design site map. They didn't have one of those, either.

    I wonder how many sites with no site map actually don't even have a design map? I would venture quite a few. Web design is similar to software enginerring: without a good plan, you're gonna get crap out of the process.

  12. Looooooong URLs by FTL · · Score: 4, Interesting
    From the (slashdotted) article:
    URL > 75 Characters Long URLs break the Web's social navigation because they make it virtually impossible to email a friend a recommendation to visit a Web page. If the URL is too long to show in the browser's address field, many users won't know how to select it. If the URL breaks across multiple lines in the email, most recipients won't know how to glue the pieces back together. The result? No viral marketing, just because your URLs are too long. Bad way to lose business.

    There are two side points to this:

    1. To shorten your addresses and make your URLs more durable to change, point your links to www.foobar.com, NOT to www.foobar.com/default.htm (or index.jsp, or whatever).
    2. Don't invoke sessions unless absolutely needed. Sometimes these are in the URL, sometimes they are cookies. It is irritating to copy a URL, mail it to someone, and find that they can't access it because it is relying on a session which expired (in the case of a URL) or a session which their computer doesn't have (in the case of a cookie).
    One kludge to get around massively long URLs is to use a service like ShortURL. Neat idea. But definitely a hack.
    --
    Slashdot monitor for your Mozilla sidebar or Active Desktop.
  13. Usability and Design go hand in hand... by x-dj · · Score: 2, Interesting
    Unfortunatly he pays attention to one and not the other.

    Most of the points he made are valid. Unfortunatly Nielson dosn't hold much credibility within the design commmunity. Many, including myself believe that he thinks the web should be vanilla plain, devoid of any asthetic value. His website reflects this.

    He is a usability expert NOT a design expert.

    Its not that difficult to create a site that is pleasing to the eye and conforms to usability guidelines. If he paid a 1/4th as much attention to design as he does to usability more designers would pay attention to what he is saying.

    --
    So is this where I stick a witty comment?
  14. Re:Fixed text size? Only because M$ broke it by fermion · · Score: 2, Interesting
    At this point this is mostly as philosophical argument. On one side is the 'original intent' people who states, correctly, that HTML is not a fixed page design tool, but an cross-platform, extendable, entity markup tool. That is, the designer marks entities with tags, gives the tag a default behavior, but ultimately does not know or care how these entities are going to be rendered.

    On the other side are those practical people who realize that the above idealization is ludicrous. We do care what things look like. Our clients do need clean well designed pages. Our clients do not understand the utopia we are trying to create, and therefore want to do stupid things like have a smidgen more space between the paragraphs, and we can do little to stop them.

    The issue should, at this point, be largely resolved. The font tag is depreciated and shouldn't be used. CSS is defined well enough to allow designers control the look of the page while allowing the rendering engine to override that look when necessary. Also, as much as we might complain, IE defines the look of the web, and most designers are crafted their page to the IE engine. Responsible designers make sure the code works well enough in other engines, but IE is the look and feel.

    What that means is that what happens in IE is not broken behavior, it is default behavior. M$ should be more responsible, but often their mistakes become default behavior.

    --
    "She's a scientist and a lesbian. She's not going to let it slide." Orphan Black