1 00:00:00,550 --> 00:00:04,420 Let's talk about with WCAG Principle 3, Understandable. 2 00:00:04,420 --> 00:00:10,030 The first step to making our web content understandable is making it readable. 3 00:00:10,030 --> 00:00:11,780 At its most basic level, 4 00:00:11,780 --> 00:00:16,010 this means making the default language of our content identifiable. 5 00:00:16,010 --> 00:00:18,150 This is a low hanging fruit. 6 00:00:18,150 --> 00:00:23,170 We can accomplish it by including the lang attribute in our HTML element. 7 00:00:23,170 --> 00:00:27,950 A predictable web page doesn't do things that the user hasn't asked it to do. 8 00:00:27,950 --> 00:00:29,290 Changing focus or 9 00:00:29,290 --> 00:00:34,420 the settings of the UI component shouldn't trigger a change of context. 10 00:00:34,420 --> 00:00:36,790 What's a change of context you ask? 11 00:00:36,790 --> 00:00:41,700 This is a great time to point out that the WCAG working group is pretty self-aware. 12 00:00:41,700 --> 00:00:45,890 They know they've used terms that might not be familiar or 13 00:00:45,890 --> 00:00:49,240 make sense to regular people in this context. 14 00:00:49,240 --> 00:00:51,910 Knowing that, they've created a glossary. 15 00:00:51,910 --> 00:00:55,700 You can click on many of the terms you'll find throughout the guidelines to see 16 00:00:55,700 --> 00:00:56,870 an explanation. 17 00:00:56,870 --> 00:00:59,820 In this case, we'll click on change of context. 18 00:01:01,790 --> 00:01:06,980 This is great because not only does it expand on the term itself, 19 00:01:06,980 --> 00:01:08,770 but it gives us an example. 20 00:01:08,770 --> 00:01:14,307 So now we now that success criteria 3.2.1 and 21 00:01:14,307 --> 00:01:21,040 3.2.2 are saying we should never trigger things like pop-up windows or 22 00:01:21,040 --> 00:01:25,640 switch to a different page just because an element has received focus or 23 00:01:25,640 --> 00:01:27,350 UI settings have changed. 24 00:01:27,350 --> 00:01:32,303 Taking the time to discover the meaning of terms you don't understand will make it 25 00:01:32,303 --> 00:01:36,489 much easier to gauge the excessive ability of your work in a long run. 26 00:01:36,489 --> 00:01:41,435 The last guideline governed by the understandable principle has to do with 27 00:01:41,435 --> 00:01:43,130 input elements. 28 00:01:43,130 --> 00:01:48,750 Whatever the user needs to do to fill out our forms should be crystal clear. 29 00:01:48,750 --> 00:01:52,550 Provide sufficient instructions and label all of your input elements. 30 00:01:54,396 --> 00:02:00,130 Any error we detect should be communicated to the user so that they can fix it. 31 00:02:00,130 --> 00:02:03,750 Have you ever filled out a form and had your input rejected but 32 00:02:03,750 --> 00:02:05,740 couldn't tell what was wrong? 33 00:02:05,740 --> 00:02:10,730 This kind of issue could keep a new user from signing up for your service, or 34 00:02:10,730 --> 00:02:12,850 a customer from buying your product.