Right now, the underlying HTML that the site generates is not "semantic" - for example, while the first "heading" on the page (the site name) uses the h1 tag, the second one (the site tagline) uses h3. And then the page name also uses h3, but it's possible to insert an h1, h2 or h3 in the page content itself. Essentially, the headings are being used to FORMAT the page (based on relative font size) and not to define the semantic nature, or MEANING of the content they are associated with on the page (i.e, this is a section, this is a subsection of the parent section, etc.). Aside from making it difficult (without custom CSS) to use (in this case) all the heading tags meaningfully, it also goes against basic accessibility recommendations, making the site harder to use by anyone who must use assistive or adaptive technology to access the site. So I do hope that your redesign includes time and effort to normalize how the HTML tags are used, and will at least consider the semantics of the markup if not it's actual level of accessibility. For more information about semantic HTML, this is a good basic article: "Using Semantic HTML":http://www.adobe.com/devnet/html5/articles/semantic-markup.html. For more information about accessibility, start with the Web Accessibility Initiative's "Web Content Accessibility Guidelines (WCAG) Overview":http://www.w3.org/WAI/intro/wcag.php.

To help with that, I also hope the plan is that the new site will be HTML5 and CSS3 compliant. :-) (By the way - I strongly recommend reviewing and following the "Web Hypertext Application Technology Working Group (WHATWG)":http://www.whatwg.org/ development of HTML rather than the W3C one. Just my opinion as a user experience and web designer myself - "check out their FAQ":http://wiki.whatwg.org/wiki/FAQ to get a better understanding of their purpose, history and position about HTML)