<...>
Since the <hr /> *is* a page element, it is announced and rendered as such -
it is a Horizontal Rule - or break, in just about every user-agent known to
mankind; it is one of the most basic of HTML constructs.  There is a reason
*why* you as a page author/content creator wants that "line/division/break"
on screen - I mean it's not just there on a whim is it?

Thats my point: there must be the reason for such separation and I don't think
that "Horizontal Rule" be it visual or aural.

 And so, ensuring
that the "intent" carries through to alternative user-agents is a goal of
Universal Accessibility.  We have the HTML "tool" to do this - the <hr /> -
yes, it's ugly, yes' it's limiting, but, yes, it has more *meaning* than
<img src="linebreak.gif" alt="" />.

Ok, let's take <img src="linebreak.gif" alt="Horizontal rule" />.
In visual media it will be horizontal rule, aural browser will
announce it as "image: horizontal rule". Is it any worse than just
"Horizontal rule"?

If inserting a meaningful Heading at that point in you content is
appropriate, then this is good (but why would you hide it from some, and not
others?  Would not the meaningful header also be of aid/assistance to those
with cognitive load issues, those with lower comprehension or literacy
skills - perhaps ESL?).

Exactly. If separation is indeed that meaningful why not to use
something more meaningful to announce it?


 However, again, I will ask: if you are using the
image to convey *any* kind of meaning what-so-ever, how are you conveying
this meaning to alternative user-agents.  It also means you must ask
yourself if there *is* a meaning to the break image (I submit that there
probably is) or is it really just eye-candy.
<...>

I still see HR as eye-candy or ear-candy. Ok, let's say you are
reading the book for someone, and encounter the separator. What would
you do? Say "three stars follow",
"horizontal line follows", or just make a longer pause?

So, if following section deserves own header - give it, if not -
render longer pause in aural version, and some eye candy for visual
media with CSS. If aural browser does not support
pause-before properly: too bad.
<...>


Regards,
Rimantas
--
http://rimantas.com/


*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
*******************************************************************

Reply via email to