alt131 - 2:04 am on Nov 26, 2010 (gmt 0)
I have always had an issue with hiding content ... not much room for discussion there ;)
However, I think this is the biggest issue
I read that as premised on the idea that, consistent with the intention behind html5 document structure and therefore proper evaluation of content, sections will have headings - but for those coders/content writers who can't be bothered evaluating their content and marking it up correctly there will be a facility for them to avoid the html5 intent ... and it's Ok because it's accessible.
Apparently Drupal 7 is to have headers for all sections (in line with HTML5 recommendations) and the ability for the end user of the CMS to hide them would be essential for theming I suppose, which is why it surfaced in Core.
To me that just means coders/content writers can slap an html5 happy face on their code without regard for the html5 intent. Sheesh, if <section>'s are supposed to have headers, then if a section of content doesn't need a header it isn't a <section>. So this seems to be actively setting in place a means to allow <section> to be mis-used. div-itis turned section-itis. Just longer to type. Oh yay.
It may be accessible, but that does not make it good code.
I'm also wondering about the tab order for AT, how many have already made adjustments for multiple h1's - and what happens to the tab order when expected h1's are hidden/not present, etc.
I think identifying that perspectives inform the discussions about hiding content is insightful. But then, I've always been surprised that even at WebmasterWorld accessibility isn't treated as an aspect of "Code, Content, and Presentation" for the purpose of grouping related forums.
based on the above, my question would be "whose usability?"
I know that Drupal 7 is considered, above all, a usability release