Welcome to WebmasterWorld Guest from 126.96.36.199
Forum Moderators: ergophobe
Its relatively easy to hide content in Drupal using CSS, however its a whole different ball game to hide content and keep it accessible to all site visitors. Disabled web users may be using a screen reader or other Assistive Technology. For Drupal 7 we wanted a way to hide content that worked in all browsers and avoided many of the issues associated with current techniques.
clip: rect(1px 1px 1px 1px); /* IE6 & 7 */
clip: rect(1px, 1px, 1px, 1px);
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.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.
I know that Drupal 7 is considered, above all, a usability releasebased on the above, my question would be "whose usability?"
(I'm not sure in Drupal parlance what a "section" is, but I assume that blocks will become sections?) have titles, but designers often choose to have them not display.
they are attempting to make up for theme designer accessibility ignorance/shortcomings from within the Drupal core.
or it is better thought out perhaps?
So I don't see it as a binary choice between doing it half-ass and doing it right, but a ternary choiceI don't agree with your conclusion - but I do agree your point is valid. And you gave me my new word for the day ;)
this to me is a core issue that has cropped up and has been fixed because of the attention to accessibility rather than SEO or design..Using clip as a means to hide content rather than display to avoid the user agent rendering issues only works if clip doesn't create a whole set of new issues. I looked at clip for a visual design outcome a few years ago, but implementation was so poor it wasn't usable. Based on the articles, testing doesn't seem that robust, including not yet testing all AT's. Seems to me this clip can't be touted as an accessibility-driven accessible solution until testing shows it is accessible, and doesn't create other problems.
the power behind the "hiding" is as important for SEO as it for navigation/access - at least I think soMe too. Although I wish they weren't frequently constructed as being in opposition, and given priority in that order. But I do think the argument that this is a way of making up for ignorance/knowledge shortcomings has merit - and add on laziness, and the "it doesn't affect me personally, so I won't bother" brigade as well.
Seems to me this clip can't be touted as an accessibility-driven accessible solution until testing shows it is accessible, and doesn't create other problems.