sethstacey -
Thank you for your feedback it is appreciated. If I could respond to my reasoning for some of the elements and possibly rebuttal some points as well.
So, here I go:
1. You Stated: "I really hate tables"
Tables - I would agree that for HTML statically loaded websites that tables are useless to say the least. Tables were never intended to be used for design but nearly as a "place holder" for data. Eventually tables on site will be linked to databases, as this is the only rational way to display server-side dynamically loaded content. Browser side static content has no use for tables. I do not know if you noticed that the site is an asp.net website driven by Visual Basic, with dynamically loaded content via a Microsoft SQL database and XML files. As far as the browser problems, here is a great tool to test before you implement:
http://www.totalvalidator.com This site gives you a great way to view a screenshot of multiple desktop environments. You thought things were bad now, wait until IE version 8 comes out. Many problems already in the beta version.
2. You stated: "background image is huge"
I would agree with the background image. I just have not gotten around to it yet.
3. You stated "border.........could be a little darker"
I would have to agree, as I am not a graphic designer, but the code I write is error free.
4. You stated: "love the drop down menus to death...........I hate tables"
Thank you for the drop down menus compliment, this is a feature of asp.net development, server side scripting. It would not be possible to develop this with HTML Divs.
5. You stated: a link was placed to a validator that validates HTML
I believe this opinion comes from a misunderstanding of the website, as the site is being loaded dynamically(asp.net 3.5 IIS 7, visual basic, SQL, XML) and then sent to the browser, which is much different then a static html website. This is the potential problem for the html validation. If you notice at the bottom of the site there is a button that states this site is valid CSS. Click on the button and see the results! Once again www.w3.org validation focuses on CSS and HTML, and cannot check an asp.net 3.5 website accurately for HTML validation. If the site was not developed correctly it would not even render correctly in the browser, you would just see a bucn of programming errors, unreadable to most. You can do a validation on this website or Microsoft's or Yahoo's and come up with much more errors. As well if you view the source of Yahoo or Microsoft's website you will notice Divs wrapped around Tables, as the the CSS divs are used for what the user sees, and the tables hold the server side dynamic content. To simplify Static HTML = DIV's, Dynamic Server Side = Tables.
6. You stated: "the validator finds things that are helpful"
The validator link you gave me is for static html. When I develop static html sites, I no longer need to validate, as I can write the code with absolutely no errors. I might get a warning or two, but no errors.
7. You stated: "better.............search engine results"
I would have to agree that I this site could use some tweaks for Search Engine Optimization, but I am focusing on driving traffic through marketing rather then just utilizing search engines.
8. You stated: "spacing feels funny"
Once again, I would have to agree. I am not a graphic designer but my code is error free.
Finally, I most certainly did not take offense to your comments, as I always like to hear someone's point of view.