WEBVTT - Making Tech Accessible

0:00:04.120 --> 0:00:07.160
<v Speaker 1>Get in touch with technology with tech Stuff from how

0:00:07.200 --> 0:00:13.760
<v Speaker 1>stuff works dot com. Hey there, and welcome to tech Stuff.

0:00:13.800 --> 0:00:16.520
<v Speaker 1>I'm your host, Jonathan Strickland. I'm an executive producer with

0:00:16.560 --> 0:00:19.759
<v Speaker 1>how stuff Works, and I love all things tech. And

0:00:19.920 --> 0:00:24.000
<v Speaker 1>one of my favorite things about technology is how we

0:00:24.040 --> 0:00:28.640
<v Speaker 1>can provide people with capabilities they otherwise might not possess

0:00:28.840 --> 0:00:31.880
<v Speaker 1>or might not be able to tap into. For all

0:00:31.960 --> 0:00:35.480
<v Speaker 1>walks of life. It can open up access to incredible

0:00:35.600 --> 0:00:40.120
<v Speaker 1>volumes of knowledge and expertise. It can boost our ability

0:00:40.200 --> 0:00:43.279
<v Speaker 1>to do everything from travel faster to figuring out what

0:00:43.360 --> 0:00:46.199
<v Speaker 1>book we should read next. And it can enhance the

0:00:46.280 --> 0:00:51.200
<v Speaker 1>lives of people who live with injuries, disabilities, or other

0:00:51.240 --> 0:00:53.880
<v Speaker 1>factors that make our world a little more challenging to

0:00:53.960 --> 0:00:57.320
<v Speaker 1>navigate for them than for other people. Which brings us

0:00:57.320 --> 0:01:00.760
<v Speaker 1>to today's topic, which is a request from tech stuff.

0:01:00.760 --> 0:01:04.560
<v Speaker 1>Listener can can ask me this quite some time ago,

0:01:04.600 --> 0:01:07.200
<v Speaker 1>so I apologize for how long it's taken me to

0:01:07.240 --> 0:01:10.679
<v Speaker 1>get to this. But Ken wanted to know about the development, design,

0:01:10.720 --> 0:01:15.720
<v Speaker 1>and deployment of accessible technology. That is, technology meant to

0:01:15.760 --> 0:01:21.880
<v Speaker 1>provide accessibility to people who might otherwise have a challenge

0:01:21.920 --> 0:01:25.800
<v Speaker 1>accessing that technology. They might have a visual impairment or

0:01:25.959 --> 0:01:30.240
<v Speaker 1>hearing impairment, or health condition or injury that prevents them

0:01:30.280 --> 0:01:33.440
<v Speaker 1>from accessing technology the way other people do. So this

0:01:33.480 --> 0:01:36.880
<v Speaker 1>episode is all about making tech accessible, and this is

0:01:36.959 --> 0:01:42.520
<v Speaker 1>just an overview because accessible tech covers an enormous spectrum

0:01:42.560 --> 0:01:45.800
<v Speaker 1>of approaches and technologies. So I may go into further

0:01:45.880 --> 0:01:49.040
<v Speaker 1>detail on some of these in future episodes, but this

0:01:49.080 --> 0:01:53.840
<v Speaker 1>is kind of a very high level look at the

0:01:53.840 --> 0:01:56.880
<v Speaker 1>the whole idea of accessible technology, with just a few

0:01:57.000 --> 0:02:00.840
<v Speaker 1>examples thrown in. So I want to stress that this

0:02:00.920 --> 0:02:03.680
<v Speaker 1>is something that can be really difficult to do well.

0:02:04.240 --> 0:02:07.080
<v Speaker 1>And part of that is just because the designers and

0:02:07.160 --> 0:02:10.680
<v Speaker 1>engineers who are responsible for making the hardware and software

0:02:10.720 --> 0:02:14.440
<v Speaker 1>that we rely upon might not have the same challenges

0:02:15.000 --> 0:02:18.000
<v Speaker 1>as some of the people who will be using that

0:02:18.040 --> 0:02:22.959
<v Speaker 1>technology do, and so those designers and engineers might make

0:02:23.160 --> 0:02:26.720
<v Speaker 1>assumptions about how that tech needs to be used, and

0:02:26.800 --> 0:02:31.760
<v Speaker 1>sometimes those assumptions can exclude people who have these problems,

0:02:31.840 --> 0:02:36.160
<v Speaker 1>these issues, these disabilities, these challenges. I don't want to

0:02:36.320 --> 0:02:39.600
<v Speaker 1>classify everything as a problem. I'm just saying, you know,

0:02:39.840 --> 0:02:44.799
<v Speaker 1>people who are incapable of accessing the technology the way

0:02:45.040 --> 0:02:49.560
<v Speaker 1>everyone else tends to do. The intent these designers might

0:02:49.600 --> 0:02:52.760
<v Speaker 1>have is to help, and even if they're trying to

0:02:52.800 --> 0:02:57.480
<v Speaker 1>design assistive technology specifically for that purpose, the execution can

0:02:57.560 --> 0:03:01.160
<v Speaker 1>sometimes be clunky or inelegant, or it fails to make

0:03:01.200 --> 0:03:04.160
<v Speaker 1>the technology more accessible at all. I think it's of

0:03:04.200 --> 0:03:08.160
<v Speaker 1>critical importance that designers work with people whose life experience

0:03:08.400 --> 0:03:15.079
<v Speaker 1>mirrors that of those who actually uh do have those challenges, right, So,

0:03:15.200 --> 0:03:18.800
<v Speaker 1>if you're trying to design accessibility technology to help with

0:03:18.840 --> 0:03:22.080
<v Speaker 1>people who have visual impairments, it's important to have people

0:03:22.160 --> 0:03:25.359
<v Speaker 1>working with you on the development who also have those

0:03:25.400 --> 0:03:29.280
<v Speaker 1>visual impairments to give you real time feedback on designs

0:03:29.360 --> 0:03:32.799
<v Speaker 1>to make sure that the technology you're creating actually does

0:03:32.840 --> 0:03:36.360
<v Speaker 1>what was intended. So in the United States, there are

0:03:36.360 --> 0:03:40.400
<v Speaker 1>no laws that mandate accessibility with tech hardware. In general,

0:03:40.840 --> 0:03:45.000
<v Speaker 1>no company is legally required to make certain the technology

0:03:45.040 --> 0:03:48.720
<v Speaker 1>it creates is accessible to those who are differently abled,

0:03:49.360 --> 0:03:52.200
<v Speaker 1>and there's a lack of standards and expertise in the

0:03:52.240 --> 0:03:56.360
<v Speaker 1>field in general, a lack of awareness and education in

0:03:56.400 --> 0:04:00.000
<v Speaker 1>the field, and that complicates matters. It is a little

0:04:00.120 --> 0:04:03.160
<v Speaker 1>different if you happen to work for the federal government

0:04:03.160 --> 0:04:08.200
<v Speaker 1>in the United States, there there is a legal basis

0:04:08.280 --> 0:04:12.120
<v Speaker 1>for accessibility, but only if you're working for the federal government.

0:04:12.440 --> 0:04:16.520
<v Speaker 1>Section five oh eight Standards for Electronic and Information Technology

0:04:16.640 --> 0:04:22.960
<v Speaker 1>states that quote, when federal agencies develop, procure, maintain, or

0:04:23.160 --> 0:04:28.279
<v Speaker 1>use electronic and information technology, federal employees with disabilities have

0:04:28.480 --> 0:04:32.520
<v Speaker 1>access to and use of information and data that is

0:04:32.600 --> 0:04:36.400
<v Speaker 1>comparable to the access and use by federal employees who

0:04:36.480 --> 0:04:41.120
<v Speaker 1>are not individuals with disabilities, unless and undoe burden would

0:04:41.160 --> 0:04:44.080
<v Speaker 1>be imposed on the agency end quote. So it's saying,

0:04:44.480 --> 0:04:50.719
<v Speaker 1>anytime you're going to be uh incorporating technology into a

0:04:50.839 --> 0:04:55.680
<v Speaker 1>federal agency, there must be consideration put toward making that

0:04:55.800 --> 0:05:00.159
<v Speaker 1>accessible to people who have disabilities. But that puts the

0:05:00.160 --> 0:05:03.920
<v Speaker 1>burden more on the agency than the companies that are

0:05:03.960 --> 0:05:07.520
<v Speaker 1>making the technology, Right Like, unless the federal agency is

0:05:07.560 --> 0:05:11.599
<v Speaker 1>making its own technology, it's outsourcing that. And when it

0:05:11.600 --> 0:05:14.479
<v Speaker 1>outsources it, it may mean that the agency has to

0:05:15.000 --> 0:05:18.320
<v Speaker 1>take a very close look at the different competing products

0:05:18.360 --> 0:05:20.680
<v Speaker 1>that are on the market, and it may very well

0:05:20.720 --> 0:05:24.159
<v Speaker 1>mean that the federal agency will make a choice of

0:05:24.200 --> 0:05:30.440
<v Speaker 1>a product not because it was the best cost for

0:05:30.600 --> 0:05:34.280
<v Speaker 1>what they needed to do, but because it fit this

0:05:34.480 --> 0:05:38.640
<v Speaker 1>other requirement more than the competitors did. It does create

