WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: hide decorative characters from screen readers

for

From: Benjamin Hawkes-Lewis
Date: Aug 13, 2011 3:48AM

On Sat, Aug 13, 2011 at 2:14 AM, Jason Kiss < <EMAIL REMOVED> > wrote:
> On 13/08/11 06:57, John Foliot wrote:
>> Yes, I agree that screen readers (NVDA has the same behavior) shouldn't
>> real aloud :before or :after pseudo-selector characters. We have a
>> precedent here in that you cannot copy and paste those same characters
>> from the browser screen (they are treated like background images) and
>> screen readers should treat them the same way as well, IMHO.
>>
>> Anyone disagree, and if so why (please)?
>
> I tend to agree with you, John, and foresee this possibly becoming a
> thorny issue as the current draft of "Implementing UAAG 2.0"
> (http://www.w3.org/TR/IMPLEMENTING-UAAG20/#sc-414) also suggests that
> user agents should make CSS generated content available to accessibility
> APIs

WAI-ARIA, which is in CR, makes this a requirement:

http://www.w3.org/TR/wai-aria/roles#namecalculation

See also:

http://www.w3.org/Bugs/Public/show_bug.cgi?id=13668

> I wonder if browsers should then also be making such generated content
> selectable for copy and paste?

Copy and paste is very idiosyncratically implemented, but already does
include some generated content.

--
Benjamin Hawkes-Lewis