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
The user needs to be able use your app.
This video doesn't have any notes.
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
The second WCAG principle states that
our web content must be operable.
0:00
This is, again, fairly straight forward.
0:05
Our users need to be
able to use our content.
0:08
Sounds reasonable, right?
0:12
This principle covers four more
of the accessibility guidelines.
0:13
The first of these is pretty simple,
0:18
at least on the surface, make all
functionality available from a keyboard.
0:20
At it's core, this means that
our users should be able to do
0:24
absolutely everything they might
want to do using a keyboard.
0:29
This might sound like an extension
of the same thing but
0:33
be certain that anything that can
be navigated to using the keyboard
0:36
can be navigated from
using only the keyboard.
0:41
This will sometimes come into
play with modal content.
0:45
Your user might trigger it and
have focus on the first element contained
0:48
within the modal, but then have no
way to return to the main page.
0:52
Guideline 2.2,
users also must be given enough time.
0:56
Think about this,
1:02
have you ever tried to read all
the credits at the end of a movie?
1:03
Chances are, at some point,
they scroll by too fast for
1:08
you to read and
understand every single line.
1:11
If you want to make sure you
get every scrap of information,
1:15
you have to pause the movie.
1:18
It's very much the same with web content,
we want to give our
1:20
users the control they need to access
everything we've made available.
1:24
That means that anything with a time
limit such as a ticket sales app
1:28
must somehow allow the user
to affect that limit.
1:33
For any moving or
changing content like a carousel,
1:37
the user must be able to pause, stop,
or hide that content all together.
1:40
The next guideline is
as simple as they come.
1:46
Do not design content in a way
that is known to cause seizures.
1:49
Specifically, nothing should flash
more than three times per second,
1:54
no web-based strobe lighting.
1:58
And on to guideline 2.4,
2:01
as web creators, we build worlds for
our users to explore.
2:03
In order for them to do so effectively,
they need to know where they are.
2:08
This section isn't strictly
a development issue,
2:13
it also touches on the quality
of the content itself.
2:16
You may or may not have direct control
over the wording used in text content.
2:19
But it's a conversation
that needs to be had.
2:24
Many of your users will use headings
to navigate through blocks of content.
2:27
Since that's the case, you'll need
to make sure that those headings
2:31
give some indication of
the content that follows.
2:34
Catchy headings might sound cool,
but they often obscure meaning and
2:37
make it harder for
some users to scan your page.
2:41
The Detroit Soup website has some
examples of useful link text.
2:44
Even this first one which just says,
more information, makes sense in context.
2:49
It's clearly part of a larger element and
2:55
provides more information about
the content already displayed.
2:58
We see more useful links,
such as learn more about how SOUP works,
3:01
more info and
submit further down the page.
3:07
It can be tempting to get fancy with our
presentation of content, but that should
3:10
never conflict with any user's ability to
understand what we're trying to convey.
3:16
By the same token, your links
should make their purpose clear.
3:21
Avoid using phrases like click here, but
3:25
rather, include words that describe
what clicking on that link will do.
3:28
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