Accessibility and Websites - Svetlana Kouznetsova
-
0:04 - 0:07(Steve Bruner)
Alright, welcome to the WordPress -
0:07 - 0:10New York City meetup!
-
0:10 - 0:11Okay, so tonight we are going to have
-
0:11 - 0:25Sveta present about accessibility with websites.
-
0:25 - 0:27(Sveta voiced by an interpreter)
Hi, everyone! -
0:27 - 0:28My name is Sveta.
-
0:28 - 0:31Actually it's short for
-
0:31 - 0:33a longer version of my name.
-
0:33 - 0:36I'm originally from Russia,
that's why I have such a long name. -
0:36 - 0:39And i'm presenting about web
accessibility - something i'm very -
0:39 - 0:42interested in as a deaf person.
-
0:42 - 0:46As someone who is disabled,
naturally I'm very interested in -
0:46 - 0:50web accessibility.
-
0:50 - 0:53And this is a logo created by some university
-
0:53 - 0:55that represent accessibility.
-
0:55 - 0:58Because not everyone uses a wheelchair,
there are people who are blind or deaf, -
0:58 - 1:01who have cognitive disabilities
-
1:01 - 1:04as well who aren't necessarily
represented by the wheelchair logo -
1:04 - 1:07that's usually used for accessibility.
-
1:07 - 1:15So you have the eye, the hand, and the ear,
and the brain to represent cognitive abilities as well. -
1:15 - 1:20So I am sure you all know who Tim Berners-Lee is.
Is there anyone who doesn't know? -
1:20 - 1:24Who knows who he is?
-
1:24 - 1:28OK many of you know who he is -
and this is a quote from him: -
1:28 - 1:32"The power of the web is in its
universality. Access by everyone -
1:32 - 1:37regardless of disability is
an essential aspect." -
1:37 - 1:41In the early days of the web
-
1:41 - 1:44it was actually more accessible than now
-
1:44 - 1:47because most of the websites were text and links,
-
1:47 - 1:51and not very many images and videos.
-
1:51 - 1:56So there wasn't a lot of audio, but today
-
1:56 - 2:0397% of websites are not accessible.
-
2:03 - 2:06Many people who are blind.
They think: "Oh they can just -
2:06 - 2:10use screen readers. That's good enough
for them." But actually the web, -
2:10 - 2:13the sites must be coded
-
2:13 - 2:16in order to be compatible with screen
readers, or people -
2:16 - 2:17who can't use a mouse,
-
2:17 - 2:21or who can't use a keyboard,
need other devices. -
2:21 - 2:26Automatic captions are not very
accessible for deaf people. -
2:26 - 2:34So 97% of websites as a
result are not accessible. -
2:34 - 2:38Maybe people think that people with
disabilities are a small group of people, -
2:38 - 2:40but actually disabled people can
constitute the largest minority group - -
2:40 - 2:46more than foreigners
-
2:46 - 2:49and the market here for people
in the United States -
2:49 - 2:52is $1 trillion.
-
2:52 - 2:55That's double the spending power
of teenagers. -
2:55 - 3:00Worldwide, people with
disabilities constitute -
3:00 - 3:02a $ 4 trillion market place.
-
3:02 - 3:04That's almost the size of China.
-
3:04 - 3:13So it's a really important group of
people that should not be ignored. -
3:13 - 3:15It's not just people with disabilities
-
3:15 - 3:19who benefit from web accessibility
as you see from these pictures. -
3:19 - 3:23You have a mother with a stroller and
also a businessperson carrying -
3:23 - 3:25a roller suitcase.
-
3:25 - 3:33Ramps are actually very helpful
for people in all these situations. -
3:33 - 3:39It also benefits people who use carts
or any sort of wheeled devices. -
3:39 - 3:41Ramps and elevators help
-
3:41 - 3:42these people as well.
-
3:42 - 3:45So it's not just for people
who are using wheelchairs. -
3:45 - 3:49Also captions not only benefit people
who are deaf. -
3:49 - 3:52Speakers of foreign languages also
-
3:52 - 3:53benefit from captions.
-
3:53 - 3:54People who are developing
their literacy skills or -
3:54 - 3:58if someone's in some sort
of noisy environment and -
3:58 - 4:01they want to watch something
quietly on the web, -
4:01 - 4:10that's another reason why captions
for videos are so important. -
4:10 - 4:14In talking about the spending power
of people who have disabilities -
4:14 - 4:17doesn't only affect people with
disabilities, but their friends and -
4:17 - 4:18family members as well.
-
4:18 - 4:21If products and services are
not accessible -
4:21 - 4:24then you lose those extra clientele
as well because -
4:24 - 4:28you have 2 billion people worldwide
-
4:28 - 4:31are connected to people with disabilities.
-
4:31 - 4:35That constitutes a disposable income
of $8 trillion. -
4:35 - 4:40So it's another benefit.
-
4:40 - 4:42The devices that can help
-
4:42 - 4:47people with independence in terms of
computers or mobile phones - -
4:47 - 4:49you have a large audience.
This participation, -
4:49 - 4:52this increased market opportunity,
-
4:52 - 4:57also having a positive image,
not just waiting for someone to sue you -
4:57 - 4:58because your website is inaccessible.
-
4:58 - 5:04If u show that you're making
an investment for accessibility, -
5:04 - 5:09it's a much better better investment than
spending money on a lawsuit later. -
5:09 - 5:15Improved visibility is another benefit,
and also higher search engines results. -
5:15 - 5:20Speaking of search engines -
-
5:20 - 5:24this is the largest accessibility needs
user on the Internet, -
5:24 - 5:29because Google, Yahoo!, and Bing -
-
5:29 - 5:33those sites can't see images and
they really rely on captioning -
5:33 - 5:36for the images.
-
5:36 - 5:40If a video doesn't have captions it
does not appear in search results, -
5:40 - 5:43because Google can't hear a video.
-
5:43 - 5:47Thus captioning and the tags
-
5:47 - 5:56are very important for
search engines. -
5:56 - 5:58And with javascript...
-
5:58 - 6:06sometimes the code in javascript is not
compatible with some keyboards as well. -
6:06 - 6:13How many of you are familiar with Web
Accessibility Guidelines? -
6:13 - 6:16It seems that there are a number of you.
-
6:16 - 6:19Perhaps it might be very
overwhelming because the list -
6:19 - 6:20of guidelines is quite long
-
6:20 - 6:25and even for myself I can be quite
overwhelmed with that, so people tend -
6:25 - 6:28to make these categorizations
-
6:28 - 6:30and create basic guidelines
-
6:30 - 6:37which are described as
the acronym P.O.U.R. -
6:37 - 6:38Perceivable.
-
6:38 - 6:41Meaning blind people who
can perceive the image, -
6:41 - 6:45they might need an audio to supplement,
-
6:45 - 6:50or for people who can't hear,
they rely on captions. -
6:50 - 6:50Operable.
-
6:50 - 6:53Means people who use a keyboard
-
6:53 - 6:56to make sure that everything -
all the functions can be used -
6:56 - 6:59by a keyboard not just by a mouse.
-
6:59 - 7:03You don't have to hover over something
to be able to see the option. -
7:03 - 7:06People can't rely on a mouse would then
-
7:06 - 7:07not be able to use that function.
-
7:07 - 7:10Understandability.
-
7:10 - 7:15Understandable means if text is there
to make sure that text is easily -
7:15 - 7:16understood by any user.
-
7:16 - 7:19Even though maybe you might think:
-
7:19 - 7:22"Well, there's a YouTube video -
YouTube has automatic captions - -
7:22 - 7:24that might be good enough."
-
7:24 - 7:27But automatic actions are
usually unintelligible. They really -
7:27 - 7:29do need to be cleaned up
-
7:29 - 7:33otherwise most deaf people will not
be able to understand them. -
7:33 - 7:34Robust.
-
7:34 - 7:45Means something that's compatible with
current and possibly future technologies. -
7:45 - 7:49So now talking a little bit about how to
make a website accessible in terms of -
7:49 - 7:51the technical aspects.
-
7:51 - 7:53The semantic web.
-
7:53 - 7:56In terms of the semantic web,
content is king. -
7:56 - 7:57Perhaps someone has
-
7:57 - 8:01a fabulously beautiful looking website
-
8:01 - 8:04but the functionality in the content
is weak. -
8:04 - 8:08We have these three elements:
html, css, and javascript. -
8:08 - 8:11The html provides a very strong
foundation first, -
8:11 - 8:15and then you can use style sheets
with css, -
8:15 - 8:17and then javascript - it's probably
-
8:17 - 8:21best to use javascript only
when necessary. -
8:21 - 8:24I know it might seem fun to add some more
fun functions, but -
8:24 - 8:28the less javascript, the more accessible
a website could be. -
8:28 - 8:31How many of you are familiar with
-
8:31 - 8:34that WordPress has this word 'role' - R-O-L-E
-
8:34 - 8:38- how many of you have noticed that in WordPress?
-
8:38 - 8:40A few of you?
-
8:40 - 8:43I've noticed that role
-
8:43 - 8:48equals main role banner
-
8:48 - 8:51and I thought that perhaps some people think
you can just delete that but that's very -
8:51 - 8:53important part of the web accessibility.
-
8:53 - 8:57Here's some examples of role -
-
8:57 - 8:59like body,
-
8:59 - 9:02the role document,
-
9:02 - 9:03header
-
9:03 - 9:06has a role, banner,
-
9:06 - 9:08and if main will have a role, main,
-
9:08 - 9:11footer has its content info.
-
9:11 - 9:13So on the WordPress
-
9:13 - 9:18template keep the role,
don't get rid of that. -
9:18 - 9:25There are more examples
of this role as well. -
9:25 - 9:29In terms of the html structure,
it's important to have a good structure -
9:29 - 9:31to the website.
-
9:31 - 9:32Many of you might
-
9:32 - 9:35skip links, but it's important
-
9:35 - 9:38that it's in the top of the html page,
-
9:38 - 9:43because many people who use screenreaders
-
9:43 - 9:47don't want to hear link over and over.
again for every page. -
9:47 - 9:51So they prefer to have the option
of 'skip link' -
9:51 - 9:55to the main content or other parts
of the webpage. -
9:55 - 9:57You can also hide that
-
9:57 - 10:00with the css style sheets,
-
10:00 - 10:04but don't use 'display none'
-
10:04 - 10:06or 'visible none'
-
10:06 - 10:12because that will cause the screenreader
not to show the content. -
10:12 - 10:16If you indent over -
-
10:16 - 10:18over position -
-
10:18 - 10:22then you can hide
-
10:22 - 10:26those commands that only the screenreader
will be able to distinguish. -
10:26 - 10:28Talking about images -
-
10:28 - 10:33navigation - all the navigation buttons
must have bullets -
10:33 - 10:35and
-
10:35 - 10:42for the screenreader.
-
10:42 - 10:45You can style with css,
-
10:45 - 10:48but it's important to have those
bullet points. -
10:48 - 10:55Drop-down menus - it's best if you use
html and css not javascript for those. -
10:55 - 10:59You can have the drop downs in css,
-
10:59 - 11:04but it's also important to keep the drop
downs limited to maybe two levels, -
11:04 - 11:07because the screenreader is going to repeat
-
11:07 - 11:10that over and over again.
-
11:10 - 11:13Header , , -
-
11:13 - 11:15it's best to use that
-
11:15 - 11:19for the content organization, not for
decoration. -
11:19 - 11:23The keep that just for
the page title, -
11:23 - 11:27and for subcategories -
-
11:27 - 11:29not using that for the menu
-
11:29 - 11:31or for anything other than
-
11:31 - 11:36just the content.
-
11:36 - 11:39It's really annoying to see
'click here'. -
11:39 - 11:44To download you don't need that. Just
click here to download is very annoying. -
11:44 - 11:47Or click here to download with check list.
-
11:47 - 11:51You can just have download checklist and
the kind of file that it is because the -
11:51 - 11:55screenreader reads click here, click here,
and the screenreader isn't sure what -
11:55 - 11:57you're clicking for.
-
11:57 - 12:02So the message, if it's just very clear -
download to a pdf - -
12:02 - 12:06then the person who is using the website
will know to expect the certain -
12:06 - 12:11kind of document.
-
12:11 - 12:12For the content text,
-
12:12 - 12:18make sure it can be resized in terms
of a percentage, or -
12:18 - 12:20in the terms of em.
-
12:20 - 12:22This way people who have low vision,
-
12:22 - 12:27who have some vision but can't see very
well, can resize the text. -
12:27 - 12:30Similarly on mobile devices,
-
12:30 - 12:31don't have frames,
-
12:31 - 12:33image maps,
-
12:33 - 12:35or layout tables.
-
12:35 - 12:39Those are very hard for screenreaders
to be able to detect. -
12:39 - 12:43Make sure that all functions can be
accessible all through the keyboard, -
12:43 - 12:47and that javascript - if you have to use it -
-
12:47 - 12:48it's better if it's downgradable,
-
12:48 - 12:54because then it there is a problem with
javascript the website is still functional. -
12:54 - 13:00Write in simple language using
bullet points. Most people - -
13:00 - 13:04anyone could have a disability,
or the general public doesn't -
13:04 - 13:05necessarily have as
-
13:05 - 13:07much time to spend reading
-
13:07 - 13:09a lot of text on a web page.
-
13:09 - 13:16You'll also want to have the web
layout consistent for each page. -
13:16 - 13:21If you need to, it's best to use
html 5 canvas instead of flash. -
13:21 - 13:24You can make flash accessible,
-
13:24 - 13:26but html 5 is a better way to go.
-
13:26 - 13:35Flash is also not accessible
to users of iPhones and iPads anyway. -
13:35 - 13:40I'm talking about the images and logos.
-
13:40 - 13:46There's a lot of confusion between
'alt' and 'title'. -
13:46 - 13:50alt means what you can't see.
-
13:50 - 13:54the title tag is an optional thing -
you don't need to have that. -
13:54 - 13:58If it's an image that leads to
another page, -
13:58 - 14:01like a logo on the top left of the
the navigation, -
14:01 - 14:04you could have a description of what
the image is. -
14:04 - 14:07Accessibility logo, for example, alt.
-
14:07 - 14:13And then the title will say "go to home page"
or going to a different website. -
14:13 - 14:15If the image is just decorative
-
14:15 - 14:17then you can keep the alt empty,
-
14:17 - 14:21but don't remove it.
Just had it there, but it doesn't need -
14:21 - 14:22to have anything in there.
-
14:22 - 14:26Also no text in the graphics -
it's best to use -
14:26 - 14:29html for the text
-
14:29 - 14:33as screenreaders will not be able to
read the text inside of an image. -
14:33 - 14:39Avoid image maps if possible,
that would be the best. -
14:39 - 14:43Providing text or shapes for a color button,
-
14:43 - 14:46and i'll talk about color in a moment.
-
14:46 - 14:50Don't use strobing, flickering, or
any sort of optical illusion because -
14:50 - 14:53people who have seizures
-
14:53 - 14:56will be sensitive to that, and they might not
even be able to see that or detect that. -
14:56 - 14:59If it's something that's a slower
-
14:59 - 15:02pulsating type of image that could be ok,
-
15:02 - 15:05but not something that's an optical illusion.
-
15:05 - 15:09I mean, I know maybe it's apropos
for some websites but usually -
15:09 - 15:11it's not very accessible.
-
15:11 - 15:13Talking about color -
-
15:13 - 15:17one in ten men are color blind.
-
15:17 - 15:18I've met a lot of men
-
15:18 - 15:22who are color blind,
but actually I haven't met a woman -
15:22 - 15:27who is color blind, and statistically
it's only one in two hundred. -
15:27 - 15:29If you notice a subway map,
-
15:29 - 15:33typically I'll say to my friend, oh I will take
the green line, or take the red line, -
15:33 - 15:35or the orange line.
-
15:35 - 15:42I rarely will reference the number but if
someone's color blind it might be harder. -
15:42 - 15:46Red and green are typically colors
that people who are color blind are -
15:46 - 15:48sensitive to,
-
15:48 - 15:50yellow and blue not so much,
-
15:50 - 15:53and rare that you would see black
and white color blindness -
15:53 - 15:57but this is sort of an image
of what that might be like. -
15:57 - 16:01So you don't want to rely on color only.
-
16:01 - 16:05For example these buttons -
-
16:05 - 16:08stop and go here -
-
16:08 - 16:12you can read it. It's a little hard, but
for someone who is color blind, -
16:12 - 16:16that's what it will look like. It just
looks like brown on brown, -
16:16 - 16:20and then the text gets lost
in the color. -
16:20 - 16:23Contrast is a better way to make
something more accessible. -
16:23 - 16:26Whether or not you want to add an image
-
16:26 - 16:29make sure that someone is not
reliant on the color of the -
16:29 - 16:31information for the information.
-
16:31 - 16:36I'm sure you're familiar
that facebook is blue. Do you know why? -
16:36 - 16:40Because Mark Zuckerberg is actually
color blind, that's why facebook is blue. -
16:40 - 16:48I just read about about that.
I thought that was cool. -
16:48 - 16:51In terms of tables I'm not going to go
-
16:51 - 16:53into great depth in terms of the code
-
16:53 - 16:55but here's a summary about it because
-
16:55 - 16:58some tables are more simple, some are more complex.
-
16:58 - 17:03Here is a summary just so you have
a heads up about this. -
17:03 - 17:05In terms of captions
-
17:05 - 17:11to explain what's in the table
-
17:11 - 17:14must be there for the header,
-
17:14 - 17:18and scope should be included.
-
17:18 - 17:25and also CSS has specific rules for
the table. -
17:25 - 17:31Tables should only be used for
tabular data - -
17:31 - 17:35like a spreadsheet or something that's
in a matrix format. -
17:35 - 17:38They shouldn't be be used for layout.
-
17:38 - 17:45You should just use css for the layout.
-
17:45 - 17:50In the past tables were used much more
commonly but now not so much. -
17:50 - 17:55In terms of these tags for the heads,
body, footer, -
17:55 - 18:01you can find more of these
in google or online in other places. -
18:01 - 18:04Forms.
-
18:04 - 18:12It's important to have labels
for the input. -
18:12 - 18:19It is also good because the screenreader
user is reliant on the keyboard. -
18:19 - 18:22Most of us are relying on the keyboard
as well. -
18:22 - 18:25The 'label for' tag
-
18:25 - 18:27might only be for
-
18:27 - 18:30these small radio buttons.
-
18:30 - 18:32If you use
-
18:32 - 18:34that means that you can also include
-
18:34 - 18:37the entire text. So if you click on the
word - -
18:37 - 18:41that also gives you the selection as well.
It's great for the keyboard users -
18:41 - 18:47and people using screenreaders.
-
18:47 - 18:50If you use groups like radio buttons
-
18:50 - 18:52checkbox
-
18:52 - 18:56or setting up a field - .
-
18:56 - 18:58and ,
-
18:58 - 19:04those are basic rules for tables.
-
19:04 - 19:08Now we're talking about video and audio
and as a deaf person this is something -
19:08 - 19:12I've experienced a lot of frustration with -
most videos online are not captioned. -
19:12 - 19:16Many video broadcasts are not
accessible to deaf people. -
19:16 - 19:18Some people think, well YouTube has
-
19:18 - 19:21automatic captions - and I encorage people
-
19:21 - 19:27to use YouTube not Vimeo.
Vimeo does not support captions at all, -
19:27 - 19:31YouTube has some captioning support.
-
19:31 - 19:34I also recommend YouTube because
it's very easy to use and it's an easy way -
19:34 - 19:36to add captions, but
-
19:36 - 19:38do not reply on the auto-captions
-
19:38 - 19:40because they are
-
19:40 - 19:41really hard to understand,
-
19:41 - 19:44and I'll show you in a moment an example.
-
19:44 - 19:49It's important to have good quality
captions and transcript - -
19:49 - 19:54not just relying on speech recognition.
You could use that perhaps but make sure -
19:54 - 19:56that it's cleaned up.
-
19:56 - 19:58Or perhaps hire someone
-
19:58 - 20:01who can produce a good quality transcript
-
20:01 - 20:06beyond just what an automatic speech to
text recognition can do. -
20:06 - 20:11Also if you use radio podcasts
-
20:11 - 20:13you can have a good enough transcript for that,
-
20:13 - 20:18but make sure that you have
the proper style - -
20:18 - 20:26identifying speakers for example;
make sure punctuation is correct; -
20:26 - 20:31and if there are any sound effects like
laughter or playing music, that that -
20:31 - 20:34information is included as well.
Because a deaf person is not going -
20:34 - 20:37to hear those audio cues.
-
20:37 - 20:40For videos you should have
-
20:40 - 20:43both captions and transcript
available. -
20:43 - 20:47The reasoning is because if someone
is both deaf and blind -
20:47 - 20:49they're not going to be able to follow
the transcripts - -
20:49 - 20:52I mean the captions.
-
20:52 - 20:57They might be reliant on a braille
display that pops up -
20:57 - 21:02for them to be able to read the
transcript as away to access the video. -
21:02 - 21:05Transcripts benefit not only deaf
-
21:05 - 21:09people and deaf-blind people,
perhaps for an hour long video somebody -
21:09 - 21:13would be able to skim through the
transcript a lot faster than watching -
21:13 - 21:15the entire video.
-
21:15 - 21:20So it really in general is best to have
both the transcript and the captions. -
21:20 - 21:24Sometimes you want to be able to watch
and hear the video, and then be able -
21:24 - 21:25to read the captions,
-
21:25 - 21:30without first watching the video
-
21:30 - 21:36or just read the transcript.
-
21:36 - 21:40Just as it's important to have
the audio and video in sync, -
21:40 - 21:44it's important the captions
be synced as well. -
21:44 - 21:47In terms of webinars
-
21:47 - 21:51it's important to hire someone who's
a professional transcriptionist, -
21:51 - 21:53somebody who is professionally trained
for that, -
21:53 - 21:57so that they have 98% accuracy
-
21:57 - 22:02with 220 words per minute.
-
22:02 - 22:08That's the required speed and
not everyone can do that. -
22:08 - 22:15So if you want to have a video pick
a player that supports captions, -
22:15 - 22:20and if you want a transcript that may be
too much for you to do yourself - -
22:20 - 22:24this is a popular service CastingWords -
-
22:24 - 22:28and you can use that for podcasts and
-
22:28 - 22:30also YouTube videos.
-
22:30 - 22:32If there's a time stamp,
-
22:32 - 22:35you can then upload it to YouTube,
-
22:35 - 22:39and they have a way that you can sync
ticket options with the video. -
22:39 - 22:43I have more information on my own website.
-
22:43 - 22:46Usually I'll give a one hour
presentation on this kind of information -
22:46 - 22:49so I'm only touching on points here.
-
22:49 - 22:57I want to show you why automatic captions
are not reliable. -
22:57 - 23:51There's no sound on purpose,
just for you to watch it. -
23:51 - 23:54So I've actually listened with a person
-
23:54 - 23:58who could hear whether the captions matched,
-
23:58 - 24:01and they said that it didn't.
-
24:01 - 24:04The speech recognition is just
relying on a machine. -
24:04 - 24:09It's good that it does something,
-
24:09 - 24:13but it's hard to rely on the auto-captions.
-
24:13 - 24:16Most people think that it's no big deal,
-
24:16 - 24:17we can just use that, but they do really
-
24:17 - 24:27need to be cleaned up by a person.
-
24:27 - 24:30So here's some general information.
-
24:30 - 24:34WebAIM is a great resource
-
24:34 - 24:36for making your websites accessible,
-
24:36 - 24:41and very clearly presented,
the information there. -
24:41 - 24:43If you'd like to have an evaluation tool
-
24:43 - 24:47this is a very popular site - WAVE -
-
24:47 - 24:51developed by the WerbAIM team.
-
24:51 - 24:55I do have that on my computer and
it's very helpful. -
24:55 - 24:57It's not 100% reliable or accurate.
-
24:57 - 25:02Sometimes it might miss
certain elements of the site. -
25:02 - 25:05Firefox also has accessibility
extensions, -
25:05 - 25:09and the WAI has a lot of
different tools here. -
25:09 - 25:13Captioning, if you're more curious
about that, -
25:13 - 25:15I do have a website here with
-
25:15 - 25:27a lot of information and my contact
information is there as well. -
25:27 - 25:32If anyone has any questions?
-
25:32 - 25:39(Audience Member)
Are there any WordPress templates -
25:39 - 25:47and/or plugins that you recommend
as being very accessible? -
25:47 - 25:53(Sveta voiced by an interpreter)
I'd have to google it in terms of
accessibility and WordPress.. -
25:53 - 25:54(Audience Member)
Anything that you've used or come across -
25:54 - 25:57that you're really comfortable with?
-
25:57 - 26:00(Sveta voiced by an interpreter)
I've just started using WordPress -
26:00 - 26:08earlier this year so i'm not as familiar.
-
26:08 - 26:10(Audience Member)
What websites are potentially liable to being sued -
26:10 - 26:17for not being accessible, and for what period?
-
26:17 - 26:26(Sveta voiced by an interpreter)
There are so many. -
26:26 - 26:29Well, ninety seven percent of web sites
are not accesible, -
26:29 - 26:34for example, Netflix.
-
26:34 - 26:38The deaf community's actually suing,
in process with a lawsuit right now with Netflix -
26:38 - 26:41because they refused to caption
-
26:41 - 26:46their streaming videos. Their dvds have captions,
but they don't have streaming captions. -
26:46 - 26:50CNN is also involved in a lawsuit right now,
-
26:50 - 26:54they have captions on television but they
don't have captions on their web content. -
26:54 - 27:00I know that blind people, they sued
Target. There was a blind community -
27:00 - 27:02involved in a lawsuit against
the Target website. -
27:02 - 27:07(Audience Member)
So there's some examples, and like I say
it's a better investment -
27:07 - 27:12to make their website accessible than
be liable and possibly be spending money -
27:12 - 27:22on a lawsuit later. Are there any ways of tracking,
-
27:22 - 27:25using Google analytics, to see how many access-challenged
users are coming to your site -
27:25 - 27:42so you can say to a client,
you need to address this? -
27:42 - 27:45(Sveta voiced by an interpreter)
I don't think there's any way -
27:45 - 27:49to track using Google analytics.
I think user testing is the only way -
27:49 - 27:51to really track accessibility,
-
27:51 - 27:53and these accessibility valuation tools.
-
27:53 - 27:58(Audience Member)
Aren't there separate browsers -
27:58 - 28:06that can be used by accessibility...
-
28:06 - 28:07(Sveta voiced by an interpreter)
What do you mean? -
28:07 - 28:10(Audience Member)
Uh... for the speech, -
28:10 - 28:13it can read through..
-
28:13 - 28:14There are certain browsers that can..
-
28:14 - 28:33that, if you need it read to you,
0:28:18.430,0:28:25.430
you can..use that browser,but I'm not sure
if it's capturable in analytics. -
28:33 - 28:36(Sveta voiced by an interpreter)
No, not that I'm aware. -
28:36 - 28:41It's the same concept as if you
design a regular website, -
28:41 - 28:47and your user experience is not just
about the people who are disabled but -
28:47 - 28:51you might try to have some user testing
to see whether or not -
28:51 - 28:53the website conforms to the expectations
-
28:53 - 28:57of a certain user group that's very similar
-
28:57 - 28:59to people who are disabled.
-
28:59 - 29:02The only really way to find out is
the survey people with -
29:02 - 29:10disabilities and get their feedback.
-
29:10 - 29:16(Audience Member)
That's one of the questions I am asking about
developers asking the disabled community -
29:16 - 29:20how to do certain things.
I mean, I am beginning to lose my vision, -
29:20 - 29:27and I've found it's very difficult
to get somebody to say, -
29:27 - 29:30well, it's very easy
-
29:30 - 29:39to do this because I see other technology
-
29:39 - 29:44being used broadly and maybe
the inference about ramps, -
29:44 - 29:46well everybody uses ramps and
it's part of the culture -
29:46 - 29:57not just about accessibility and those
who need it and it's really for everybody. -
29:57 - 30:04(Sveta voiced by an interpreter)
I'm sorry. Is that a comment or a question? -
30:04 - 30:05(Audience Member)
The question is ... -
30:05 - 30:07How do you get people's minds
-
30:07 - 30:09wrapped around that you should be
developing for everybody all the time, -
30:09 - 30:11rather than to step back and say
I'm going to do this site for blind people, -
30:11 - 30:22I'm going to do this site for deaf people.
It's just that why shouldn't you just -
30:22 - 30:32include all these accessibility tools
as part of your regular development? -
30:32 - 30:35(Sveta voiced by an interpreter)
Well, because people aren't aware -
30:35 - 30:39unless they have had that
explicitly explained to them -
30:39 - 30:44as it a deaf person I might say well I need
captions, but I might be perceived -
30:44 - 30:46as being just one deaf person asking for that.
-
30:46 - 30:49People don't realize that captions
benefit speakers of other languages. -
30:49 - 30:52My parents have perfect hearing
-
30:52 - 30:55but their first language is Russian,
not English, -
30:55 - 30:58and they watch television with the
captions on, -
30:58 - 31:01because it helps them understand and
learn English better, -
31:01 - 31:04The disability market is huge
-
31:04 - 31:07and so they shouldn't be overlooked.
-
31:07 - 31:11People who are becoming older,
you'll notice the baby boomers -
31:11 - 31:15are now a very large segment of the
population and and more and more of them -
31:15 - 31:18are developing disabilities as they age.
-
31:18 - 31:20So I mean it's not easy,
-
31:20 - 31:25I can overload people with statistics.
People who care tend to really -
31:25 - 31:28make the investment, and others
-
31:28 - 31:32don't, they won't.
-
31:32 - 31:34Do you want to do responsive,
-
31:34 - 31:38type of reactive design, or
be like people who want to -
31:38 - 31:41develop based on user experience?
Those are two different -
31:41 - 31:44approaches that people can take.
-
31:44 - 31:49(Audience Member)
No. I am just making, I guess, the comment
that the very fact that you are here -
31:49 - 32:02raises the fact that a lot of people in
this room probably never even thought about - -
32:02 - 32:09I mean that may be just an assumption on my part, but -
I think this is just a way of raising -
32:09 - 32:13the awareness for the rest of the community.
-
32:13 - 32:16(Sveta voiced by an interpreter)
Yes, right. And, for me, I'm a sighted person -
32:16 - 32:21but sometimes, if a page is slow to load,
-
32:21 - 32:26I still like to have the description
of the image -
32:26 - 32:28because I might shut off images
-
32:28 - 32:32and still want to to be able
to see what it is to make it -
32:32 - 32:36load the page faster.
0:32:33.270,0:32:36.429
Just having "something dot jpg" -
32:36 - 32:42isn't necessarily going to be very helpful.
-
32:42 - 32:45It helps the searchability
-
32:45 - 32:49as well if those tags are there in the
descriptions. Even though I am not -
32:49 - 32:52blind I benefit
-
32:52 - 32:55from accessibility for blind users.
-
32:55 - 32:58And even with captions, people think well
they don't need that, -
32:58 - 33:03and then later on when they use them,
they'll realize how they -
33:03 - 33:08appreciate it and they wish
they had used them earlier. -
33:08 - 33:12I think there was some in the back
with a question? -
33:12 - 33:19(Audience Member)
I was just wanting to respond to something that
the gentleman up there said earlier -
33:19 - 33:22about why include it in everything that you do
as kind of a default thing. -
33:22 - 33:37Well why do we include mobile versions
and responsive versions of sites
0:33:25.770,0:33:28.210
by default? I think it should be treated
the same way. I'm not arguing with you. (laughter) -
33:37 - 33:37(Sveta voiced by an interpreter)
That's a good point. Yes. -
33:37 - 33:43(Audience Member)
Could you speak more about
0:33:40.419,0:33:43.200
responsive design? -
33:43 - 33:45Are you saying that responsive has
-
33:45 - 33:53a better capability for the disabled?
-
33:53 - 33:57(Sveta voiced by an interpreter)
Well, not exactly. It can overlap, -
33:57 - 34:00but not exactly.
-
34:00 - 34:05Because if you use mobile phones
-
34:05 - 34:09but the code is not compatible
-
34:09 - 34:14for a mobile phone, I'm not sure how
exactly people with limited vision -
34:14 - 34:17even use the mobile phone. That's still new
for me but that's another example -
34:17 - 34:19in terms of having the code be compatible for
-
34:19 - 34:26what shows up on a mobile phone.
-
34:26 - 34:30I know how people with disabilities use
an actual standard computer. I'm not as -
34:30 - 34:48familiar with people with disabilities
using mobile devices. -
34:48 - 34:51(Audience Member)
This is more in reference to
how do we make accessibility -
34:51 - 34:55more standard. I think we are
at a good time now with html 5, -
34:55 - 34:57css 3, and all these new additions.
They are still in the works of -
34:57 - 35:01being the global rule of the land,
compared to how html was very much -
35:01 - 35:04do it until it looks right kind of thing,
so right now, if we do push for it -
35:04 - 35:17in as many places as we can
I think it will potentially be more.. -
35:17 - 35:18(Sveta voiced by an interpreter)
Correct, but that isn't enough. -
35:18 - 35:22We need to remember also about color -
-
35:22 - 35:24it's not just about coding,
-
35:24 - 35:27it's also about the design,
and the visual aspects -
35:27 - 35:31of the website as well.
-
35:31 - 35:37(Audience Member)
That's a good point, thanks. -
35:37 - 35:40(Audience Member)
Are there tools?
As a designer and front end developer, -
35:40 - 35:42I'm always using tools like browser stats and
from other devices because you can't -
35:42 - 35:44possibly have all the devices..
and this is something I need -
35:44 - 35:47to consider that there's even more
devices that I'm designing for -
35:47 - 35:50that we're not even looking at.
So I'm wondering if there are tools -
35:50 - 35:55that as developers we can access to
get an experience of what -
35:55 - 36:08a disabled person may be seeing.
-
36:08 - 36:14(Sveta voiced by an interpreter)
Yes. You can download the free tools. -
36:14 - 36:18I think if you have a Mac,
-
36:18 - 36:22Mac has screen reader software already
built in. I just found this out. -
36:22 - 36:28There is captioning support too
which i was really amazed at. I'm curious -
36:28 - 36:33as to what the screenreader with captioning is
going to look like. -
36:33 - 36:37The Mac screenreader also has captions,
-
36:37 - 36:41that's telling me what it says.
It's really cool. So if you have a Mac -
36:41 - 36:45you use the VoiceOver
-
36:45 - 36:49that's the Mac feature
-
36:49 - 36:51you can select as an option.
-
36:51 - 36:55I think in windows, I'm not sure what
it's called because i don't use windows -
36:55 - 36:58there might be something that's
-
36:58 - 36:59parallel that does
-
36:59 - 37:06the same thing for windows.
-
37:06 - 37:13(Audience Member)
Can I just comment, add to that? -
37:13 - 37:15Because I do use windows, can I just
follow up, is that ok? -
37:15 - 37:17(Sveta voiced by an interpreter)
Sure, go ahead. -
37:17 - 37:20(Audience Member)
OK. On windows there are a couple of speech -
37:20 - 37:22detects software. One is called Natural
Reader, that will read the text on a page, -
37:22 - 37:26detects software. One is called Natural
Reader, that will read the text on a page, -
37:26 - 37:28and also turn it into a wav file, so that
you can automatically... -
37:28 - 37:37So, it will read through the copy you've
written, turn it into a wav file, and -
37:37 - 37:42you can repost it on the site. So you've
automatically turned it into something for -
37:42 - 37:51people who can't see but would like to
hear what you've just written. -
37:51 - 37:53(Sveta voiced by an interpreter)
Thank you for saying, that. -
37:53 -OK, I think that's it (Applause)
- Title:
- Accessibility and Websites - Svetlana Kouznetsova
- Description:
-
Accessibility and Websites - Svetlana Kouznetsova at WordPress NYC Meetup at NYU Poly NYC on Oct 16 2012
Tim Berners-Lee, the inventor of the world wide web, said: "The power of the Web is in its universality. Access by everyone regardless of disability is an essential aspect." The internet is definitely one of the best things that happened to people with disabilities. However, there are still many websites that are not accessible to those visitors because they are not designed or coded properly to be used effectively even with assistive technologies. This presentation covers the basics of accessibility and explains why it benefits everyone, regardless of disabilities, and even website owners.
Svetlana Kouznetsova (Sveta) is a NYC-based web professional with a BFA in Graphic Design, an MS in Internet Technology, and over a decade of project experience with national/international organizations and non-profit/educational institutions. Her main interests are user experience, accessibility, front-end design/coding based on the latest web standards.
http://s-v-k.com/http://www.meetup.com/WordpressNYC/events/86067492/
PUNKCAST 2103-01
Webcast support: NYI http://nyi.netMore videos: http://wpnyc.org/video/
- Duration:
- 38:04
Amara Bot edited English subtitles for Accessibility and Websites - Svetlana Kouznetsova | ||
Amara Bot added a translation |