E-mail List Archives
Re: Is generated content reliably read by screen readers today?
From:
- Next message: Birkir R. Gunnarsson: "Re: Is generated content reliably read by screen readers today?"
- Previous message: Steve Green: "Re: Is generated content reliably read by screen readers today?"
- Next message in Thread: Birkir R. Gunnarsson: "Re: Is generated content reliably read by screen readers today?"
- Previous message in Thread: Steve Green: "Re: Is generated content reliably read by screen readers today?"
- View all messages in this Thread
When I tested this in 2015, the only browser not to accessibility
support the before/after pseudo-selectors, was IE. The common browser
and screen reader combinations across all platforms were able to handle
content generated in this way.
https://tink.uk/accessibility-support-for-css-generated-
On 23/11/2018 09:47, Detlev Fischer wrote:
> Hi,
>
> In 2013, there was a discussion here that stated that some browser /
> Screenreader combinations did not reliably expose CSS-generated content
> (via ::before). In the UA / SR combinations I have tried now, 5 years
> later, CSS-generated text content was exposed and read. While I reckon
> it is still not a recommended practice to use generated content on all
> but decorative or supplemental information - is there still a case for
> calling out such practice as WCAG failure?
>
> Opinions?
>
> Best, Detlev
>
--
@LeonieWatson tink.uk Carpe diem
- Next message: Birkir R. Gunnarsson: "Re: Is generated content reliably read by screen readers today?"
- Previous message: Steve Green: "Re: Is generated content reliably read by screen readers today?"
- Next message in Thread: Birkir R. Gunnarsson: "Re: Is generated content reliably read by screen readers today?"
- Previous message in Thread: Steve Green: "Re: Is generated content reliably read by screen readers today?"
- View all messages in this Thread