Because of possible security reasons, some customization may not be
possible, some may.
In other words, web app author must not be able to control everything in
the speech GUI.
R13 has two parts. One is the "include a clickable graphic to invoke
speech recognition", the other one is "indicate the progress of the
recognition through various states".
It is the first one which *may* need to be limited a bit.
And the latter one is already implicitly handled in the requirement for
different kinds of events.
-Olli
On 12/08/2010 12:39 PM, Dan Burnett wrote:
> Group,
>
> This is the next of the requirements to discuss and prioritize based on
> our ranking approach [1].
>
> This email is the beginning of a thread for questions, discussion, and
> opinions regarding our first draft of Requirement 13 [2].
>
> Please discuss via email as we agreed at the Lyon f2f meeting.
> Outstanding points of contention will be discussed live at an upcoming
> teleconference.
>
> -- dan
>
> [1]
> http://lists.w3.org/Archives/Public/public-xg-htmlspeech/2010Oct/0024.html
> [2]
> http://lists.w3.org/Archives/Public/public-xg-htmlspeech/2010Oct/att-0001/speech.html#r13
>
>
>
>