Well, I guess there are multiple reasons to be compliant
1) It is a standard. Standards are good for the industry in that they make it easier to create things and less of a hassle to maintain.
2) Because it is a standard, I've found best rendering behavior across browsers by remaining standards Compliant. The docTypes at the top of your XHTML file basically say, "This page is coded to certain standard" and when you SAY that, but don't do it in the page, it can lead to rendering problems (such as IE6 and IE7 quirks mode)
3) Straddling the line of designer and developer, I see what the LACK of attention to Standards can do. For instance IE6. I wasted almost 4 hours again today tracking down an IE6 bug because they don't render pages in a standards compliant way.
Finally, regardless of whether you care about it or not, I DO care about it, and unfortunately there are some things I can't change on jReviews. I completely understand that you have it set up the way you do, but - as far as I understand it - I wouldn't be able to rectify these issues (I would happily do it if I can though)
The only other thing I could find that generated errors besides the two I mentioned were the S2 tags
<s2:nocache>
Thanks for considering this.
Steve
