Speech recognition support

[marius andreiana]

Hi,

Would it be possible to add speech recognition support to Chrome,
similar Android Voice Actions?
It would be great to type messages like this one by voice (a11y, RSI,
speed, star trek fun :)

Thanks

[Peter Beverloo]

> --
> Chromium Discussion mailing list: chromium...@chromium.org
> View archives, change email options, or unsubscribe:
>    http://groups.google.com/a/chromium.org/group/chromium-discuss
>

Hello Marius,

Work is currently being done on a prototype implementation of speech
input fields. It was first proposed in May[1], a design document is
available[2] as well and rendering on both Mac as Windows seems to be
progressing rather nicely as well[3].

Since most of the current changes are related to WebKit (although some
plumbing was done with r54981), and not the actual recognition itself,
it most likely won't be available in the very near future. There are
two bugs which you can star to be informed of any changes, I suspect
they'll be closed when a working implementation "ships" in the
nightlies. A team member will most likely be able to tell you more on
the progress.

http://crbug.com/44844
http://crbug.com/7767

Regards,
Peter Beverloo

[1] http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2010-May/026338.html
[2] https://docs.google.com/Doc?docid=0AaYxrITemjbxZGNmZzc5cHpfM2Ryajc5Zmhx&hl=en
[3] http://trac.webkit.org/browser/trunk/LayoutTests/platform/chromium-mac/fast/speech/input-appearance-speechbutton-expected.png?rev=64746

[Ben]

On Fri, 2010-08-13 at 19:18 +0200, Peter Beverloo wrote:
> On Fri, Aug 13, 2010 at 19:08, marius andreiana
> <marius.a...@gmail.com> wrote:
> > Hi,
> >
> > Would it be possible to add speech recognition support to Chrome,
> > similar Android Voice Actions?
> > It would be great to type messages like this one by voice (a11y, RSI,
> > speed, star trek fun :)
> >
> > Thanks
> >
>

> Hello Marius,
>
> Work is currently being done on a prototype implementation of speech
> input fields. It was first proposed in May[1], a design document is
> available[2] as well and rendering on both Mac as Windows seems to be
> progressing rather nicely as well[3].

[snip]

What about speech input into regular text input fields? To me, that
sounds more like what he was asking about. But a special tag for that
isn't bad either, I guess.

> Regards,
> Peter Beverloo
>
> [1] http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2010-May/026338.html
> [2] https://docs.google.com/Doc?docid=0AaYxrITemjbxZGNmZzc5cHpfM2Ryajc5Zmhx&hl=en
> [3] http://trac.webkit.org/browser/trunk/LayoutTests/platform/chromium-mac/fast/speech/input-appearance-speechbutton-expected.png?rev=64746
>

--
Ben

[Peter Beverloo]

Hi Ben,

Currently speech input is being implemented using an additional
attribute, "speech". Actual code of the screenshot I referred to would
be this:

<input style="font-size: 10px" value="A quick brown fox jumps over the
lazy dog" speech>

An image displaying it on <input type="number"> is available as well:
http://trac.webkit.org/export/64746/trunk/LayoutTests/platform/chromium-mac/fast/speech/input-appearance-numberandspeech-expected.png

Regards,
Peter Beverloo

[D]

hi guys, sorry for being selfish, but is it ok to blog about this yet ?

Greetings,

Dinsan

Chromestory.com 

--

[Ben]

Ah, thanks, that makes sense. Though, I was thinking more along the
lines of not needing an attribute or tag. But I don't know much about
how websites are designed with accessibility in mind, is that a bad idea
for some reason?

--
Ben

[PhistucK]

Of course you can, every public code can be discussed and it is public.

☆PhistucK

[PhistucK]

Please, do not advertise here.

☆PhistucK

On Fri, Aug 13, 2010 at 21:06, D <din...@gmail.com> wrote:

thanks ! its up there now !

digg love will be much appreciated :) http://digg.com/d31ZXvn

[D]

thanks ! its up there now !

digg love will be much appreciated :) http://digg.com/d31ZXvn

Greetings,

Dinsan

Chromestory.com 

On Fri, Aug 13, 2010 at 11:33 PM, PhistucK <phis...@gmail.com> wrote:

[Marius Andreiana]

On Fri, Aug 13, 2010 at 8:49 PM, Ben <benj...@gmail.com> wrote:

> > What about speech input into regular text input fields? To me, that
> > sounds more like what he was asking about. But a special tag for that
> > isn't bad either, I guess.
> 

> Currently speech input is being implemented using an additional
> attribute, "speech". 

Ah, thanks, that makes sense. Though, I was thinking more along the
lines of not needing an attribute or tag. But I don't know much about
how websites are designed with accessibility in mind, is that a bad idea
for some reason?

Thanks for discussion, Peter and Ben.

My thoughts are in line with Ben's - being able to start using speech to fill all text fields which are in use today, without any additional tags. Why is a new element necessary, when we already have text and textarea in wide use? (pardon my ignorance)

 Marius

[PhistucK]

In case you did not notice - it was changed to be an attribute, not element.

PhistucK

--

[Marius Andreiana]

On Sat, Aug 14, 2010 at 9:55 AM, PhistucK <phis...@gmail.com> wrote:

In case you did not notice - it was changed to be an attribute, not element.

Will speech recognition work with elements without this attribute? Otherwise all webpages will have to be updated to just include "speech". 

I still don't understand the reasoning for a separate attribute. To me it seems similar to a "paste" attribute (which would allow one to paste contents in a text field), which wouldn't make sense.

With labels, why wouldn't the current HTML markup be enough to fully complete a web form with speech?

 

PhistucK

[PhistucK]

I believe it will eventually be a default option, but for now, it is an attribute. Do not forget that it is still in an early stage of conceptual development.

☆PhistucK

[Ben]

I was thinking, and it occurred to me that you could make a very simple
extension which adds the speech attribute to text fields
automatically--just as a temporary measure, of course. But since this
feature is still in-development, I'm not sure if that's a good idea or
not.

--
Ben