- From: Martin Wheatman <martin@wheatman.net>
- Date: Fri, 14 Jun 2019 15:37:42 +0100
- To: Adi Latif <adi.latif@abilitynet.org.uk>
- Cc: Michellanne Li <michellanne.li@gmail.com>, W3c-wai Ig <w3c-wai-ig@w3.org>
- Message-ID: <4616622e56df549e9d96116d30ff03d7@wheatman.net>
Many thanks for your encouraging replies - always welcome! I'm in the process of getting the basic interface up and running at the moment. It currently works with buttons, links and input text boxes, and it covers basic navigation. It still needs to do radio buttons and checkboxes, and do screen-reading! For the moment, it uses the Return key to initiate the listen cycle - I'm just assuming you can find the Return key! It also means you have to use it's language for the moment, I'm hoping this will be easy enough: I'll post more examples as I do them. Also, it needs the web page to contain a line of PHP providing the control panel (including the "listen" button), and the web-server to contain this PHP. The whole idea of "accessibility" software puzzles me - it really means providing access to screens and keyboards, when we can already do speech-to-text-to-speech, seamlessly. I've done this on Android, under the Enguage project: it's just the world uses the Web! NB. when I get Enguage ported, you should be able to construct you own language - vocal "macros" allowing you to program your own interface: everything by voice. --- Kind regards, Dr Martin Wheatman, t: +44 (0)7976 394225 e: martin@wheatman.net w: https://enguage.org/ On 2019-06-14 2:55 pm, Adi Latif wrote: > Im a blind voiceOver user i love this idea > > Sent from my iPhone > > On 14 Jun 2019, at 13:39, Michellanne Li <michellanne.li@gmail.com> wrote: > > This is fascinating! I'm interested. > > Michellanne Li > (512) 718-2207 > > http://www.michellanne.com > > On Tue, Jun 11, 2019 at 8:38 AM Martin Wheatman <martin@wheatman.net> wrote: > > Hello, > > I developed a vocal interface (2011-12) as an Android app (2013-15), which I'm now connecting to the Web. It should have use as an accessibility layer, although it's not really accessibility software because rather than connecting the user to the GUI, it attempts to bypass the paradigm. > > https://youtu.be/JYSO7fE6liA > > Is this of interest to the group? > > -- > Kind regards, > Dr Martin Wheatman, > t: +44 (0)7976 394225 > e: martinAtWheatmanDotNet > w: https://enguage.org/
Received on Friday, 14 June 2019 14:38:06 UTC