WEBVTT
Kind: captions
Language: en

00:00:01.740 --> 00:00:02.940
<v Sheryl> My name is Sheryl Burgstahler

00:00:02.940 --> 00:00:07.820
and I direct Accessible Technology Services
at the University of Washington in Seattle.

00:00:07.820 --> 00:00:11.820
Our services also reach out to our
branch campuses in Bothell and Tacoma.

00:00:13.440 --> 00:00:14.920
<v Hadi> My name is Hadi Rangin

00:00:14.920 --> 00:00:21.160
and I’m a member of IT Accessibility Team
at University of Washington.

00:00:25.820 --> 00:00:31.280
<v Narrator> Hadi’s an accessibility expert,
and he's also a user of accessible technology.

00:00:31.290 --> 00:00:35.050
He uses a refreshable Braille display
and screen reading software

00:00:35.050 --> 00:00:37.360
that reads everything on the screen.

00:00:38.020 --> 00:00:42.000
<v Hadi> I am blind and I use
a screen reader program

00:00:42.000 --> 00:00:45.180
at home and here, everywhere.

00:00:45.180 --> 00:00:50.850
A screen reader program is software
that communicates with the operating system

00:00:50.850 --> 00:00:54.080
and conveys the information to me.

00:00:54.080 --> 00:00:56.600
[screen reader reads fast]

00:00:56.600 --> 00:01:00.440
<v Hadi> Even if you are
reading as a sighted person,

00:01:00.440 --> 00:01:03.680
you do not read every content
at the same speed.

00:01:03.680 --> 00:01:04.680
Right?

00:01:04.680 --> 00:01:09.310
Sometimes you have to make a pause
and then review what you have read

00:01:09.310 --> 00:01:11.700
and then digest the information.

00:01:11.700 --> 00:01:13.049
For us it's the same thing.

00:01:13.049 --> 00:01:20.420
When we are reading, for example,
normal conversation we can read it very fast.

00:01:20.420 --> 00:01:26.490
But when we are reading technical content
then we go a little slower.

00:01:26.490 --> 00:01:27.869
We make more pauses.

00:01:27.869 --> 00:01:29.219
<v Screen reader> Accessible University.

00:01:29.219 --> 00:01:30.219
One.

00:01:30.219 --> 00:01:32.979
<v Hadi> I have slowed down
my screen reader program.

00:01:32.979 --> 00:01:34.210
<v Screen reader> Banner.

00:01:34.210 --> 00:01:35.570
Heading level one
graphic Accessible University.

00:01:35.570 --> 00:01:36.570
Banner end.

00:01:36.570 --> 00:01:39.579
<v Hadi> But if it is, for example,
about email I can go...

00:01:39.579 --> 00:01:41.100
<v Screen reader> Faster faster faster faster
faster

00:01:41.100 --> 00:01:45.100
[so fast that audio becomes unintelligible].

00:01:45.100 --> 00:01:47.240
<v Hadi> I can go that fast.

00:01:47.240 --> 00:01:50.479
<v Narrator> But it’s not enough
for Hadi to have a screen reader.

00:01:50.479 --> 00:01:53.299
Websites must be designed accessibly
in order for the screen reader

00:01:53.300 --> 00:01:56.580
to provide a full experience
of the webpage.

00:01:56.580 --> 00:02:01.040
<v Hadi> I would like
to show you two pages

00:02:01.049 --> 00:02:07.810
that are visually pretty much
consistent, identical.

00:02:07.810 --> 00:02:09.220
But one of them is accessible.

00:02:09.220 --> 00:02:11.420
One of them is not accessible.

00:02:11.420 --> 00:02:17.110
You will see in an inaccessible page
how difficult it is

00:02:17.110 --> 00:02:19.980
when those accessibility features
are not present.

00:02:24.720 --> 00:02:25.720
<v Hadi> This is the...

00:02:25.720 --> 00:02:27.000
<v Screen reader> Accessible University

00:02:27.000 --> 00:02:29.840
<v Hadi> This is the
accessible version of

00:02:29.860 --> 00:02:34.720
a fictional university that
we have developed here.

00:02:34.720 --> 00:02:38.050
We call that Accessible University.

00:02:38.050 --> 00:02:40.270
Here for example,
on this accessible page,

00:02:40.270 --> 00:02:45.480
I can ask my screen reader to show me
the major components of the page.

00:02:45.480 --> 00:02:46.860
<v Screen reader> Document Regions Dialog.

00:02:46.860 --> 00:02:47.860
Regions tree view.

00:02:47.860 --> 00:02:50.160
<v Hadi> It tells me
we have a banner section.

00:02:50.160 --> 00:02:51.160
<v Screen reader> Main menu navigation

00:02:51.160 --> 00:02:53.150
<v Hadi> We have a main menu section...

00:02:53.150 --> 00:02:54.150
<v Screen reader> Main

00:02:54.150 --> 00:02:55.350
<v Hadi> And the main body...

00:02:55.350 --> 00:02:56.350
<v Screen reader> Apply Now form.

00:02:56.350 --> 00:02:57.780
<v Hadi> There is another region...

00:02:57.780 --> 00:02:58.830
<v Screen reader> content information

