Quote:
Originally Posted by bookman156
I would normally make a space between some paragraphs in text by adding the requisite top or bottom margin to a p class.
|
I've written about this many times over the years:
See my posts in:
And I even cover all the pros/cons in extreme detail here:
Long story short.
DO NOT use only a gap like a physical book.
Use centered asterisks (or fleurons, or ANYTHING VISIBLE) to indicate your scenebreaks.
Quote:
Originally Posted by bookman156
However, EPUB 3 Best Practices (ten years old) tells me this is bad for accessibility since readers for the blind (ten years ago) couldn't interpret such a margin. That book recommends instead that I use a horizontal rule, a hr tag, in which I make the width zero to dispense with the rule and then add top and bottom margin.
|
I would still stick with centered asterisks over HTML5's usage of <hr> + CSS3 to change the look.
Remember, KISS (Keep It Simple, Stupid!). And not all devices have CSS.
I discussed this all in extreme detail in:
Side Note: If you want the ultimate latest topic on "Italics <i> vs. Emphasis <em>" + Accessibility, see my breakdown in:
Quote:
Originally Posted by bookman156
Clever I suppose, but to me this is a bad semantic practice, since my three-line space is a pause, not a rule or a fleuron.
|
In HTML5, they changed the semantics of <hr>.
In the modern web, there's also this thing called the "Accessibility Tree" + ARIA Roles... and <hr> helps generate new HTML <section>s in your text. (Allowing easier navigation via Screen Readers, etc.)
Semantically, it is the correct way of doing scenebreaks... but in reality, I would tentatively avoid using <hr> like that in your ebooks.
I mean, <hr> is OKAY—and it's definitely better than your visual gap—but there are disadvantages compared to centered asterisks. (It was all discussed in those thread above.)
Quote:
Originally Posted by bookman156
Some people probably still use numerous br tags, but this is a leftover from bad web design.
|
No. Rarely, if ever, should you use <br>.