E-mail List Archives
Thread: What's The State Of Support For Screen Readers And CSS-generated Content?
Number of posts in this thread: 5 (In chronological order)
From: Jim Homme
Date: Wed, May 25 2022 2:28PM
Subject: What's The State Of Support For Screen Readers And CSS-generated Content?
No previous message | Next message →
Hi,
I just ran across some CSS-generated content that I could read in Chrome with JAWS and NVDA. That's what prompted the question of the subject of this message. How are things with this, and what is the best way to keep up with such things so I can avoid giving bad advice?
Thanks.
Jim H
=========Jim Homme
Senior Digital Accessibility Consultant
Bender Consulting Services
412-787-8567
https://www.benderconsult.com/
Support the dreams of independence through employment for students with disabilities with your Amazon purchases.
https://smile.amazon.com/ch/83-0988251
From: Bryan Garaventa
Date: Wed, May 25 2022 5:51PM
Subject: Re: What's The State Of Support For Screen Readers And CSS-generated Content?
← Previous message | Next message →
Hi,
I'm not sure about the best way to keep up with this, but CSS content has been supported now for several years that I am aware of.
This is part of the W3C AccName spec, and it is directly added to the accessibility tree within Chrome, Firefox, Edge, and Safari.
This is why screen readers pick it up. Visual ARIA uses this technique to display all discovered ARIA roles and attributes on the page.
All the best,
Bryan
Bryan Garaventa
Principal Accessibility Architect
Level Access, Inc.
= EMAIL ADDRESS REMOVED =
415.624.2709 (o)
www.LevelAccess.com
From: Steve Green
Date: Thu, May 26 2022 12:27AM
Subject: Re: What's The State Of Support For Screen Readers And CSS-generated Content?
← Previous message | Next message →
Internet Explorer 11 doesn't support CSS content, but not many people will worry about that now.
Steve Green
Managing Director
Test Partners Ltd
From: Léonie Watson
Date: Thu, May 26 2022 1:53AM
Subject: Re: What's The State Of Support For Screen Readers And CSS-generated Content?
← Previous message | Next message →
When I looked into this back in 2015, the only browser not to support
exposing content generated using the before/after selectors as part of
the accessible name for links, was IE. Otherwise all browsers on all
platforms with the common screen readers on each platform did.
https://tink.uk/accessibility-support-for-css-generated-content/
Note: the test case linked from that post has disappeared. I'll restore
it as soon as I have a few minutes.
Léonie.
On 26/05/2022 00:51, Bryan Garaventa via WebAIM-Forum wrote:
> Hi,
> I'm not sure about the best way to keep up with this, but CSS content has been supported now for several years that I am aware of.
>
> This is part of the W3C AccName spec, and it is directly added to the accessibility tree within Chrome, Firefox, Edge, and Safari.
>
> This is why screen readers pick it up. Visual ARIA uses this technique to display all discovered ARIA roles and attributes on the page.
>
> All the best,
> Bryan
>
>
> Bryan Garaventa
> Principal Accessibility Architect
> Level Access, Inc.
> = EMAIL ADDRESS REMOVED =
> 415.624.2709 (o)
> www.LevelAccess.com
>
>
From: Bryan Garaventa
Date: Thu, May 26 2022 2:40AM
Subject: Re: What's The State Of Support For Screen Readers And CSS-generated Content?
← Previous message | No next message
Thanks, my sense of time is a bit screwy. ð
Bryan Garaventa
Principal Accessibility Architect
Level Access, Inc.
= EMAIL ADDRESS REMOVED =
415.624.2709 (o)
www.LevelAccess.com