true. CSS is injecting content that does not show up in the DOM.
Rich Schwerdtfeger
From: Dominic Mazzoni <dmazzoni@google.com>
To: James Craig <jcraig@apple.com>
Cc: Ben Peters <Ben.Peters@microsoft.com>, "public-indie-ui@w3.org"
<public-indie-ui@w3.org>
Date: 11/07/2014 02:09 PM
Subject: Re: Intention Events and Javascript Screen Readers
On Fri, Nov 7, 2014 at 11:45 AM, James Craig <jcraig@apple.com> wrote:
2. Someone mentioned ChromeVox which, to my knowledge is the only screen
reader that relies entirely on the Web Browser (this may no longer be an
accurate statement) rather than on a platform accessibility API.
Initially it was dependent on the DOM, but I think it now has more hooks
into browser internals, not just the client-side DOM.
This is correct. Initially it was a design goal to see if we could build
ChromeVox using only web APIs. This proved to be an unreasonable limitation
because there are too many corner cases where DOM APIs are insufficient,
and as the web continues to evolve, these APIs are constantly one step
behind.