0:05:38.640 --> 0:05:42.080
<v Speaker 1>an incentive. But this is just a policy that only

0:05:42.839 --> 0:05:45.760
<v Speaker 1>applies to people who work for the federal government. It

0:05:45.800 --> 0:05:48.680
<v Speaker 1>doesn't apply to state governments or local governments, and it

0:05:48.720 --> 0:05:52.960
<v Speaker 1>doesn't apply to consumer products in general. But things are

0:05:53.000 --> 0:05:57.080
<v Speaker 1>not dire. There are a lot of companies, major companies

0:05:57.120 --> 0:05:59.520
<v Speaker 1>that are working very hard to make certain that the

0:05:59.560 --> 0:06:03.800
<v Speaker 1>technolog ology they create is accessible to people of all abilities.

0:06:04.560 --> 0:06:07.800
<v Speaker 1>More on those efforts in a bit. One other thing

0:06:07.839 --> 0:06:11.600
<v Speaker 1>I want to mention is that accessible technology is distantly

0:06:11.839 --> 0:06:17.000
<v Speaker 1>related to another concept called regionalization. This refers to adapting

0:06:17.040 --> 0:06:20.280
<v Speaker 1>technology so is meaningful and helpful to people in different

0:06:20.320 --> 0:06:23.480
<v Speaker 1>parts of the world. Again, people who speak a different

0:06:23.560 --> 0:06:26.440
<v Speaker 1>language than the developers do, or who live in a

0:06:26.520 --> 0:06:31.360
<v Speaker 1>culture that has different values and therefore different needs, different challenges.

0:06:31.680 --> 0:06:35.800
<v Speaker 1>Those require special consideration. Technology is not always a one

0:06:35.880 --> 0:06:39.200
<v Speaker 1>size fits all solutions. Sometimes you have to tweak things

0:06:39.320 --> 0:06:42.760
<v Speaker 1>for the end user. And I'll probably do a dedicated

0:06:42.800 --> 0:06:45.560
<v Speaker 1>episode about regionalization in the future because there's a lot

0:06:45.640 --> 0:06:50.240
<v Speaker 1>of different aspects to that as well, from software to hardware.

0:06:50.520 --> 0:06:54.320
<v Speaker 1>But let's go back to accessibility. I'd like to quote

0:06:54.680 --> 0:06:58.719
<v Speaker 1>the organization earn E a r N that stands for

0:06:58.839 --> 0:07:03.520
<v Speaker 1>employer Assistant and Resource Network on disability inclusion, as they

0:07:03.600 --> 0:07:07.040
<v Speaker 1>lay out in their web page about technological accessibility quote

0:07:07.360 --> 0:07:11.480
<v Speaker 1>when talking about technology, accessible means tools that can be

0:07:11.600 --> 0:07:15.920
<v Speaker 1>used successfully by people with a wide range of abilities

0:07:16.000 --> 0:07:20.520
<v Speaker 1>and disabilities. When technology is accessible, each user is able

0:07:20.560 --> 0:07:23.040
<v Speaker 1>to interact with it in ways that work best for

0:07:23.240 --> 0:07:28.400
<v Speaker 1>him or her. Accessible technology is either directly accessible, whereby

0:07:28.440 --> 0:07:34.000
<v Speaker 1>it is usable without additional assistive technology a t or

0:07:34.000 --> 0:07:37.880
<v Speaker 1>it is compatible with a system of technology. For example,

0:07:37.920 --> 0:07:40.880
<v Speaker 1>a mobile smartphone with a built in screen reader is

0:07:40.960 --> 0:07:44.840
<v Speaker 1>directly accessible, whereas a website that can be navigated effectively

0:07:44.880 --> 0:07:48.800
<v Speaker 1>by people with visual impairments using a screen reader is

0:07:48.840 --> 0:07:53.000
<v Speaker 1>a syste of technology compatible. Now, another thing I want

0:07:53.080 --> 0:07:57.720
<v Speaker 1>to mention early on is another tool called edge, which

0:07:57.720 --> 0:08:00.680
<v Speaker 1>in North America is a technology assessment tool developed by

0:08:00.720 --> 0:08:05.360
<v Speaker 1>the Urban Libraries Council. The ULC creates a place for

0:08:05.480 --> 0:08:09.600
<v Speaker 1>libraries to share and learn from best practices in numerous

0:08:09.640 --> 0:08:13.120
<v Speaker 1>fields that relate to libraries and communities. And to all

0:08:13.160 --> 0:08:16.840
<v Speaker 1>you librarians out there, thank you. You guys are awesome.

0:08:17.400 --> 0:08:20.720
<v Speaker 1>And hey, a former tech stuff host is among your number.

0:08:21.760 --> 0:08:24.960
<v Speaker 1>One of our former tech stuff hosts is a librarian.

0:08:25.120 --> 0:08:28.760
<v Speaker 1>So back to edge and to talk about what's important

0:08:28.800 --> 0:08:33.720
<v Speaker 1>here for this podcast. The Edge Toolkit includes many different

0:08:33.760 --> 0:08:37.000
<v Speaker 1>benchmarks to guide libraries in making the best use of

0:08:37.000 --> 0:08:41.120
<v Speaker 1>technology in order to help communities, and that includes everything

0:08:41.160 --> 0:08:45.280
<v Speaker 1>from training people to become more tech savvy, to increase

0:08:45.360 --> 0:08:50.040
<v Speaker 1>digital literacy, provide access to the Internet, and other valuable

0:08:50.120 --> 0:08:56.560
<v Speaker 1>services that are absolutely crucial to interact with society today. So, uh,

0:08:57.080 --> 0:09:00.080
<v Speaker 1>it's it's very easy to get left behind if you

0:09:00.160 --> 0:09:04.760
<v Speaker 1>are not of a particular demographic, right. I come from

0:09:04.800 --> 0:09:09.040
<v Speaker 1>a very rural part of Georgia. I live in Atlanta now,

0:09:09.080 --> 0:09:11.960
<v Speaker 1>but I come from a very rural community. When I

0:09:12.000 --> 0:09:14.480
<v Speaker 1>was growing up, it was extremely rural, to the point

0:09:14.480 --> 0:09:17.439
<v Speaker 1>where we had cattle farms and chicken farms around us,

0:09:17.960 --> 0:09:20.840
<v Speaker 1>and uh, you know, I was in a little subdivision,

0:09:20.880 --> 0:09:24.000
<v Speaker 1>so it wasn't like I was miles away from everybody,

0:09:24.040 --> 0:09:27.640
<v Speaker 1>but a lot of people didn't have access to technology.

0:09:27.720 --> 0:09:30.199
<v Speaker 1>And granted, the Internet was not really a big thing

0:09:30.240 --> 0:09:33.359
<v Speaker 1>when I was growing up. I'm old enough to predate

0:09:33.760 --> 0:09:38.720
<v Speaker 1>when the Internet was it was prevalent, but even to

0:09:38.800 --> 0:09:44.000
<v Speaker 1>this day, people in those communities don't necessarily have access

0:09:44.720 --> 0:09:47.160
<v Speaker 1>on a daily basis to the technology that a lot

0:09:47.200 --> 0:09:50.600
<v Speaker 1>of us take for granted and their local libraries act

0:09:50.840 --> 0:09:55.240
<v Speaker 1>as a community center and a source of contact for

0:09:55.280 --> 0:09:58.360
<v Speaker 1>that kind of technology. They can also serve as a

0:09:58.400 --> 0:10:01.960
<v Speaker 1>way for people to become more educated about that technology

0:10:02.040 --> 0:10:05.319
<v Speaker 1>so that they can make meaningful contributions in a world

0:10:05.360 --> 0:10:10.160
<v Speaker 1>that is increasingly reliant on that tech. And so libraries

0:10:10.200 --> 0:10:14.160
<v Speaker 1>are one of those points where people aren't being left

0:10:14.200 --> 0:10:17.319
<v Speaker 1>behind because they have the access to those libraries. This

0:10:17.360 --> 0:10:22.400
<v Speaker 1>is Jonathan on a soapbox saying libraries are really important more.

0:10:22.840 --> 0:10:26.040
<v Speaker 1>It's more than just checking out books, which by the way,

0:10:26.400 --> 0:10:30.520
<v Speaker 1>also really important, But it's more than that anyway. Let's

0:10:30.520 --> 0:10:33.120
<v Speaker 1>get back to the benchmarks. There's a specific one called

0:10:33.120 --> 0:10:38.240
<v Speaker 1>benchmark eleven that's about accessibility with technology. The core statement

0:10:38.280 --> 0:10:42.959
<v Speaker 1>for benchmark eleven is libraries ensure participation in digital technology

0:10:43.040 --> 0:10:47.080
<v Speaker 1>for people with disabilities. So to meet that benchmark, that

0:10:47.360 --> 0:10:52.400
<v Speaker 1>libraries should in fact also provide access to people who

0:10:52.400 --> 0:10:56.160
<v Speaker 1>have disabilities, provide access of technology to peopleho have disabilities.

0:10:56.679 --> 0:10:59.520
<v Speaker 1>The library must have at least one public terminal has

0:10:59.559 --> 0:11:02.920
<v Speaker 1>assisted of technology incorporated for the visually impaired. It has

