WEBVTT

1
00:00:00.000 --> 00:00:03.240
Thank you to the workshop organisers

2
00:00:05.086 --> 00:00:07.982
for inviting me to share our work.

3
00:00:09.765 --> 00:00:12.480
My name is Emmanuel Jacq.

4
00:00:13.235 --> 00:00:14.600
I am Deaf.

5
00:00:14.640 --> 00:00:17.700
I lead International Deaf Emergency,

6
00:00:19.620 --> 00:00:22.080
a Deaf-led nonprofit

7
00:00:22.404 --> 00:00:24.940
in the United States.

8
00:00:26.306 --> 00:00:29.640
After the 2010 Haiti earthquake,

9
00:00:31.908 --> 00:00:34.540
we worked with the Red Cross

10
00:00:36.805 --> 00:00:39.569
to build an accessible camp

11
00:00:40.941 --> 00:00:43.620
for four hundred Deaf
and disabled people.

12
00:00:43.660 --> 00:00:46.137
That experience taught us:

13
00:00:50.707 --> 00:00:52.841
people left out

14
00:00:53.805 --> 00:00:56.080
must help design the solution.

15
00:00:56.120 --> 00:00:59.387
Today, I am here as an implementer.

16
00:01:01.105 --> 00:01:04.400
Our system receives live CAP alerts

17
00:01:06.146 --> 00:01:08.060
from IPAWS

18
00:01:11.600 --> 00:01:13.968
and the National Weather Service.

19
00:01:14.008 --> 00:01:16.315
We also work under

20
00:01:18.706 --> 00:01:24.480
a Memorandum of Agreement
with FEMA's IPAWS program.

21
00:01:25.908 --> 00:01:28.393
We work on the last step:

22
00:01:32.341 --> 00:01:34.280
from the alert

23
00:01:36.300 --> 00:01:38.160
to the person.

24
00:01:38.200 --> 00:01:40.620
Our focus is simple.

25
00:01:42.215 --> 00:01:44.920
How can a CAP alert become

26
00:01:45.740 --> 00:01:48.531
a signal people can notice

27
00:01:50.139 --> 00:01:53.444
through light, touch, or sound?

28
00:01:53.905 --> 00:01:57.300
CAP helps systems share a warning.

29
00:02:01.011 --> 00:02:03.900
But a message reaching a device

30
00:02:05.201 --> 00:02:07.280
does not mean

31
00:02:08.880 --> 00:02:11.400
it has reached the person.

32
00:02:11.600 --> 00:02:14.140
A siren needs hearing.

33
00:02:16.920 --> 00:02:19.340
A screen needs sight.

34
00:02:20.620 --> 00:02:26.460
For Deaf, DeafBlind, and blind
people, warnings can still miss us.

35
00:02:28.320 --> 00:02:31.340
We need to ask two questions.

36
00:02:35.205 --> 00:02:37.920
Can the person notice the warning?

37
00:02:38.340 --> 00:02:40.500
Can they understand

38
00:02:43.506 --> 00:02:45.460
what is happening

39
00:02:45.600 --> 00:02:47.600
and what to do?

40
00:02:47.700 --> 00:02:50.640
Reception is not communication.

41
00:02:52.008 --> 00:02:54.960
Imagine you are inside a building.

42
00:02:58.406 --> 00:03:00.663
An alarm goes off.

43
00:03:02.600 --> 00:03:04.120
Fire?

44
00:03:06.080 --> 00:03:07.920
Tsunami?

45
00:03:08.060 --> 00:03:09.700
Tornado?

46
00:03:10.020 --> 00:03:13.980
Different dangers can
require different actions.

47
00:03:14.020 --> 00:03:16.620
The alert may tell you which.

48
00:03:17.720 --> 00:03:20.740
One general signal does not.

49
00:03:21.209 --> 00:03:23.919
Getting attention is one step.

50
00:03:26.103 --> 00:03:28.560
Understanding is another.

51
00:03:29.480 --> 00:03:31.580
Think of SOS.

52
00:03:35.407 --> 00:03:37.700
A rhythm can carry

