Charles --

Thanks for the hat. It was a long time in the making, and I did my best to struggle between meeting accessibility guidelines and the difficulty of having IE/Win display the damn page right.

To address some specific points:
And now that the long list of links is down at the bottom of the page, it might be nice to use, as the first child of the BODY element, Skip to content | Skip to external navigation

I'll think about this. The only thing before the "content," however, is the main navigation link bar, so I'm not sure how useful "Skip to content" would really be. And "Skip to external naviagation" would only link to the other IMCs...not exactly "External Navigation" generally speaking. But perhaps worth linking to directly nonetheless. (Bear in mind that the new code is really based on a non-IMC-specific codebase, so Media Centers aren't privileged in any way).

I need to see "Baltimore IMC" at the top of the page when the images are not presented. And it should be your H1 element:.

The printheader (normally hidden from graphical browsers) shows up at the top of the page...you don't think that suffices? As for needing it to be the H1 element of the page, I'm not sure I concur...while I have purist tendancies myself, I'm not convinced that the strict Hn hierarchy is appropriate for contemporary page design. It assumes that all information should be structured in descending order of significance, which may be logical from one perspective, but it ignores a wealth of other mental organizational factors. Feature categories, for example, are h3 tags (less important than H1 titles or H2 sub-titles), but are nonetheless presented above the titles, which makes much more sense from an structural standpoint.

And frankly, the page TITLE should be the identifying marker for the site, not the first H1 tag. Your online Lynx viewer does not display the page title anywhere, which seems to me a more serious omission. ;-)

Your "More..." links are problematic...

I did notice that when I was doing Accessibility testing, but I didn't get a chance to address it. For things like Features, it should be easy to remedy, though it might end up looking a bit strange sometimes (if there isn't much of a summary). Using the "title" attribute would seem like a good solution, but it doesn't pass muster with the Accessibility validator...hmmm. Will have to try something else.

You have at the end of the page a long list of links that is marked up as a number of paragraphs with line breaks. You should mark up all lists as lists...This has nothing to do with accessibility, but your CSS is not valid.

Fair enough. The list is actually parsed from XML, and it _would_ be valid CSS, but there's a bug in the XML formatting. Blech. Marking it up as a list would probably solve the problem as well, so I'll look into it...

Thanks for the input!