Then we wonder why the W3C is toothless.
Also Design By Committee.
Wh00ps I went off topic.
For I while I really was trying to use the logo/sitename (and the logo often ISN'T and image, just some stylised site/company name) as the h1 on the main page, since the meaning of the h1 and that text matched (the page is about the comapany, name of company counts as page title). On other pages, logo got relegated to a p or whatever and the h1 switched places to where appropriate.
However when doing this latter bit, if there's a header earlier in the document (say there's a header block with navigation and whatsits that come before the "main content"... site chrome) then you get issues with, if that navigation menu header is an h2, you have an h2 before the h1. And switching positions makes no sense: let's say you did move the navigation and its header under the h1, on the About page, that "Main navigation" h2 (so yeah I'm talking about when people add accessibility headers above menus, but this could be anything) still doesn't count as being "under" about Us. It's "under" Joe's Company. Yet the page is about About Us and that should be its h1.
This gets worse if the site is created with a floated sidebar that comes before the main content in source order (say, just to have unfloated main section able to site side-by-side with sidebar). There may be a heap of headers in that sidebar, and they'd all be coming before the h1 in source.
if browsers understood the new document outline designed in HTML5 (and they don't), then this could be solved: the About Us could have its h1 wherever in the document it is, as About Us is the whole point of the page and that content is the reason the page exists... but the sidebar (esp if it doesn't change from page to page) becomes an <aside> (which is vaguely-related content that can stand on its own) and site chrome can be separated from Main content.
Sometimes it's way too much dancing around to have site chrome (headers, sidebars, footers, site-wide navigation lists, and social BS icons) always somehow come after the Main Content while look however you need it to look.
In any case I stopped with the h1 position switching, not because that might confuse people (tho maybe it did), but because the back-end templating system always got it wrong, and I'm a front-ender so I have little control over back-end screwups.