Chapter 11 illustrates on the importance of having user accessibility on a website. I had never thought about the need for accessibility on the web and assumed that the people who used the web would have the full ability to do so. Although after reading this chapter, I found myself in complete agreement with Krug on the simple fact that “making sites more usable for “the rest of us” is one of the most effective ways to make them more effective for people with disabilities.” It is easy and ignorant to believe that the majority of the population who uses the web is the same. This kind of mindset disregards the reality that even people with disabilities can access and use the web. For years now, the web has become an increasingly common and convenient tool and a primary resource for information. How can anyone conclude that only a specific demographic that excludes disabilities uses the web? Krug explains that web designers and developers most often fear two things about the implementation of accessibility. The first fear is that it is more work, “just one more complicated new thing to fit into an already impossible project schedule”. The second fear is the result of a compromised design which will be “less appealing and less useful for the majority of their audience”. Frankly, this is their chosen profession and making a website that has good usability and accessibility to all users should be included in the job description. I always have more appreciation and respect for those who go a little beyond the requirements of their task because it shows that they actually care for their users and not just about getting the job done. Why not make everyone happy and feel good about doing your job that much better? As Krug states, it is just the right thing to do.
In Chapter 12, Krug provides sample letters that can be given to bosses with irrational web design demands. Is it really possible to use these letters on your boss when dealing with bad design decisions? Although Krug’s letters deliver some very valuable insights and can serve to be useful in this type of situation, I would probably consider using his letters as a last resort or at least once I have grown the balls to face the possibility of getting canned.
Related Links:
http://www.infinitcolours.com/
http://www.theologos.gr/
http://www.digaworks.com/
Tuesday, November 24, 2009
Wednesday, November 18, 2009
Thursday, November 12, 2009
WEEK 6: READING BLOG
As my reading continues further into the textbook, I begin to wish that the same rules that Krug proposes in his writings on good usability websites could apply to homework. The world would be one step closer to Utopia if homework was designed in the same way that requires less effort from students and, most importantly, does not make us think. However, I suppose that I can keep dreaming until then…
Chapter 8 focuses on the tendency to assume that most web users have the same likes and dislikes and uses the web in the same way. Krug has witnessed the reality of this assumption which is that “all web users are unique and all web use is basically idiosyncratic”. He describes an effective usability website as one that is “carefully thought out, well executed, and tested”.
Chapter 9 elaborates on usability testing where Krug stresses on the importance of testing early during the web development process. I had learned a few new terms throughout my reading which had helped me to better understand their differences. If Krug had not provided an explanation on the definitions of ‘focus groups’ and ‘usability test’ and their appropriate use, I would have simply thought that both methods are similar and the same. ‘Focus Groups’ consists of a small group of people who react to ideas and designs whereas ‘Usability Test’ is comprised of a single user who is requested to perform typical tasks to deliver results. It is important to consider focus groups during the preliminary stages of the development process so that these results can then be applied to the designing aspect. There is really no excuse for not conducting any kind of usability testing on a website as it can be fairly easy and affordable, such as Krug’s ‘Lost-Our-Lease Testing’. Ultimately, conducting several testing throughout the phases of development will do more for the website than to hurt it. As Krug states, “testing reminds you that not everyone thinks the way you do, knows what you know, uses the web the way you do”. The opportunity will provide some valuable insights and allow for some significant improvements for any website.
At the end of my reading journey through these two chapters, I can only conclude that Krug tends to use some very unusual subheadings in his book. Can anyone explain what is meant by “Don't throw the baby out with the dishes”? Why waste dishes anyway?
Related Links:
Tuesday, November 10, 2009
WEEK 5: READING BLOG
In Chapter 10, Krug discusses usability as common courtesy and includes a list of techniques that can increase and decrease goodwill. Aside from a website being convenient and requiring less amount of effort from their users, a site should also be considerate and show that they have their users’ best interest at heart. As Krug had stated, users usually have a reservoir of goodwill that measures their experience on a site. The amount of goodwill in the reservoir will be determined by the user’s level of satisfaction.
While reading Krug’s list of things that diminish goodwill, I can recall some of the bad experiences that I have had with a few websites. I can certainly understand the frustration in having to search for a contact number for several hours and then sometimes never finding it. This is especially frustrating when dealing with an issue caused by one of their products and the only way to resolve the issue is through the company itself. Another bad experience that I can relate to is with formatting data on a site. It can be very annoying when you have spent time filling out a form on a website and then find out that you had entered it incorrectly because you did not follow a specific format. In this kind of situation, the site should state on the form how to enter the information correctly to avoid any waste of time and frustration. Otherwise, there is no guideline to follow and users cannot prevent from having to redo the information correctly a second time.
Related Links:
http://www.cwtv.com/ (no visible contact link)
http://www.aofmpro.com (no prices on single items)
http://iqqubeauty.com/ (no FAQ section)
Monday, November 2, 2009
WEEK 4: READING BLOG
In Chapter 7, Krug explains the purpose for having a homepage on a website and how to ensure that it is effective. He makes a lot of valid points which I would think are mostly common sense. One element that Krug mentions is that the homepage should have content that teases its users. This refers to content promos such as the newest, best, or most popular pieces on the site that will serve to entice its users.
Another element that should be considered on the homepage of a website is the use of taglines. Initially, I had confused the definition of taglines with mottos, but now acknowledge the difference. Krug defines taglines as a “concise statement of the site’s purpose” and one that “conveys a value proposition” whereas mottos “express a guiding principle, a goal, or an ideal”. Basically, taglines exist to help users understand what the website is about and what to expect from it. These taglines should be clear, informative, and not too long in length. I definitely agree with these principles because I have seen websites where the site ID has either had a tagline that was too vague or no tagline at all. I feel that taglines are beneficial to include along with the site ID because it enables users to understand the purpose of the site without investing too much effort. There is no harm in having a tagline. It is a win-win situation that leaves both the users and website owner happy since the users will experience less frustration on the site and will likely come back to visit.
Related Links:
http://hallmark.com/ - (Navigation with dropdown menus)
http://www.walgreens.com/ - (Navigation with distinctive icons)
http://www.youtube.com/ - (Tagline – is it too vague?)
Another element that should be considered on the homepage of a website is the use of taglines. Initially, I had confused the definition of taglines with mottos, but now acknowledge the difference. Krug defines taglines as a “concise statement of the site’s purpose” and one that “conveys a value proposition” whereas mottos “express a guiding principle, a goal, or an ideal”. Basically, taglines exist to help users understand what the website is about and what to expect from it. These taglines should be clear, informative, and not too long in length. I definitely agree with these principles because I have seen websites where the site ID has either had a tagline that was too vague or no tagline at all. I feel that taglines are beneficial to include along with the site ID because it enables users to understand the purpose of the site without investing too much effort. There is no harm in having a tagline. It is a win-win situation that leaves both the users and website owner happy since the users will experience less frustration on the site and will likely come back to visit.
Related Links:
http://hallmark.com/ - (Navigation with dropdown menus)
http://www.walgreens.com/ - (Navigation with distinctive icons)
http://www.youtube.com/ - (Tagline – is it too vague?)
Subscribe to:
Posts (Atom)