0:11:02.960 --> 0:11:06.240
<v Speaker 1>to have a public terminal that is accessible for people

0:11:06.240 --> 0:11:09.600
<v Speaker 1>who have motor and dexterity impronments. It needs to have

0:11:09.640 --> 0:11:12.840
<v Speaker 1>a workstation that can accommodate people who are in a

0:11:12.840 --> 0:11:17.040
<v Speaker 1>wheelchair or other mobility vehicle, that kind of thing, etcetera.

0:11:17.160 --> 0:11:21.560
<v Speaker 1>So it needs to have these points of access for

0:11:21.679 --> 0:11:24.040
<v Speaker 1>people who otherwise would be left out. And I think

0:11:24.080 --> 0:11:26.560
<v Speaker 1>it's valuable to look at the edge tool, not just

0:11:26.600 --> 0:11:30.880
<v Speaker 1>to acknowledge how important libraries are and uh and because

0:11:31.120 --> 0:11:32.840
<v Speaker 1>me it's clear that I think they are very important,

0:11:32.920 --> 0:11:36.160
<v Speaker 1>but because they lay out goals, they get the conversation

0:11:36.320 --> 0:11:39.959
<v Speaker 1>rolling about making technology accessible to all people. Now, some

0:11:40.080 --> 0:11:44.000
<v Speaker 1>areas of tech are ahead of the game compared to others,

0:11:44.040 --> 0:11:48.240
<v Speaker 1>like the world Wide Web. So the Worldwide Web Consortium

0:11:48.440 --> 0:11:52.520
<v Speaker 1>or W three C formed back in Nino with the

0:11:52.640 --> 0:11:55.960
<v Speaker 1>goal to develop standardized protocols for the evolution of the

0:11:55.960 --> 0:12:00.040
<v Speaker 1>Web to make sure that it moved forward in a

0:12:00.080 --> 0:12:06.240
<v Speaker 1>way that was uh easily distributed and developed so that

0:12:06.320 --> 0:12:10.120
<v Speaker 1>you didn't have a bunch of splintered experiences. They wanted

0:12:10.160 --> 0:12:13.439
<v Speaker 1>something that was going to be interoperable across the entire web.

0:12:13.960 --> 0:12:16.960
<v Speaker 1>One of the four domains that covers is the Web

0:12:17.040 --> 0:12:21.240
<v Speaker 1>Accessibility Initiative or w a I, and that has five

0:12:21.280 --> 0:12:25.440
<v Speaker 1>primary purposes to ensure that web tech supports accessibility, to

0:12:25.520 --> 0:12:29.960
<v Speaker 1>develop guidelines for accessibility, to develop tools to evaluate and

0:12:30.000 --> 0:12:34.960
<v Speaker 1>facilitate accessibility, to conduct education and outreach, and finally to

0:12:35.000 --> 0:12:38.080
<v Speaker 1>coordinate with research and development. So as such, the W

0:12:38.200 --> 0:12:41.880
<v Speaker 1>three C has issued guidelines for Web content accessibility to

0:12:41.920 --> 0:12:45.559
<v Speaker 1>help ensure that developers make sites and services that are

0:12:45.559 --> 0:12:48.720
<v Speaker 1>in fact accessible for a broad range of people. And

0:12:48.720 --> 0:12:54.400
<v Speaker 1>those guidelines are pretty exhaustive. They have sixty five checkpoints

0:12:54.440 --> 0:12:59.800
<v Speaker 1>and each checkpoint has an assigned priority between one and three.

0:13:00.120 --> 0:13:03.679
<v Speaker 1>A Priority one checkpoint is one that tackles a barrier

0:13:04.040 --> 0:13:07.600
<v Speaker 1>that would make access impossible for one or more groups

0:13:07.679 --> 0:13:11.559
<v Speaker 1>of people, so it identifies something that could potentially make

0:13:11.640 --> 0:13:17.720
<v Speaker 1>technology completely inaccessible too an entire group. Priorities two and

0:13:17.840 --> 0:13:20.559
<v Speaker 1>three mark challenges that would make it difficult, but not

0:13:20.640 --> 0:13:23.760
<v Speaker 1>necessarily impossible, for one or more groups to access the

0:13:23.760 --> 0:13:27.560
<v Speaker 1>web content. And this is a big issue UH in general,

0:13:27.679 --> 0:13:30.440
<v Speaker 1>just the idea of accessibility. A two thousand eleven report

0:13:30.480 --> 0:13:34.440
<v Speaker 1>from the University of New Hampshire's Institute on Disability saw

0:13:34.520 --> 0:13:38.400
<v Speaker 1>that people with disabilities make up nineteen of the United

0:13:38.440 --> 0:13:44.000
<v Speaker 1>States population. Now that report points out that if people

0:13:44.080 --> 0:13:48.000
<v Speaker 1>with disabilities were recognized as a minority group, that would

0:13:48.000 --> 0:13:51.640
<v Speaker 1>actually be the largest minority group in the United States.

0:13:52.200 --> 0:13:57.559
<v Speaker 1>It represents a large population of people, and without these

0:13:58.320 --> 0:14:02.960
<v Speaker 1>UH considerations for excess stability, that would be nearly one

0:14:03.120 --> 0:14:07.120
<v Speaker 1>fifth of all citizens of the United States left out

0:14:08.160 --> 0:14:11.760
<v Speaker 1>of being able to access that technology. So that's why

0:14:11.800 --> 0:14:14.920
<v Speaker 1>this is of critical importance. When I come back, I'll

0:14:14.960 --> 0:14:18.520
<v Speaker 1>give you some more examples of some of the types

0:14:18.640 --> 0:14:22.040
<v Speaker 1>of assistive technology and accessible technology that are out there,

0:14:22.320 --> 0:14:24.840
<v Speaker 1>But first let's take a quick break to thank our sponsor.

0:14:32.280 --> 0:14:35.680
<v Speaker 1>For people who have visual impairments, there are a variety

0:14:36.000 --> 0:14:39.240
<v Speaker 1>of assistive technologies and they range from ways to help

0:14:39.240 --> 0:14:42.720
<v Speaker 1>people with limited vision to ways to help people who

0:14:42.800 --> 0:14:46.600
<v Speaker 1>have no site at all. And one of the ones

0:14:46.640 --> 0:14:52.160
<v Speaker 1>that is a fairly simple implementation is screen magnification systems,

0:14:52.160 --> 0:14:56.400
<v Speaker 1>and these are digital screen magnification systems. They enlarge text

0:14:56.480 --> 0:14:58.680
<v Speaker 1>and graphics on the computer screen make it easier for

0:14:58.760 --> 0:15:02.440
<v Speaker 1>people who have paired vision to read and see things.

0:15:02.480 --> 0:15:06.160
<v Speaker 1>So it does act like a magnifying class. Typically, a

0:15:06.240 --> 0:15:09.880
<v Speaker 1>user will move a cursor over the page using keyboard

0:15:09.880 --> 0:15:13.680
<v Speaker 1>strokes or a mouse, and wherever the cursor is, that's

0:15:13.720 --> 0:15:15.840
<v Speaker 1>the area that will increase in size to make it

0:15:15.840 --> 0:15:18.480
<v Speaker 1>easier to see, so you can scan across the page

0:15:18.520 --> 0:15:20.960
<v Speaker 1>as if you're using a magnifying glass and you're reading

0:15:21.160 --> 0:15:24.920
<v Speaker 1>text on a piece of paper. Some systems also will

0:15:24.960 --> 0:15:28.480
<v Speaker 1>include things like a a an option to scroll down

0:15:28.520 --> 0:15:31.520
<v Speaker 1>the page at a predefined rate, so that you don't

0:15:31.520 --> 0:15:34.000
<v Speaker 1>have to just sit there and and babysit the mouse

0:15:34.160 --> 0:15:38.400
<v Speaker 1>and or keyboard and move the cursor manually. It'll move

0:15:38.480 --> 0:15:41.360
<v Speaker 1>automatically at a speed that you've already determined, so that

0:15:41.440 --> 0:15:44.600
<v Speaker 1>you can just read along. Many will also offer a

0:15:44.640 --> 0:15:49.440
<v Speaker 1>contrast adjustment so that the highlighted or magnified text or

0:15:49.480 --> 0:15:53.480
<v Speaker 1>image stands out more dramatically against the background. Here in

0:15:53.600 --> 0:15:57.800
<v Speaker 1>Georgia are electronic voting systems have that kind of capability

0:15:57.840 --> 0:16:01.200
<v Speaker 1>built into them, which is a good thing. But pretty

0:16:01.280 --> 0:16:07.080
<v Speaker 1>much everything else about those electronic voting kiosks isn't so great. Uh.

0:16:07.120 --> 0:16:11.440
<v Speaker 1>They are a very old and vulnerable technology, but that's

0:16:11.440 --> 0:16:15.480
<v Speaker 1>a matter for another podcast. The accessibility features of that

0:16:15.520 --> 0:16:19.080
<v Speaker 1>technology are good, so I want to stress that's the

0:16:19.120 --> 0:16:22.040
<v Speaker 1>rest of it that may not be so great. Operating