53
00:03:38.340 --> 00:03:41.020
a learned, shared meaning.

54
00:03:41.540 --> 00:03:44.360
That idea inspired our work:

55
00:03:45.220 --> 00:03:48.280
the Three Senses Alerting Standard.

56
00:03:48.680 --> 00:03:51.720
It is a draft specification,

57
00:03:54.208 --> 00:03:56.980
published for anyone to review.

58
00:03:57.500 --> 00:04:00.291
Six families of danger,

59
00:04:04.506 --> 00:04:06.300
plus a test pattern,

60
00:04:06.340 --> 00:04:08.760
plus one defined fallback

61
00:04:08.800 --> 00:04:11.520
for anything we cannot place.

62
00:04:12.709 --> 00:04:15.440
One rhythm for each family.

63
00:04:17.800 --> 00:04:20.340
The same pattern through

64
00:04:21.507 --> 00:04:23.040
light,

65
00:04:23.280 --> 00:04:25.020
touch,

66
00:04:25.240 --> 00:04:27.000
and sound.

67
00:04:27.260 --> 00:04:29.820
Learn a pattern on one device.

68
00:04:29.860 --> 00:04:32.260
Recognise it on another.

69
00:04:33.905 --> 00:04:36.920
Our application is called Deaflare.

70
00:04:37.420 --> 00:04:39.855
We are building it for

71
00:04:41.902 --> 00:04:45.700
Deaf, hard of hearing,
and DeafBlind users.

72
00:04:46.200 --> 00:04:48.880
It is one implementation

73
00:04:53.006 --> 00:04:55.500
of the Three Senses approach.

74
00:04:55.540 --> 00:04:57.651
Let me show you.

75
00:05:02.282 --> 00:05:05.760
Fire uses fast, short pulses.

76
00:05:08.009 --> 00:05:11.380
Water uses long, rolling waves.

77
00:05:13.080 --> 00:05:15.180
Watch the difference.

78
00:05:16.220 --> 00:05:18.200
That was water.

79
00:05:23.507 --> 00:05:26.100
Long, rolling waves.

80
00:05:29.405 --> 00:05:30.600
Now compare it with fire.

81
00:05:30.640 --> 00:05:33.300
Fast, short pulses.

82
00:05:35.605 --> 00:05:37.480
Two dangers.

83
00:05:38.440 --> 00:05:40.820
Two different patterns

84
00:05:40.960 --> 00:05:43.260
on the same phone.

85
00:05:43.640 --> 00:05:46.780
This video shows the visual pattern.

86
00:05:46.820 --> 00:05:49.260
Feeling the vibration

87
00:05:56.407 --> 00:05:59.180
needs a hands-on demonstration.

88
00:06:02.515 --> 00:06:04.020
How does this connect to CAP?

89
00:06:04.060 --> 00:06:06.700
Start with the event information

90
00:06:06.740 --> 00:06:08.740
in the CAP alert.

91
00:06:09.060 --> 00:06:11.540
Our software maps that information

92
00:06:11.580 --> 00:06:13.980
to a hazard family.

93
00:06:15.112 --> 00:06:17.800
That family selects a rhythm.

94
00:06:18.580 --> 00:06:21.018
A water-related hazard

95
00:06:23.705 --> 00:06:26.180
maps to the water pattern.

96
00:06:26.220 --> 00:06:29.060
The original alert still carries

97
00:06:31.400 --> 00:06:33.780
the specific event

98
00:06:34.906 --> 00:06:37.100
and its instructions.

99
00:06:37.280 --> 00:06:39.580
How would an originator

100
00:06:42.114 --> 00:06:44.260
say this in CAP?

101
00:06:44.905 --> 00:06:48.290
CAP 1.2 already gives us

102
00:06:48.660 --> 00:06:51.140
the parameter block.

103
00:06:52.508 --> 00:06:55.140
We propose one parameter.

104
00:06:55.707 --> 00:06:57.660
You may ask:

105
00:07:00.105 --> 00:07:02.780
CAP already has category.

106
00:07:03.100 --> 00:07:05.740
Why not just use that?

107
00:07:05.940 --> 00:07:08.480
Because the category Met

