Not very accessible, lots of images used in place of text, like on the "our story" page.

I like their clothes, but they should have gone that extra yard when developing the site.

@ifohdesigns The "our story" page, among a few others are still in the process of being updated with new content. They're old pages (from the old site), we focused primarily on the redesign of the shopping experience and are now working on these old pages. They will be updated and more accessible in the near future. As I'm sure you know, it's difficult to launch a redesign on a short time line... Thanks!

Understood James.

For the tab content stuff "men's page" for example with the shirts, sweaters, etc. rather than using the inline JavaScript, you should look into http://onlinetools.org/tools/domtabdata/

Nice little unobtrusive script that actually works pretty darn well.

Best of luck!

@ifohdesigns We're well versed in DOM scripting, the problem is that the 'owners' of those particular sections need the flexibility of having complete control over each tab or link without any knowledge of JS. By keeping the JS inline, it gives the 'owner' the flexibility of controlling the link without a degree in geek.

Usability and accessibility needs to be considered from both ends of the spectrum, the 'content owner' and the end user.

Thanks for your feedback!

James, that and like scripts require zero knowledge of any JavaScript. It is completely idiot proof, and great for end users.

There is never a good reason to include inline JS that relies on JS being active for that feature to work. Turn JS off and wave goodbye to that section.

My final point would be, for a client of that size, I would have expected a little more attention to detail and patience to deliver to the widest possible audience...

Take care.

@ifohdesigns It's not "completely idiot proof", cause it depends on the HTML being structured in a certain way or having certain attributes on elements. Try explaining to a client, "the tabs are not working because you added the class on the wrong HTML element."

There's a good reason for including inline JS, it allows the content owner complete control over the functionality of their content without any knowledge of JS (and very little HTML knowledge). Therefore when the content owner wants to change the tabs to simple external links, they can do so by simply changing the anchor tag.

My final point is this... know all the facts before judging someone and their work. We all live in glass houses...

Good night, and good luck.

OUCH! good arguments guys! hee hee... the site looks good.

James there is nothing you can say, nor try to explain to me that using inline JavaScript for ease of client use could ever make sense.

In response to your argument about having to include html elements to achieve desired results...Why wouldnt you use a server side language to automate the html formatting for them?

I would think that a client would be more concerned about their product being delivered to their audience than it not, but that is just me, I know a crazy thought.

Fight, fight, fight........

Why aren't the URLs search-engine friendly?