 Dobre, Gabrieli, začne, kako se zelo potrebe. Ok, zelo potrebe. Kaj je začnevo? Ok, začnevo. Znači, začnevo je, da tehnologije je tebe jezge na skorbu, grešu, in prihlicu na plače v izvastaj, ne odliščne, neč vsego, vsok vsošalje in ekonomi. Vse skorov in pokršenje tudi skorbe je skorodina. Tudi skorodina je začelovana technoločnja, o či je tačne kot, boo evacuation or ability. The World Web Consortium, as well as accessibility is. And that created dishes to these things. WWEis Web accessibility initiative, is a team that develops standard and support material for developers for implement pro garmenta akšesibiliti in theirarte basis. First work of the web accessibility initiatives, was the area attribute, complained of HTML attribute which counsel a way to make web content glow readable from the screen reader. Area attribute are divided in roles, properties, properties and states. WCG are a set of guidelines for making web content more accessible. WCG are divided in four layers. There are the principles. For every principle there are some guidelines. And for every guideline there are the success criteria and the sufficient advisory techniques. There are the four principles of content accessibility guidelines. The principles are percevable, operable, understandable, and robust. Let's see the guidelines for each other. For the percevable principle WCG defines a wide line for alternative for non-text content, alternative for live streaming, audio and video, for the content orientation and the independence from the platform. And wide lines about colors, audio control, contrast, and test sides. For the operable principle there are specifications about cable shortcuts, timing, time and content, for animation and color flashes, for navigability and for the input modalities. This is simple. The understandable principle has only three guidelines about readability, predictability, and input assistance. For the robust principle is one. One guideline about compatibility. Let's see some tricks for quickly refactor output bases. First rule, do you know the difference between these two structures? First rule is use semantic tags in HTML. Simple. Other tricks could be alternative text for images, alternative text for audio and video content, and cable navigation with roll and tab index attribute. If you want to improve your accessibility of your website, just use this tool that I show you. This is a platform of W3C that compiles for you accessibility reports and send via email. This is a checklist suitable for... We do the task for a good accessible application. This is a native tool for check the contrast of the page. This is another tool, but online, where you put your foreground color and your application background color, and you find for you every better contrast than yours with similar color. Dynamapper is another cloud service for web accessibility report, but it's pay. Wave is a free alternative to Dynamapper. Let's see wave is a very good tool. It shows a preview of the website with warnings where are things with problems. The website has a bit of a bit of a color contrast problem. Webinter is another tool for check the best practice on your application and also as the accessibility section. Webinter is also available as a web extension, so you can use... It's like Google Lighthouse, you know? Perfecto. And it compiles reports about accessibility. There are no issues. It's a black page with an image. There are no issues here. OK. For check your accessibility, you can use the tools of your browser. The tools for accessibility are included in Firefox and are available as an extension for Chrome. OK. This is a GitHub collection that collects every resource about web accessibility available on GitHub. OK. That was nice. Thank you for catching up. Do you have questions? We have time for questions. Question? Different? He wants the first slide or the second slide and then he asks questions about that. Can you explain what name rule value is? Name rule for the input control and for the HTML elements. OK. And input name. OK. It's not clear yet. Input name, input value. Other question? Hi. How much of these suggestions would be applicable to desktop applications, say written and queued? Would it be a good start or do you have other... For developer desktop application? Yes. I'm not a desktop application developer, but you can use the same guideline. Adaptate it, but WCAG could be the principle and the guidelines could be used also for desktop application. Hi. Thank you for your talk. My question would be like, you know, with developing, I'm working on a web-based application and what would be your suggestion for an automated way of checking accessibility when developing a web-based application? I know there are solutions. Automated? At the moment for React components, but just as a web application, I'm pretty sure there are some good tools for that. Thank you. Good question. I don't know if there are automatic tester, but I use an ESLint plugin that expressively for accessibility. And I use that so I can build accessible application in a built time. Accessibility-wise, what framework I don't know, either to, like React Angular or on the CSS side, which frameworks do you advise and accessibility-wise, which one are kind of more aware of this? Accessibility is not related to any framework. You can use the one you want. No, no, sure, sure, but sometimes a lot of frameworks provide a lot of widgets and components that they have accessibility issues. If I get a component with a lot of buttons. Yeah. So do you think in the scope of frameworks, which one is the one that is more accessibility aware, in the community? I don't know, but I use React for work and it does very good, it does no issues with accessibility. I use React and ESLint with the accessibility plugin. Could you give us an example of social and economic disabilities? People are illiterated. So they can't read on the text and can use the screen reader for understanding the content. I'm gonna step in, hi. I have a token accessibility later on, but more on the social part. And I would add that the criteria for this is that in many countries internet is extremely expensive. Like for 35 years you get around max one gigabyte and many will not be able to load your page. There is a really good talk by a friend of mine that I recommend. He is literally comparing the websites, how much they load and how much memory they will eat out of your internet connection. Besides the price money wise, accessibility to a good connection is also limited in many countries. These two, like exactly how much internet costs outside, we are like in Europe, I'm saying outside Europe and maybe even USA, even if in USA you get max 10 gigabytes for 35 dollars, which for me is extremely expensive for what we paid here. And again accessibility to, access to a good connection where you can load stuff, not 2G or even less than that. Any other questions? Is there any way to measure if somebody is trying to use, let's say a screen reader on my site? For me as a developer to see that's actually like, if somebody is trying to do that. I don't know if there is a way but you have to implement accessibility. Before thinking of screen reader you have to implement an accessible code base and you don't have problem with screen reader. More questions? No, so thank you Gabrielle.