WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Is generated content reliably read by screen readers today?

for

From: Birkir R. Gunnarsson
Date: Nov 23, 2018 6:43AM

I filed an issue against WCAG failure technique f87
https://github.com/w3c/wcag/issues/433

which forbids use of CSS pseudo content. I filed it based on the fact
that the accessible name and description calculation includes CSS
generated content.

That being said, while I think it should be valid, I agree with the
great points that Steve makes that it is problematic for a variety of
reasons, so shoud not be recommended. Fortunately sVG icons are
increasingly replacing CSS icons, which is a win for accessibility,
minor screen reader sVG support issues aside.


On 11/23/18, Léonie Watson < <EMAIL REMOVED> > wrote:
> 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
> > > > >


--
Work hard. Have fun. Make history.