Bummer! You must be logged in to access this page.

Heads up! To view this whole video, sign in with your Courses account or enroll in your free 7-day trial. Sign In Enroll

Web Accessibility Compliance

Well done!

You have completed Web Accessibility Compliance!

Sign up for Treehouse Back to Library

Understandable

2:13 with Aisha Blake

It can be tempting to get really fancy with our presentation of content, but that should never conflict with any users ability to understand what we’re trying to convey.

This video doesn't have any notes.

Related Discussions

Have questions about this video? Start a discussion with the community and Treehouse staff.

Sign up

    Related Discussions

    Have questions about this video? Start a discussion with the community and Treehouse staff.

    Sign up

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

    You need to sign up for Treehouse in order to download course files.

    Sign up

      You need to sign up for Treehouse in order to set up Workspace

      Sign up