108
00:07:09.000 --> 00:07:11.240
can cover a flood

109
00:07:12.500 --> 00:07:14.520
and a tornado.

110
00:07:15.120 --> 00:07:17.500
Those need different rhythms.

111
00:07:18.680 --> 00:07:21.080
And the event string

112
00:07:23.104 --> 00:07:25.160
is free text.

113
00:07:25.814 --> 00:07:28.321
So the mapping must be

114
00:07:29.409 --> 00:07:31.380
written down

115
00:07:31.500 --> 00:07:33.309
and versioned.

116
00:07:33.980 --> 00:07:36.140
Our mapper reads

117
00:07:38.520 --> 00:07:40.440
the CAP event and category.

118
00:07:40.480 --> 00:07:43.040
It is unit tested against

119
00:07:43.809 --> 00:07:46.620
real National Weather Service

120
00:07:46.940 --> 00:07:48.980
event strings.

121
00:07:51.412 --> 00:07:54.200
This is our proposed convention.

122
00:07:55.904 --> 00:07:58.660
It is not a CAP requirement.

123
00:08:00.060 --> 00:08:02.820
No schema change is needed.

124
00:08:04.308 --> 00:08:07.260
We can use CAP 1.2

125
00:08:07.806 --> 00:08:09.880
as it stands.

126
00:08:10.911 --> 00:08:13.640
But each system must pass

127
00:08:14.640 --> 00:08:17.020
the parameter on,

128
00:08:18.305 --> 00:08:20.880
and the receiving software

129
00:08:22.105 --> 00:08:24.342
must understand it.

130
00:08:25.040 --> 00:08:27.488
The rhythm is one part

131
00:08:30.120 --> 00:08:32.080
of the warning.

132
00:08:32.600 --> 00:08:35.080
It helps someone notice

133
00:08:36.606 --> 00:08:39.320
and recognise a family of danger.

134
00:08:39.360 --> 00:08:41.620
Then they need the message:

135
00:08:45.006 --> 00:08:46.760
What happened?

136
00:08:49.906 --> 00:08:51.360
Where?

137
00:08:51.806 --> 00:08:53.320
When?

138
00:08:53.600 --> 00:08:55.500
What should I do?

139
00:08:55.540 --> 00:08:57.840
That must stay accessible

140
00:08:59.641 --> 00:09:01.640
through the tools the person uses.

141
00:09:01.680 --> 00:09:03.900
There are two limits

142
00:09:06.909 --> 00:09:09.380
I want to make clear.

143
00:09:09.880 --> 00:09:11.340
One.

144
00:09:13.101 --> 00:09:16.540
The rhythm identifies
a danger family.

145
00:09:16.900 --> 00:09:19.980
It does not carry the full message.

146
00:09:20.580 --> 00:09:22.876
Water does not say

147
00:09:25.509 --> 00:09:27.300
which river,

148
00:09:27.840 --> 00:09:29.700
how high,

149
00:09:30.705 --> 00:09:33.260
or whether to climb or leave.

150
00:09:33.500 --> 00:09:36.240
The action comes from the alert.

151
00:09:38.540 --> 00:09:40.180
Two.

152
00:09:43.508 --> 00:09:45.860
We cannot yet promise

153
00:09:47.100 --> 00:09:48.680
the same rhythm

154
00:09:48.720 --> 00:09:50.380
when the phone is locked

155
00:09:50.420 --> 00:09:53.080
or the app is in the background.

156
00:09:54.820 --> 00:09:57.820
That depends on the platform,

157
00:09:59.980 --> 00:10:01.980
the device,

158
00:10:03.905 --> 00:10:06.200
and our implementation.

159
00:10:07.340 --> 00:10:09.800
We need help testing

160
00:10:09.840 --> 00:10:12.740
and improving that last step.

161
00:10:12.806 --> 00:10:16.080
And for DeafBlind users especially,

162
00:10:17.306 --> 00:10:19.660
a vibration alone

163
00:10:21.204 --> 00:10:23.480
is not the full warning.

164
00:10:23.760 --> 00:10:26.660
We can demonstrate the patterns.