0:16:22.040 --> 0:16:25.400
<v Speaker 1>systems like Windows, and it's not just Windows, just saying

0:16:25.440 --> 0:16:28.760
<v Speaker 1>Windows does have this have accessibility features that can adjust

0:16:28.840 --> 0:16:33.800
<v Speaker 1>font size, resolution, scroll bars, icons, color scheme, and more.

0:16:34.360 --> 0:16:38.640
<v Speaker 1>Mac Os has a similar series of options, all designed

0:16:39.000 --> 0:16:45.160
<v Speaker 1>to make use of that technology more uh well easier

0:16:45.280 --> 0:16:50.200
<v Speaker 1>for people who have visual impairments. Uh. Windows also or

0:16:50.280 --> 0:16:52.600
<v Speaker 1>vision impairments. I guess I should say visual impairments is

0:16:52.640 --> 0:16:55.680
<v Speaker 1>a improper way of saying it, but vision impairments. Windows

0:16:55.720 --> 0:16:59.280
<v Speaker 1>also has a screen magnifier feature built in. It's not

0:16:59.400 --> 0:17:01.560
<v Speaker 1>the only U BRING system to do this, but again

0:17:02.280 --> 0:17:07.400
<v Speaker 1>it has that. There are also screen reader technologies. Essentially

0:17:07.400 --> 0:17:09.600
<v Speaker 1>that gets down to sort of a text to speech

0:17:09.640 --> 0:17:12.720
<v Speaker 1>program that can read out text to a user. I've

0:17:12.760 --> 0:17:15.840
<v Speaker 1>definitely engaged that by accident in the past. Found it

0:17:15.880 --> 0:17:19.720
<v Speaker 1>pretty interesting that it was a integrated feature. Now I

0:17:19.760 --> 0:17:21.719
<v Speaker 1>don't need a screen reader, but the fact that it

0:17:21.800 --> 0:17:24.119
<v Speaker 1>was built into the operating system did impress me. It

0:17:24.160 --> 0:17:27.080
<v Speaker 1>meant that the designers were thinking ahead and wanted to

0:17:27.119 --> 0:17:30.199
<v Speaker 1>have that capability to be standard and not something a

0:17:30.280 --> 0:17:32.920
<v Speaker 1>user would need to add on as an option. Apple

0:17:33.000 --> 0:17:36.439
<v Speaker 1>has a feature called voice over. It's frequently cited as

0:17:36.480 --> 0:17:41.679
<v Speaker 1>an innovative assistive technology. Voiceover gives auditory descriptions of what

0:17:41.960 --> 0:17:44.520
<v Speaker 1>is on a screen, including all the different on screen

0:17:44.560 --> 0:17:47.600
<v Speaker 1>elements such as on screen controls, and it can work

0:17:47.600 --> 0:17:50.920
<v Speaker 1>with apps as well. Now that requires developers to actually

0:17:50.960 --> 0:17:54.119
<v Speaker 1>tag the various elements in their apps so that the

0:17:54.200 --> 0:17:57.800
<v Speaker 1>voiceover function can effectively relay that information to the user.

0:17:57.880 --> 0:18:00.360
<v Speaker 1>So it's kind of like meta information at specific meta

0:18:00.400 --> 0:18:04.399
<v Speaker 1>information for voiceover. So, for example, a play button on

0:18:04.440 --> 0:18:07.639
<v Speaker 1>an app that would initiate a sound would need an

0:18:07.640 --> 0:18:10.639
<v Speaker 1>appropriate tag so that the voiceover system could alert the

0:18:10.720 --> 0:18:13.679
<v Speaker 1>user about the function and relative position of the button.

0:18:14.080 --> 0:18:17.680
<v Speaker 1>Then there are things like refreshable brail displays that provides

0:18:17.760 --> 0:18:22.160
<v Speaker 1>access to information on a computer display through brail. Uh.

0:18:22.200 --> 0:18:24.080
<v Speaker 1>And this time we're talking about a computer display that's

0:18:24.080 --> 0:18:29.119
<v Speaker 1>not necessarily it's it's not a screen. It's typically a

0:18:29.119 --> 0:18:33.600
<v Speaker 1>a flat surface that has little holes through which retractable

0:18:33.640 --> 0:18:37.800
<v Speaker 1>pins rounded pins can extend up and then form characters

0:18:37.800 --> 0:18:41.439
<v Speaker 1>in brail. And a typical brail display can show around

0:18:41.480 --> 0:18:44.920
<v Speaker 1>eighty characters at a time. It's refreshable because the pins

0:18:44.960 --> 0:18:48.240
<v Speaker 1>can fall or rise up and form different characters, and

0:18:48.280 --> 0:18:50.760
<v Speaker 1>they'll do this as you move a cursor around the screen,

0:18:50.880 --> 0:18:54.119
<v Speaker 1>So you can scan over a screen and these characters

0:18:54.160 --> 0:18:56.680
<v Speaker 1>will change under your fingertips and you can read Brail

0:18:56.760 --> 0:18:59.119
<v Speaker 1>that way. The history of Brail, by the way, is

0:18:59.119 --> 0:19:01.280
<v Speaker 1>pretty darn interesting all on its own, so here's a

0:19:01.359 --> 0:19:06.000
<v Speaker 1>quick tangent about the history of Braille. Louis Braill was

0:19:06.160 --> 0:19:10.640
<v Speaker 1>a young man in France born in eighteen o nine

0:19:11.119 --> 0:19:14.320
<v Speaker 1>who suffered a childhood injury at the age of three,

0:19:14.440 --> 0:19:18.399
<v Speaker 1>and it left him blind. He attended school and he

0:19:18.440 --> 0:19:21.320
<v Speaker 1>would listen very carefully to lessons. He was a good student,

0:19:22.040 --> 0:19:25.199
<v Speaker 1>and then went on to attend the Royal Institution for

0:19:25.280 --> 0:19:29.639
<v Speaker 1>Blind Youths in Paris UH and that school owned a

0:19:29.680 --> 0:19:33.000
<v Speaker 1>few books that had raised print on them. That raised

0:19:33.000 --> 0:19:36.560
<v Speaker 1>print was essentially created by stamping pages with copper wire

0:19:36.640 --> 0:19:39.359
<v Speaker 1>that was bent in the shape of letters, so it

0:19:39.480 --> 0:19:44.040
<v Speaker 1>was just, you know, the letters of the alphabet UH

0:19:44.560 --> 0:19:48.879
<v Speaker 1>embossed essentially on pieces of paper. Braill heard a story

0:19:49.600 --> 0:19:54.200
<v Speaker 1>about a soldier named Captain Charles Barbier de la Sere.

0:19:54.880 --> 0:19:57.080
<v Speaker 1>He was a captain in the French army who had

0:19:57.119 --> 0:19:59.760
<v Speaker 1>developed a system of writing for soldiers so that they

0:19:59.800 --> 0:20:03.600
<v Speaker 1>could send and read messages even at nighttime without turning

0:20:03.600 --> 0:20:06.240
<v Speaker 1>on any lights, because a light would give away your position,

0:20:06.520 --> 0:20:11.320
<v Speaker 1>which in war time is not great. So this system

0:20:11.440 --> 0:20:16.280
<v Speaker 1>used raised dots and dashes on paper. You would create

0:20:16.320 --> 0:20:19.320
<v Speaker 1>these raised elements and then by running your finger across

0:20:19.400 --> 0:20:22.560
<v Speaker 1>you could read the message. So Braile decided to adopt

0:20:22.560 --> 0:20:25.639
<v Speaker 1>that method when developing his own system of writing. In

0:20:25.680 --> 0:20:29.280
<v Speaker 1>eighty nine, Louis published the first book written in Brail,

0:20:29.560 --> 0:20:31.840
<v Speaker 1>and he would later add some more characters to his

0:20:31.920 --> 0:20:36.679
<v Speaker 1>system to incorporate stuff like musical notation and mathematics, and

0:20:36.720 --> 0:20:39.600
<v Speaker 1>a system would be tweaked over the decades that followed.

0:20:40.320 --> 0:20:43.800
<v Speaker 1>It really only began to get widespread adoption well after

0:20:43.920 --> 0:20:47.520
<v Speaker 1>his death in eighteen fifty two. But flash forward to

0:20:47.640 --> 0:20:51.600
<v Speaker 1>nineteen seventy and a company called Pop and Meyer and

0:20:51.720 --> 0:20:55.199
<v Speaker 1>a man named Dr Werner Bolt of dortmun University in

0:20:55.200 --> 0:21:00.679
<v Speaker 1>Germany created a refreshable Brail display called Braile X. And

0:21:00.800 --> 0:21:02.840
<v Speaker 1>so it's like Brail with an X at the end.

0:21:03.320 --> 0:21:06.800
<v Speaker 1>It was a stand alone system for information storage and retrieval,

0:21:06.880 --> 0:21:09.359
<v Speaker 1>so it's not like it was a computer peripheral in itself.

0:21:10.160 --> 0:21:14.879
<v Speaker 1>Was a system that would allow you to create information

0:21:14.920 --> 0:21:17.639
<v Speaker 1>and store it in Brail, and to retrieve information and

0:21:17.680 --> 0:21:21.159
<v Speaker 1>have it displayed in Brail. When writing on the device,

