Posted: Tue Aug 26, 2003 3:22 am
Hmmm, generally I don't charge less than 75 an hour for usability analysis but since it is for a good cause…. I apologize for the wandering style of the text below but it is off the top of my head and I am trying to address two issues at the same time. The first is to outline the struggle I went through to find the auction status page. The second is to point out some glaring usability flaws that should be fixed. I know you are doing this as a volunteer and don’t mean to be harsh. Hopefully this will be useful to you. So here we go:
Part of the appeal of designing a site in xhtml is that you design it from a structural standpoint and thus you create an outline of the information you are try to present. Flash designs generally are more from a visual sense so you have to be even more aware of the underlying information architecture.
Lets look at an example of what I did to try to find the auction status page. I know it exists and I want to find it again.
When you open up the url you come to the splash page. This is generally considered bad form for site of this nature. If it were for a multimedia site or a bands site it would be ok. Currently it is keeping me from seeing the information that I seek. Since I am a web savvy user I realize that I can click on it to skip it. This will not always be the case. I would recommend shortening it to just to less than 5 seconds. This will increase load time and force you to condense the message down to the essential bits. Also DEFINATELY add a skip navigation link.
Now I am on the home page. I am met with three different navigation systems and multiple objects vying for my attention. I would recommend choosing something to be visual anchor and using that to base your primary message around. This means you need to define your primary message. At minimum, fix the rollover menu. I would actually say get rid of it. All it does is keep the user from seeing all the choices that they have to navigate through the site. I would rework the nav options down to one system and have all of the options visible. You can have pull down menus but only for the sub levels in the silos.
Back to my case study.... I know the status page has to do with fundraising so I click on the bright orange donation bar. It is a link but it takes me to a donation page (why not have the pay pall and mail details on the page rather than hidden behind another layer of links) not the status page. I see a little arrow with "how much has been donated" next to it and I click it. Upon clicking it, end up with a bigger version of where I started.
Frustrated, I look to the navigation options. The menu drops down and look at the options. I pick donations because that makes sense to me. I explore the options to no avail. Every time I roll over an option multiple menus and choices pop up further confusing me. (Only one pop up at a time) Notice that I do not distinguish between the auction and donations in general.
Finally I look under action and I see the status menu. It took me a lot of steps to find what I was looking for.
I know this is a lot to chew on and I know how much time structural changes can take on a website. You know as well as I do that time is money so I leave you to take from this what you want.
I would HIGHLY recommend that you read Jacob Neilson’s book Designing Web Usability. It will probably help you structure sites that you build in the future.
If you have more specific questions I would be willing to answer them but I don’t know how much more time I am going to be hanging around on the board. Squamish is calling. You can always email me though.
Part of the appeal of designing a site in xhtml is that you design it from a structural standpoint and thus you create an outline of the information you are try to present. Flash designs generally are more from a visual sense so you have to be even more aware of the underlying information architecture.
Lets look at an example of what I did to try to find the auction status page. I know it exists and I want to find it again.
When you open up the url you come to the splash page. This is generally considered bad form for site of this nature. If it were for a multimedia site or a bands site it would be ok. Currently it is keeping me from seeing the information that I seek. Since I am a web savvy user I realize that I can click on it to skip it. This will not always be the case. I would recommend shortening it to just to less than 5 seconds. This will increase load time and force you to condense the message down to the essential bits. Also DEFINATELY add a skip navigation link.
Now I am on the home page. I am met with three different navigation systems and multiple objects vying for my attention. I would recommend choosing something to be visual anchor and using that to base your primary message around. This means you need to define your primary message. At minimum, fix the rollover menu. I would actually say get rid of it. All it does is keep the user from seeing all the choices that they have to navigate through the site. I would rework the nav options down to one system and have all of the options visible. You can have pull down menus but only for the sub levels in the silos.
Back to my case study.... I know the status page has to do with fundraising so I click on the bright orange donation bar. It is a link but it takes me to a donation page (why not have the pay pall and mail details on the page rather than hidden behind another layer of links) not the status page. I see a little arrow with "how much has been donated" next to it and I click it. Upon clicking it, end up with a bigger version of where I started.
Frustrated, I look to the navigation options. The menu drops down and look at the options. I pick donations because that makes sense to me. I explore the options to no avail. Every time I roll over an option multiple menus and choices pop up further confusing me. (Only one pop up at a time) Notice that I do not distinguish between the auction and donations in general.
Finally I look under action and I see the status menu. It took me a lot of steps to find what I was looking for.
I know this is a lot to chew on and I know how much time structural changes can take on a website. You know as well as I do that time is money so I leave you to take from this what you want.
I would HIGHLY recommend that you read Jacob Neilson’s book Designing Web Usability. It will probably help you structure sites that you build in the future.
If you have more specific questions I would be willing to answer them but I don’t know how much more time I am going to be hanging around on the board. Squamish is calling. You can always email me though.