WEBVTT

00:00:00.000 --> 00:03.480
It often feels like accessibility is seen as a compliance checklist.

00:03.480 --> 00:05.400
It is not because, ultimately,

00:05.400 --> 00:07.760
and in fact, if we think about what it really is,

00:07.760 --> 00:09.000
it's kind of an effort

00:09.000 --> 00:11.840
to keep a digital experience meaningful and usable,

00:11.840 --> 00:14.360
and do the right thing, do the design work.

00:14.360 --> 00:17.160
But on the other hand, I often want to kind of mention that

00:17.160 --> 00:19.080
when we actually start designing and building,

00:19.080 --> 00:21.040
if we look at the blank canvas, right?

00:21.040 --> 00:22.320
And you just put text in it,

00:22.320 --> 00:23.480
and if you look into wireframes

00:23.480 --> 00:26.080
that we are creating, or maybe low-fidelity mockups or so,

00:26.080 --> 00:29.080
very often we might not be considering accessibility there,

00:29.080 --> 00:30.640
which is, of course, a problem.

00:30.640 --> 00:33.240
But the issue is whenever you start building, right? Whenever

00:33.240 --> 00:36.040
you start designing, we start with accessibility.

00:36.040 --> 00:38.080
We don't want the text to be illegible.

00:38.080 --> 00:39.160
We wanted to just work.

00:39.160 --> 00:39.960
And on the other hand, when we think about accessibility, it's

00:39.960 --> 00:41.680
And on the other hand, when we think about accessibility, it's

00:41.680 --> 00:45.160
not just something that we need to add; it's just something we need to retain.

00:45.160 --> 00:47.440
It is not something we add to a website, but something

00:47.440 --> 00:48.760
we start with initially

00:48.760 --> 00:51.600
and risk losing with every single change that we make.

00:51.600 --> 00:55.760
So, our task as designers is to retain it throughout the entire design process.