If someone knows more about accessibility as it relates to CSS content, I’m sure we’d all love to know more. I was really bad at using VoiceOver and found it frustrating to get it to do what I was trying to do even at the most basic levels.
If that is the case, try opening your website in a popup. I had trouble getting it to do that, but I thought I did get it to do it once somehow. This could mean that your application has some settings preventing it from being opened in an iframe. For best accessibility, I would think the goal would be to get it to read the whole text, including the CSS content being added. I was trying to use VoiceOver with Safari on my Mac with the email popout links demo. Regarding accessibility, I’m just not 100% sure what the situation was. email-address::before Īll the major browsers (Firefox 3+, Safari 3+, Chrome 3+, Opera 10+, and Internet Explorer 8+) ( See the full chart) support CSS content with the ::after/::before pseudo-elements and the spec is in its full candidate recommendation status. It is written like a pseudo selector (with the colon), but it’s called a pseudo-element because it’s not actually selecting anything that exists on the page but adding something new to the page. It can only be used with the pseudo-elements ::after and ::before.
0 kommentar(er)
