You don't have to be an accessibility expert to make your sites accessible. This course will help you attain the knowledge and skills to meet web accessibility guidelines and make your sites accessible to all users.
If you are a web/front-end developer, the work you produce must be accessible to all users. In this course, Meeting Web Accessibility Guidelines (Section 508/ WCAG 2.0), you will get hands-on, practical code examples that you can start using today towards your goal of meeting official accessibility guidelines. First, you will learn the differences between Section 508 and WCAG 2.0, helping you to decide which guideline to use. Next, you'll dive into real-world, reusable code patterns/techniques and matching them to relevant guidelines. After finishing this course, not only will you be equipped to acquire government/education-related contracts, but you'll be able to make sites that meet established accessibility conformance guidelines and are more usable for everyone.
Gerard K. Cohen loves front end engineering so much that he is on a mission to make sure that the web is inclusive to all users, making rich internet experiences available for all. He believes great Ux includes performance and accessibility.
Gerard lives in Oakland with his wife, and when he is not sleeping or drinking Zombies at tiki bars, he helps raise awareness by speaking at Front End and Accessibility conferences around the country
Section Introduction Transcripts
Section Introduction Transcripts
Choosing a Web Conformance Guideline All right, first things first. We need to talk about web accessibility conformance guidelines. So in this section, I will help you navigate through the very important decision of choosing the proper web conformance guideline. I'll start with a brief introduction of official conformance guidelines. Then, I will introduce you to Section 508 and the Web Content Accessibility Guidelines, or WCAG. We will do a high-level overview of both, and discuss how they compare, contrast, and overlap. And finally, we will discuss which you should choose. Web conformance guidelines help in providing guidance on how to ensure that your websites are accessible to people with various disabilities. They can also cover you from expensive discrimination lawsuits. Now, I don't mention lawsuits to scare you, but it is a real thing, and it does happen. I would rather you focus on the positive benefits of ensuring access to users with disabilities that will also impact all of your other users, including better SEO and greater usability. You will also be doing your future self a big favor, as one way of looking at disabilities are the certain effects of old age. At some point, you will eventually have diminished vision, hearing, and use of your hands. When it comes to web accessibility there are 2 main guidelines to follow that I've already mentioned, Section 508 and WCAG. Let's first talk about Section 508.
Media One reason why the internet has exploded over the years has been the introduction of media, images, audio, and video. This rich media has turned the internet into an immersive experience. We need to make sure that this immersive experience translates to users with disabilities, and WCAG has some very specific guidelines around media that I'll be talking about in this video. The basis for accessible media comes from Level A guideline 1. 1. 1 for Non-text Content, which states that all non-text content that is presented to the user has a text alternative that serves the equivalent purpose. Level A only requires that you provide text alternatives to media, but I'll also be talking about Level AA guidelines that require alternate means of providing equivalent purpose and meaning. The important takeaway is that you need to make sure that users with hearing and vision impairments can also benefit from rich media content. A quick overview of this section. I'm going to talk about images, including background images via CSS and accessible SVG, then I'll go over the guidelines for making audio accessible, as well as video, and finally some additional media guidelines I want you to be aware of.
Responsive Web Design and Accessibility Responsive web design and accessibility are natural partners. If you consider that the goal of responsive web design is supporting as many screen sizes and devices as possible, you can easily see how it begins to help with accessibility. But of course there are a few things that I want to make you aware of, including the last couple of guidelines to meet. Most of the things that you need to worry about when implementing a responsive design revolve around switching context, order of content, focus order, and finally I will go over some loose ends with additional responsive patterns and guidelines.