Heads up! To view this whole video, sign in with your Courses account or enroll in your free 7-day trial. Sign In Enroll
Preview
Start a free Courses trial
to watch this video
Each of the four principles are pretty easy to understand on their own. They might even sound like common sense to you. The first, that web content should be perceivable, means that content “must be presentable to users in ways they can perceive.”
Related Discussions
Have questions about this video? Start a discussion with the community and Treehouse staff.
Sign upRelated Discussions
Have questions about this video? Start a discussion with the community and Treehouse staff.
Sign up
Each of the four principles are pretty
easy to understand on their own.
0:00
They might even sound
like common sense to you.
0:05
The first,
that web content should be perceivable,
0:08
means that content must be presentable
to users in ways they can perceive.
0:12
For me this is the very
essence of accessibility.
0:18
All fo you users need to have
access to the same content.
0:22
No matter what disability
they might have or
0:26
what sort of device they might
be using to get at that content.
0:28
Under the what is WCAG 2.0 heading
let's hit the link to WCAG 2.0.
0:33
To dig in and
take a look at the guidelines themselves.
0:40
This is a pretty dense document,
0:44
but you don't have to try to read
through it from beginning to end.
0:46
We're gonna hang out here and
0:50
get comfortable reading
it throughout this stage.
0:52
But it's okay to take your time and
only pick out the parts you need.
0:55
We'll talk about how you can figure out
which guidelines apply to your project
0:59
in another video.
1:04
Let's scroll down to
the table of contents and
1:05
check out the very first guideline, 1.1.
1:08
It says provide text alternatives for
any non-text content, so
1:12
that it can be changed into
other forms people need,
1:17
such as large print, braille,
speech symbols, or simpler language.
1:21
Now, there's just one
success criterion for this.
1:26
It's easy to manipulate and
communicate text.
1:31
So anything that isn't already text should
have a text alternative that serves
1:34
the equivalent purpose.
1:39
For images, for example,
1:41
this is accomplished by simply giving
the image an ALT attribute with the value.
1:42
Note that there are exceptions
even to this very basic guideline.
1:47
Check out the teacher notes for
1:51
a link too a talk by Lewis Garcia on
exceptions to WCAG success criteria.
1:53
Next up is guideline 1.2 Time-based Media.
1:58
This one has nine success criteria
spread across all three levels.
2:03
Note that most refer to
pre-recorded content.
2:08
But two are specific to live audio.
2:11
Again, it's important
to remember exceptions.
2:14
Here where it says except when
the media is a media alternative for
2:17
text, and is clearly labeled as such,
2:22
means that we're only going to one level
deep with our alternative content.
2:25
We don't need to provide backups for
our backups.
2:31
If you scroll down below this video,
2:34
you'll find a transcript of
everything I'm saying right now.
2:36
This is a perfect example of how you might
handle the accessibility of audio visual
2:40
content.
2:44
There are services that
will handle this for you.
2:46
You can write transcript yourself or
2:48
you might be able to get a passable
transcript written automatically.
2:50
See the teacher's notes for
more on creating caption for
2:55
your audio-video content.
2:58
Let's take a look at Guideline 1.3.
3:00
Our content must be adaptable.
3:03
In that its meaning should still be clear
no matter what user agent is accessing it.
3:06
The relationships between
elements should be clear.
3:12
For example, if I have a text input
element on the page as part of a form and
3:15
the label that is visible to cited users.
3:20
It should be equally clear to all
other users that that label is
3:23
intended to identify
that specific text input.
3:28
We'll talk a way more deeply about
this sort of thing in the next stage.
3:31
The last guideline under
this principle states
3:35
that our content must be distinguishable.
3:38
This deals a lot with allowing users
to separate the important parts of our
3:41
content out.
3:46
The level A criteria states that color
3:46
may not be used as the only visual
means of communicating information.
3:49
Going back to the example of a form,
this means we
3:54
can't rely on color alone to show a user
that they've missed a required field.
3:57
We also need to make sure that any
audio content longer than three seconds
4:03
can be paused or stopped.
4:08
This is because it can literally
interfere with a user's
4:10
ability to use the whole page.
4:14
Consider a user who's attempting
to listen to a screen reader
4:17
over your unstoppable audio content.
4:20
Or one who is simply
very distracted by it.
4:23
We've covered the essentials of all the
guidelines that fall under making our web
4:27
content perceivable.
4:32
In the next video, we'll move on
to the principal of operability,
4:33
which deals more with the users
ability to interact with content.
4:37
You need to sign up for Treehouse in order to download course files.
Sign upYou need to sign up for Treehouse in order to set up Workspace
Sign up