I think what the accessibility group was getting at, was that software can be programmed to recognize an <hr/> and treat it differently than the <p> or <div>. Visually it doesn't make a difference, but the standards that support accessibility should be followed.
Using their 2nd example, I was able to include images, or fleurons, within the <hr/>. It actually became easier/shorter to code as well.
I previously used this when inserting a scene break:
Code:
<div class="ChDiv"><img alt="" src="../Images/fleur.gif"/></div>
Now I can use:
Code:
<hr class="ChDiv"/>
and the CSS for <hr> is fairly straight forward:
Code:
hr.ChDiv {
border:none;
margin:1.25em auto; height:.5em;
background: transparent url("../Images/fleur.gif") no-repeat center;
background-size: auto 100%;
overflow: hidden;
page-break-inside: avoid;
break-inside: avoid;
}