John Foliot wrote:
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.
I agree completely. I like your example, Rimantas, but there is indeed
meaning there, which is more than simply 'presentational' (unless you
define 'presentational' as whatever isn't fully digestible by your PDA).
Maybe you'd chose to answer this with an audio and braille stylesheet
containing p.s1:after{content:"[separation]"}... But I actually believe
all of this is way too convoluted a way of compensating for the fact
that something very simple is missing.
Besides, the separation does not occur within the pounds of that
paragraph. If the paragraph before or after the separation were to be
deleted, there is no immediate reason for the separation to disappear -
it is an object in its own right and deserves independence.
Regards,
Barney
*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
*******************************************************************
