You are completely missing the point. It needs to be *MORE* than just visual for Accessibility reasons. While an <hr /> may not have any true semantic meaning (in a strict sense), it is structural none-the-less; it indicates a clean break between what proceeds it and what follows it. This "concept" is not hard to understand - it is neither ephemeral nor hard-to-define. However, it renders horribly in today's ultra-cool graphic interface designs, and so designers/developers shun it.
Very interesting and very unconvincing. For one, HR can be styled, so not too much problem for today's ultra-cool graphic interface. As for "Accessibility" I am really interested how HR helps it, and how it is rendered in non visual browsers, and is this the best way of doing it.
And so the "way it comes to life" *is* important - it should be integral to the source code. The way it visually renders... Now that's where there is room for improvement.
Ok, how about this improvement - give the section which must be separated from the previous one some meaningful header, but hide it with CSS, rendering only visual separator, like line, three stars, whatever. Regards, Rimantas -- http://rimantas.com/ ******************************************************************* List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *******************************************************************