165
00:10:30.406 --> 00:10:32.980
What we cannot do alone

166
00:10:35.204 --> 00:10:37.700
is test the whole path

167
00:10:38.340 --> 00:10:40.740
across your systems.

168
00:10:41.301 --> 00:10:43.740
Does the hazard mapping

169
00:10:45.814 --> 00:10:47.840
stay correct?

170
00:10:49.320 --> 00:10:52.180
Does the receiving software

171
00:10:52.220 --> 00:10:54.800
choose the intended pattern?

172
00:10:54.860 --> 00:10:57.600
What happens on a device

173
00:10:58.712 --> 00:11:01.132
that does not support it?

174
00:11:02.711 --> 00:11:04.880
These are questions

175
00:11:06.908 --> 00:11:09.440
we want to test with you.

176
00:11:09.541 --> 00:11:11.800
Three requests.

177
00:11:16.406 --> 00:11:17.940
One.

178
00:11:18.906 --> 00:11:21.040
Review our mapping

179
00:11:21.660 --> 00:11:23.900
from CAP event information

180
00:11:23.940 --> 00:11:26.280
to hazard families.

181
00:11:27.106 --> 00:11:29.820
Choose an event you know well.

182
00:11:30.180 --> 00:11:33.100
Tell us where the mapping works

183
00:11:34.706 --> 00:11:37.240
and where it needs to change.

184
00:11:38.606 --> 00:11:41.056
Please send your feedback

185
00:11:44.310 --> 00:11:47.540
by 30 November 2026.

186
00:11:47.580 --> 00:11:49.260
Two.

187
00:11:53.005 --> 00:11:57.640
Test passing the proposed
parameter through your own system:

188
00:11:58.346 --> 00:12:00.480
from origination,

189
00:12:02.105 --> 00:12:04.280
to the receiving software,

190
00:12:04.320 --> 00:12:06.240
to the signal.

191
00:12:07.628 --> 00:12:09.100
Three.

192
00:12:10.905 --> 00:12:13.120
Test with the people

193
00:12:13.321 --> 00:12:15.480
who will use the warning.

194
00:12:15.520 --> 00:12:19.140
Deaf, DeafBlind, and blind people

195
00:12:20.005 --> 00:12:22.040
must help design and test this.

196
00:12:22.080 --> 00:12:24.220
Check both halves:

197
00:12:28.005 --> 00:12:30.420
Can they notice the danger?

198
00:12:33.005 --> 00:12:35.080
Can they understand

199
00:12:37.706 --> 00:12:39.542
what to do?

200
00:12:39.605 --> 00:12:41.880
Our draft specification

201
00:12:45.504 --> 00:12:47.940
is available to review

202
00:12:48.020 --> 00:12:49.820
and implement royalty-free.

203
00:12:49.860 --> 00:12:52.840
There is also a software library

204
00:12:54.807 --> 00:12:56.840
you can install.

205
00:12:58.200 --> 00:13:00.800
ideafe.org/standard

206
00:13:03.508 --> 00:13:05.740
We want this work

207
00:13:07.120 --> 00:13:09.300
to be used and improved.

208
00:13:09.340 --> 00:13:11.840
CAP connects systems.

209
00:13:12.820 --> 00:13:15.420
Together, we can help

210
00:13:15.820 --> 00:13:18.640
those systems reach people.

211
00:13:19.280 --> 00:13:21.960
Deaf people know what happens

212
00:13:23.280 --> 00:13:25.960
when warnings fail us.

213
00:13:26.408 --> 00:13:28.760
We should be their engineers.

214
00:13:30.206 --> 00:13:32.820
Please write your questions

215
00:13:34.980 --> 00:13:37.080
to my email.

216
00:13:37.540 --> 00:13:40.064
I will answer in writing.

217
00:13:41.520 --> 00:13:43.680
Emmanuel Jacq,

218
00:13:44.504 --> 00:13:47.300
International Deaf Emergency,

219
00:13:47.920 --> 00:13:50.800
emmanuel.jacq@ideafe.org

220
00:13:50.840 --> 00:13:52.460
Thank you.