WEBVTT 00:00:10.400 --> 00:00:14.000 Accessibility is a process, its's not an end result. 00:00:14.200 --> 00:00:17.000 So I think that's the biggest mistake. 00:00:17.000 --> 00:00:20.600 If you think about testing, for example, companies spend 00:00:20.600 --> 00:00:23.700 tons of money testing the website, but that's the end result. 00:00:23.700 --> 00:00:24.700 That's what you're testing. 00:00:25.000 --> 00:00:26.400 But if you embed accessibility in 00:00:26.400 --> 00:00:28.600 the process, then it's, 00:00:28.800 --> 00:00:30.900 so when you think of, think 00:00:30.900 --> 00:00:34.500 about PDF remediations, if that's the end result, you're going to 00:00:34.500 --> 00:00:41.300 invest millions and millions of euros to test or to remediate PDFs. 00:00:41.400 --> 00:00:45.600 But if you embed training, if you really embed accessibility in 00:00:45.600 --> 00:00:50.500 different roles within, so everybody can to acknowledge 00:00:50.500 --> 00:00:55.800 the role in making better environments in the process, then we have 00:00:55.800 --> 00:00:58.700 sustainable accessibility in the long run. 00:01:03.100 --> 00:01:06.400 So that's the first thing, is to have the discussions and make 00:01:06.400 --> 00:01:11.800 sure that you're aware of all the obstacles and gaps 00:01:11.800 --> 00:01:12.600 that could be in front of you. 00:01:13.400 --> 00:01:14.600 And I think, you know, 00:01:14.600 --> 00:01:18.100 taking that time to have that strategic discussion 00:01:18.100 --> 00:01:19.600 with the right people is crucial, 00:01:20.200 --> 00:01:21.600 hands down the first thing that needs to be done 00:01:21.600 --> 00:01:24.200 because you don't know what you don't know. 00:01:29.000 --> 00:01:33.000 In a sense, you know, the EA unites accessibility laws across, 00:01:33.100 --> 00:01:38.600 you know, all the EU countries, kind of trying to spread the word, 00:01:38.600 --> 00:01:41.600 you know, not having somewhat such fragmented, you know, 00:01:42.200 --> 00:01:44.200 so it's trying to unite, which I think is good. 00:01:48.500 --> 00:01:51.900 So, from my experience, just to highlight that the UN, 00:01:51.900 --> 00:01:58.400 the EU standard is, from my perspective and in the world that 00:01:58.400 --> 00:02:01.600 I do, is seen as a good, the best practice, in the sense that 00:02:01.600 --> 00:02:05.200 there's so many countries that are aligned to one single standard. 00:02:05.500 --> 00:02:09.000 So, for instance, I can tell you for a fact that in Africa and 00:02:09.000 --> 00:02:14.700 Kenya, for instance, in South Africa and Mexico, in Chile, 00:02:14.900 --> 00:02:19.400 there's so many countries that are, I don't want to say copy, but 00:02:19.400 --> 00:02:25.200 are using as a base the EU standard to develop their own standards. 00:02:29.400 --> 00:02:31.600 If you do not understand accessibility, 00:02:31.800 --> 00:02:34.000 you won't be able to implement AI. 00:02:34.300 --> 00:02:35.700 Think about ChatGPT. 00:02:35.700 --> 00:02:38.100 I use it because it makes my work 00:02:38.400 --> 00:02:42.900 quicker, but I need to know, what I need to know in 00:02:42.900 --> 00:02:44.200 order to use it correctly. 00:02:48.300 --> 00:02:50.000 The other areas is, you know, not 00:02:50.000 --> 00:02:53.400 just focusing solely on the legal compliance aspect of it. 00:02:53.500 --> 00:02:56.600 You know, not meeting the requirements, but, you know, 00:02:56.600 --> 00:03:00.800 making sure that e organisations have this integrated 00:03:00.900 --> 00:03:06.200 into the DNA in a sense, and that it's important to their business. 00:03:07.400 --> 00:03:11.900 And that's a unique area that, you know, 00:03:11.900 --> 00:03:13.000 it's really the business case. 00:03:13.000 --> 00:03:16.300 And I don't think that we do, 00:03:16.300 --> 00:03:20.000 being G3ict and IAAP, as well as others, do a good job 00:03:20.000 --> 00:03:21.000 of putting that out there. 00:03:22.400 --> 00:03:23.400 You know, we need to do 00:03:23.400 --> 00:03:23.900 a better job, 00:03:23.900 --> 00:03:25.400 i think of showing that 00:03:25.400 --> 00:03:28.200 this is good business and this is the business case behind it. 00:03:33.100 --> 00:03:36.200 And we do believe in the certification that we have. 00:03:36.200 --> 00:03:38.700 We need a procurement certification of some sort, or 00:03:38.700 --> 00:03:39.400 a certificate. 00:03:40.000 --> 00:03:41.400 We need to make sure that we are, 00:03:41.800 --> 00:03:43.800 because that's where a lot of the bleeding is happening- is that 00:03:43.800 --> 00:03:46.700 we're purchasing, you know, hard run software that's not fully accessible. 00:03:47.200 --> 00:03:49.000 A lot of work has to be done in that area. 00:03:49.400 --> 00:03:52.800 So I'm hopeful, 00:03:52.800 --> 00:03:53.800 but it's going to take a village. 00:03:57.800 --> 00:03:59.200 But what I'm really excited about 00:03:59.200 --> 00:04:02.300 is more the quantum computing aspect of it. 00:04:02.700 --> 00:04:04.000 You know, that's going to be, 00:04:04.300 --> 00:04:05.200 i mean, that's just going to 00:04:05.200 --> 00:04:09.200 change things, not only for the disability area, but, you know, 00:04:09.300 --> 00:04:10.700 specifically in the areas of healthcare. 00:04:10.700 --> 00:04:11.600 You know what I mean? 00:04:12.300 --> 00:04:15.600 So now we're going to see it shift in the next 00:04:15.600 --> 00:04:18.600 three to five years, once we figure out, you know, getting the 00:04:18.600 --> 00:04:21.700 cost down and the cooling system, so that, you know, these, 00:04:22.000 --> 00:04:25.200 that things will cool off quicker so the data can be 00:04:25.200 --> 00:04:27.400 utilised much quicker. 00:04:27.400 --> 00:04:28.800 So there's some exciting stuff, 00:04:28.800 --> 00:04:30.600 I think, with quantum computing, that we're going to see.