We're speaking about 1.5 million people in different ages. It could be old people or not old, old ages and old genders. And so it's about the same. So if I were to talk about every place, the statistics are very similar. Also in the U.S. it's very similar.
OK, so we saw that this is not only a problem of Joe and a problem of Beverly, but it's not only pizza. It's pizza and it's a donut, if you're from the States or baguette if you're from France. If you can order a baguette, I don't know. And it's a problem if you want to enter your bank account or if you want to buy tickets for this conference. If you think about it, there was no way to do it without a computer. I mean you just can't do things today without a computer. So when we are not making our services accessible, we're not only losing money because people can't use it, it prevents people from equal opportunities because everything is digital, everything.
So what's the first phase for making things accessible? So if you want to make things accessible, the first thing is that we need to test, to test them for accessibility. And this is something which is, we will go into today and also fixing. And we're going to do a lot of things related to accessibility. And again, I encourage you to ask questions freely. As one of my teachers once said, there are no stupid questions. There are only stupid mentors or something like that. I don't remember the, I mean, feel free. Okay. And, um, it would be very interesting. I hope. So before we start, uh, I'll introduce myself. So I'm a stuff I'm the one, um, with the tongue out, and this is my daughter's star. I have a three kids, sorry. Time of day I married to Netta. I've been to in the industry for more than 12 years in various roles in the uh, uh, I have a blog program on.net. You're welcome to, uh, to enter and to read about things that I find the interesting, I hope they interest you too. Uh, it can be my friends on LinkedIn. And in the, uh, in the past three plus years, I'm the front end tech lead at Aviv where, uh, I'm at eight. And we together. And, um, I don't know, the city is yours. Thank you. So I'm a time. Um, I've been working in software development for over 15 years now. Um, I worked for, um, Several companies, um, sizes from a few dozens to many thousands, uh, mostly on the front end. And for the past year and a half, I've been working with, uh, stuff in advanced, um, which is a very cool company. If I might say so myself that, uh, deals with, uh, developing software for accessibility testing, which is, uh, why we are all here today. And today we're going to talk about. About, um, several interesting things. Um, first we're going to discuss a few of the tools used in the industry for testing accessibility, um, manual testing and automated testing. Um, so we'll discuss a few of those. Uh, then we'll get to a live accessibility testing session where we'll see, um, like a demo app prepared and I'll walk you through, uh, how we go about testing accessibility on that application, find some bugs, fix them, and improve the world just by a tiny little bit. Um, and finally, we'll talk about, um, like the bigger picture, how you maintain accessibility, um, on an ongoing project. Um, best practices we currently use, uh, for making sure your applications stay accessible once you've fixed all your problems, um, as the application gains more functionality and updates. Okay, so, let's start with the tools. Um, first thing is one we are all familiar with. Uh, we've been using it for decades now. Uh, at least I have, uh, it's the keyboard. Um, now the keyboard is again, we're all familiar with it, but it has a special meaning when it comes to accessibility testing. Um, because first thing, um, not all our users or quite a lot of them might not be able to use a common mouse or even just feel less comfortable with it, because of various known disabilities and keyboard is an excellent alternative, but not a common one that's found in very affordable. It's found in every household. And, uh, when you make sure once you make sure that your application is accessible by keyboard, um, you're also in a very good place to make sure it's accessible by other assistive technology, uh, such as the one next on the list, um, screen reader. Um, screen readers. So there are quite a few of those. Um, Some more prominent than others and some work better on some kinds of operating systems, uh, more than others or, uh, like, uh, different kinds of browsers. Uh, we'll take a look later at one example, which is a, uh, problem using which is a Apple's voiceover. And. Uh, finally, after screen reader, we'll talk about, uh, several extensions that we use for testing accessibility. So, um, extensions such as a browser extensions or extensions to your, uh, development environment, your ideas, uh, and it's on. Um, so with that out of the way, um, let's move to some coding.