 Добро първо, всеки. Добре. Добро за да оттежнаме сеси. Надякувам да ви приятелете. Не имаме много време. Почнем. Върх, че ще го говорим? Върх, имам да го даде себе, конечно. Върх, ще го обреждаме са митър на аксистабилити. Върх, ще го подпишам за 4 пилерси. Добро за това сеси е да имаме понякога на аксистабилити върх, което няма да знати, че е да ме е върху за да знатите, за да се е върху за ВЛУ. Върху за мен... Ментото е човесен, тригърът, се е стръска, което е върху за да е работи в QA и които е върху за 8 години. В това пасто, в това сега наминали да е работи в QA domain knowledge lead на FFW, meaning that I am responsible for our quality assurance growth and process in our European entities. When we are talking about the FW we create and scale digital experiences that move enterprise and people forward. What this means is basically that we've delivered more than 2,000 almost exclusively Drupal solutions to more than 500 clients клиents and they were healing enough to tailor the things basically every world possible. So let's start with accessibility. First, we have to start with accessibility. So accessibility, according to Wikipedia, is a design of product devices, services, vehicles, or environments, so as to be usable by people with disabilities. The concept of accessible design and practice for accessible development ensures both direct and indirect Не matter да имате директата. Дорно. Л Hidden Advice here is that accessibility is for people with disabilities. The Time Diss spans disability ways. Disability is true, but not only for people with disability. It makes sense to have accessible design. And now we are going to make some midst. In the following slides I will share with you some quotes based from my experience in the past years about midst accessibility. Just a warning the next slide contains a video that might be ...at people with eating fillbacks. So myth number one, accessibility in web is for blind or low vision users. This is the most common misconception that accessibility is for blind and low vision users. While this is true the spectrum of the disabilities is much broader. we have to cover motor disabilities, cognitive disabilities, hearing disabilities, and here in the example we have a person who is using moustic to navigate and the girl on the bottom is a deaf person who requires subtitles to see the video. And now I'll play the video that I was talking about. This video is from a Pokémon and it's known as the Pokémon shock from Japan и си да го са от 700 къс, докато си изликащите лътвите. Така, много шторм, ето възборът е не за българен или малки виждане. Метната номер два. Възборът е за пълни с дизабилистите това. Как и мето, възборът е възборът за пълни с дизабилистите. If you have to push a stroller on staircase, you can't, right? If you have to watch a video in an extremely noisy environment you can't, you need subtitles or transcript. When you are looking at your phone in the guide,1 if you do pretty often, it's hard to read, right? So, what this means is that if you have great color contrast at the end of the day, си тук по-почоваме да се бържи на телефон, възбирая екифицията, така няма дизабилите, и ситуационални лимитани, че да ви да бърbowи отającто, във товато wenn не има вячески дизабилити сааа right now. Така, както саа donими на дизабилите са саааао, е Бължавата. Във във NextMed, няма дизабилите за на judiciary Para. here I have recorded the video from a website, and you can see that it first looks good both in color and in black and white. Meaning that it is perceivable from people with low vision as well. But it is not only that. A huge part of it is actually under the hood. It is not something that we can see right here. It´s in the HTML, so.. for the end-user, making a website accessible is not making it look bad, it´s making it look either equally good but making it more usable in more conditions. So the next meet. Accessibility is too expensive in time-consuming. this can be true if you started thinking about accessibility before your goal live date. And this is something that happens eventually but if you are planning for accessibility, If you have accessibility in mind from the planning phase and in each iteration you do accessibility testing from the design implementation and everything, it does not increase the cost of accessibility повиннато поittoто дворо година и от това не ете тъmmckt есть and personnel . Depending in your region' or your country, different law supplies nevertheless more and more laws are getting taking place right now, that are enforcing accessibility. Meaning that even thought today you might not be obliged to by a law, it does mean that in a year you don't have to ... your site should not be accessible. But even if you don't have to be accessible by law, why you should do it? Well first, we have the ethical responsibility. Internet is the place, that solves a lot of the problems. If you are a person with disability and you have to do something by groceries, it might take hours to go to actual physical store and purchase them. Но, ако ви можете да го опорим отлайн и да има има къде на ваша двор, в�оя в мурата минути, това са ими стане много върху, това са е да се емпроводите лифта. И това е да дали, както са фен от някакой, или е мето, както е. Хочете да знаме Мегазин в Брео Афобет. Тето ме да се найдете върху и да първаме вашата информация, да има и хобито да живе нормално. ہодаUR is number one. getsominous reach, Emergencyfolded websites are ranked higher by the search engines. So, when your site is accessible, you actually reach a broader audience and by doing so you have more customer. Which makes the business decision of having an accessible website to investing in it easier from от стейхолдърът да купи. И, във това, но не е лист, като има това позитивна брантът. Това е на дължина за възнавални възнати, които е възнавални. Това не е на дължина за възнавални възнавални, които не обтежда от товато. Така, това е му обтежда на мит, и са е възнавални възнати. Тук ще го говорим овъзнати на компленти. Минус за компленти е структирено в WCAG за W3C, които чертва и обие контингт в агсистабилити гайлилинаво наържената на각о на свежата. В разърживане на три категории. Левъв 1, двойната на върхата, върхата е нинистата, и върхата е нинистата. В всесите страни, върхата е стандартната за агсистабилити върхата по-почивано на двойната за части избръжда. and AAA is needed only for government websites and websites that are expected to have a big amount of people with disabilities visiting them. Inside WCAG, the four principal lives, as I called them before, the four pillars of accessibility. They are perceivable, operable, understandable and robust. You can remember them by the word they create, the poor. So now we'll go through each and one of those principles and I'll try to explain their concept so you'll be able to understand accessibility without knowing accessibility. First we have perceivable. Perceivable stands for the biological way, we gather information, sight, sound, smell and taste and touch. For the sake of web, we skip the smelling and tasting and we leave the rest. So for easier understanding, we can think that we lack one of the other senses. So in example, if you are not able to see, you should be able to hear everything. So if you have a video, in example, or an image or something like that, you should be able to hear what this video is about or what this image has in it. If you're a deaf person, this means that you should be able to see everything. So if there is some audio or some video, there should be a transcript describing everything that is taking place right now. So in perceivable, basically you should think of how people are perceiving information and provides different ways, at least two ways from them to obtain that information. Then we have operable. So in perceivable, we are gathering information, in operable, we are inputting information. So here we should be able to use every website with every technology possible. All types of pointers, voice recognition, keyboard only and everything that you can imagine. So I'll give you a couple of examples for operable. The first one is about the smallest thing in the world, which is the close up button. In the new WCG 2.2, there is a success criteria that says that it should be no less than 24 by 24 pixels, if we want for our website to be accessible. So you can imagine the person from the first slides who is using mouse sticks to find and close this button, it would be a nightmare. And also being that small for a person with low vision to actually find it, again a complete nightmare. Now we have the focus. If you are operating the website using the top button, the tabulation, you should be able to see where you are currently at, because otherwise you would not know which element has the focus or when you click enter what will happen. So it's simple as that. This blue outline is what the focus is. Then we have the time. Again, in order to operate a website, people with disabilities, elderly people, they require more time. So we should not time box some functionality. We should not ask a person to make timed keystrokes in order to achieve something. But we should just leave them work with their website at their own pace. Next one, we have understandable. Understandable basically means is that we should not reinvent the wheel. There are good practices around the world that most of the big sites are following and we should implement them. Consistency and predictability. Those two words are really strong and they work really well. If you open a website for a first time, you'll be able to quickly navigate through it. If it's done in the proper way, it will be easier for you to understand it. This is the way that we should build our websites in an understandable way. I'll give you a couple more examples about understandable. First one is the language. I'll be honest with you. This gift here might have been omled from us. But after the session before that, I've removed it. About the language. It's one line in the HTML code to say what's your website language. If you don't have it, the website will be read in the assistive technology, default, fallback language. And if they don't match, this website will become unusable for that user. Also, if you're expecting that a lot of people will be using your website who are not proficient in that language, you might skip the terminology, the high level Shakespeare wording and stuff like that. You can keep it simple so everyone can understand everything. One of my favorites is the error prevention and error correction. I'm not sure if you can actually see it. The error message states, this value should not be no. So here we have multiple issues. First one is what is this? And here we can input some JavaScript jokes, but we'll skip that. So we're referring to this field, which is marked in red. Okay, but if the person who is using the website is colorblind, they would not know that this field is actually marked in red. So instead of this field, we should say the name of the field. Then we have, it should not be no. Well, no is kind of a technical term. Maybe we should use the word empty. Then we have the category with the red asterisk, which is the symbol of mandatory, right? We know it, but not everyone knows the symbols. So if we simply use a help text that says this field is mandatory, we will be doing an error prevention, and this would not have happened. And the last one from our four pillars is robust. Robust basically means semantically correct HTML. Here I have listed most of the things that you can consider. Have a meaningful title, use landmarks, heading should be used as such, et cetera, et cetera. Of course, together with the correct HTML, we should use area attributes. So we cannot test every device. So robust means that we should provide similar experience on all of the devices, all readers, all browsers, everything. But we cannot test them. I've been working as a QA, as I've mentioned, for more than eight years. I know how time consuming is cross device testing. So what we can do is we can try to make sure that we've built everything the best way possible, following the good practices, using static code analysis for the HTML, et cetera, et cetera. So at the end of the day, we should expect if we've done everything the right way, that it will be working for every browser and every device. And if it is not working, this means that it's not working for one device. This means that it's probably the problem with the device and not with us. I mean, if it's working for everyone else. And for conclusion, I hope that you've gathered enough information about accessibility. It's important for everyone, not just people with disabilities. And I hope you'll get on the boat with me and start making our websites more accessible. Thank you.