View Single Post
Old 06-23-2020, 05:40 PM   #126
Turtle91
A Hairy Wizard
Turtle91 ought to be getting tired of karma fortunes by now.Turtle91 ought to be getting tired of karma fortunes by now.Turtle91 ought to be getting tired of karma fortunes by now.Turtle91 ought to be getting tired of karma fortunes by now.Turtle91 ought to be getting tired of karma fortunes by now.Turtle91 ought to be getting tired of karma fortunes by now.Turtle91 ought to be getting tired of karma fortunes by now.Turtle91 ought to be getting tired of karma fortunes by now.Turtle91 ought to be getting tired of karma fortunes by now.Turtle91 ought to be getting tired of karma fortunes by now.Turtle91 ought to be getting tired of karma fortunes by now.
 
Turtle91's Avatar
 
Posts: 3,368
Karma: 20212733
Join Date: Dec 2012
Location: Charleston, SC today
Device: iPhone 15/11/X/6/iPad 1,2,Air & Air Pro/Surface Pro/Kindle PW & Fire
There WAS a need when they deprecated <i>/<b>. It is/was more semantically correct because <i>/<b> are just visual...it's understandable that you don't see a need when you aren't working with audio readers or other accessibility issues.

I just learned that chapter/scene breaks are supposed to be done using an <hr/> because audio readers/accessibility devices can't tell the difference between sections if you just use a <div> or <p>. Soooo.... I went in and figured out how to do it properly - even though I don't need or use accessibility devices (yet). Do my books look OK without using the <hr/>, of course - they look great - but it is more correct to use the <hr/> so I do. Likewise, it is more correct to use the <em>/<strong> so I do.
Turtle91 is offline   Reply With Quote