<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Regarding the minutes, regarding the following:<br>
<br>
PK: ... The refresh adds a bunch of new rules. One of the notable
additions is real-time text for the deaf and a much more significant
effort on the deaf and on communication technologies<br>
<br>
PB: On the speech reco angle, did they talk about whether it was good
enough for what we want to do?<br>
<br>
PK: I don't remember any mention of speech recognition. The NRPM says
at a high level that someone without hands needs to be able to use your
app. Doesn't specifically mention speech recognition. Apps that support
audio and video chat must also support real-time text. <br>
<br>
This is an accurate representation of the exchange during the meeting,
but what I really was asking is, in the case where speech reco might be
used to transcribe speech, will the current (or near in) state of the
art of speech reco technology be able to provide acceptable real-time
text, considering the challenge of large vocabularies, speaker
independence, the variety of speakers, and conversational speech? Or
do the requirements allow for the use of real time human transcribers
(either local or remote)?<br>
<br>
<div class="moz-signature">-- <br>
<font color="#0060a0" face="Arial, sans-serif" size="1"><b>Pete Brunet</b></font><br>
<font color="#0060a0"><span style="text-decoration: line-through;">
</span></font><br>
<font color="#333333" face="Arial, sans serif" size="1">
a11ysoft - Accessibility Architecture and Development<br>
(512) 238-6967 (work), (512) 689-4155 (cell)<br>
Skype: pete.brunet<br>
IM: ptbrunet (AOL, Google), <a class="moz-txt-link-abbreviated" href="mailto:ptbrunet@live.com">ptbrunet@live.com</a> (MSN)<br>
<a class="moz-txt-link-freetext" href="http://www.a11ysoft.com/about/">http://www.a11ysoft.com/about/</a><br>
Ionosphere: WS4G
<br>
</font>
</div>
</body>
</html>