- From: Charles McCathieNevile <chaals@opera.com>
- Date: Thu, 10 Nov 2011 18:19:20 +0100
- To: "Jim Allan" <jimallan@tsbvi.edu>
- Cc: WAI-ua <w3c-wai-ua@w3.org>
On Thu, 10 Nov 2011 17:56:06 +0100, Jim Allan <jimallan@tsbvi.edu> wrote: > On Thu, Nov 10, 2011 at 9:42 AM, Charles McCathieNevile > <chaals@opera.com>wrote: > >> On Wed, 09 Nov 2011 18:09:09 +0100, Jim Allan <jimallan@tsbvi.edu> >> wrote: >> >> could find no reference to prohibiting CSS generated content from >>> appearing in the DOM. >>> >> >> But what is the mechanism by which it appears? It is part of style, so >> should be accessible through getComputedStyle, but I am not sure that is >> actually useful. I'm not sure how DOM handles pseudo-elements, which >> are in any event defined in CSS. >> >> >> Jim: I am not sure of the mechanism. it just appears on the screen, but >> is not in the DOM. It isn't an object in the normal flow of the DOM. You could query the rules applied to the element, via the DOM, but that is a step too far for most AT. >> there doesn't appear to be anything that a UA can do to access this >>> information. A screen reader could scrape the screen and keep >>> refreshing to find generated content...tedious, many cpu cycles, etc. >>> >> >> Opera just exposes the content directly. I don't see why other browsers >> don't do that. >> >> Jim: New Information: created a test page > http://test.tsbvi.edu/generated.htm with style > http://test.tsbvi.edu/generated.css > tested with Jaws 12. predicted results in FF7 and IE8 - that is Jaws did > not read the generated text. > BUT Jaws read the text in Chrome. Not sure why or how. Because Firefox has a bug that Chrome doesn't. Opera on Mac, using Voiceover, also reads the text. I'd suggest filing a bug on Firefox. cheers -- Charles 'chaals' McCathieNevile Opera Software, Standards Group je parle français -- hablo español -- jeg kan litt norsk http://my.opera.com/chaals Try Opera: http://www.opera.com
Received on Thursday, 10 November 2011 17:20:10 UTC