from a judge's standpoint, i like it, it looks good, the only thing that dosen't fit in is the funky tabs, they don't really match the rest of your site which is sharp and angular. there is a lot of content which is the most important of course, and the whole site has a nice warm feeling to it.
from a web developer's standpoint, it's almost totally valid - you neglected to use <label> tags around your search input box. it's really well organized, but uses tables for layout?!?!?!?!??! it's 2007, not 1995.
the biggest thing is that it definately fails web accesibility testing, here is what a screenreader output when trying to read your page.
Quote:
|
Page has six headings and thirty-five linksWBI dash West Side Boiler Invasion, Team four hundred sixty-one dash Internet ExplorerTable with three columns and thirty-five rowsTable with one column and thirty-four rowsTable with six columns and one rowLinkGraphicHomeLinkGraphicGeneral InformationLinkGraphicFind out more about WBILinkGraphicSee what we doLinkGraphicView multimediaEdit SearchbuttonTable endTable with one column and three rowsTable with one column and two rowsLinkGraphicFIRSTLinkGraphicSponsorsTable endTable endTable with one column and twenty-six rowsTable with one column and twenty-four rowsTable with one column and seven rows OverviewTable with three columns and five rowsTable with one column and four rowsThis page linkGraphic slash GeneralSectionPreviewImage dash Hover.jpgThis page linkGraphic slash OurTeamSectionPreviewImage.jpgThis page linkGraphic slash WhatWeDoSectionPreviewImage.jpgThis page linkGraphic slash MultimediaSectionPreviewImage.jpgTable endGraphicSection Preview Image
|
Here is a
website i've recently built with web accesibility in mind, and here is how it is output.
Quote:
|
Page has fifteen headings and seventeen linksPQL dash Portable Query Language dash Internet ExplorerGraphicPQL LogoHeading level one Portable Query LanguageHeading level four What is PQL The next generation flat dash file DBMS. Packed with features unrivaled by its competitors, it is well ahead of the competition. And with a comprehensive online manual, there's no reason why you can't learn PQL in an hour. Heading level four Why PQL If you need to build a small scale site, but require a better way to store large amounts of data than a makeshift system, you might not be too keen on such a complicated software like mySQL. This is where PQL comes in. PQL does not need any installation, and can be used even on low dash cost hosting that does not offer a database system. PQL's hybrid filetype system greatly reduces processing time and memory usage because it will only read what it needs dash not a byte more. The advanced query capability allows you to refine your queries using infinitely complex clauses that use the familiar paranthesis system. There is full support for the AND, OR and XOR logical operators, as well as ten relational operators that evaluate conditions to true slash false.
|
notice how your's spends over two minutes rambling on about your table structure and images (and it's not done yet!) while mine reads the page title, then one image, and it's gone straight into the content in less than 10 seconds... I used to ignore things like this thinking 'blind people don't use computers' but you know, they do. And not only blind people use screenreaders, old people who can't see clearly do, as well as people with perfect eyesight like me but use a screenreader so we can work on something else while browsing the web with voice commands and receiving information with sound.
The other big thing is that since you are using tables, the layout is basically never going to be viewable on a mobile device (unless it has Opera and the person knows how to change the display mode to desktop). Even with css turned off, it won't degrade into a neat, one column mode that is completely usable and not confusing (
try it on my site).
The first thing to do would be start using an ordered list for your links, which really are just that. Replace the images and use the sliding-doors technique which are excellent for tabs like those you are trying to pull off.
The second thing to do would be to organize your markup not by the order they appear on they page, but the order you want your user to read it. Content should always come before navigation! After you do this, then move them to the correct positions using css. The reason why we do this is so that screenreaders start reading the content first, instead of repeating your navigation first every time a page is loaded.
The last thing that the site is very slow to load, but I can't blame you cause it's only in development and your hosting could just be having a bad day. Might be worth looking into though, some pages don't even load.
Overall i would give it a 4/5 at this point, great job! Im sure it'll be amazing once you're done.