0:21:21.480 --> 0:21:24.600
<v Speaker 1>you would assign a code word to that information, and

0:21:24.640 --> 0:21:27.200
<v Speaker 1>it was essentially a file name, so you could call

0:21:27.359 --> 0:21:29.840
<v Speaker 1>up a code word or file name and then retrieve

0:21:29.880 --> 0:21:33.200
<v Speaker 1>the information and read it in brail. It originally used

0:21:33.560 --> 0:21:36.840
<v Speaker 1>an audio cassette data storage system, so would store everything

0:21:36.840 --> 0:21:40.119
<v Speaker 1>on magnetic tape, and then later models would upgrade to

0:21:40.160 --> 0:21:43.359
<v Speaker 1>a floppy disk system. Later still it would include a

0:21:43.400 --> 0:21:45.639
<v Speaker 1>serial port which would allow the user to connect to

0:21:45.760 --> 0:21:49.199
<v Speaker 1>the device to other peripherals like a computer system or

0:21:49.240 --> 0:21:51.720
<v Speaker 1>a brail emboss or or brail printer, so you could

0:21:51.840 --> 0:21:55.440
<v Speaker 1>actually print your workout on paper. The first refreshable brail

0:21:55.480 --> 0:21:58.280
<v Speaker 1>display for users in the United States was the Versa

0:21:58.320 --> 0:22:00.879
<v Speaker 1>Brail that did not launch till night teen e two,

0:22:01.440 --> 0:22:06.080
<v Speaker 1>and the National Federation of the Blind released NFB Trands,

0:22:06.400 --> 0:22:10.320
<v Speaker 1>which was a brail translation program in nineteen eighty. That

0:22:10.359 --> 0:22:13.760
<v Speaker 1>program could translate text into brail and send it to

0:22:13.800 --> 0:22:17.840
<v Speaker 1>a special brail embosser or brail printer. That original program

0:22:17.840 --> 0:22:20.000
<v Speaker 1>sold for hundreds of dollars when it first came out,

0:22:20.000 --> 0:22:23.840
<v Speaker 1>but in nine its utility was considered so important that

0:22:23.920 --> 0:22:27.240
<v Speaker 1>the NFB released the software to the public domain. In

0:22:28.680 --> 0:22:34.119
<v Speaker 1>Dr Kenneth Yearnigan opened up the International Brail and Technology

0:22:34.200 --> 0:22:37.520
<v Speaker 1>Center for the Blind at the National Federation of the

0:22:37.560 --> 0:22:42.600
<v Speaker 1>Blind Headquarters, and that center evaluates assistive technology for the blind,

0:22:42.880 --> 0:22:45.399
<v Speaker 1>so it puts it to the test to make certain

0:22:45.440 --> 0:22:48.760
<v Speaker 1>that the technology does in fact help as opposed to

0:22:48.840 --> 0:22:53.119
<v Speaker 1>just become a frustration or or an impediment to using technology.

0:22:53.280 --> 0:22:55.400
<v Speaker 1>And as you would expect, this technology found its way

0:22:55.400 --> 0:22:59.560
<v Speaker 1>into other foreim factors, including portable devices. In fact, really

0:22:59.560 --> 0:23:01.879
<v Speaker 1>early and it found its way into portable devices. In

0:23:02.920 --> 0:23:06.639
<v Speaker 1>seven the Brail and Speak became an early forerunner of

0:23:06.680 --> 0:23:09.719
<v Speaker 1>the personal digital assistant, and this was all for the blind.

0:23:10.240 --> 0:23:13.280
<v Speaker 1>This became the first of a class of devices called

0:23:13.480 --> 0:23:17.399
<v Speaker 1>note takers, and it had a speaker and a six

0:23:17.480 --> 0:23:22.520
<v Speaker 1>key Brail keyboard, and it was made in Germany, so

0:23:22.560 --> 0:23:26.160
<v Speaker 1>it had a data system where it could speak to you.

0:23:26.720 --> 0:23:28.680
<v Speaker 1>And because it was made in Germany, the system actually

0:23:28.720 --> 0:23:30.800
<v Speaker 1>had a bit of a German accent and it synth

0:23:30.800 --> 0:23:32.800
<v Speaker 1>the size speech, which is kind of interesting. I watched

0:23:32.800 --> 0:23:36.000
<v Speaker 1>a video that played some of the audio from one

0:23:36.040 --> 0:23:40.080
<v Speaker 1>of these devices. Typing would involve pressing key combinations to

0:23:40.440 --> 0:23:43.359
<v Speaker 1>access options and type in letters and I could save

0:23:43.400 --> 0:23:46.000
<v Speaker 1>information and bring you back to it later. And this

0:23:46.080 --> 0:23:49.440
<v Speaker 1>was all before personal digital assistants would emerge. For cited

0:23:49.600 --> 0:23:52.960
<v Speaker 1>users there have been many note takers since that one

0:23:53.000 --> 0:23:57.200
<v Speaker 1>way back in There's been some cool pieces of technology

0:23:57.200 --> 0:24:00.600
<v Speaker 1>to incorporate brail displays over the years. One recent one

0:24:00.640 --> 0:24:02.600
<v Speaker 1>I've seen that I thought was pretty interesting was the

0:24:02.760 --> 0:24:06.679
<v Speaker 1>dot watch, which I think debuted in TV. It's a

0:24:06.720 --> 0:24:09.679
<v Speaker 1>smart watch with its own refreshable brail display. So it

0:24:09.720 --> 0:24:14.720
<v Speaker 1>looks like a big white watch face with a little

0:24:15.200 --> 0:24:18.680
<v Speaker 1>little round circles cut into the watch face which through

0:24:18.680 --> 0:24:23.960
<v Speaker 1>which the pens can extend and create the various characters

0:24:24.000 --> 0:24:29.280
<v Speaker 1>in brail. The watch thus can can display time, it

0:24:29.359 --> 0:24:32.880
<v Speaker 1>can alert you to messages that can actually spell out messages.

0:24:33.400 --> 0:24:36.320
<v Speaker 1>It's it's like a smart watch, and it's pretty nifty

0:24:36.320 --> 0:24:38.479
<v Speaker 1>and concept. I have no, well, no idea how well

0:24:38.520 --> 0:24:42.119
<v Speaker 1>it performs in the wild. I don't know if it

0:24:42.200 --> 0:24:46.280
<v Speaker 1>works as well as the concept UH would have you think,

0:24:46.720 --> 0:24:49.800
<v Speaker 1>but I love the idea. I hope it works as

0:24:49.800 --> 0:24:53.560
<v Speaker 1>well as the videos suggest it does, because I think

0:24:53.560 --> 0:24:57.960
<v Speaker 1>it's super cool to have a brail smart watch. Well,

0:24:57.960 --> 0:25:01.359
<v Speaker 1>I have a lot more to talk about with accessibility technology,

0:25:01.359 --> 0:25:03.359
<v Speaker 1>but first let's take another quick break to thank our

0:25:03.400 --> 0:25:14.920
<v Speaker 1>sponsors for the Heart of Hearing and the Deaf Community.

0:25:15.160 --> 0:25:20.960
<v Speaker 1>Assistive Technology can include things like captions and transcripts. Automatic

0:25:21.000 --> 0:25:25.200
<v Speaker 1>systems that generate captions and transcripts do exist. They typically

0:25:25.240 --> 0:25:30.399
<v Speaker 1>use speech recognition technology to analyze speech and try to

0:25:30.520 --> 0:25:35.040
<v Speaker 1>create text based on that. They are a variable quality.

0:25:35.400 --> 0:25:38.280
<v Speaker 1>I've seen some caption programs that are pretty good, and

0:25:38.280 --> 0:25:40.960
<v Speaker 1>I've seen others that end up telling a story that

0:25:41.000 --> 0:25:42.960
<v Speaker 1>turns out to be very different from the one that's

0:25:43.000 --> 0:25:49.600
<v Speaker 1>being delivered by audio, which could be funny while you're

0:25:49.640 --> 0:25:51.560
<v Speaker 1>watching it if you're able to hear, you know, you're

0:25:51.600 --> 0:25:54.639
<v Speaker 1>able to hear the difference, and you're reading the text

0:25:54.720 --> 0:25:57.000
<v Speaker 1>and you're seeing where it's not matching up, and you're thinking, oh,

0:25:57.000 --> 0:25:59.800
<v Speaker 1>that's kind of funny. But if that's the way that

0:26:00.080 --> 0:26:05.960
<v Speaker 1>you get the information, it's really frustrating. It is it

0:26:06.119 --> 0:26:09.760
<v Speaker 1>is not accessible, it is not inclusive. It's excluding you,

0:26:10.720 --> 0:26:15.040
<v Speaker 1>and I can't imagine how uh upsetting that's got to

0:26:15.119 --> 0:26:18.000
<v Speaker 1>be after a while, when you realize as you're reading

0:26:18.000 --> 0:26:20.200
<v Speaker 1>in you're like, there's no way that's what that person

0:26:20.280 --> 0:26:24.880
<v Speaker 1>is saying, because it doesn't make any sense. But those

0:26:24.960 --> 0:26:29.280
<v Speaker 1>are technologies that are getting wider us, and as speech

