Re: How are screen readers supposed to read <hr> which has icons as generated contents?

2017-01-22 5:18 GMT+08:00 Amelia Bellamy-Royds <
amelia.bellamy.royds@gmail.com>:

> On the question of what screen-readers *should* do (note, I don't know if
> this is what they *do* do):
>
> An <hr> element should be treated like the ARIA non-interactive (assuming
> no tabindex) "separator" role:
> http://w3c.github.io/aria/aria/aria.html#separator
>
> An element with the ARIA separator role is supposed to be treated as if
> any child content is presentational, which means the child content is
> ignored by screen-readers.  Child content includes any text or child
> elements you add by script, but it also includes CSS-generated text.
>
> You may add a name to a separator element (using aria-label,
> aria-labelledby, or even title), but that would normally only make sense if
> it is an interactive separator (that is, a slider used to adjust the size
> of adjacent regions).  For interactive sliders, additional attributes & JS
> are required to make it functional.
>
> In other words, unless you give it extra attributes, an <hr/> should
> always be read out only as a "break" or "thematic break", regardless of any
> content added inside it.
>
> FYI, I don't think the @media speech query is well supported, nor is
> aria-hidden able to be set via CSS.
>
> ~ABR
>

Thank you for the info. Is there a spec defines that CSS generated content
should be treated as child content? could you please also provide the data
of the support for @media speech? Cheers.

Yes. There is currently no such declaration as "aria-hidden: true" in CSS.
That was just an example I used to illustrate the convenience if such
declaration exists.

Ian Yang