This wouldn’t work so great if every website used different headline tags.
It reminds me of the battles about CSS vs Tables for layout where screen readers were always wheeled out as an argument for not using tables. Expect that all the shipping screen readers seemed to cope fairly well with tables.
(There are many ways in which your markup can break screen-readers but the issues are often more subtle and complex than 'use this tag or that tag' and require someone to actually test in a specific screen reader)
It’s pretty cool actually: You can rotate with two fingers to switch between different ways of navigating the page: headline to headline, link to link, container to container, line to line and so on.
I suggest you try it out when you have the chance. (If you want you can test out HN to see how the experience here could be significantly improved if headline tags were used correctly.) Here is a short video if you can’t try yourself: http://www.youtube.com/watch?v=rxlxx6RXbs8
Do you really think accessibility advocates were asking everyone to correctly use headline tags for fun?
For example, pre-HTML5 sites often use a variety of <div id="head">, <div id="heading">, <div id="header">, etc. If each website is a separate entity that's fine, but if we have a longer term goal of creating some kind of global project - a programmable, mashable, indexable web - it's easier with a pre-agreed vocabulary.
I agree there may be a better way to do it and tag names could be taken to far, but with iterative development we'll get something that works and can be used by everyone (which is better than a perfect solution that never leaves the drawing board), IMO.