0:26:29.280 --> 0:26:32.920
<v Speaker 1>recognition gets better, I will expect that we'll see those

0:26:33.040 --> 0:26:35.760
<v Speaker 1>error rates go down and it will become less of

0:26:35.800 --> 0:26:39.639
<v Speaker 1>a frustrating experience. But in the meantime that is a problem. Now. Granted,

0:26:39.680 --> 0:26:43.600
<v Speaker 1>there are plenty of UH services out there that actually

0:26:43.680 --> 0:26:48.160
<v Speaker 1>use human beings to create transcripts and captions, where it's

0:26:48.200 --> 0:26:51.680
<v Speaker 1>someone listening to the content and actually typing it out,

0:26:52.080 --> 0:26:56.360
<v Speaker 1>and they tend to be a little more reliable in general,

0:26:57.080 --> 0:27:01.879
<v Speaker 1>depending upon the content they're listening to, the dialect or

0:27:01.960 --> 0:27:07.520
<v Speaker 1>accent that is being spoken, and the home dialect or

0:27:07.560 --> 0:27:11.679
<v Speaker 1>accent of the person doing the transcription, because sometimes you

0:27:11.800 --> 0:27:14.520
<v Speaker 1>listen to someone from a different part of the country

0:27:14.640 --> 0:27:16.800
<v Speaker 1>or a different part of the world, and it becomes

0:27:16.800 --> 0:27:18.960
<v Speaker 1>a real challenge to figure out what the heck they're saying.

0:27:19.560 --> 0:27:22.440
<v Speaker 1>I should know, I married a woman from Philadelphia, and

0:27:22.520 --> 0:27:24.960
<v Speaker 1>there are days where we just don't understand each other.

0:27:25.080 --> 0:27:27.720
<v Speaker 1>She talks faster than I can hear. To be fair,

0:27:28.400 --> 0:27:34.520
<v Speaker 1>we Southerners are, We're slow talking people. So another technology

0:27:34.560 --> 0:27:40.159
<v Speaker 1>that is often used for accessibility is haptic feedback technology.

0:27:40.880 --> 0:27:44.000
<v Speaker 1>Haptics referred to feedback that engages the sense of touch.

0:27:44.520 --> 0:27:49.280
<v Speaker 1>So typically it involves a rotating weight that's slightly off center,

0:27:49.440 --> 0:27:52.199
<v Speaker 1>and so when it rotates, it creates vibration or a

0:27:52.280 --> 0:27:56.040
<v Speaker 1>rumble sensation. This is the technology that's inside a phone

0:27:56.119 --> 0:28:00.000
<v Speaker 1>to create the vibrate feature or in a rumble feature

0:28:00.000 --> 0:28:03.680
<v Speaker 1>in a video game controller uses the same sort of thing. Uh.

0:28:03.760 --> 0:28:07.520
<v Speaker 1>That's a very common use of haptics, and they're often

0:28:07.520 --> 0:28:12.280
<v Speaker 1>incorporated into things like robotic prosthetics, which help give pressure

0:28:12.280 --> 0:28:14.959
<v Speaker 1>feedback to users so that they can get a sense

0:28:15.200 --> 0:28:19.040
<v Speaker 1>of important informations just how hard a robotic hand is

0:28:19.040 --> 0:28:22.680
<v Speaker 1>gripping an object. So if you have a robotic prosthetic,

0:28:22.760 --> 0:28:25.440
<v Speaker 1>let's say you've got a robotic arm, and it gives

0:28:25.440 --> 0:28:28.760
<v Speaker 1>you the capability of picking up different objects, and you

0:28:28.760 --> 0:28:31.240
<v Speaker 1>can pick up a whole variety of things that a

0:28:31.359 --> 0:28:34.240
<v Speaker 1>variety of weights. You know, ideally you want to have

0:28:35.000 --> 0:28:38.920
<v Speaker 1>a robotic prosthetic that is as capable as the average

0:28:39.000 --> 0:28:42.280
<v Speaker 1>human's arm is. Then you need to have some sort

0:28:42.280 --> 0:28:44.360
<v Speaker 1>of feedback to let you know how hard you are

0:28:44.440 --> 0:28:46.800
<v Speaker 1>gripping the thing right, so that way you're not going

0:28:46.840 --> 0:28:49.240
<v Speaker 1>to cause damage to something. If you're picking up let's

0:28:49.240 --> 0:28:51.800
<v Speaker 1>say a lightbulb, you don't want to squeeze it so

0:28:51.840 --> 0:28:54.040
<v Speaker 1>hard that you break it. But if you're picking up

0:28:54.040 --> 0:28:55.600
<v Speaker 1>a brick, you want to make sure the grip is

0:28:55.600 --> 0:29:00.160
<v Speaker 1>strong enough to actually lift the brick. So that's frequently

0:29:00.240 --> 0:29:04.120
<v Speaker 1>used as a feedback mechanism to alert the user how

0:29:04.200 --> 0:29:08.160
<v Speaker 1>much force is being exerted by that robotic prosthetic. It's

0:29:08.200 --> 0:29:11.400
<v Speaker 1>also used in systems to help visually impaired people navigate

0:29:11.440 --> 0:29:14.720
<v Speaker 1>through different environments. I've seen some videos of this. I

0:29:14.760 --> 0:29:17.000
<v Speaker 1>don't I'm not aware of any technology that's out in

0:29:17.040 --> 0:29:21.040
<v Speaker 1>the wild beyond the prototype stage, but I've seen this

0:29:21.160 --> 0:29:24.760
<v Speaker 1>approach and I think it's fascinating. It provides haptic feedback

0:29:24.800 --> 0:29:29.240
<v Speaker 1>systems that are hooked up to optical sensors cameras, essentially,

0:29:29.880 --> 0:29:34.720
<v Speaker 1>so the wearer can walk around where who has a

0:29:36.680 --> 0:29:40.600
<v Speaker 1>impairment in their in their vision, They're walking around and

0:29:40.760 --> 0:29:44.400
<v Speaker 1>whenever they get close to an obstacle that's picked up

0:29:44.400 --> 0:29:47.440
<v Speaker 1>by the optical sensors, they get feedback. They get a

0:29:47.560 --> 0:29:50.360
<v Speaker 1>vibration that tells them, oh, you're getting close to something,

0:29:50.440 --> 0:29:53.760
<v Speaker 1>maybe it's a table or some stairs or something. And

0:29:53.800 --> 0:29:56.880
<v Speaker 1>it's sort of like spidy sense in a way, which

0:29:56.920 --> 0:29:59.040
<v Speaker 1>I think is pretty interesting. But again, I'm not aware

0:29:59.080 --> 0:30:02.680
<v Speaker 1>of any technology on the wild that people have access

0:30:02.720 --> 0:30:07.560
<v Speaker 1>to easily. I have seen laboratory videos of this sort

0:30:07.600 --> 0:30:12.280
<v Speaker 1>of stuff. Uh, there's so much more we can talk about. UM,

0:30:12.360 --> 0:30:16.120
<v Speaker 1>I haven't really touched on mobility issues. There are many

0:30:16.200 --> 0:30:19.520
<v Speaker 1>technologies designed to help people who have challenges in moving

0:30:19.960 --> 0:30:23.560
<v Speaker 1>on their own to operate technology. These range from Bluetooth

0:30:23.560 --> 0:30:27.600
<v Speaker 1>controllers that can map app commands to simple switches that

0:30:27.680 --> 0:30:31.240
<v Speaker 1>some one might operate with a foot or a finger,

0:30:32.080 --> 0:30:37.440
<v Speaker 1>um or even their mouth. These sort of devices do exist.

0:30:37.480 --> 0:30:41.760
<v Speaker 1>These switches do exist, and mapping them to apps allows

0:30:41.800 --> 0:30:48.000
<v Speaker 1>people to navigate that technology and that it improves accessibility. Uh.

0:30:48.040 --> 0:30:50.240
<v Speaker 1>There are all these other types of apparatus that people

0:30:50.320 --> 0:30:53.720
<v Speaker 1>might depend upon, including things like mouth sticks or head

0:30:53.760 --> 0:30:56.960
<v Speaker 1>pointers that can allow them to interface with computers and

0:30:57.000 --> 0:31:00.800
<v Speaker 1>other devices. Uh. There's eye tracking technology that can allow

0:31:00.880 --> 0:31:03.760
<v Speaker 1>someone with mobility issues to take control of the device

0:31:03.920 --> 0:31:07.360
<v Speaker 1>using their eyes to navigate or to type out messages.

0:31:07.960 --> 0:31:11.440
<v Speaker 1>There are brain computer interface designs that are the next

0:31:11.640 --> 0:31:14.560
<v Speaker 1>step out. They would interface directly with a brain to

0:31:15.160 --> 0:31:18.320
<v Speaker 1>send commands from someone's brain to a computer system to

0:31:18.680 --> 0:31:24.000
<v Speaker 1>create some sort of effect. Those are still fairly rare,

0:31:24.160 --> 0:31:26.440
<v Speaker 1>and they're still very much in the testing phase for

0:31:26.480 --> 0:31:29.800
<v Speaker 1>a lot of different use cases. But we've seen some

0:31:29.880 --> 0:31:34.200
<v Speaker 1>incredible advances in that it does require a very long

