-
Notifications
You must be signed in to change notification settings - Fork 229
/
audio-only-live.html
158 lines (101 loc) · 6.01 KB
/
audio-only-live.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
<!DOCTYPE html>
<html lang="en" xml:lang="en" xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta charset="UTF-8"></meta>
<title>Understanding Audio-only (Live)</title>
<link rel="stylesheet" type="text/css" href="../../css/sources.css" class="remove"></link>
</head>
<body>
<h1>Understanding Audio-only (Live)</h1>
<section id="intent">
<h2>Intent of Audio-only (Live)</h2>
<p>The intent of this Success Criterion is to make information conveyed by live audio,
such as web-based audio conferencing, live speeches and radio Webcasts, accessible through the
use of a text alternative. A live text caption service will enable live audio to be
accessible to people who are deaf or hard of hearing, or who cannot otherwise hear
the audio. Such services use a trained human operator who listens in to what is being
said and uses a special keyboard to enter the text with only a small delay. They are
able to capture a live event with a high degree of fidelity, and also to insert notes
on any non spoken audio which is essential to understanding the event. A transcript
is sometimes a possibility if the live audio is following a set script; but a live
caption service is preferred because it plays out at the same pace as the audio itself,
and can adapt to any deviations from the script that might occur.
</p>
<p>Using untrained operators, or providing a transcript which differs markedly from what
actually happens would not be considered meeting this Success Criterion.
</p>
<p>This success criterion was intended to apply to broadcast of audio and is not intended
to require that two-way audio calls between two or more individuals through web apps
must be captioned regardless of the needs of users. Responsibility for providing captions
would fall to the content providers (the callers) or the “host” caller, and not the
application.
</p>
</section>
<section id="examples">
<h2>Examples of Audio-only (Live)</h2>
<ul>
<li>A public relations firm uses Web based caption services to cover live events; the
output from the service is incorporated in a sub frame of the Web page which includes
the streaming audio control.
</li>
<li>A live radio play of a fringe theatre group is being broadcast to the Web. As the
actors stick largely to a set script, and the budget for the program is small, the
producers provide a link (with the playwright's permission) to the script of the play.
</li>
<li>A streaming audio server uses a technology which can also accommodate text and graphics,
such as HTML5 or Silverlight. A stenographer is used to create live captions at an
event, and these are mixed on the fly to produce live captions in the media stream
which can be viewed by the media player.
</li>
<li>A CEO is to give a press release by telephone to the media in response to a breaking
news story, the audio is being recorded and streamed over the internet, but due to
time constraints a Web captioning service cannot be set up in time. As the press release
is a set statement which the CEO will be reading out, the company simultaneously provides
the transcript of the release.
</li>
</ul>
</section>
<section id="resources">
<h2>Resources for Audio-only (Live)</h2>
<ul>
<li>
<a href="http://www.captioningandsubtitling.com.au/work/internet/">Captioning and Subtitling International</a>
</li>
<li>
<a href="http://webaim.org/techniques/captions/realtime">WebAIM Real time captioning resource</a>
</li>
<li>
<a href="http://www.uiaccess.com/transcripts/transcript_services.html">uiAccess list of transcription services</a>
</li>
<li>
<a href="http://www.uiaccess.com/transcripts/transcripts_on_the_web.html">Transcripts on the Web: Getting people to your podcasts and videos</a>
</li>
</ul>
</section>
<section id="techniques">
<h2>Techniques for Audio-only (Live)</h2>
<section id="sufficient">
<h3>Sufficient Techniques for Audio-only (Live)</h3>
<ol>
<li>
<a href="https://www.w3.org/WAI/WCAG21/Techniques/general/G151" class="general">Providing a link to a text transcript of a prepared statement or script if the script
is followed
</a>
</li>
<li>
<a href="https://www.w3.org/WAI/WCAG21/Techniques/general/G150" class="general">Providing text alternatives for live audio-only content</a>
</li>
<li>
<a href="https://www.w3.org/WAI/WCAG21/Techniques/general/G157" class="general">Incorporating a live audio captioning service into a Web page</a>
</li>
</ol>
</section>
<section id="advisory">
<h3>Additional Techniques (Advisory) for Audio-only (Live)</h3>
</section>
<section id="failure">
<h3>Failures for Audio-only (Live)</h3>
</section>
</section>
</body>
</html>