RE: Intention Events and Javascript Screen Readers

I’m not sure who said it. If that’s not a requirement, that’s fine too. Let me know if anyone has this request. Thanks!

From: James Craig [mailto:jcraig@apple.com]
Sent: Friday, November 7, 2014 11:46 AM
To: Ben Peters
Cc: public-indie-ui@w3.org
Subject: Re: Intention Events and Javascript Screen Readers

Do you recall who mentioned that? It doesn’t sound familiar.

Possible mentions that you might be recalling:

1. Native (non-JavaScript) screen readers like VoiceOver sometimes operate on views by getting or setting the value directly. So the “select text” intention could come on the form of something like setSelectionForRange.

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.

On Nov 7, 2014, at 11:05 AM, Ben Peters <Ben.Peters@microsoft.com<mailto:Ben.Peters@microsoft.com>> wrote:
You mentioned at TPAC that a good use case for Intentions would be building a javascript screen reader that could listen to and fire Intentions. Could one of you send me a use case for that? Example use cases can be found on the Editing Explainer (http://w3c.github.io/editing-explainer/#use-cases). Thanks!

Ben