WEBVTT 00:00:00.000 --> 00:00:02.640 I want you to travel back in time with me for 00:00:02.640 --> 00:00:05.559 a second to a very specific kind of academic 00:00:05.559 --> 00:00:07.679 panic. Oh, I think I know where this is going. 00:00:07.860 --> 00:00:12.560 You probably do. So picture this. You are in 00:00:12.560 --> 00:00:14.939 school, and you've just stayed up way too late 00:00:14.939 --> 00:00:17.519 finishing a massive paper. Right. And you saved 00:00:17.519 --> 00:00:20.480 it onto a floppy desk. Wow, really going back 00:00:20.480 --> 00:00:23.079 there. Yeah, the classic plastic square. So you 00:00:23.079 --> 00:00:25.300 walk into the school computer lab the next morning 00:00:25.300 --> 00:00:27.519 feeling, you know, incredibly accomplished. Yeah. 00:00:27.679 --> 00:00:30.219 You slide that disk into the drive, and you are 00:00:30.219 --> 00:00:33.539 just hit with this sudden icy wave of dread. 00:00:33.759 --> 00:00:36.159 Because the computer says the file format is 00:00:36.159 --> 00:00:38.659 unrecognized. Exactly. You wrote the entire document 00:00:38.659 --> 00:00:41.780 at home using, like, Microsoft works. Oh, man. 00:00:41.899 --> 00:00:43.799 But your school's computer lab is strictly a 00:00:43.799 --> 00:00:46.320 Microsoft Word environment. That is a deeply 00:00:46.320 --> 00:00:48.439 visceral memory for a lot of people. I mean, 00:00:48.439 --> 00:00:51.460 you're describing an era where the primary bottleneck 00:00:51.460 --> 00:00:53.640 to sharing knowledge wasn't the quality of the 00:00:53.640 --> 00:00:56.380 ideas, right? It was the literal physical and 00:00:56.380 --> 00:00:58.740 software barriers. Right. Isolated machine. Yeah. 00:00:59.119 --> 00:01:02.759 We were fighting this this war of hardware formats 00:01:02.759 --> 00:01:06.120 and proprietary file extensions. And that specific 00:01:06.120 --> 00:01:08.400 frustration is actually the jumping off point 00:01:08.400 --> 00:01:11.760 for today's deep dive. We are looking at a really 00:01:11.760 --> 00:01:14.840 fascinating piece by Dr. Gary Ackerman from his 00:01:14.840 --> 00:01:18.439 site hackscience .education. It's a great article. 00:01:18.780 --> 00:01:21.200 It really is. And he's specifically exploring 00:01:21.480 --> 00:01:25.140 ADA compliance in education. Ackerman basically 00:01:25.140 --> 00:01:28.019 uses that nostalgic floppy disk panic to make 00:01:28.019 --> 00:01:30.900 a really profound point about how far we've actually 00:01:30.900 --> 00:01:33.459 come with educational tech. Well, yeah, because 00:01:33.459 --> 00:01:35.620 we transitioned away from those nightmare days 00:01:35.620 --> 00:01:38.579 of incompatible disks. Right. We moved into a 00:01:38.579 --> 00:01:41.379 world dominated by universally recognized file 00:01:41.379 --> 00:01:43.780 types and eventually to the seamless cloud networks 00:01:43.780 --> 00:01:46.930 that we all rely on today. But the mission of 00:01:46.930 --> 00:01:48.689 our deep dive today, what we really want you 00:01:48.689 --> 00:01:51.230 to take away from this, is looking at the massive 00:01:51.230 --> 00:01:53.969 blind spot we developed along that journey. Because 00:01:53.969 --> 00:01:56.030 it turns out we haven't actually solved the whole 00:01:56.030 --> 00:01:58.230 puzzle of information sharing. Not at all. I 00:01:58.230 --> 00:02:01.230 mean, we spent literal decades and probably billions 00:02:01.230 --> 00:02:04.250 of dollars throwing money at the problem of hardware 00:02:04.250 --> 00:02:06.329 and software interoperability. That was the holy 00:02:06.329 --> 00:02:08.090 grail. Yeah, just getting the machines to talk. 00:02:08.569 --> 00:02:11.009 Exactly. And we eventually gravitated toward 00:02:11.009 --> 00:02:13.610 universal standards, mostly driven by market 00:02:13.610 --> 00:02:16.830 dominance. Microsoft Office established the baseline 00:02:16.830 --> 00:02:19.849 for a long time. Right. Word, PowerPoint, Excel. 00:02:20.169 --> 00:02:23.889 And then during periods when institutional budgets 00:02:23.889 --> 00:02:26.530 were super tight, you saw massive deployments 00:02:26.530 --> 00:02:28.969 of open source stuff like OpenOffice just to 00:02:28.969 --> 00:02:30.629 keep people on the same page. Yeah, I remember 00:02:30.629 --> 00:02:33.990 using that in college. Right. And now that landscape 00:02:33.990 --> 00:02:36.550 has shifted almost entirely to the cloud. I mean, 00:02:36.650 --> 00:02:38.789 the vast majority of educational institutions 00:02:38.789 --> 00:02:41.870 operate within G Suite or Microsoft 365. It's 00:02:41.870 --> 00:02:45.090 everywhere. It is. You create a file and it just 00:02:45.090 --> 00:02:47.370 lives in this interconnected ecosystem. You can 00:02:47.370 --> 00:02:49.509 access it on your phone, in a coffee shop, a 00:02:49.509 --> 00:02:51.770 tablet. on a train. A desk hop in a classroom. 00:02:52.210 --> 00:02:55.270 Exactly. We successfully solved the machine interoperability 00:02:55.270 --> 00:02:57.650 problem, but Ackerman draws a really crucial 00:02:57.650 --> 00:02:59.669 distinction here. Right, the human element. Yeah. 00:02:59.870 --> 00:03:02.990 We mastered how machines talk to machines, but 00:03:02.990 --> 00:03:06.250 we have been remarkably slow to solve human interoperability. 00:03:06.729 --> 00:03:09.460 Human interoperability. Such a great phrase. 00:03:09.919 --> 00:03:13.340 And I want you, the listener, to critically examine 00:03:13.340 --> 00:03:16.680 your own daily digital habits for a moment. It's 00:03:16.680 --> 00:03:19.840 a good exercise. Think about the last time you 00:03:19.840 --> 00:03:22.419 prepped for a team meeting or maybe you sent 00:03:22.419 --> 00:03:24.659 a syllabus to a group of students. You probably 00:03:24.659 --> 00:03:26.860 just hit that big blue share link button, right? 00:03:27.289 --> 00:03:30.349 Fire it off an email and moved on. Exactly. Mentally 00:03:30.349 --> 00:03:32.909 check that task off your list. You assumed your 00:03:32.909 --> 00:03:35.069 job was done because the file was floating safely 00:03:35.069 --> 00:03:37.930 in the cloud. But true human interoperability 00:03:37.930 --> 00:03:41.210 means engineering that information so that absolutely 00:03:41.210 --> 00:03:44.189 everyone, regardless of their physical or cognitive 00:03:44.189 --> 00:03:47.030 abilities, can actually extract the meaning from 00:03:47.030 --> 00:03:49.189 it. Right. And we kind of fell into a trap, didn't 00:03:49.189 --> 00:03:51.969 we? Oh, a massive trap of false equivalence. 00:03:52.110 --> 00:03:54.610 Because we move from hardware anxiety to cloud 00:03:54.610 --> 00:03:57.219 convenience, we assume the cloud magic fix the 00:03:57.219 --> 00:03:59.419 whole concept of access. Like, hey, I can open 00:03:59.419 --> 00:04:02.120 it so everyone can open it. Exactly. The underlying 00:04:02.120 --> 00:04:04.719 logic became the hyperlink resolved successfully 00:04:04.719 --> 00:04:07.960 on my screen. Therefore, the information is universally 00:04:07.960 --> 00:04:11.539 accessible. We fundamentally misjudged what access 00:04:11.539 --> 00:04:14.620 actually requires in practice. OK, let's unpack 00:04:14.620 --> 00:04:17.060 this, though. I want to push back slightly, maybe 00:04:17.060 --> 00:04:19.600 on behalf of a listener who feels pretty confident 00:04:19.600 --> 00:04:22.319 in their current workflow. Sure, go for it. If 00:04:22.319 --> 00:04:25.079 an institution is entirely integrated into G 00:04:25.079 --> 00:04:27.980 Suite, and literally anyone with the link can 00:04:27.980 --> 00:04:30.800 open that Google Doc on a browser and the browser 00:04:30.800 --> 00:04:33.639 translates the data into readable text on their 00:04:33.639 --> 00:04:36.899 screen. Haven't we technically achieved universal 00:04:36.899 --> 00:04:39.439 access? I mean the data packet arrived right. 00:04:39.620 --> 00:04:42.149 The text is visible so what's the issue? Well, 00:04:42.430 --> 00:04:45.170 that assumes visibility is the only metric for 00:04:45.170 --> 00:04:48.389 comprehension. And that fundamentally misinterprets 00:04:48.389 --> 00:04:50.970 the legal and, frankly, the functional reality 00:04:50.970 --> 00:04:54.129 of the Americans with Disabilities Act. The ADA. 00:04:54.350 --> 00:04:57.389 Right, the ADA. It was designed to ensure all 00:04:57.389 --> 00:04:59.689 citizens have equal use of information created 00:04:59.689 --> 00:05:01.990 by government sources. And as Ackerman points 00:05:01.990 --> 00:05:04.290 out in the text, public education is an arm of 00:05:04.290 --> 00:05:06.250 the government, so it's bound by those standards. 00:05:06.329 --> 00:05:08.350 So it's not just a suggestion? Not at all. We 00:05:08.350 --> 00:05:11.009 have to separate the concept of rendering a file 00:05:11.079 --> 00:05:14.339 from comprehending a file. Access doesn't just 00:05:14.339 --> 00:05:16.439 mean your browser successfully renders a page 00:05:16.439 --> 00:05:18.740 without crashing. OK, so what does it mean? Yeah. 00:05:18.819 --> 00:05:21.139 It means the author hasn't actively prevented 00:05:21.139 --> 00:05:24.139 individuals who use screen reading software or 00:05:24.139 --> 00:05:26.560 people who have severe difficulty processing, 00:05:27.199 --> 00:05:30.839 like low contrast visual information, from actually 00:05:30.839 --> 00:05:33.800 comprehending the material. So if the data packet 00:05:33.800 --> 00:05:36.399 arrives but their assistive tech can't parse 00:05:36.399 --> 00:05:38.600 it? You haven't provided access. You've just 00:05:38.600 --> 00:05:41.959 delivered a locked box. Wow. That reframing. 00:05:42.189 --> 00:05:45.029 really completely shifts the burden of responsibility, 00:05:45.250 --> 00:05:47.370 doesn't it? It absolutely does. It moves ADA 00:05:47.370 --> 00:05:50.129 compliance out of the realm of like an IT networking 00:05:50.129 --> 00:05:53.129 problem and drops it squarely onto the desk of 00:05:53.129 --> 00:05:55.990 the individual educator or creator. Which is 00:05:55.990 --> 00:05:58.569 intimidating for some. Yeah, but it transforms 00:05:58.569 --> 00:06:01.069 accessibility from this annoying legal checklist 00:06:01.069 --> 00:06:04.529 managed by some distant bureaucracy into a core 00:06:04.529 --> 00:06:07.170 daily philosophy of communication. And that shift 00:06:07.170 --> 00:06:09.629 is exactly what Ackerman is advocating for. Think 00:06:09.629 --> 00:06:11.709 about a student with severe visual impairment 00:06:11.600 --> 00:06:14.800 who opens your seamlessly shared cloud document. 00:06:15.100 --> 00:06:17.560 Their screen reading software is this incredibly 00:06:17.560 --> 00:06:20.579 sophisticated tool designed to translate digital 00:06:20.579 --> 00:06:24.000 code into spoken audio. But if that software 00:06:24.000 --> 00:06:26.439 encounters a document that wasn't structurally 00:06:26.439 --> 00:06:28.899 formatted to be read by a machine... It just 00:06:28.899 --> 00:06:30.819 fails. It can't make heads or tails of the text. 00:06:30.959 --> 00:06:33.399 At that point, your pristine G Suite link is 00:06:33.399 --> 00:06:35.399 functionally just as useless to that student 00:06:35.399 --> 00:06:38.399 as your Microsoft Works floppy disk was to the 00:06:38.399 --> 00:06:40.699 Microsoft Word computer lab. Oh, that's a brilliant 00:06:40.699 --> 00:06:43.509 connection. the barrier to entry isn't a proprietary 00:06:43.509 --> 00:06:46.170 floppy drive anymore. No, the barrier is the 00:06:46.170 --> 00:06:48.649 author's lazy formatting. Here's where it gets 00:06:48.649 --> 00:06:50.870 really interesting, though. When we talk about 00:06:50.870 --> 00:06:53.389 how to actually build human accessibility into 00:06:53.389 --> 00:06:56.350 the fabric of these files, I keep visualizing 00:06:56.350 --> 00:06:58.750 this through the lens of physical architecture. 00:06:58.970 --> 00:07:01.750 Oh, I like that. How so? So imagine a standard 00:07:01.750 --> 00:07:04.589 10 -page text document is a physical building. 00:07:05.410 --> 00:07:07.930 To a sighted person, when an author highlights 00:07:07.930 --> 00:07:11.290 a line of text, increases the font size to 16, 00:07:11.500 --> 00:07:13.699 and makes it bold at the top of a paragraph. 00:07:13.839 --> 00:07:16.639 It acts as a visual signpost. Right. It immediately 00:07:16.639 --> 00:07:18.459 signals, hey, a new concept is starting here. 00:07:18.579 --> 00:07:20.540 It's the visual equivalent of a doorway. But 00:07:20.540 --> 00:07:22.720 a screen reader isn't looking at the paint on 00:07:22.720 --> 00:07:25.060 the walls. Exactly. It's software navigating 00:07:25.060 --> 00:07:27.240 the foundational blueprint of the document's 00:07:27.240 --> 00:07:31.420 code. To that software, just making text bold 00:07:31.420 --> 00:07:34.259 means absolutely nothing structurally. Right. 00:07:34.490 --> 00:07:37.589 Without the underlying metadata explicitly defining 00:07:37.589 --> 00:07:40.730 that text as a heading, that entire 10 -page 00:07:40.730 --> 00:07:43.629 document is just a massive, flat, terrifying 00:07:43.629 --> 00:07:45.750 wall of noise. That's a great way to put it. 00:07:45.970 --> 00:07:48.389 Headings are the structural load -bearing walls 00:07:48.389 --> 00:07:51.589 that allow assistive technology to actually navigate 00:07:51.589 --> 00:07:53.850 the building. What's fascinating here is that 00:07:53.850 --> 00:07:56.089 your architecture analogy perfectly captures 00:07:56.089 --> 00:07:59.220 the mechanics of Ackerman's first major directive 00:07:59.220 --> 00:08:02.759 for ADA compliance. Which is? Well, the structure 00:08:02.759 --> 00:08:04.720 of a document exists in what's called the Document 00:08:04.720 --> 00:08:07.139 Object Model, or the DOM. The DOM, right. Yeah. 00:08:07.300 --> 00:08:10.319 And that DOM is entirely invisible to a sighted 00:08:10.319 --> 00:08:12.279 user who really only cares about the visual output. 00:08:12.959 --> 00:08:15.819 But the DOM is the literal universe for a visually 00:08:15.819 --> 00:08:18.720 impaired user relying on a screen reader. Because 00:08:18.720 --> 00:08:21.290 that's what the software actually reads. Precisely. 00:08:21.610 --> 00:08:24.009 Ackerman insists that the very first habit creators 00:08:24.009 --> 00:08:26.829 need to build is using the native heading styles 00:08:26.829 --> 00:08:29.529 in their word processors. So no more just highlighting 00:08:29.529 --> 00:08:32.070 and clicking bold. Exactly. You cannot just highlight 00:08:32.070 --> 00:08:34.330 text, bump up the point size, and hit the bold 00:08:34.330 --> 00:08:36.710 button. You are required to go to the formatting 00:08:36.710 --> 00:08:39.649 ribbon and actively select heading one, heading 00:08:39.649 --> 00:08:42.450 two, and so on. OK, because the screen readers, 00:08:43.090 --> 00:08:47.450 like JAWS or NVDA, they parse the DOM looking 00:08:47.450 --> 00:08:51.649 for those specific HTML tags. Yes. That underlying 00:08:51.649 --> 00:08:54.690 tagging architecture is the only way a user can 00:08:54.690 --> 00:08:56.909 quickly skip from the introduction straight to 00:08:56.909 --> 00:08:58.909 chapter three. Oh, right. Otherwise, they'd have 00:08:58.909 --> 00:09:00.789 to listen to the whole thing. Exactly. Imagine 00:09:00.789 --> 00:09:03.110 being forced to listen to a robotic voice read 00:09:03.110 --> 00:09:05.470 every single syllable of chapters one and two 00:09:05.470 --> 00:09:08.090 just to find where chapter three starts. That 00:09:08.090 --> 00:09:10.289 sounds agonizing. Yeah. But you know, the friction 00:09:10.289 --> 00:09:12.990 here is very real, and Ackerman actually acknowledges 00:09:12.990 --> 00:09:16.110 it directly. The aesthetic friction. Yes. The 00:09:16.110 --> 00:09:18.690 reason educators and professionals resist using 00:09:18.690 --> 00:09:21.190 those built -in heading styles is that the default 00:09:21.190 --> 00:09:23.669 aesthetics are often just atrocious. Oh they 00:09:23.669 --> 00:09:27.669 can be so ugly. Right. You spend hours crafting 00:09:27.669 --> 00:09:30.870 a syllabus with a specific visual identity and 00:09:30.870 --> 00:09:34.669 then Microsoft Word or Google Docs insists on 00:09:34.669 --> 00:09:38.230 forcing your heading one to be this massive bizarre 00:09:38.230 --> 00:09:41.320 shade of light blue aerial font. Which completely 00:09:41.320 --> 00:09:44.059 ruins the vibe of your design. Completely. And 00:09:44.059 --> 00:09:46.820 it creates a real psychological barrier to compliance. 00:09:47.539 --> 00:09:49.480 Nobody wants their presentation to look like 00:09:49.480 --> 00:09:52.620 a default template from 2005. They don't. But 00:09:52.620 --> 00:09:55.039 the solution Ackerman provides is incredibly 00:09:55.039 --> 00:09:57.340 empowering once you realize how simple it is. 00:09:57.399 --> 00:09:59.559 What's the trick? You are not locked into those 00:09:59.559 --> 00:10:02.500 default aesthetics. The software actually separates 00:10:02.500 --> 00:10:05.019 the visual style from the structural metadata. 00:10:05.340 --> 00:10:07.440 Oh, so you can change how it looks without breaking 00:10:07.440 --> 00:10:10.350 the code. Exactly. You can format a line of text 00:10:10.350 --> 00:10:13.049 to use your preferred custom font size and color 00:10:13.049 --> 00:10:15.610 and then you just right click the heading 1 button 00:10:15.610 --> 00:10:18.149 and select update heading to match selection. 00:10:18.370 --> 00:10:20.409 Wait, really? Just right click and update? That's 00:10:20.409 --> 00:10:22.570 it. In about three seconds, you've permanently 00:10:22.570 --> 00:10:24.789 altered the visual output to match your branding 00:10:24.789 --> 00:10:27.350 while simultaneously injecting that invisible 00:10:27.350 --> 00:10:30.389 HTML architecture that the screen reader desperately 00:10:30.389 --> 00:10:33.470 needs. That is so easy. And Ackerman notes that 00:10:33.470 --> 00:10:35.769 if you feel intimidated by the software menus, 00:10:36.309 --> 00:10:39.289 a 30 -second conversation with your IT department 00:10:39.289 --> 00:10:42.029 will permanently solve the problem for your templates. 00:10:42.649 --> 00:10:45.830 So it's really about realizing that visual design 00:10:45.799 --> 00:10:48.500 and structural metadata don't have to be enemies. 00:10:48.879 --> 00:10:51.399 Beautifully put. And I think that exact same 00:10:51.399 --> 00:10:54.120 philosophy applies to the second architectural 00:10:54.120 --> 00:10:58.000 element Ackerman focuses on, images. Ah, yes, 00:10:58.440 --> 00:11:00.759 alt text. Right. We all know we're supposed to 00:11:00.759 --> 00:11:03.059 use alt text, alternative text, for our pictures. 00:11:03.600 --> 00:11:05.840 But in the rush of throwing together a slide 00:11:05.840 --> 00:11:07.899 deck for a Tuesday morning lecture, it's usually 00:11:07.899 --> 00:11:09.659 the first thing that gets skipped. Because we 00:11:09.659 --> 00:11:12.000 assume the visual context is self -evident. Exactly. 00:11:12.080 --> 00:11:14.159 When a sighted user sees an embedded chart showing 00:11:14.159 --> 00:11:16.759 a rising trend line, their brain processes the 00:11:16.759 --> 00:11:19.440 implication instantly. Ah, profits are up. But 00:11:19.440 --> 00:11:21.840 when a screen reader encounters that image in 00:11:21.840 --> 00:11:24.580 the DOM without alt text, it hits a dead end. 00:11:24.899 --> 00:11:26.779 In the worst case scenario, it will literally 00:11:26.779 --> 00:11:29.500 read the raw file name allowed to the user. Oh, 00:11:29.539 --> 00:11:33.409 like image underscore final version 2 .jpg. Yes, 00:11:33.950 --> 00:11:36.769 deeply unhelpful. Alt text isn't just a caption. 00:11:37.190 --> 00:11:39.929 It's a hidden metadata field where the author 00:11:39.929 --> 00:11:42.549 translates the semantic meaning of the visual 00:11:42.549 --> 00:11:44.950 element into text. So you're basically acting 00:11:44.950 --> 00:11:47.009 as the translator between the visual medium and 00:11:47.009 --> 00:11:49.710 the auditory medium. Exactly. The screen reader 00:11:49.710 --> 00:11:52.370 parses that hidden field and reads your description 00:11:52.370 --> 00:11:55.029 aloud, maintaining the narrative flow of the 00:11:55.029 --> 00:11:57.710 lesson. Which brings up a very pragmatic concern. 00:11:58.029 --> 00:12:00.070 I can imagine the listener doing the math right 00:12:00.070 --> 00:12:02.750 now thinking, OK, wait. I need to structurally 00:12:02.750 --> 00:12:06.169 tag every section with custom headings, and I 00:12:06.169 --> 00:12:08.370 need to manually translate the semantic meaning 00:12:08.370 --> 00:12:11.169 of every single graphic into hidden alt text. 00:12:11.389 --> 00:12:12.730 They're wondering about the time commitment. 00:12:12.830 --> 00:12:15.250 Yeah. Are we talking about doubling the hours 00:12:15.250 --> 00:12:17.990 required to prep a standard slide deck? It is 00:12:17.990 --> 00:12:20.610 the most common anxiety whenever a new technical 00:12:20.610 --> 00:12:23.269 workflow is introduced. But Ackerman stresses 00:12:23.269 --> 00:12:26.029 that ADA compliance does not double your workload. 00:12:26.230 --> 00:12:28.289 Really? It sounds like a lot of extra steps. 00:12:28.750 --> 00:12:31.289 It just recalibrates how you execute the initial 00:12:31.289 --> 00:12:34.909 creation phase. Once building the DOM architecture 00:12:34.909 --> 00:12:37.950 becomes muscle memory, the time difference is 00:12:37.950 --> 00:12:40.429 negligible. And more importantly, we aren't operating 00:12:40.429 --> 00:12:42.490 in an era where you have to manually hunt for 00:12:42.490 --> 00:12:45.269 your own mistakes anymore. Oh, right. The tools 00:12:45.269 --> 00:12:47.909 have evolved. Exactly. The platforms have evolved 00:12:47.909 --> 00:12:50.070 to do the heavy lifting of compliance checking 00:12:50.070 --> 00:12:53.870 for you. So we aren't flying blind. We have automated 00:12:53.870 --> 00:12:56.289 building inspectors to check if our digital architecture 00:12:56.289 --> 00:12:58.809 is up to code. That's a perfect analogy. Let's 00:12:58.809 --> 00:13:01.409 look at the Microsoft ecosystem first. Microsoft 00:13:01.409 --> 00:13:04.409 Office products now feature an incredibly robust 00:13:04.409 --> 00:13:06.990 native accessibility checker. Where do you find 00:13:06.990 --> 00:13:09.919 that? You trigger the tool, and it opens a dedicated 00:13:09.919 --> 00:13:12.039 pane on the right side of your interface. And 00:13:12.039 --> 00:13:14.820 it actively sends the entire DOM of your document 00:13:14.820 --> 00:13:17.159 in real time. So it tells you what's broken while 00:13:17.159 --> 00:13:19.559 you work. Exactly. It identifies missing alt 00:13:19.559 --> 00:13:22.200 text. It highlights skipped heading levels and 00:13:22.200 --> 00:13:24.279 flags elements that a screen reader will struggle 00:13:24.279 --> 00:13:26.879 with. It essentially gamifies the compliance 00:13:26.879 --> 00:13:29.120 process. Oh, I love that. Yeah, you click on 00:13:29.120 --> 00:13:31.379 an error, correct the alt text, and the error 00:13:31.379 --> 00:13:34.629 vanishes from the pane. There is this deeply 00:13:34.629 --> 00:13:37.710 satisfying psychological loop in clearing that 00:13:37.710 --> 00:13:40.029 board before you distribute a file. Gamifying 00:13:40.029 --> 00:13:42.610 the architecture is such a brilliant way to drive 00:13:42.610 --> 00:13:45.269 adoption. But what about the massive segment 00:13:45.269 --> 00:13:48.149 of the educational sector that is entirely embedded 00:13:48.149 --> 00:13:50.389 in G Suite? That's a good point. Google's native 00:13:50.389 --> 00:13:53.509 tools have historically been a bit lighter on 00:13:53.509 --> 00:13:56.360 proactive compliance scanning. They have. And 00:13:56.360 --> 00:13:59.320 Ackerman specifically addresses that Google ecosystem 00:13:59.320 --> 00:14:02.580 gap. For users building out complex presentations 00:14:02.580 --> 00:14:05.539 in Google Slides, he highly recommends unspelling 00:14:05.539 --> 00:14:07.899 third -party add -ons to handle the inspection. 00:14:08.179 --> 00:14:10.159 OK, what does he suggest? He points specifically 00:14:10.159 --> 00:14:12.399 to a tool called Grackle Slides. Grackle Slides. 00:14:12.500 --> 00:14:15.460 Right. Once integrated, Grackle operates very 00:14:15.460 --> 00:14:17.980 similarly to the Microsoft pane. It parses the 00:14:17.980 --> 00:14:20.179 Google Slide DOM to ensure the reading order 00:14:20.179 --> 00:14:23.120 is logical and tags are present. Because reading 00:14:23.120 --> 00:14:26.070 order on slides is notoriously tricky. Oh, it's 00:14:26.070 --> 00:14:29.049 a nightmare. So having an automated parser enforce 00:14:29.049 --> 00:14:31.529 the structural necessities that the native Google 00:14:31.529 --> 00:14:34.350 interface might let you ignore is huge. Yeah, 00:14:34.370 --> 00:14:36.549 that sounds like a game changer. But there is 00:14:36.549 --> 00:14:39.190 another tool Ackerman mentions that tackles an 00:14:39.190 --> 00:14:42.870 entirely different vector of accessibility, color. 00:14:43.190 --> 00:14:45.970 Yes, this is crucial. Because up until now, we've 00:14:45.970 --> 00:14:48.210 been focusing really heavily on screen readers 00:14:48.210 --> 00:14:52.080 and the invisible HTML architecture. But ADA 00:14:52.080 --> 00:14:55.059 compliance also protects users who are sighted, 00:14:55.159 --> 00:14:57.960 but who struggle with low vision, contrast sensitivity, 00:14:58.139 --> 00:15:00.100 or color blindness. And this is where we shift 00:15:00.100 --> 00:15:03.159 from structural coding to the actual mathematics 00:15:03.159 --> 00:15:06.019 of visual design. Okay, mathematics. Yeah. Ackerman 00:15:06.019 --> 00:15:09.799 introduces this free, lightweight piece of software 00:15:09.799 --> 00:15:13.000 available for both Mac and PC called the Color 00:15:13.000 --> 00:15:15.649 Contrast Analyzer. What does it do? It's designed 00:15:15.649 --> 00:15:18.110 to tackle a problem that authors are notoriously 00:15:18.110 --> 00:15:20.870 bad at judging subjectively, which is bad color 00:15:20.870 --> 00:15:22.889 combinations. Right. A designer might think, 00:15:22.889 --> 00:15:25.389 you know, a pastel yellow font on a white background 00:15:25.389 --> 00:15:27.490 looks sleek and modern. Oh, I've seen that. But 00:15:27.490 --> 00:15:30.009 to a user with contrast sensitivity, that text 00:15:30.009 --> 00:15:33.129 literally disappears into the background. I have 00:15:33.129 --> 00:15:36.110 absolutely sat in the back of a conference room 00:15:36.110 --> 00:15:38.889 squinting at a presentation where the speaker 00:15:38.889 --> 00:15:43.039 thought, like... Neon green text on a dark blue 00:15:43.039 --> 00:15:45.740 background was a great idea. It's awful. You 00:15:45.740 --> 00:15:48.220 can feel the physical strain on your eyes trying 00:15:48.220 --> 00:15:50.100 to separate the letters from the background. 00:15:50.299 --> 00:15:52.419 Exactly. So what the color contrast analyzer 00:15:52.419 --> 00:15:55.019 does is it removes human subjectivity from the 00:15:55.019 --> 00:15:57.820 equation entirely. How does it work? It uses 00:15:57.820 --> 00:16:00.509 a really simple eyedropper interface. You sample 00:16:00.509 --> 00:16:02.190 the background color, and then you sample the 00:16:02.190 --> 00:16:04.870 foreground text color. OK. The software immediately 00:16:04.870 --> 00:16:07.149 calculates the relative luminance of those two 00:16:07.149 --> 00:16:09.509 colors against the strict mathematical ratios 00:16:09.509 --> 00:16:12.169 defined by the Web Content Accessibility Guidelines. 00:16:12.250 --> 00:16:15.509 The WCEG. Right, the WCAG. For standard text, 00:16:15.730 --> 00:16:19.129 the ADA compliance ratio is typically 4 .5 to 00:16:19.129 --> 00:16:21.889 1. 4 .5 to 1, OK. The software doesn't give you 00:16:21.889 --> 00:16:24.710 design advice. It just gives you a binary objective 00:16:24.710 --> 00:16:27.830 result based on that math. You get a green checkmark 00:16:27.830 --> 00:16:30.419 indicating the contrast ratio. passes the legal 00:16:30.419 --> 00:16:33.740 threshold, or a red X telling you to pick a darker 00:16:33.740 --> 00:16:36.220 font. It completely eliminates the guesswork. 00:16:36.500 --> 00:16:39.779 Okay, so we've established a really solid workflow 00:16:39.779 --> 00:16:41.980 here. Right. We're using custom -styled headings 00:16:41.980 --> 00:16:44.240 to build the DOM. Right. We're embedding alt 00:16:44.240 --> 00:16:46.139 text, we're running Grackle to check our Google 00:16:46.139 --> 00:16:48.639 slides, and we're validating our color ratios. 00:16:48.820 --> 00:16:51.919 Muscle memory. Exactly. So once the creation 00:16:51.919 --> 00:16:55.039 phase is optimized, the conversation naturally 00:16:55.039 --> 00:16:58.519 shifts to distribution. How do we package these 00:16:58.519 --> 00:17:01.759 pristine digital architectures and send them 00:17:01.759 --> 00:17:03.600 out into the world? And this brings us to the 00:17:03.600 --> 00:17:07.259 ubiquitous PDF. Yes, the PDF. In my experience, 00:17:07.660 --> 00:17:10.180 a significant portion of professionals view the 00:17:10.180 --> 00:17:14.099 save as PDF function as like the ultimate accessibility 00:17:14.099 --> 00:17:16.440 mic drop. Whoa, absolutely. The assumption is 00:17:16.440 --> 00:17:19.099 that because a PDF is universally viewable and 00:17:19.099 --> 00:17:21.099 it locks all your fonts and layout perfectly 00:17:21.099 --> 00:17:23.759 in place, it is inherently accessible to everyone. 00:17:23.900 --> 00:17:26.279 If we connect this to the bigger picture, the 00:17:26.279 --> 00:17:28.680 PDF myth is arguably one of the most dangerous 00:17:28.680 --> 00:17:31.220 traps in digital distribution. Really? Yeah. 00:17:31.480 --> 00:17:34.099 And it echoes the exact same fallacy we discussed 00:17:34.099 --> 00:17:37.200 regarding the cloud. A PDF is a brilliant format 00:17:37.200 --> 00:17:40.299 for guaranteeing device universality. A smartphone, 00:17:40.559 --> 00:17:43.220 a tablet, or a 15 -year -old desktop can all 00:17:43.220 --> 00:17:46.400 render a PDF identically. But rendering pixels 00:17:46.400 --> 00:17:49.660 on a screen does not guarantee human interoperability. 00:17:50.359 --> 00:17:53.640 When you convert a Word document to a PDF, if 00:17:53.640 --> 00:17:56.180 your settings are incorrect, the conversion engine 00:17:56.180 --> 00:17:58.890 will strip out the entire DOM. Wait, really? 00:17:59.009 --> 00:18:01.049 It just deletes it? It deletes your headings, 00:18:01.410 --> 00:18:04.069 erases your alt text, and essentially flightens 00:18:04.069 --> 00:18:06.869 the file into a single massive image. Oh, wow. 00:18:07.250 --> 00:18:09.750 So you could spend hours building the perfect 00:18:09.750 --> 00:18:11.349 invisible architecture. Yeah. And the moment 00:18:11.349 --> 00:18:14.410 you click Save as PDF, you basically bulldoze 00:18:14.410 --> 00:18:16.730 the entire building. You obliterate the architecture. 00:18:17.009 --> 00:18:19.849 A visually impaired student opens the PDF, and 00:18:19.849 --> 00:18:22.210 their screen reader just reports a blank document. 00:18:22.289 --> 00:18:25.109 That is heartbreaking. It is. So, Ackerman is 00:18:25.109 --> 00:18:27.769 very clear on this. If you utilize PDFs... you 00:18:27.769 --> 00:18:30.430 must use Adobe Acrobat's native accessibility 00:18:30.430 --> 00:18:32.910 checker. You have to ensure that the conversion 00:18:32.910 --> 00:18:35.950 process explicitly included document tags, which 00:18:35.950 --> 00:18:38.710 is essentially Adobe's version of the DOM architecture. 00:18:39.130 --> 00:18:41.349 You cannot assume the format handles compliance 00:18:41.349 --> 00:18:44.329 automatically. The tags must survive the export. 00:18:44.730 --> 00:18:46.750 Making sure the structure survives the export 00:18:46.750 --> 00:18:49.210 is a great rule of thumb for static documents. 00:18:50.329 --> 00:18:52.430 But modern education and corporate communication 00:18:52.430 --> 00:18:55.069 aren't just text anymore. Far from it. We are 00:18:55.069 --> 00:18:57.559 heavily reliant on the video frontier. We're 00:18:57.559 --> 00:19:00.200 dealing with moving images, synchronized sound, 00:19:00.619 --> 00:19:03.400 dynamic visual information. How do we ensure 00:19:03.400 --> 00:19:06.180 human interoperability when we introduce dual 00:19:06.180 --> 00:19:10.059 sensory streams? Video is the ultimate accessibility 00:19:10.059 --> 00:19:12.480 hurdle, honestly, because you are demanding the 00:19:12.480 --> 00:19:15.759 user process auditory and visual data simultaneously, 00:19:16.500 --> 00:19:18.279 and building a DOM tree doesn't help someone 00:19:18.279 --> 00:19:20.660 who can't hear the audio track. So what's the 00:19:20.660 --> 00:19:23.490 solution? Ackerman breaks down a highly strategic, 00:19:23.769 --> 00:19:26.150 incredibly efficient workflow for tackling video 00:19:26.150 --> 00:19:28.529 compliance. Instead of struggling with native 00:19:28.529 --> 00:19:30.829 video files and trying to manually code caption 00:19:30.829 --> 00:19:33.809 files, which is awful, he advises leveraging 00:19:33.809 --> 00:19:36.130 the infrastructure of YouTube. Now this is interesting 00:19:36.130 --> 00:19:38.390 because institutional IT departments often push 00:19:38.390 --> 00:19:41.869 back against public platforms. But Ackerman is 00:19:41.869 --> 00:19:44.990 advocating for standard YouTube as the primary 00:19:44.990 --> 00:19:48.480 hosting solution. Yes, specifically for its backend 00:19:48.480 --> 00:19:51.299 tools. Because YouTube has spent billions of 00:19:51.299 --> 00:19:53.740 dollars perfecting automatic speech recognition, 00:19:54.119 --> 00:19:57.440 or ASR. Oh, the auto -captions. Exactly. When 00:19:57.440 --> 00:20:00.200 you upload a video to YouTube, their algorithms 00:20:00.200 --> 00:20:03.599 automatically parse the audio track and generate 00:20:03.599 --> 00:20:06.299 a timed transcript. So you don't have to manually 00:20:06.299 --> 00:20:09.440 sync the timestamps of the text. to the video 00:20:09.440 --> 00:20:12.299 frames. No, which is historically the most agonizing 00:20:12.299 --> 00:20:14.460 part of captioning. It takes forever. It really 00:20:14.460 --> 00:20:17.420 does. But with YouTube, the creator simply enters 00:20:17.420 --> 00:20:20.259 the studio dashboard, opens the auto -generated 00:20:20.259 --> 00:20:23.440 captions, and just corrects the inevitable spelling 00:20:23.440 --> 00:20:26.460 errors or missed punctuation. Just a quick cleanup. 00:20:26.779 --> 00:20:29.599 Exactly. By cleaning up that auto -generated 00:20:29.599 --> 00:20:32.440 transcript, you instantly provide an accurate, 00:20:32.759 --> 00:20:35.799 synchronized, closed captioning track. You bridge 00:20:35.799 --> 00:20:39.019 the gap. That's amazing. Yeah. or hard of hearing 00:20:39.019 --> 00:20:41.880 student can read the exact spoken content in 00:20:41.880 --> 00:20:44.660 real time, completely integrating them into the 00:20:44.660 --> 00:20:47.140 flow of the presentation. It is genuinely remarkable 00:20:47.140 --> 00:20:49.880 how powerful these tools are when you actively 00:20:49.880 --> 00:20:52.059 choose to engage with the mechanics behind them. 00:20:52.140 --> 00:20:54.059 It takes very little time once you know they're 00:20:54.059 --> 00:20:56.430 there. Right. And when you step back and look 00:20:56.430 --> 00:20:59.829 at the arc of this entire conversation, it represents 00:20:59.829 --> 00:21:03.809 a massive paradigm shift in how we view our responsibilities 00:21:03.809 --> 00:21:06.250 as creators. It really does. I mean, we started 00:21:06.250 --> 00:21:09.329 with the purely nostalgic frustration of hardware 00:21:09.329 --> 00:21:12.670 incompatibility, the MSWorks floppy disk failing 00:21:12.670 --> 00:21:15.710 in the MS Word lab. The dark ages. Yeah. And 00:21:15.710 --> 00:21:19.089 then we recognized that graduating to device 00:21:19.089 --> 00:21:22.150 agnostic cloud systems like G Suite didn't actually 00:21:22.150 --> 00:21:25.500 solve the core human problem. Right. The data 00:21:25.500 --> 00:21:27.680 packets were arriving, but the information was 00:21:27.680 --> 00:21:30.380 still heavily encrypted by formatting barriers 00:21:30.380 --> 00:21:32.619 that locked out millions of people. Because we 00:21:32.619 --> 00:21:35.079 spent decades celebrating the fact that the technology 00:21:35.079 --> 00:21:37.559 could finally deliver the file without pausing 00:21:37.559 --> 00:21:39.720 to ask if the human could actually decode the 00:21:39.720 --> 00:21:42.099 file once it arrived. Yes. We forgot about the 00:21:42.099 --> 00:21:44.079 human at the end of the line. But Ackerman's 00:21:44.079 --> 00:21:46.680 roadmap proves that the decoding process doesn't 00:21:46.680 --> 00:21:49.220 require a degree in computer science. It just 00:21:49.220 --> 00:21:51.599 requires intentionality. Just a few extra clicks. 00:21:51.880 --> 00:21:54.150 Exactly. We understand the necessity of using 00:21:54.150 --> 00:21:56.509 built -in headings to construct an avocable DOM 00:21:56.509 --> 00:21:58.849 tree instead of just painting the walls with 00:21:58.849 --> 00:22:01.609 bold text. We understand the semantic translation 00:22:01.609 --> 00:22:04.190 required for alt text so images can be heard 00:22:04.190 --> 00:22:07.299 and not just seen. We know to leverage automated 00:22:07.299 --> 00:22:10.059 parsers like Grackle for Google Slides, the Microsoft 00:22:10.059 --> 00:22:11.920 Checkers, and the objective mathematics of the 00:22:11.920 --> 00:22:14.500 Color Contrast Analyzer to make sure our designs 00:22:14.500 --> 00:22:16.900 aren't inadvertently hiding data. And tagging 00:22:16.900 --> 00:22:20.140 our PDFs. Yes, ensuring PDFs survive the export 00:22:20.140 --> 00:22:23.240 and using YouTube's ASR infrastructure for video 00:22:23.240 --> 00:22:26.819 accessibility. It's a comprehensive, highly manageable 00:22:26.819 --> 00:22:30.779 toolkit. It is. So to you, the listener, the 00:22:30.779 --> 00:22:33.079 next time you sit down to draft a document, build 00:22:33.079 --> 00:22:35.240 a presentation or share a critical update. I 00:22:35.240 --> 00:22:37.180 want you to remember that taking a few extra 00:22:37.180 --> 00:22:39.819 moments to run an accessibility checker is the 00:22:39.819 --> 00:22:41.680 literal difference between broadcasting your 00:22:41.680 --> 00:22:44.279 ideas into a void and guaranteeing your work 00:22:44.279 --> 00:22:47.380 can actually be experienced by everyone. Intentionality 00:22:47.380 --> 00:22:50.180 is the dividing line between rendering data and 00:22:50.180 --> 00:22:52.519 sharing knowledge. And, you know, I want to leave 00:22:52.519 --> 00:22:54.240 you with one final thought to ponder. Oh, please 00:22:54.240 --> 00:22:56.579 do. Something that builds on the technical context 00:22:56.579 --> 00:22:59.359 of Ackerman's work, but looks toward the immediate 00:22:59.519 --> 00:23:02.779 rapidly approaching horizon. If you explore Dr. 00:23:02.980 --> 00:23:04.559 Ackerman's site, you'll notice in the sidebar 00:23:04.559 --> 00:23:07.500 that he produces a podcast called Hutral Plus 00:23:07.500 --> 00:23:10.460 Classroom. OK. And one of his episodes delves 00:23:10.460 --> 00:23:14.900 into the deeply complex topic of bias in AI decision 00:23:14.900 --> 00:23:18.180 making. Wow. That is an incredibly urgent topic 00:23:18.180 --> 00:23:20.180 given how quickly workflows are changing right 00:23:20.180 --> 00:23:22.960 now. It is the defining technological shift of 00:23:22.960 --> 00:23:25.619 this decade. I mean, we are currently witnessing 00:23:25.619 --> 00:23:28.920 the explosive integration of generative AI into 00:23:28.920 --> 00:23:31.299 our daily software. What's everywhere? We are 00:23:31.299 --> 00:23:34.160 increasingly prompting AI agents to automatically 00:23:34.160 --> 00:23:36.900 generate our slide decks, draft our foundational 00:23:36.900 --> 00:23:39.839 syllabi, and instantly format our corporate documents 00:23:39.839 --> 00:23:42.200 just to save time. Sure, super convenient. But 00:23:42.200 --> 00:23:44.680 the provocative architectural question is this. 00:23:45.200 --> 00:23:47.579 As we eagerly hand over the digital heavy lifting 00:23:47.579 --> 00:23:50.299 to these algorithms, are these generative AI 00:23:50.299 --> 00:23:52.859 tools being rigorously trained to automatically 00:23:52.859 --> 00:23:56.000 construct proper DOM trees? Are they enforcing 00:23:56.000 --> 00:23:59.980 ADA contrast ratios natively and generating semantic 00:23:59.980 --> 00:24:03.000 alt text by default? Oh. That's a good question. 00:24:03.480 --> 00:24:06.480 Or are these models simply scraping the vast, 00:24:06.700 --> 00:24:08.839 historically inaccessible internet, learning 00:24:08.839 --> 00:24:11.880 from our decades of lazy formatting, and mass 00:24:11.880 --> 00:24:14.039 producing our inaccessible blind spots at an 00:24:14.039 --> 00:24:17.599 unprecedented automated scale? Wow. It is a structural 00:24:17.599 --> 00:24:19.559 question to deeply consider the next time you 00:24:19.559 --> 00:24:21.619 ask an algorithm to quickly generate a file. 00:24:22.059 --> 00:24:24.259 Are you using AI to automate human accessibility, 00:24:24.400 --> 00:24:26.019 or are you just automating the barriers?