00:02:58.830 --> 00:03:04.080
<v Hadi> and content information
which is the same as footer section.

00:03:04.080 --> 00:03:07.980
So assuming the page has
been developed correctly,

00:03:07.980 --> 00:03:12.980
I have good idea about the
major components of the page.

00:03:17.740 --> 00:03:25.500
<v Hadi> Let me now go to see this page,
the inaccessible version of this page.

00:03:25.500 --> 00:03:28.260
<v Screen reader> Home Page,
Accessible University

00:03:28.260 --> 00:03:33.900
<v Hadi> This looks pretty much the same
as the other one, the accessible version

00:03:33.900 --> 00:03:39.990
but here when I ask my screen reader
to convey the major components...

00:03:39.990 --> 00:03:40.990
<v Screen reader> No region found

00:03:40.990 --> 00:03:43.350
<v Hadi> It said "no region found."

00:03:43.350 --> 00:03:52.760
So for me, practically,
I have to read from top to bottom.

00:03:52.760 --> 00:03:55.650
If those accessibility
features are not present,

00:03:55.650 --> 00:03:58.590
everything has the same weight.

00:03:58.590 --> 00:04:04.430
So we do not, there is no way
for us to say that

00:04:04.430 --> 00:04:09.010
where a major section starts
or where it ends.

00:04:09.010 --> 00:04:13.070
It is really not just the
fact reading the content,

00:04:13.070 --> 00:04:15.110
it is also about navigation.

00:04:15.110 --> 00:04:20.549
We have to discover the page

00:04:20.549 --> 00:04:26.800
and then that is the most
time-consuming problem.

00:04:26.800 --> 00:04:32.979
Once you know where you are,
what you are reading,

00:04:32.979 --> 00:04:36.840
then it is usually fine.

00:04:36.840 --> 00:04:39.870
But the discovery process
or navigation process

00:04:39.870 --> 00:04:44.740
is the most complicated process
in an accessibility field.

00:04:44.740 --> 00:04:49.379
In order to do it I have to
read from top to bottom.

00:04:49.379 --> 00:04:51.570
Whereas in the accessible version,

00:04:51.570 --> 00:04:55.460
I could easily see what
the major components were

00:04:55.460 --> 00:05:02.160
and then select the desired ones
and move to that section quickly.

00:05:02.180 --> 00:05:04.900
<v Screen reader> Leaving menus.
Heading List dialog. Headings List view.

00:05:04.920 --> 00:05:13.300
<v Hadi> Headings is also
a means to get information

00:05:13.300 --> 00:05:19.300
about the structure
of the content.

00:05:20.640 --> 00:05:24.940
It gives me a good understanding,
a good overview, about

00:05:24.949 --> 00:05:29.409
the major or minor
components of the content.

00:05:29.409 --> 00:05:30.510
So I see that here...

00:05:30.510 --> 00:05:32.419
<v Screen reader> Welcome 2.

00:05:32.419 --> 00:05:33.969
Featured Stories Slideshow 2.

00:05:33.969 --> 00:05:35.310
Accessible University 1.

00:05:35.310 --> 00:05:41.490
<v Hadi> Accessible University itself
is a Heading 1 and under that we have...

00:05:41.490 --> 00:05:42.490
<v Screen reader> Feature Stories.

00:05:42.490 --> 00:05:45.010
<v Hadi> Feature Stories,
which is Heading 2.

00:05:45.010 --> 00:05:48.360
It automatically conveys
the information

00:05:48.360 --> 00:05:52.949
that this section is a
subsection of the heading above.

00:05:52.949 --> 00:05:58.389
You know you will see also
that overall get an outline

00:05:58.389 --> 00:06:02.190
of the page and the
major sections of that.

00:06:02.190 --> 00:06:05.940
That is the difference between
accessible and inaccessible.

00:06:07.700 --> 00:06:12.040
<v Sheryl> That screen reader can only access
the text that's presented on the screen

00:06:12.050 --> 00:06:16.949
and so if someone just scans in a document
and puts an image up on their website

00:06:16.949 --> 00:06:19.990
that screen reader is not going
to be able to read that content.

00:06:19.990 --> 00:06:25.449
And so the web developer in that case
needs to know to create all their materials

00:06:25.449 --> 00:06:28.199
so that they're accessible
to a screen reader, in other words

00:06:28.199 --> 00:06:34.249
so they can access the text for that
screen reader to read it aloud

00:06:34.249 --> 00:06:35.840
to a person who's blind.

00:06:35.920 --> 00:06:36.820
<v Screen reader> Enter.

00:06:36.830 --> 00:06:37.830
Message from.

00:06:37.830 --> 00:06:38.830
Hi All.

00:06:38.830 --> 00:06:40.389
<v Sheryl> It’s essential that
people with disabilities

00:06:40.389 --> 00:06:44.800
have access to assistive technology
but that’s not the end of the story.

00:06:44.800 --> 00:06:47.940
In order for them to be
effective users of technology,

00:06:47.940 --> 00:06:49.809
the technology that
other people develop

00:06:49.809 --> 00:06:54.969
like websites and software
and PDF files and so forth

00:06:54.969 --> 00:06:56.430
must be designed in such a way

00:06:56.430 --> 00:06:59.500
that they can use it with
their assistive technology.

