WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: JAWS issue for mandatory fields

for

From: Birkir R. Gunnarsson
Date: Apr 16, 2018 5:52AM

The Accessible name and description computation spec refers to
including cSS generated content:
https://www.w3.org/TR/accname-1.1/
(search for "CSS gen" or "example 3".
I think there is value in being able to add content to CSS classes,
e.g. to consistently indicate when something is a PDF file or a secure
link etc. I also admit that blurring the lines between styling and
content can lead to problems.



On 4/16/18, Patrick H. Lauke < <EMAIL REMOVED> > wrote:
> On 16/04/2018 12:17, Steve Green wrote:
>> I can't find a specification anywhere that says what the behaviour should
>> be. My instinct is that Internet Explorer is right and the others are
>> wrong - CSS content is an oxymoron and it feels so wrong. How did it ever
>> get into the CSS spec?
>
> There is no spec that authoritatively says "this is what a user agent
> should expose in its accessibility tree".
>
> With that said: lots of authors started using CSS-generated content.
> User agents and AT decided to expose this to their users.
>
> It's a bit late NOW, years after they've all been consistently doing it,
> to say "I think all browsers are wrong here". Again, because so many
> sites rely on it in the wild.
>
> P
> --
> Patrick H. Lauke
>
> www.splintered.co.uk | https://github.com/patrickhlauke
> http://flickr.com/photos/redux/ | http://redux.deviantart.com
> twitter: @patrick_h_lauke | skype: patrick_h_lauke
> > > > >


--
Work hard. Have fun. Make history.