0:31:34.280 --> 0:31:38.600
<v Speaker 1>session of training, not just the person who's using the technology,

0:31:38.640 --> 0:31:42.840
<v Speaker 1>but the technology itself to interpret the person's UH commands,

0:31:43.360 --> 0:31:47.240
<v Speaker 1>because our brains when we send commands are not doing

0:31:47.240 --> 0:31:52.720
<v Speaker 1>it in a in a precisely identical way. So it

0:31:52.800 --> 0:31:57.040
<v Speaker 1>actually requires quite a bit of adaptation and tweaking to

0:31:57.120 --> 0:32:00.160
<v Speaker 1>get the system tuned just right to the specific and

0:32:00.240 --> 0:32:05.480
<v Speaker 1>but it does have the potential to really improve accessibility. Uh,

0:32:05.560 --> 0:32:08.520
<v Speaker 1>it's really exciting stuff. Some R and D labs are

0:32:08.560 --> 0:32:14.640
<v Speaker 1>incorporating various ways to simulate these challenges so that a

0:32:14.960 --> 0:32:18.160
<v Speaker 1>person a designer or an engineer who may not have

0:32:18.960 --> 0:32:23.640
<v Speaker 1>these sort of disabilities or other issues, can simulate that

0:32:24.240 --> 0:32:27.920
<v Speaker 1>and see what it's like to interact with their technology

0:32:28.960 --> 0:32:32.920
<v Speaker 1>with that simulated disability. So, for example, you might have

0:32:32.960 --> 0:32:37.040
<v Speaker 1>gloves that limit hand mobility, or you might have goggles

0:32:37.080 --> 0:32:41.080
<v Speaker 1>that reproduce color blindness, and then you try to navigate

0:32:41.160 --> 0:32:44.480
<v Speaker 1>your product, your technology, and you see where the challenges

0:32:44.520 --> 0:32:46.040
<v Speaker 1>may be and you think, oh, we need to fix

0:32:46.120 --> 0:32:49.320
<v Speaker 1>this because I didn't realize that because I made this design,

0:32:50.040 --> 0:32:53.280
<v Speaker 1>you can't effectively see a very important element on the

0:32:53.280 --> 0:32:57.760
<v Speaker 1>website because people who have color blindness. They're not gonna

0:32:57.760 --> 0:33:00.600
<v Speaker 1>be able to to differentiate these colors I've picked out,

0:33:00.840 --> 0:33:05.280
<v Speaker 1>so it may require either creating an alternative so that

0:33:05.280 --> 0:33:07.480
<v Speaker 1>people who are color blind are able to see it,

0:33:08.720 --> 0:33:11.920
<v Speaker 1>or just changing the design entirely. All of it is

0:33:11.960 --> 0:33:14.200
<v Speaker 1>meant to get designers to think outside of their own

0:33:14.280 --> 0:33:17.720
<v Speaker 1>experience when they're creating products like hardware and software to

0:33:17.760 --> 0:33:21.920
<v Speaker 1>make sure it's accessible to that larger user base. UM

0:33:21.960 --> 0:33:24.560
<v Speaker 1>there's an organization that I think is really important that's

0:33:24.560 --> 0:33:27.760
<v Speaker 1>going to help a lot called Teach access It's working

0:33:27.800 --> 0:33:32.560
<v Speaker 1>to create tools and curricula to introduce accessibility design in

0:33:33.080 --> 0:33:40.000
<v Speaker 1>education in academia. So ultimately the goal is to create courses,

0:33:40.320 --> 0:33:44.960
<v Speaker 1>educational courses that would be part of your design education

0:33:45.080 --> 0:33:47.200
<v Speaker 1>when you were starting to look into going into this

0:33:47.280 --> 0:33:51.560
<v Speaker 1>sort of field, and to learn about accessibility design while

0:33:51.600 --> 0:33:54.280
<v Speaker 1>you're still in school. And the group hopes to encourage

0:33:54.320 --> 0:33:57.960
<v Speaker 1>the engineers and designers of tomorrow to take accessibility into

0:33:58.000 --> 0:34:01.680
<v Speaker 1>consideration as a core design principle, not as something you

0:34:01.720 --> 0:34:04.080
<v Speaker 1>add on at the very end, but something that's incorporated

0:34:04.120 --> 0:34:07.440
<v Speaker 1>from the beginning. The group's website asserts that a lack

0:34:07.440 --> 0:34:12.240
<v Speaker 1>of understanding about basic accessibility issues presents a huge challenge

0:34:12.360 --> 0:34:15.759
<v Speaker 1>today and that by creating these curricula, these courses that

0:34:15.840 --> 0:34:19.400
<v Speaker 1>can be incorporated into a student's work, much of that

0:34:19.440 --> 0:34:21.440
<v Speaker 1>can be mended. And this goes back to what I

0:34:21.480 --> 0:34:23.640
<v Speaker 1>was saying at the beginning of the show. Designers draw

0:34:23.719 --> 0:34:27.480
<v Speaker 1>primarily upon their own experience, their own life experience when

0:34:27.480 --> 0:34:30.439
<v Speaker 1>they're building their tools and their products, and it takes

0:34:30.480 --> 0:34:33.839
<v Speaker 1>a lot of discipline and effort to step outside of

0:34:33.880 --> 0:34:37.720
<v Speaker 1>your own world experience and to create stuff that's for everyone,

0:34:37.800 --> 0:34:40.120
<v Speaker 1>not just people who happen to think and behave the

0:34:40.120 --> 0:34:42.520
<v Speaker 1>way you do. And again, this isn't coming from any

0:34:42.560 --> 0:34:46.800
<v Speaker 1>sort of exclusionary mindset necessarily. It's not like people are

0:34:46.800 --> 0:34:51.560
<v Speaker 1>trying to create stuff that's that's excluding others. You can

0:34:51.600 --> 0:34:54.040
<v Speaker 1>probably think of a few different companies that have made

0:34:54.040 --> 0:34:57.520
<v Speaker 1>products that appeal to a certain niche audience that happens

0:34:57.520 --> 0:35:01.040
<v Speaker 1>to be similar to the people who made those products. So,

0:35:01.080 --> 0:35:04.440
<v Speaker 1>for example, I'm gonna throw Google under the bus here. Now,

0:35:04.440 --> 0:35:07.560
<v Speaker 1>I'm an Android user. I use a lot of Google products,

0:35:07.640 --> 0:35:10.960
<v Speaker 1>and I've come to the conclusion that many of their

0:35:11.280 --> 0:35:14.040
<v Speaker 1>especially their web based products, many of their web based

0:35:14.040 --> 0:35:19.680
<v Speaker 1>products were made by engineers for engineers, and that people

0:35:19.680 --> 0:35:23.160
<v Speaker 1>who were not of the engineering mindset may have found

0:35:23.360 --> 0:35:28.319
<v Speaker 1>some of those products and services challenging to navigate or

0:35:28.960 --> 0:35:35.160
<v Speaker 1>counterintuitive or non intuitive, and as a result, those various

0:35:35.160 --> 0:35:38.399
<v Speaker 1>products and services didn't get widespread adoption. And so it's

0:35:38.440 --> 0:35:43.640
<v Speaker 1>become kind of a longstanding joke that Google would introduce

0:35:44.360 --> 0:35:49.120
<v Speaker 1>a new product online product and then within three or

0:35:49.120 --> 0:35:53.640
<v Speaker 1>four years discontinue it because of lack of adoption. But

0:35:53.680 --> 0:35:55.880
<v Speaker 1>I think a large part of that was because some

0:35:55.960 --> 0:35:59.120
<v Speaker 1>of the design was while it made perfect sense to

0:35:59.120 --> 0:36:02.120
<v Speaker 1>the people who were making the product, did not necessarily

0:36:02.160 --> 0:36:06.640
<v Speaker 1>make sense to other people from different experiences. So it

0:36:06.680 --> 0:36:09.200
<v Speaker 1>wasn't that the products were bad, It's just that they

0:36:09.440 --> 0:36:15.120
<v Speaker 1>were not accessible to everybody. Teach access has grown out

0:36:15.120 --> 0:36:19.400
<v Speaker 1>of efforts from accessibility teams that were founded in Yahoo

0:36:19.440 --> 0:36:22.759
<v Speaker 1>and Facebook, but now there are lots and lots of

0:36:22.800 --> 0:36:28.320
<v Speaker 1>companies and institutions that are part of it, like Stanford, Microsoft, Twitter, Adobe,

0:36:28.920 --> 0:36:31.200
<v Speaker 1>Google is part of it, LinkedIn A T and T,

0:36:31.440 --> 0:36:35.319
<v Speaker 1>A whole bunch of different companies and organizations are part

0:36:35.320 --> 0:36:38.960
<v Speaker 1>of this initiative. It's exciting to see companies take such

0:36:38.960 --> 0:36:43.200
<v Speaker 1>an active role in a holistic approach to increasing accessibility.

0:36:43.239 --> 0:36:46.960
<v Speaker 1>Acknowledging the education and incorporation into fundamental design strategies is

0:36:47.000 --> 0:36:50.080
<v Speaker 1>a really good start. And there are two really big

0:36:50.120 --> 0:36:52.440
<v Speaker 1>reasons that I am so passionate about this. You know,

