Скачать или смотреть Intro to WCAG 2.1 AA: What are the web content accessibility guidelines or WCAG?

00:11 content accessibility guidelines so these are the standards that we are using um and they stand for, well web content accessibility uh guidelines is #wcag or wake ag so you'll hear me say that from now on and they're created by the world wide web consortium you might have heard of them I like to call them a group of nerds that create the rules of the internet and they have graced us with some #accessibilityguidelines so that we have some kind of tool to measure our work and ensure that we are creating accessible digital products so the current standard is wcag 2.0 and that's been adopted pretty much internet internationally by most organizations 2.1 wcag 2.1 was released in 2018 and organizations have been transitioning to version 2.1 it's important to note that version 2.0, 2.2 will be coming out ​later this year i believe if not next year and they're also working on version 3.0 what these standards do is you know set a bunch of principles and guidelines for us
and there are testable statements so there are three levels of compliance a double a and triple a level double a is what most organizations go with level a is the lowest level triple a is the highest level so level double a is sort of a healthy medium, so there are four principles that these guidelines revolve around to help us kind of understand the spirit of accessibility and that is they spell the acronym poor p-o-u-r so think of this as you are pouring content into your website perceivable operable understandable and robust so
02:18 I'm going to go through each of these right now okay so principle one perceivable will people with disabilities be able to perceive what is on your website, so some quick examples of that are if somebody is blind they cannot see how will they be able to perceive images on your website and that is rectified by adding alternative text to include a description for your image and your image could be an #inclusivedigital logo or it could be a picture of a person sitting at their desk you know on a computer working right it could be a number of things but unless you write a detailed description of what
03:02 that image is somebody such as myself with a screen reader will not be getting any meaningful information out of that image same for videos for folks who are deaf or hard of hearing if your videos have captions that make your videos perceivable to folks who are deaf or hard of hearing principle number two is operable so will people with disabilities be able to operate your digital product so if you have some interactive content or if you have forms or applications to fill out will people with disabilities be able to function and be able to get to you know let's say if somebody cannot use a mouse will they be able to use the keyboard to get to all of the fields to fill out and be able to just solely do the whole thing using a keyboard
04:02 so principle three is understandable and it basically you know speaks to will people with disabilities be able to understand what they're doing on your website in the in the case of let's say filling out a job application and I think we've all at this point filled out an online job application and have felt those frustrations right we want to make those kinds of experiences really smooth and clear and just for people to understand what they need to be doing next right and understand the whole process, so that comes with instructions it also comes with having pagination so if it's a multi-step process let folks know they're in step one or step two of five right making sure that required fields have text alternatives so a lot of times required fields are just marked in red that doesn't work for somebody who's blind right so we need a text alternative such as a star in the label to note that it is required and instructions to let folks know that
05:06 star notes a required field or any kind of instructions about how you're supposed to fill out those fields so just making sure that it's clear and obvious for all users what they're supposed to be doing at each step of the process and four principles four is robust and this speaks to compatibility with assistive technologies various ones uh different platforms and browsers right so I should be able to have a similar experience if I'm using the screen reader on windows using a windows 10 and let's say chrome I should be having a similar experience if I'm using the mac screen reader called voiceover on the mac os using let's say safari right and this speaks to how your website is built under the hood are you using standard html5 elements

#ADA & #WCAG compliant: https://www.inclusiveweb.co/
LinkedIn:   / inclusive-digital-llc  
Twitter:   / inclusivedigit1