E-mail List Archives
Thread: CSS 'content: '
Number of posts in this thread: 4 (In chronological order)
From: Nancy Johnson
Date: Wed, Nov 13 2013 9:54AM
Subject: CSS 'content: '
No previous message | Next message →
Hi,
Is there accessibility issues with CSS generated content?
If so is Jquery a better option?
Thanks
Nancy
From: Alastair Campbell
Date: Wed, Nov 13 2013 10:58AM
Subject: Re: CSS 'content: '
← Previous message | Next message →
Nancy Johnson wrote:
> Is there accessibility issues with CSS generated content?
>
> If so is Jquery a better option?
In short, yes and yes.
CSS generated content is supported in most browsers, but last time I
checked in JAWs was essentially invisible (VoiceOver will read it). It
isn't really on the list of 'reliable' methods to convey information yet.
Content generated by a script and inserted onload should be available to
virtually all access technology. (Putting aside the JavaScipt !=
Accessibility arguments.) It can be different if the content is added
dynamically as you go through the page, but as an equivalent to CSS
content, I assume you mean onload.
Hth,
-Alastair
From: Jared Smith
Date: Wed, Nov 13 2013 11:08AM
Subject: Re: CSS 'content: '
← Previous message | Next message →
On Wed, Nov 13, 2013 at 9:54 AM, Nancy Johnson wrote:
> Is there accessibility issues with CSS generated content?
There are some foundational issues that need to be resolved with CSS
generated content. How can something be style *and* content at the
same time? We have for years advocated separation of content from
style - meaning moving stylistic definitions out of HTML content and
into CSS. Now we're shifting to the other extreme - content is moving
into CSS. There's much debate over whether CSS generated content
should be read by screen readers at all, and as Alastair noted, some
read it because they see it as content and some do not because they
see it as styles. Neither is right or wrong, because it has yet to be
defined what the proper behavior should be.
I'd recommend caution and the assumption that generated content will
not usually be read, while also ensuring that if it is read, that it
does not result in a poor user experience.
Jared
From: Nancy Johnson
Date: Wed, Nov 13 2013 11:10AM
Subject: Re: CSS 'content: '
← Previous message | No next message
Thank you.
I was hoping that that had changed.
Nancy
On Wed, Nov 13, 2013 at 12:58 PM, Alastair Campbell < = EMAIL ADDRESS REMOVED = > wrote:
> Nancy Johnson wrote:
>
>> Is there accessibility issues with CSS generated content?
>>
>> If so is Jquery a better option?
>
>
> In short, yes and yes.
>
> CSS generated content is supported in most browsers, but last time I
> checked in JAWs was essentially invisible (VoiceOver will read it). It
> isn't really on the list of 'reliable' methods to convey information yet.
>
> Content generated by a script and inserted onload should be available to
> virtually all access technology. (Putting aside the JavaScipt !=
> Accessibility arguments.) It can be different if the content is added
> dynamically as you go through the page, but as an equivalent to CSS
> content, I assume you mean onload.
>
> Hth,
>
> -Alastair
> > >