E-mail List Archives
Re: JAWS issue for mandatory fields
From: Patrick H. Lauke
Date: Apr 16, 2018 5:21AM
- Next message: Birkir R. Gunnarsson: "Re: JAWS issue for mandatory fields"
- Previous message: Steve Green: "Re: JAWS issue for mandatory fields"
- Next message in Thread: Birkir R. Gunnarsson: "Re: JAWS issue for mandatory fields"
- Previous message in Thread: Steve Green: "Re: JAWS issue for mandatory fields"
- View all messages in this Thread
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
- Next message: Birkir R. Gunnarsson: "Re: JAWS issue for mandatory fields"
- Previous message: Steve Green: "Re: JAWS issue for mandatory fields"
- Next message in Thread: Birkir R. Gunnarsson: "Re: JAWS issue for mandatory fields"
- Previous message in Thread: Steve Green: "Re: JAWS issue for mandatory fields"
- View all messages in this Thread