0:36:52.480 --> 0:36:54.840
<v Speaker 1>I know I've talked about this kind of thing and

0:36:55.280 --> 0:36:58.120
<v Speaker 1>a very touchy feely kind of way that some people

0:36:58.200 --> 0:37:01.520
<v Speaker 1>might find off putting, but uh, frankly, I don't care,

0:37:01.920 --> 0:37:06.880
<v Speaker 1>because I think the two things that really drive my

0:37:06.960 --> 0:37:11.480
<v Speaker 1>passion in this is. First, there's compassion. I want inclusions

0:37:11.480 --> 0:37:16.760
<v Speaker 1>so that people are not frustrated, they're not isolated because

0:37:16.800 --> 0:37:18.840
<v Speaker 1>of the design of technology. I want them to be

0:37:18.920 --> 0:37:25.560
<v Speaker 1>able to enjoy the benefits of technology, to flourish in

0:37:25.680 --> 0:37:28.799
<v Speaker 1>part because technology is allowing them to do so in

0:37:28.840 --> 0:37:31.919
<v Speaker 1>ways they could not otherwise. I want that to be

0:37:32.239 --> 0:37:36.040
<v Speaker 1>the case. And from a selfish perspective, I want it

0:37:36.080 --> 0:37:40.880
<v Speaker 1>because you can't even imagine the contributions people might be

0:37:40.920 --> 0:37:44.920
<v Speaker 1>able to make if they just have access to technology

0:37:44.960 --> 0:37:47.920
<v Speaker 1>in a meaningful way. You never know who's going to

0:37:47.960 --> 0:37:52.320
<v Speaker 1>come up with the next incredible innovation or next scientific principle.

0:37:52.400 --> 0:37:57.040
<v Speaker 1>Imagine if Stephen Hawking had been silenced due to his

0:37:57.400 --> 0:38:01.040
<v Speaker 1>uh A L s, If if he had been rendered

0:38:01.680 --> 0:38:06.080
<v Speaker 1>incapable of communicating without the use of technology, or even

0:38:06.160 --> 0:38:08.319
<v Speaker 1>with the use of technology. If he could not communicate,

0:38:09.400 --> 0:38:12.880
<v Speaker 1>it would have not just been a terrible personal tragedy

0:38:12.920 --> 0:38:15.239
<v Speaker 1>for him, because of course it would be, and for

0:38:15.320 --> 0:38:18.799
<v Speaker 1>his family, it would also have left a gap in

0:38:18.880 --> 0:38:25.440
<v Speaker 1>scientific discourse that would have been a terrible detriment for everybody.

0:38:25.480 --> 0:38:29.520
<v Speaker 1>So I think accessible technology is important for everyone, not

0:38:29.600 --> 0:38:34.080
<v Speaker 1>just the people that directly benefit from it, but from everybody,

0:38:34.080 --> 0:38:36.520
<v Speaker 1>because we can all stand to benefit in the long

0:38:36.640 --> 0:38:39.840
<v Speaker 1>run in ways that we can't imagine. Here's here's a

0:38:39.880 --> 0:38:44.840
<v Speaker 1>simple and silly, somewhat silly example in the sense of

0:38:44.960 --> 0:38:50.480
<v Speaker 1>the aid that it gave everybody. So back in and Kalamazoo, Michigan,

0:38:51.120 --> 0:38:54.160
<v Speaker 1>the city began to alter their sidewalks. They started to

0:38:54.200 --> 0:38:57.480
<v Speaker 1>create curb cuts. So these are the first curb cuts.

0:38:57.840 --> 0:39:01.280
<v Speaker 1>This is the sloped section on a herb that allows

0:39:01.360 --> 0:39:05.239
<v Speaker 1>someone who's in a wheelchair to move from street level

0:39:05.320 --> 0:39:08.319
<v Speaker 1>up to sidewalk level so they can cross streets. That

0:39:08.360 --> 0:39:11.960
<v Speaker 1>part is not the silly part. That part is incredibly important.

0:39:12.320 --> 0:39:16.600
<v Speaker 1>It gives people in wheelchairs the capability of navigating around

0:39:16.680 --> 0:39:19.440
<v Speaker 1>their city in a way that they otherwise would have

0:39:19.719 --> 0:39:22.640
<v Speaker 1>problems doing. So. That part is important, But the part

0:39:22.680 --> 0:39:24.640
<v Speaker 1>that's a little more silly is that that those singing

0:39:25.160 --> 0:39:28.960
<v Speaker 1>ramps allowed for other uses, Like if you happen to

0:39:29.000 --> 0:39:32.560
<v Speaker 1>travel around on the scooter and you don't want to

0:39:32.600 --> 0:39:37.000
<v Speaker 1>go in the street and there are no, i you know,

0:39:37.040 --> 0:39:39.719
<v Speaker 1>no local laws that prevent you from going on sidewalks

0:39:39.719 --> 0:39:43.000
<v Speaker 1>with a scooter, then these slopes allow you to do that.

0:39:43.120 --> 0:39:46.080
<v Speaker 1>For parents who are pushing strollers, they can move from

0:39:46.120 --> 0:39:50.600
<v Speaker 1>street to sidewalk. Those were not the primary intent of

0:39:50.640 --> 0:39:53.959
<v Speaker 1>those curb cuts, but they are other benefits that rose

0:39:54.120 --> 0:39:59.880
<v Speaker 1>up from that program. So there can be benefits beyond

0:40:00.680 --> 0:40:06.279
<v Speaker 1>the primary intended purpose for accessible technology, both from the

0:40:06.320 --> 0:40:09.480
<v Speaker 1>technology standpoint and the people who get to take advantage

0:40:09.480 --> 0:40:11.880
<v Speaker 1>of it. So that's why I think it's an important

0:40:12.000 --> 0:40:16.799
<v Speaker 1>concept and an important endeavor to pursue. Now, obviously we

0:40:16.840 --> 0:40:19.919
<v Speaker 1>could talk in greater detail about all these different types

0:40:19.960 --> 0:40:22.879
<v Speaker 1>of technology, and probably in the future I will cover

0:40:22.960 --> 0:40:26.719
<v Speaker 1>them more in more depth. UM eye tracking technology I've

0:40:26.719 --> 0:40:29.200
<v Speaker 1>talked about before in the past, but going into greater

0:40:29.280 --> 0:40:33.239
<v Speaker 1>detail with that would be great because the tech has

0:40:33.560 --> 0:40:37.239
<v Speaker 1>improved significantly since I first started playing around with it

0:40:37.280 --> 0:40:40.000
<v Speaker 1>a few years ago, and it'd be great to sort

0:40:40.040 --> 0:40:43.719
<v Speaker 1>of talk about the implications of that, but we've kind

0:40:43.719 --> 0:40:46.040
<v Speaker 1>of run out of time, so I want to thank

0:40:46.160 --> 0:40:52.600
<v Speaker 1>Ken again for the suggestion to do accessible Technology. And uh,

0:40:52.640 --> 0:40:55.160
<v Speaker 1>if you guys have any suggestions for future episodes of Tech,

0:40:55.200 --> 0:40:58.160
<v Speaker 1>whether it's a type of tech, a company, a person

0:40:58.200 --> 0:41:01.000
<v Speaker 1>in tech, maybe there's someone I should enter you let

0:41:01.000 --> 0:41:03.920
<v Speaker 1>me know. Send me an email. The addresses tech Stuff

0:41:04.000 --> 0:41:06.640
<v Speaker 1>at how stuff works dot com. Remember, you can also

0:41:06.719 --> 0:41:09.719
<v Speaker 1>get in touch with me on Twitter and Facebook. The

0:41:09.800 --> 0:41:12.200
<v Speaker 1>handle with both of those is tech Stuff hs W.

0:41:12.760 --> 0:41:17.719
<v Speaker 1>Don't forget. If you haven't yet picked up your amazing

0:41:17.960 --> 0:41:21.560
<v Speaker 1>Ada Lovelace T shirt, you should go to the tech

0:41:21.600 --> 0:41:25.840
<v Speaker 1>Stuff store over at t public dot com slash tech Stuff.

0:41:25.880 --> 0:41:29.439
<v Speaker 1>That's t e public dot com slash tech Stuff. We've

0:41:29.480 --> 0:41:32.240
<v Speaker 1>got all sorts of designs that can go on anything

0:41:32.320 --> 0:41:34.440
<v Speaker 1>from a T shirt to a tope bag, to a

0:41:34.440 --> 0:41:38.240
<v Speaker 1>coffee mug to phone case, lots of different stuff, stickers,

0:41:39.080 --> 0:41:42.040
<v Speaker 1>and every purchase you make helps out the show a

0:41:42.040 --> 0:41:44.200
<v Speaker 1>little bit. Plus you get cool stuff, so go check

0:41:44.239 --> 0:41:47.879
<v Speaker 1>it out and don't forget follow us on Instagram. That's

0:41:47.880 --> 0:41:50.600
<v Speaker 1>it for me. I'll talk to you again really soon

0:41:56.280 --> 0:41:58.720
<v Speaker 1>for more on this and thousands of other topics because

0:41:58.760 --> 0:42:05.560
<v Speaker 1>it how stuff works. Dot com want