TRASCRIZIONE 🔗
WEBVTT
00:00.593 --> 00:04.167
The Event Industry News Podcast is sponsored by Prezent Communications.
00:04.824 --> 00:08.687
Prezent provides broadcast-quality live, hybrid, and virtual event
00:09.187 --> 00:12.903
production trusted by organizations where reliability really matters.
00:13.640 --> 00:17.391
From corporate town halls and conferences to high-profile live streams,
00:17.904 --> 00:21.575
they design and deliver fully resilient systems that work first
00:27.762 --> 00:31.001
Hello everybody and welcome along to the Event Industry News Podcast
00:31.033 --> 00:33.631
with me, James Dixon, wishing you all a very good morning,
00:33.679 --> 00:36.998
afternoon, or evening, whenever or wherever you tune into
00:37.127 --> 00:41.793
today's podcast from. And as you can probably see straight
00:42.293 --> 00:45.208
off the bat at the start of today's podcast, I'm not in my usual surroundings,
00:45.305 --> 00:49.089
sat on an upright piano at home with a dog sat on the sofa behind
00:49.589 --> 00:53.066
me, which is where I often find, and over the last few years I've mostly
00:53.082 --> 00:56.528
found myself recording these podcasts. I am really excited to
00:57.028 --> 01:01.079
say that we are in the fantastic surrounds of the ICC Wales
01:01.752 --> 01:05.165
down in Newport. The Event Industry News team came down
01:05.181 --> 01:09.202
here yesterday. We've had a lovely experience touring some of the venue,
01:09.459 --> 01:12.792
staying over last night, treated to a very nice dinner, and we've
01:13.292 --> 01:16.942
got the pleasure of recording some episodes of the podcast here at the ICC Wales
01:17.006 --> 01:20.306
today. So thank you very much to all the team for facilitating
01:20.338 --> 01:23.915
this and having Event Industry News along to record some of our podcasts.
01:24.043 --> 01:29.054
So on today's episode, we're going to be talking accessibility,
01:29.151 --> 01:31.881
closing the accessibility gap in events.
01:31.961 --> 01:35.029
Accessibility is increasingly part of
01:35.529 --> 01:39.349
the events conversation, but the experience of disabled delegates suggests that
01:39.365 --> 01:42.898
there is still a significant gap between intention and reality.
01:42.995 --> 01:46.416
I'm joined on the podcast today by Dr. Shani Danda, first of
01:46.916 --> 01:50.896
all, and Amy Phillips, the Sales Director from
01:51.396 --> 01:52.550
ICC Wales. So Amy, first of all, I'll come to you and say thank you
01:53.050 --> 01:56.290
for hosting us here at the venue, it's fabulous. Tell us a little
01:56.790 --> 02:00.050
bit about yourself, what you do here. Okay, thanks, Ciarán. So yeah, as you said,
02:00.550 --> 02:03.810
I'm the Sales Director here at ICC Wales, so I manage the sales team and
02:04.310 --> 02:08.190
I'm responsible for our sales strategy. And we also commissioned the
02:08.690 --> 02:12.370
Access All Areas report in conjunction with the Business of Events, and we involved Sharni
02:12.870 -->
Load full transcript
02:15.710
from the start to include her expert opinion along the way.
02:16.076 --> 02:19.572
Fabulous. And Sharni, welcome along to the podcast. Again, give us a
02:19.620 --> 02:22.651
little bit of background and some context as to who you are,
02:22.667 --> 02:26.516
what you do, and why you're here today. Sure. So I'm an accessibility specialist,
02:26.580 --> 02:29.756
so I work with different businesses and brands across all
02:29.884 --> 02:33.525
different industries and sectors and help them to make everything more
02:33.557 --> 02:37.662
accessible, either for their customers, their employees, or their overall business
02:38.162 --> 02:41.559
strategy. But my background and career started in events.
02:41.672 --> 02:45.476
I studied a degree in event management and spent 10 years in
02:45.524 --> 02:49.217
the industry working in-house and agency
02:49.717 --> 02:53.808
side. And yeah, I've always been passionate about events,
02:54.016 --> 02:57.612
not only from working in the industry myself, but going to
02:57.628 --> 03:00.341
them and trying to enjoy events too.
03:01.321 --> 03:04.387
I always say to guests that come on the podcast who are doing something now
03:04.467 --> 03:07.918
but have a background in agency and corporate, in actual events,
03:07.983 --> 03:11.740
hands-on event management, that that gives people a very good sort of
03:11.772 --> 03:14.903
contextual starting place, that you have that basic understanding of
03:15.403 --> 03:18.805
how events work. Because we get a lot of people and experts in
03:18.902 --> 03:22.499
any industry telling us how we should be doing things, but really, unless somebody
03:22.515 --> 03:27.059
has got a background in doing that and understands the pain points of people organizing
03:27.284 --> 03:30.126
events, it's difficult to provide that expert opinion.
03:30.303 --> 03:33.675
Yeah, you need to understand the operations behind it,
03:34.012 --> 03:37.175
the conflicting priorities, the the budget
03:37.223 --> 03:41.264
constraints. Yeah, you absolutely have to understand the
03:41.312 --> 03:45.080
parameters in which you're operating in and all the things that
03:45.580 --> 03:49.378
are involved in that. Absolutely. Which leads us on to, I suppose, the basis of
03:50.051 --> 03:54.028
today's conversation on the podcast, which is this
03:54.525 --> 03:57.973
report and research that's been commissioned. Amy, I'm going to come to you first
03:58.053 --> 04:02.046
a little bit to sort of explain what the report is and ICC Wales'
04:02.639 --> 04:06.427
involvement and place within that research? Yeah, absolutely.
04:06.556 --> 04:10.554
So the report was born through just curiosity really,
04:10.892 --> 04:14.778
and wanting to learn and develop. So the report essentially
04:14.842 --> 04:18.616
looks at what venues say they're doing, but also the delegate
04:19.116 --> 04:23.450
experience. So we were looking at sort of bridging that gap between,
04:23.579 --> 04:27.385
you know, what venues are saying and what delegates' experiences are. So for
04:27.433 --> 04:30.757
us, it was really interesting to look across the breadth of the report.
04:30.870 --> 04:34.113
So kind of not just looking at ramps and physical
04:34.613 --> 04:37.260
accessibility, but looking at neurodiversity as well,
04:38.288 --> 04:42.446
looking at digital accessibility. So yeah,
04:42.543 --> 04:45.320
we've learned a lot ourselves from the report, and I think it's been a really
04:45.353 --> 04:48.050
good tool for the industry to use to learn and improve.
04:48.885 --> 04:53.012
Could I just ask, how many venues were contacted as
04:53.060 --> 04:55.613
part of the research? Do you know that sort of figure off the top of
04:56.113 --> 04:59.523
your heads? Yes, I think it was in excess of 100 venues.
05:00.116 --> 05:04.490
Right, okay, so we're talking about quite a breadth and of all sort of varieties
05:04.522 --> 05:07.870
as well. Do they all fall into one category or? No, it was a breadth,
05:07.902 --> 05:11.475
so from convention centres to hotels to smaller venues. So I think,
05:11.971 --> 05:15.320
you know, we're a purpose-built convention centre, so lucky in a
05:15.820 --> 05:20.190
way to be built with accessibility from the start. However, not all venues have
05:20.222 --> 05:23.939
that luxury, so there's, you know, historic buildings, listed buildings, of course,
05:24.371 --> 05:28.264
where things can be a little bit more challenging. So yeah, survey went
05:28.393 --> 05:31.999
out to a breadth of different venues. And the
05:32.336 --> 05:35.172
sort of headline stat that I pulled out of the information that I was given
05:35.188 --> 05:38.779
before today's podcast was, while venues
05:38.827 --> 05:41.503
are reporting significant investment in accessibility,
05:41.920 --> 05:45.142
93% of disabled delegates surveyed said
05:45.642 --> 05:47.995
that they still encounter barriers when attending events.
05:48.652 --> 05:50.623
That's not just a majority, that's,
05:51.713 --> 05:55.159
you know, and everybody that was surveyed is still saying, look, it could be better.
05:55.223 --> 05:57.373
It's never going to be perfect, or is it?
05:58.449 --> 06:01.823
No, no, I don't think anything's perfect,
06:01.903 --> 06:06.079
and there's actually no such thing as fully accessible because what
06:06.579 --> 06:09.935
could be accessible to one person could be completely inaccessible
06:10.435 --> 06:13.838
to another. But that's not a reason for us not to care about it.
06:14.256 --> 06:17.051
There are lots of reasons why we should care about accessibility,
06:17.629 --> 06:20.135
but when we look at that stat, um,
06:21.243 --> 06:24.279
what we learned is that many people are still struggling with
06:24.649 --> 06:28.245
different barriers. So things like inaccessible layouts,
06:28.631 --> 06:31.216
overstimulating environments, uh,
06:31.681 --> 06:35.519
staff that perhaps haven't had disability awareness
training,
06:36.177 --> 06:40.175
uh, inaccessible toilets. So quite simple
06:41.155 --> 06:44.141
and easy to solve things, I would say.
06:44.703 --> 06:48.846
But when we talk about accessibility, what we're really talking about is
06:49.890 --> 06:53.897
disabled people having an equivalent user experience to non-disabled
06:53.929 --> 06:57.600
people. Like, nobody has to be an expert in different people's
06:58.100 --> 07:02.137
medical conditions or different people's health conditions. We manage that
07:02.585 --> 07:06.160
with those professionals. What we should be focusing
07:06.272 --> 07:10.200
on is what are the barriers, whether it's a venue or an event,
07:10.520 --> 07:14.688
and how can we reduce and remove them. So the
07:15.188 --> 07:18.856
venues, the sort of quote that I gave out there from my notes,
07:18.920 --> 07:21.741
while venues report significant investment in accessibility,
07:22.062 --> 07:25.559
significant investment again is ambiguous
07:25.671 --> 07:29.007
in some respects, isn't it? Because if they're starting from ground zero as
07:29.055 --> 07:32.487
a venue, if they've not really addressed the topic previously,
07:32.984 --> 07:36.192
significant investment might still only sort of scratch the
07:36.692 --> 07:40.025
surface a little bit of what they could be doing in order to be,
07:40.410 --> 07:43.249
you know, fully inclusive, if we can use that term.
07:43.490 --> 07:46.729
Again, when it comes to the investment that's being made, Amy,
07:46.922 --> 07:50.306
by those venues, was there a disparity and were you able to actually
07:50.434 --> 07:53.870
look at what that type of investment represented amongst some of the venues?
07:54.528 --> 07:57.964
Yeah, I think it's hard to pinpoint across the board, but it can be anything
07:58.140 --> 08:01.592
from investment in time and training and even
08:01.673 --> 08:04.964
having internal working groups if you haven't got that
08:05.464 --> 08:09.845
budget to go out and pay for expert training. I think everybody
08:09.877 --> 08:13.024
needs to have a starting point, and I think everybody's starting point is very different.
08:13.088 --> 08:16.829
So yeah, I think in terms of investment, it could mean a lot of things.
08:16.990 --> 08:20.937
You know, in terms of— yeah, but it's an interesting point where
08:21.246 --> 08:24.550
you raise about training and the
08:25.050 --> 08:28.254
idea that it's sort of investment in a venue from an
08:28.754 --> 08:31.764
accessibility point of view has to be in terms of its physical structure and,
08:32.118 --> 08:35.757
you know, that the actual infrastructure of the building— investment
08:35.789 --> 08:38.839
can be just in the people that run and operate a venue so that they
08:38.855 --> 08:41.985
have a better understanding, I guess. Yeah, absolutely, and,
08:42.421 --> 08:46.593
you know, the different knowledge that you can gain can lead you to doing very
08:46.930 --> 08:49.734
free or low-cost changes as well.
08:50.199 --> 08:53.259
So there's a company called AccessAble, and they,
08:54.028 --> 08:57.233
um, they're like the TripAdvisor for
08:57.249 --> 09:00.213
the disability community, right? So if you want to visit somewhere,
09:00.534 --> 09:03.690
they audit places. They'll, they will have different pictures
09:03.738 --> 09:07.488
of the layouts, how many toilets or steps there are. You get the gist.
09:07.728 --> 09:11.589
Yeah. Um, they did some research and they found that 95% of
09:12.089 --> 09:15.839
disabled people research a venue before
09:16.339 --> 09:21.003
they go and visit it, and 96% of disabled people say when
09:21.051 --> 09:24.660
they have that information on accessibility, it influences their
09:25.160 --> 09:29.376
decision to attend or not. Yeah, so one of my biggest gripes,
09:29.392 --> 09:32.905
just, just me as an attendee myself, and it's something I
09:33.226 --> 09:37.075
face all the time, is that when you go on an event's page
09:37.155 --> 09:40.748
or perhaps a venue's website, is there's no dedicated page
09:40.780 --> 09:44.151
for accessibility. Accessibility. So yeah, I might
09:44.651 --> 09:46.591
know that I want to go to this event, but I don't know if it's
09:46.639 --> 09:50.219
going to be accessible. And then you have to contact someone,
09:50.412 --> 09:53.221
hope they get back to you, hope they get back to you in time.
09:54.249 --> 09:57.556
You're putting a lot of burden on the attendee when we want to make
09:58.056 --> 10:01.023
it a really frictionless process for everybody.
10:01.312 --> 10:03.736
I'm really pleased that you've raised that because it was actually in my mind a
10:04.236 --> 10:07.669
few minutes ago to ask about where the accessibility journey begins for
10:08.169 --> 10:11.325
an attendee. And it's okay having an
10:11.438 --> 10:14.692
all-singing, all-dancing venue that maybe ticks a lot of good boxes and you've done
10:14.708 --> 10:17.947
that investment, but based on what Shani's just said, Amy,
10:18.572 --> 10:21.907
if you're not communicating that to attendees before
10:21.939 --> 10:25.674
they even come to the venue, your on-site investment is almost irrelevant.
10:25.722 --> 10:29.185
So that accessibility journey has to start with the— with what
10:29.233 --> 10:31.574
you can put out as a venue as well in advance, I guess. Yeah,
10:31.782 --> 10:35.245
absolutely. It needs to start at inquiry stage or even before
10:35.745 --> 10:38.918
you've had the inquiry. You need to be telling people you can't assume that people
10:39.418 --> 10:42.224
just know what you've got, and as I said, every venue is at a different
10:42.240 --> 10:45.965
stage, so that can vary. So I mean, from the report,
10:45.981 --> 10:49.929
there was a stat that 78% of event planners weren't confident
10:49.994 --> 10:53.445
in knowing their disabled attendees' needs, so I think there's a
10:53.945 --> 10:57.008
real opportunity there for venues to help and be that
10:57.508 -->
11:01.054
starting point, you know, this is what we do, include that information in your proposals,
11:01.166 --> 11:04.617
on your website, and give them that starting point that they can go out
11:05.117 --> 11:08.788
to their delegates with. I've said this a few times on the podcast that,
11:09.429 --> 11:13.294
you know, when we look at event organizers, some event
11:13.342 --> 11:16.662
organizers and agencies may organize multiple events every year,
11:17.046 --> 11:20.478
but a lot of events, particularly in sort of business sectors and industry,
11:20.879 --> 11:24.327
there might be annual events, annual conventions, annual conferences, a trade
11:24.827 --> 11:27.694
show. So they might have that experience once a year of organizing the event,
11:27.791 --> 11:30.805
whereas as a venue, venues are doing this day in,
11:30.918 --> 11:34.111
day out. It's their bread and butter, and Do you feel, I don't know if
11:34.127 --> 11:38.607
this is maybe a question for you, Sharni, that maybe event organizers don't
11:38.944 --> 11:42.316
access the expertise of their venues as much as they could be
11:42.816 --> 11:46.298
doing if they are working with a good venue? Potentially, but I think each
11:46.410 --> 11:50.087
party has a responsibility, but I do see it as a bit
11:50.587 --> 11:54.374
of a push-pull relationship. So I'm
11:54.874 --> 11:58.885
sure Amy can speak to this, but if I was approaching
11:58.949 --> 12:02.635
a venue and I didn't talk about accessibility, I would hope that
12:03.135 --> 12:06.193
the venue would encourage me as the client to think about it
12:06.305 --> 12:10.119
and to talk about it, or vice versa. I know,
12:10.456 --> 12:14.527
you know, some venues will only get certain business because
12:14.559 --> 12:18.982
they are an accessible venue or because they've done so much work to
12:19.482 --> 12:23.197
show that they value disabled people that certain events will always go
12:23.697 --> 12:27.268
to those types of venues. So it's been pushed from the client's perspective.
12:27.604 --> 12:30.985
Yeah. And Also, we must talk about the fact
12:31.485 --> 12:35.408
that there are so many different laws and guidelines
12:36.193 --> 12:39.718
that say that, you know, whether you're a
12:39.959 --> 12:44.141
public venue, whether you're an event organizer,
12:44.526 --> 12:47.955
what you do has to be accessible because if you don't, you could be
12:48.455 --> 12:51.897
in breach of different laws. And, you know, that doesn't
12:52.397 --> 12:56.432
just mean physical accessibility, it also now includes digital accessibility
12:56.849 --> 12:59.864
with the introduction of the European Accessibility Act.
13:00.393 --> 13:04.082
So, but this isn't, this isn't a legal podcast
13:04.582 --> 13:07.209
where I'm not going to get into it. But I urge others to go and
13:07.709 --> 13:10.929
look into it because so there is a legal obligation, but there's also the commercial
13:11.522 --> 13:15.034
perspective. As an
industry, people are leaving money
13:15.066 --> 13:18.771
on the table. And it's an industry that, you know,
13:19.701 --> 13:23.565
does need more support that probably could do with more
13:24.065 --> 13:27.850
people coming to their events and venues. But disabled people globally have
13:28.350 --> 13:29.911
a spending power of £18 trillion.
13:31.952 --> 13:35.581
In the UK alone, it's a huge amount of money that's potentially, like you said,
13:35.597 --> 13:38.723
being left on the table. And in the UK alone,
13:38.837 --> 13:42.149
1 in 4 of us are disabled. So,
13:42.456 --> 13:45.941
you know, yes, there's a moral obligation,
13:45.990 --> 13:49.781
but there's absolutely a commercial perspective here. We've touched on it
13:49.798 --> 13:54.033
briefly, but something I wanted to ask you today is, is there still a
13:54.533 --> 13:59.047
kind of, I'm trying to, a muddled view of what accessibility
13:59.304 --> 14:02.844
means and do a lot of venues of any description, not just
14:03.344 --> 14:06.289
event venues but, you know, high street shops, any public area,
14:06.769 --> 14:09.926
is there still a muddled view that accessibility is giving
14:09.974 --> 14:13.082
somebody physical access? So ramps for wheelchair
14:13.582 --> 14:17.151
users, handrails in toilets, you know, are we still guilty
14:17.343 --> 14:21.412
of thinking that accessibility are physical requirements and not understanding really
14:21.428 --> 14:24.810
what accessibility means in 2026? Yeah, do you want to go first?
14:24.954 --> 14:27.841
Yeah, I think so. There's a lot of uncertainty, and I think that came out
14:28.341 --> 14:32.139
of the report as well. So I think, you know, venues,
14:32.187 --> 14:35.748
as I said, can help by giving this information, using examples as well
14:35.860 --> 14:39.388
of things that their clients have done. We had a conference
14:39.888 --> 14:44.007
called SQLBits, which is Europe's largest data conference, and their organizers
14:44.601 --> 14:49.107
really wanted to make everything as inclusive as possible. So they would project
14:49.607 --> 14:52.940
some of the breakout rooms onto partition walls instead of everybody sat
14:53.440 --> 14:56.858
in a theater style. They could sit on beanbags, the lights were lower, they could
14:57.358 --> 15:01.066
tune into that as well. They'd have snacks everywhere for
15:01.114 --> 15:04.888
people and lunch boxes as well, so people could take that and
15:05.388 --> 15:07.699
they didn't have to eat in a crowded space. They could eat wherever they wanted
15:08.199 --> 15:11.714
in the venue. And something that I've heard you say many times is what's good
15:12.214 --> 15:15.183
for disabled people is good for everybody. Yeah. And that is just so true.
15:15.408 --> 15:18.797
Like, I've been at many conferences and used the quiet rooms to just go
15:18.941 --> 15:22.152
in and reset. And go back out, you know, with food,
15:22.168 --> 15:25.844
taking it away and having that opportunity not to be in a crowded
15:26.344 --> 15:29.392
space. So you're so right when you say that, and I think that's really stuck
15:29.892 --> 15:33.485
with me. Yeah, please, please expand that because I've not come
15:33.985 --> 15:39.280
across that before. Okay, yeah, so to give some context,
15:39.906 --> 15:43.646
wheelchair users are actually a minority in the disability community
15:44.224 --> 15:48.141
because 70 to 80% of disabled people have
15:48.173 --> 15:51.352
non-visible health conditions and impairments.
15:52.027 --> 15:55.559
But I think the way in which as a society we
15:56.059 --> 15:59.429
view disability is not that great.
15:59.589 --> 16:03.186
If you just look at what comes out in the media,
16:03.892 --> 16:07.891
the government, the narrative's not brilliant at the moment.
16:08.404 --> 16:11.985
We're quite scapegoated for a lot of things happening politically.
16:13.270 --> 16:17.869
You know, a lot of people may think that the disability
16:17.933 --> 16:21.475
community are a bit work-shy, or just if you read the
16:21.975 --> 16:26.171
headlines. Of course, none of that's true. Um, so if
16:26.203 --> 16:29.504
that's all you— if that's all you're exposed to about a
16:30.004 --> 16:33.944
certain community, you are going to have certain assumptions
16:34.136 --> 16:37.662
and bias. Like, we all have bias, right? So yes,
16:38.143 --> 16:41.877
coming back to the question, I think there is a big— there are big assumptions
16:41.973 --> 16:45.213
made. But as Amy mentioned,
16:45.663 --> 16:49.660
accessibility benefits everybody, and many of us don't understand
16:49.917 --> 16:52.823
that so many of the things that we use today,
16:53.289 --> 16:56.436
everyday things, objects like an electric
16:56.936 --> 17:00.578
toothbrush, that was originally designed for a disabled person,
17:01.252 --> 17:03.885
but because it benefits so many other people,
17:04.768 --> 17:08.123
everybody else uses it too. And it's not sold to you as, oh, this is
17:08.220 --> 17:11.783
for disabled people, but So many things like that exist.
17:11.928 --> 17:15.555
Um, uh, captions, they were created for
17:15.619 --> 17:19.006
deaf people, but they also help so many other people as well.
17:19.086 --> 17:23.114
If you're, uh, dyslexic, if, if you're in a noisy environment,
17:23.243 --> 17:27.015
you're watching something on silent. Um, a bendable
17:27.515 --> 17:30.947
straw that was created for a disabled person to have a drink.
17:31.669 --> 17:34.687
Everybody likes using a straw, you know. There's so many things,
17:35.200 --> 17:38.327
and it's when I think about it as well, you don't— I guess you don't
17:38.827 --> 17:42.110
necessarily have to have a diagnosed condition or tick a box.
17:42.414 --> 17:45.636
You never know what day somebody is having. So when we talk
17:46.136 --> 17:49.628
about, you know, maybe lunch boxes that you could pick up and go to a
17:50.128 --> 17:55.174
quiet space instead, it doesn't
necessarily have to be for somebody who has a neurodiverse
17:55.639 --> 17:58.653
box that's ticked or a condition. It could be somebody who's just having a really
17:58.685 --> 18:01.955
bad day, stuff going off in their personal life, and they just— they've
18:01.971 --> 18:04.808
got to go to this event for work, but maybe they just want a quiet
18:04.856 --> 18:08.510
space for lunch. So it's— I guess of it is not just
18:09.010 --> 18:12.690
about giving people who have a condition or a box that's ticked
18:13.190 --> 18:17.250
that opportunity. Like you said, it's opening the door for everybody to potentially access these
18:17.750 --> 18:21.290
type of facilities, and it's getting younger people into events as well
18:21.790 --> 18:25.150
because, you know, events can be really overwhelming. Going in, somebody may have not attended
18:25.650 --> 18:29.270
an event before and they're thinking, whoa, there's all of these people here. So they've
18:29.770 --> 18:32.430
got that information in advance. Actually, if I feel a bit overwhelmed, this is where
18:32.930 --> 18:35.433
I can go, or even this is I can talk to these are the measures
18:35.465 --> 18:39.200
in place instead of just feeling a bit stuck. So, you know, we want
18:39.409 --> 18:42.856
to be as inclusive as possible, and I think organisers do as well.
18:42.936 --> 18:47.056
It's just working with lots of different partners
18:47.408 --> 18:50.855
on larger events, certainly, to make that happen. I've underlined in
18:51.355 --> 18:54.687
my notes the word budgets because, you know,
18:54.943 --> 18:58.566
whether we like it or not, there is still— there are still conversations at every
18:59.066 --> 19:02.403
event within every event organizing team about the budgets,
19:02.564 --> 19:06.626
you know, oh, can we afford to do this? And questions
19:06.658 --> 19:10.416
being asked at registration about, do you have any specific requirements,
19:10.432 --> 19:13.515
please get in touch with us. Are we still at a point where you feel
19:13.564 --> 19:17.819
that there is still very much an obligation on the attendee to have to contact
19:18.319 --> 19:21.785
the organizer or the venue to say, I have a requirement, can you cater
19:21.834 --> 19:25.142
for it? You know, are we making progress in that respect?
19:25.206 --> 19:28.702
But I look at things like captions, for example,
19:28.975 --> 19:32.596
at conferences, you know, they're often still deployed
19:32.660 --> 19:36.346
because there has been a requirement made to the organizer by an attendee
19:36.846 --> 19:39.855
saying, I need this, rather than it being put in as necessary.
19:39.935 --> 19:43.380
Where do we stand with that side of it? I think it depends on the
19:43.880 --> 19:47.803
nature of event and how well the event organizers understand
19:48.303 --> 19:52.049
their audience. So there will be some organizers that know
19:52.274 --> 19:55.494
they will absolutely have certain people in the audience who will have certain
19:55.994 --> 19:59.580
requirements. So let's say, well, I'm organizing my event now,
19:59.740 --> 20:03.120
the Accessible Event Show, so we know that there will be people
20:03.168 --> 20:06.196
in the audience who will need British Sign Language interpreters,
20:06.549 --> 20:10.474
that will need sign language, and for those people joining the
20:10.974 --> 20:14.896
live stream online, they have the option to request different language translations
20:15.396 --> 20:19.094
as well. So we have already booked that, we aren't waiting
20:19.110 --> 20:23.019
for people to tell us that they need it because we're very certain that
20:23.035 --> 20:25.535
those requirements are going to be needed,
20:26.160 --> 20:28.547
um, because we understand our audience.
20:28.996 --> 20:32.425
So I think, but I think
20:32.925 --> 20:36.479
what we do need to change is what needs to be standard. Like captions have
20:36.575 --> 20:40.036
to be a standard. It's so accessible now. Yeah,
20:40.261 --> 20:43.802
it is. And low cost. It is. Yeah. You know,
20:43.882 --> 20:47.151
you can have live human-generated captions, but they're,
20:47.327 --> 20:51.496
you know, AI captions are getting better all the time. My personal preference
20:51.996 --> 20:54.914
is always human, but as you say, it comes down to budget.
20:55.332 --> 20:58.927
And I think everybody should have a line item for accessibility
20:59.184 --> 21:03.036
in their overall event budget, because if
21:03.536 --> 21:06.823
you don't, I think it's a bit of a failure on your part, because what
21:07.323 --> 21:11.253
you're essentially saying is, I don't expect there to be any accessibility
21:11.753 --> 21:15.843
requests. And how can that be true if 1 in 4 of us
21:16.036 --> 21:19.313
are disabled. Absolutely. And I said,
21:19.907 --> 21:23.376
somebody asked me years ago at an event I was speaking at, a long,
21:23.505 --> 21:27.295
long time ago, and it was when event apps were really coming into the marketplace
21:27.795 --> 21:30.106
and every event, oh, we need an app. And somebody actually asked a question and
21:30.606 --> 21:33.446
said, well, you know, I don't have a huge amount of budget at the moment.
21:34.105 --> 21:37.478
I've got a choice between developing an app that's compatible with
21:37.978 --> 21:41.332
iOS on iPhone or with Android. Which one do you
21:41.832 --> 21:43.652
think I should go with? And I said, well,
21:44.978 --> 21:48.261
it's like saying, well, I'm only going to do an event and say only men
21:48.519 --> 21:51.591
can register, only women can register, or only this type of person can register.
21:51.850 --> 21:55.675
You're effectively making a choice then to alienate 50% of your
21:55.723 --> 21:59.306
audience, essentially. And I guess
21:59.370 --> 22:02.980
accessibility has some parallels to that kind of analogy that, you know,
22:03.500 --> 22:06.864
if you're not making those decisions proactively and you're waiting for people
to
22:06.880 --> 22:10.581
come to you, they could have been put off already. By knowing
22:10.677 --> 22:13.514
that it's not going to be accessible. I dare say there'll be people out there,
22:13.562 --> 22:16.478
quite rightly, who say, well, why should it have to fall on me?
22:16.766 --> 22:20.067
Why is it my obligation to contact to do that? I'm just going to not
22:20.567 --> 22:22.759
go. And it goes back to what you were saying about the amount of money
22:22.871 --> 22:26.236
that is potentially being missed out on by people who you will never know.
22:26.621 --> 22:29.329
Yeah, you never know the people who decided not to come to your event because,
22:29.585 --> 22:32.678
yeah, you put a barrier there in the first place. And as disabled people,
22:32.966 --> 22:36.395
like, we have to do this for everything, for every part of our
22:36.507 --> 22:40.040
lives. So when it comes to an event that is, let's say
22:40.540 --> 22:43.765
it's optional, let's say it's not a work event, you don't bother
22:44.262 --> 22:48.020
because you're so exhausted from doing it in every other
22:48.052 --> 22:52.194
part of your life. And I recently shared a post on LinkedIn,
22:52.853 --> 22:55.759
um, saying that I fall in this cycle of,
22:55.984 --> 22:58.697
obviously I love events, I want to go to them,
22:59.516 --> 23:03.885
uh, I book it, you know, share my accessibility
23:04.385 --> 23:07.452
requirements, perhaps it didn't go so well, then I stopped going,
23:08.111 --> 23:10.586
I get annoyed and I think they don't value me, I'm not going to give
23:10.602 --> 23:13.928
them my money, then I miss it and then I do
23:14.428 --> 23:18.138
it again and then I fall into this cycle and it's not nice.
23:18.411 --> 23:22.493
No, I should be able to enjoy events too. Absolutely. Are you,
23:23.087 --> 23:26.349
as a venue, Amy, working on this report and
23:26.365 --> 23:30.284
seeing some of this research, I've, in my experience
23:30.784 --> 23:34.378
of walking around here just this morning and yesterday afternoon as well, I've clocked
23:34.878 --> 23:38.344
things that clearly, you know, decisions in terms of the infrastructure and
23:38.393 --> 23:41.829
the layout and the building of the venue, but have you
23:41.861 --> 23:46.100
been able to actually enhance further what you can offer here through
23:46.116 --> 23:49.295
what you've learned in the report? Yeah, absolutely, and it's looking beyond
23:49.391 --> 23:53.004
the sort of physical venue, it's looking at
23:53.486 --> 23:56.935
that information in advance. So, you know, we've improved our
23:56.951 --> 24:00.481
accessibility webpage, but we're also looking at doing videos now.
24:00.721 --> 24:04.138
So videos from the train station, from the bus stop, and having
24:04.154 --> 24:07.187
a walk around to the venue to actually show those things.
24:07.299 --> 24:11.278
So this is where you register, this is the quiet room, the multi-faith room,
24:11.390 --> 24:14.887
this is where you go for lunch. So it's, it's all of these different things
24:14.919 --> 24:18.272
just to make people feel more confident in advance, you know, the car
24:18.772 --> 24:22.180
park and these are where the disabled spaces are, but this is where the lift
24:22.680 --> 24:25.940
is, so, and these are the dimensions of the lift as well. So it's just
24:26.440 --> 24:29.600
making sure you put all of that information out. So that is something that we're
24:30.100 --> 24:33.060
working on now, and to have on our website and to be able to share
24:33.560 --> 24:35.679
with our audiences. And that strikes me as something that's a quick and easy win
24:36.179 --> 24:39.500
for a venue, because if you go back, you know, 20, 25 years, if you
24:40.000 --> 24:42.870
wanted to make a video of how to get into the car park,
24:43.380 --> 24:47.000
where to park, where the lift is, etc., you'd have to get a company
24:47.500 --> 24:49.460
in with cameras and filming, then you'd have to go off and edit and all
24:49.960 --> 24:52.754
the rest of it. Somebody in a team now in a venue could go with
24:53.254 --> 24:57.242
their phone and walk that route and do like a time-lapse video or something
24:57.742 --> 25:01.906
of that. It's so easy to generate really usable content that could benefit people,
25:02.211 --> 25:05.400
and if you think about, you know, people who suffer from dyslexia, for example,
25:06.458 --> 25:09.664
reading directions and written instructions on how to do
25:10.164 --> 25:13.767
something could be a real struggle for them, whereas a 30-second video could
25:13.895 --> 25:17.117
convert— everyone learns differently, so there are quite a lot of
25:17.617 --> 25:21.125
things that we can do actually if we break it down. And you can never
25:21.625 --> 25:25.343
give someone too much information. It's better to give too much than
25:25.359 --> 25:28.696
too little. And, you know, with, with things
25:29.196 --> 25:33.187
like videos, they're brilliant tools, but again, we have to make sure they're accessible.
25:33.556 --> 25:36.972
There must be captions on there. I would say go further and,
25:37.582 --> 25:41.415
uh, put sign language on there, and if you can, audio describe them
25:41.915 --> 25:45.473
as well, because then you've hit the most amount of accessibility
25:45.570 --> 25:49.340
just in one piece of evergreen content. That you, unless your event,
25:49.437 --> 25:53.049
like a venue massively changes, which I'm sure it's not very likely
25:53.549 --> 25:56.902
to, then that's, you know, a piece of content that you can use at
25:56.982 --> 26:00.530
every event that can stay on your website. You can pop
26:00.594 --> 26:04.511
on socials as well. So many ways to repurpose this content too.
26:04.848 --> 26:08.701
And for the first time in these podcasts that we're recording here today, I'm gonna
26:09.201 --> 26:12.618
hit the AI buzzer and say that everything that you've described there in terms of
26:13.118 -->
26:16.487
adding and how to enhance a video, with some of the AI tools that we've
26:16.987 --> 26:20.178
got available to us nowadays, those tasks are actually very straightforward,
26:20.419 --> 26:23.372
much more so than they would have been a decade ago, aren't they? To add
26:23.872 --> 26:27.641
the captions, the audio descriptions, we've got tools available to us that actually can speed
26:28.141 --> 26:31.140
up the process and enhance it a little bit further. I dare say you're probably
26:31.172 --> 26:35.008
using, you know, some of those tools on a day-to-day basis, Amy. Yeah,
26:35.088 --> 26:38.876
absolutely, and I mean, we've got a great marketing team in-house who are providing
26:39.376 --> 26:42.810
all of these assets for us, so So we're very lucky there. But yeah,
26:43.310 --> 26:46.150
I think it's just building confidence in the venue. So I think, you know,
26:46.650 --> 26:49.410
back to the report saying venues are saying they're doing these things, but actually that's
26:49.910 --> 26:53.170
not what delegates are experiencing. And that starts from before you've actually
26:53.670 --> 26:57.510
set foot in the venue, before you've kind of signed up to go.
26:57.830 --> 27:01.410
That information needs to be available. Absolutely. And I mean,
27:01.910 --> 27:05.470
that's a good final thought from a venue perspective to sort of start
27:05.970 --> 27:09.090
wrapping up today. But Shani, I was going to come to you finally just to
27:09.590 --> 27:13.423
ask, you know, in terms of when you reflect on the research that's been conducted,
27:13.487 --> 27:16.084
the statistics that you've referenced in the podcast today,
27:16.854 --> 27:20.012
is this now going to be an ongoing process? Are you going to revisit this
27:20.140 --> 27:23.410
and look to go, you know, on an annual basis back to these venues and
27:23.910 --> 27:26.408
organizers? What's the plan for the report going forward?
27:26.776 --> 27:29.790
Yeah, just to give context of the report,
27:30.656 --> 27:34.519
it's a landmark report. We've never really had an understanding
27:35.032 --> 27:38.510
of accessibility in the industry like this ever before,
27:38.975 --> 27:42.470
and for me personally, as someone who's worked in the industry, loves the going
27:42.502 --> 27:46.259
to events, I found it extremely validating because
27:46.613 --> 27:50.241
sometimes you think these things are only happening to you as an individual, but now
27:50.354 --> 27:54.432
we get to see it from an industry and a community perspective.
27:54.801 --> 27:58.253
So there are plans to, to go back out there
27:58.639 --> 28:02.171
and to see if there has been any improvement, because within the report there
28:02.671 --> 28:06.265
are lots of recommendations for people as well. You know, these are all free to
28:06.329 --> 28:10.035
access. And if I may, I just
28:10.535 --> 28:13.850
wanted to urge people to redefine
28:13.882 --> 28:17.858
what their measure of success is when
it comes to events. We often
28:19.253 --> 28:22.699
look at success in different ways. It could be X amount of people,
28:22.859 --> 28:26.354
it could be X amount of revenue, but actually,
28:27.043 --> 28:30.778
is your event accessible? I think that should be part of a success
28:30.971 --> 28:33.263
factor as well. Absolutely.
28:34.305 --> 28:37.270
Could I just ask, if people are listening or watching this today and they want
28:37.770 --> 28:39.691
to find out more, they want to— they've listened to this and they think,
28:39.771 --> 28:42.935
actually, I'd like to do some of my own research. Can we give them a
28:42.983 --> 28:45.200
few pointers in the right direction? Amy,
28:45.714 --> 28:48.010
I'll come to you first of all. Is there anything that you can sort of
28:48.043 --> 28:51.110
point the podcast followers in the right direction of relevant to
28:51.610 --> 28:55.078
today's conversation? Yeah, absolutely. Well, the Access All Areas report, of course, so that
28:55.190 --> 28:58.708
can be downloaded on the ICC Wales website, and that
28:58.724 --> 29:02.546
gives just a huge array of opportunities
29:02.659 --> 29:06.337
to venues to see what they can implement, and some are quick,
29:06.369 --> 29:08.778
easy fixes, and some are you know,
29:09.950 --> 29:13.305
will cost or, you know, will take a little bit longer, but you can
29:13.722 --> 29:16.836
create your journey from the recommendations in the reports.
29:17.109 --> 29:21.234
Excellent. And Sharni, any advice for people tuning
29:21.282 --> 29:24.813
in today? Where can they go? What good resources
29:25.313 --> 29:29.147
are out there for them? Yeah, so definitely the report, and I would say work
29:29.647 --> 29:33.448
with experts in accessibility as well. You'll only get so far on
29:33.480 --> 29:37.332
your own, but like we do with all the other things that we you know,
29:37.397 --> 29:41.600
all the other areas, I don't know, like health and safety or building management,
29:41.664 --> 29:45.241
we work with experts in those spaces. So if you want
29:45.578 --> 29:49.861
to do it and get it right, work with experts. I'm one.
29:50.310 --> 29:53.471
And also please look up the Accessible Event Show.
29:54.176 --> 29:57.690
We believe as the co-founders it's the world's
29:57.770 --> 30:01.395
only event that teaches event professionals how to make their
30:01.895 --> 30:05.486
events accessible. And it's going to be taking place
30:05.550 --> 30:08.326
on the 29th of October in Wembley in London.
30:08.791 --> 30:14.310
It's free to attend in person and online, so it's just theaccessibleeventshow.co.uk.
30:14.614 --> 30:18.320
Fabulous, and we very much appreciate both of you taking the time to talk
30:18.820 --> 30:21.818
about this subject and join us on the podcast today. We've been joined by Dr.
30:21.866 --> 30:25.379
Shani Danda and Amy Phillips, the ICC Wales Sales Director, on the
30:25.879 --> 30:29.277
podcast today talking about closing the accessibility gap in
30:29.470 --> 30:32.920
events. Thank you very much for tuning in today. Thanks very much again
30:33.420 --> 30:37.140
to our hosts for today's podcast, the ICC Wales. Please do make sure that
30:37.640 --> 30:41.020
if you've listened to today's podcast on your podcast platform that you go over to
30:42.030 --> 30:45.340
eventindustrynews.com where you can check out video versions of all of the podcasts as well
30:45.840 --> 30:49.040
as all the news features, special supplements that's on the website, as well as the
30:49.540 --> 30:52.140
supplier directory. If you work in the events industry and you're looking for a product,
30:52.640 --> 30:56.080
service, or supplier, chances are you'll find it on the A to Z supplier directory
30:56.580 --> 31:00.080
on eventindustrynews.com. Thanks very much again to my guests today. Thanks very
31:00.580 --> 31:03.350
much to our hosts for looking after us, and we'll see you on the next
31:03.850 --> 31:05.447
edition of the Event Industry News Podcast.