Understanding the Guidelines and Levels3:27 with Aisha Blake
Being familiar with the expectations placed on you and your apps will make it easier to build them into your work.
[MUSIC] 0:00 Being familiar with the expectations placed on you, 0:04 as a developer, will make it easier to build them into your work. 0:07 In this stage, 0:12 you'll start to understand what we mean by web accessibility compliance. 0:13 Most of this stage will be focused on W-C-A-G, or WCAG. 0:18 To be compliant with WCAG, is to build products that meet certain objective, 0:24 testable criteria. 0:28 Depending on your country, the function of your website or application, or 0:30 the industry you're in, compliance may be required by law. 0:35 Even if it's not mandated, holding your work to an internationally 0:39 recognized standard, will achieve the core goal of making the web accessible 0:43 to as many people as possible, no matter their individual circumstances. 0:48 WCAG stands for Web Content Accessibility Guidelines. 0:54 And the current version 2.0 was published in December of 2008. 0:59 It became an ISO Standard in 2012. 1:03 So, you'll see developers from all over the world leveraging their 1:06 accessibility work against these guidelines. 1:10 See the teachers notes if you would like more information 1:13 on the International Organization for Standardization. 1:15 WCAG is broken up into four principles. 1:18 Web content must be perceivable, operable, understandable, and robust. 1:22 These principles are used as umbrellas for 12 accessibility guidelines. 1:28 Which are, in turn, broken up into testable success criteria, 1:34 that span three levels, A, AA, and AAA. 1:38 There's not a great explanation of these levels put 1:43 forth by the WCAG working group itself. 1:46 But Karl Groves, a well known web accessibility consultant, 1:47 wrote a solid analysis of them a few years ago. 1:52 You'll find a link to the article in question in the teachers notes. 1:56 But I'll give you my synopsis. 1:59 Level A criteria have a large impact across a wide spectrum of users. 2:01 Your work should pretty much always meet all Level A success criteria, 2:06 no matter what you're building. 2:10 This is widely considered the bare minimum for deeming your content accessible. 2:12 Things like providing a text based alternative to non text context, 2:17 like images. 2:21 Or making sure that the entire site can be navigated using only a keyboard. 2:22 Level AA criteria also tends to have a big impact on the accessibility of your work, 2:26 but may not affect quite as many people. 2:32 You should be hitting all the level AA success criteria, but 2:35 there are some exceptions and it won't always be feasible. 2:40 These include things like writing headings and labels to describe the topic and 2:43 purpose of relevant content. 2:48 Level AAA success criteria tend to be even more specific, and 2:50 will not always be applicable to every project. 2:55 These criteria often relate to special cases, 2:58 like providing accessible alternatives to live audio only content. 3:01 I hope you're ready to dive deeper into these principles and guidelines. 3:08 It might seem like a ton of information right now, but 3:12 I promise it's not as complicated as it sounds. 3:15 By the time we're through, WCAG won't be nearly as intimidating. 3:18 And you'll be able to use it as a tool to make your work that much better and 3:22 more accessible. 3:26
You need to sign up for Treehouse in order to download course files.Sign up