WEBVTT 00:00:00.000 --> 00:00:03.919 Welcome to today's deep dive. I am I'm so glad 00:00:03.919 --> 00:00:05.559 you're joining us today because we are starting 00:00:05.559 --> 00:00:07.440 off with a bit of a thought experiment Oh, I 00:00:07.440 --> 00:00:10.240 love these. Let's hear it. Right. Okay. So I 00:00:10.240 --> 00:00:12.460 want you to imagine you are trying to navigate 00:00:12.460 --> 00:00:15.580 through a sprawling densely populated city you 00:00:15.580 --> 00:00:17.719 have a critically important meeting to get to 00:00:17.719 --> 00:00:21.019 but There is a major catch. There's always a 00:00:21.019 --> 00:00:24.039 catch always all the street signs all the subway 00:00:24.039 --> 00:00:27.800 maps even the crosswalk signals They only appear 00:00:27.800 --> 00:00:31.059 if you are wearing a very specific, very expensive 00:00:31.059 --> 00:00:34.020 brand of glasses. Oh, wow. OK. Yeah. If you don't 00:00:34.020 --> 00:00:36.859 have those glasses, the signs are just, you know, 00:00:37.100 --> 00:00:39.600 blank metal plates. The maps are empty paper. 00:00:40.039 --> 00:00:42.039 The city is still there bustling all around you. 00:00:42.240 --> 00:00:43.960 But the infrastructure, you need to understand 00:00:43.960 --> 00:00:46.479 it to actually move through it is completely 00:00:46.479 --> 00:00:49.090 invisible. That's, I mean, it's a profoundly 00:00:49.090 --> 00:00:51.590 isolating image. You were essentially locked 00:00:51.590 --> 00:00:53.189 out of the flow of information. And the reason 00:00:53.189 --> 00:00:55.570 it's so striking is that it perfectly captures 00:00:55.570 --> 00:00:57.929 the daily reality of the digital landscape for 00:00:57.929 --> 00:01:00.549 millions of people. You know, when accessibility 00:01:00.549 --> 00:01:03.710 isn't baked into the design from the start, that's 00:01:03.710 --> 00:01:06.549 exactly what it feels like. And today we are 00:01:06.549 --> 00:01:08.849 going to explore how that exact scenario plays 00:01:08.849 --> 00:01:11.269 out in one of our most critical environments, 00:01:11.549 --> 00:01:14.200 which is the classroom. We are pulling from an 00:01:14.200 --> 00:01:16.680 incredibly insightful article by Gary Ackerman 00:01:16.680 --> 00:01:20.439 from his site hackscience .education. Yeah, his 00:01:20.439 --> 00:01:23.140 work is fantastic. It really is. The piece is 00:01:23.140 --> 00:01:27.400 titled Ed Tech for IT, Accessibility. And as 00:01:27.400 --> 00:01:29.439 a quick side note for you listening, Ackerman 00:01:29.439 --> 00:01:31.879 also produces this really cool microed audio 00:01:31.879 --> 00:01:35.120 series called Crow Plus Classroom. Oh yeah, the 00:01:35.120 --> 00:01:37.530 short ones. Exactly. It's brilliant because he 00:01:37.530 --> 00:01:40.049 tackles these massive complex topics like ADA 00:01:40.049 --> 00:01:42.989 compliance and inclusivity. But in these incredibly 00:01:42.989 --> 00:01:46.810 tight 90 -second bursts, I mean, it is pure distilled 00:01:46.810 --> 00:01:49.689 insight. Taking the sprawling complexities of 00:01:49.689 --> 00:01:52.030 educational technology and distilling them into 00:01:52.030 --> 00:01:54.269 actionable, bite -sized information is a rare 00:01:54.269 --> 00:01:56.609 skill. He manages to cut right through the academic 00:01:56.609 --> 00:01:59.540 jargon, which is so refreshing. Totally. So our 00:01:59.540 --> 00:02:01.739 mission for this deep dive is to take Ackerman's 00:02:01.739 --> 00:02:04.180 insights and uncover how the legal mandate of 00:02:04.180 --> 00:02:07.219 accessibility in schools has evolved. It's no 00:02:07.219 --> 00:02:08.960 longer just about, you know, checking a bureaucratic 00:02:08.960 --> 00:02:11.460 compliance box just to avoid a lawsuit. Right. 00:02:11.460 --> 00:02:13.520 That's the old way of thinking. Exactly. It is 00:02:13.520 --> 00:02:16.860 actually transformed into this secret underlying 00:02:16.860 --> 00:02:19.659 engine that improves the digital learning experience 00:02:19.659 --> 00:02:23.719 for absolutely everyone. OK, let's unpack this, 00:02:24.139 --> 00:02:28.060 because the way we handle accessibility has fundamentally 00:02:28.060 --> 00:02:29.979 shifted, right? Let's start with the history. 00:02:30.159 --> 00:02:32.379 It has shifted massively, yeah. If we look back 00:02:32.379 --> 00:02:34.199 to the baseline, we really have to start with 00:02:34.199 --> 00:02:37.159 the Americans with Disabilities Act or the ADA, 00:02:37.300 --> 00:02:40.539 which became law back in 1990. Right, 1990. Yeah. 00:02:40.669 --> 00:02:42.990 And this is a foundational civil rights law in 00:02:42.990 --> 00:02:45.689 the United States. Its core intention is to ensure 00:02:45.689 --> 00:02:48.449 that all individuals, regardless of their disability 00:02:48.449 --> 00:02:51.270 status, have equal access to public resources. 00:02:52.310 --> 00:02:54.550 So when we translate that legal mandate into 00:02:54.550 --> 00:02:57.009 the realm of education, it means that every single 00:02:57.009 --> 00:02:59.569 material used in a class, textbooks, handouts, 00:02:59.729 --> 00:03:02.189 media, whatever, it must be available to all 00:03:02.189 --> 00:03:04.330 students. So in the physical classroom of the 00:03:04.330 --> 00:03:07.210 1990s, that basically meant if a teacher handed 00:03:07.210 --> 00:03:09.729 out a traditional printed textbook, the school 00:03:09.729 --> 00:03:12.099 was legally obligated to provide a braille version 00:03:12.099 --> 00:03:15.240 or an audio cassette version for a student who 00:03:15.240 --> 00:03:17.340 needed it. Right, that was the baseline. But 00:03:17.340 --> 00:03:19.860 think about the logistics of that 1990s model. 00:03:20.030 --> 00:03:22.930 The burden of creating those accessible materials 00:03:22.930 --> 00:03:25.509 largely fell on massive publishing companies. 00:03:25.710 --> 00:03:28.729 Right, the textbook giants. Exactly. These giant 00:03:28.729 --> 00:03:31.810 publishers had entire departments, workflows, 00:03:32.409 --> 00:03:34.949 massive budgets dedicated entirely to producing 00:03:34.949 --> 00:03:37.650 alternative versions of their resources. They 00:03:37.650 --> 00:03:40.389 printed the standard textbook, then stamped out 00:03:40.389 --> 00:03:42.889 the Braille textbook, formatted the large print 00:03:42.889 --> 00:03:44.710 textbook. It was just part of the pipeline. Yeah, 00:03:44.710 --> 00:03:47.669 it was a known, highly managed variable in their 00:03:47.669 --> 00:03:50.199 commercial production cycle. Flash forward to 00:03:50.199 --> 00:03:53.340 today, and the landscape of education has changed. 00:03:53.500 --> 00:03:55.860 Drastically. I mean, we aren't just handing out 00:03:55.860 --> 00:03:58.199 identical textbooks anymore. Not at all. Teachers 00:03:58.199 --> 00:04:00.719 are constantly creating their own custom digital 00:04:00.719 --> 00:04:03.099 materials. They're throwing together slide decks 00:04:03.099 --> 00:04:05.460 on a Sunday afternoon, recording instructional 00:04:05.460 --> 00:04:08.379 videos, building custom web portals, formatting 00:04:08.379 --> 00:04:10.819 digital quizzes. And that is where the dynamic 00:04:10.819 --> 00:04:13.319 completely inverts. When teachers become the 00:04:13.319 --> 00:04:15.379 primary creators of instructional materials, 00:04:15.639 --> 00:04:18.220 they simultaneously inherit the legal and ethical 00:04:18.220 --> 00:04:20.279 responsibility of making sure those materials 00:04:20.279 --> 00:04:23.600 are accessible. Which is huge. It is. The burden 00:04:23.600 --> 00:04:26.459 moves practically overnight from a multi -million 00:04:26.459 --> 00:04:29.579 dollar publishing corporation directly onto the 00:04:29.579 --> 00:04:31.779 shoulders of the individual educator. It makes 00:04:31.779 --> 00:04:34.480 me think of building a house. Those massive publishers, 00:04:34.899 --> 00:04:36.360 they're like commercial contractors building 00:04:36.360 --> 00:04:39.160 a skyscraper. They have architects, legal teams, 00:04:39.420 --> 00:04:41.959 and compliance officers ensuring every single 00:04:41.959 --> 00:04:44.540 inch is built strictly to code. Right. They know 00:04:44.540 --> 00:04:47.360 the regulations inside and out. Exactly. But 00:04:47.360 --> 00:04:50.300 individual teachers. They're like DIYers building 00:04:50.300 --> 00:04:52.819 home extensions on the weekends. They are passionate, 00:04:53.040 --> 00:04:55.360 they're working incredibly hard, but they are 00:04:55.360 --> 00:04:58.139 doing it in their spare time, often late at night. 00:04:58.459 --> 00:05:01.519 How on earth does a weekend DIYer know if their 00:05:01.519 --> 00:05:04.019 custom -built digital materials are actually, 00:05:04.019 --> 00:05:07.240 you know, up to code? That is the core tension 00:05:07.240 --> 00:05:10.149 Ackerman points out. A teacher might design a 00:05:10.149 --> 00:05:13.370 highly engaging, visually stunning digital lesson, 00:05:13.790 --> 00:05:16.029 but if a student using a screen reading software 00:05:16.029 --> 00:05:18.990 can't access it, that lesson is fundamentally 00:05:18.990 --> 00:05:21.209 broken. Right. It's the invisible city again. 00:05:21.629 --> 00:05:24.430 Yes. And teachers, for all their deep expertise 00:05:24.430 --> 00:05:27.129 in pedagogy and child development, they are rarely 00:05:27.129 --> 00:05:29.870 trained as digital accessibility compliance officers. 00:05:30.310 --> 00:05:32.649 They need a standardized blueprint. Which brings 00:05:32.649 --> 00:05:35.129 us to the manual. Because if you have thousands 00:05:35.129 --> 00:05:38.230 of DIY teachers trying to build equitable digital 00:05:38.230 --> 00:05:41.009 extensions, they need a rule book. And that rule 00:05:41.009 --> 00:05:44.470 book arrived in a major way in June 2018. It 00:05:44.470 --> 00:05:47.290 did. That is when the World Wide Web Consortium, 00:05:47.430 --> 00:05:49.170 which is the international community, that basically 00:05:49.170 --> 00:05:50.949 develops web standards. Usually we just call 00:05:50.949 --> 00:05:53.970 it the W3C. Right, the W3C. Yeah. They adopted 00:05:53.970 --> 00:05:56.649 the Web Content Accessibility Guidelines version 00:05:56.649 --> 00:05:59.910 2 .1. We usually just abbreviate it to WCAG 2 00:05:59.910 --> 00:06:03.129 .1. This became the absolute gold standard. It 00:06:03.129 --> 00:06:05.670 specifies the exact characteristics that digital 00:06:05.670 --> 00:06:08.930 media must possess to be considered truly accessible. 00:06:09.610 --> 00:06:12.310 So Ackerman breaks this down into four mandatory... 00:06:12.930 --> 00:06:14.870 characteristics or pillars. And I want to walk 00:06:14.870 --> 00:06:16.850 through how a teacher actually applies these 00:06:16.850 --> 00:06:19.310 because, let's be honest, reading a web standard 00:06:19.310 --> 00:06:21.550 manual sounds about as fun as reading a stereo 00:06:21.550 --> 00:06:23.870 instruction booklet. Oh, it is extremely dry 00:06:23.870 --> 00:06:25.990 material. Right. So let's say I'm a teacher and 00:06:25.990 --> 00:06:28.290 I upload a graphic showing the water cycle. The 00:06:28.290 --> 00:06:31.730 first WSAG pillar says my material must be perceivable. 00:06:31.980 --> 00:06:33.720 I assume that just means making sure the image 00:06:33.720 --> 00:06:36.339 isn't blurry. Well, no. It's actually much deeper 00:06:36.339 --> 00:06:39.259 than visual clarity. Perceivable means that the 00:06:39.259 --> 00:06:42.399 information must be presentable to users in ways 00:06:42.399 --> 00:06:45.560 they can actively perceive through multiple sensory 00:06:45.560 --> 00:06:48.220 channels. OK. It cannot be invisible to all of 00:06:48.220 --> 00:06:50.879 their senses. In the case of your water cycle 00:06:50.879 --> 00:06:53.959 graphic, a student who is blind and using a screen 00:06:53.959 --> 00:06:56.680 reader cannot perceive those pixels on the screen. 00:06:57.060 --> 00:06:58.939 The image essentially doesn't exist for them. 00:06:59.240 --> 00:07:01.879 OK. So how do I fix that? I mean, I can't verbally 00:07:01.879 --> 00:07:04.379 describe every single image to the student during 00:07:04.379 --> 00:07:07.220 class. You build the description into the code 00:07:07.220 --> 00:07:09.620 of the document itself. You use something called 00:07:09.620 --> 00:07:12.720 alternative text or alt text. When you upload 00:07:12.720 --> 00:07:15.079 that image, you attach a hidden written description 00:07:15.079 --> 00:07:18.139 to it. Like a tag. Exactly. Now, the how is really 00:07:18.139 --> 00:07:20.720 important here. Bad alt text is just leaving 00:07:20.720 --> 00:07:24.660 the file name, like, you know, IMG4092 .jpg. 00:07:24.879 --> 00:07:26.500 Oh, and the screen reader would just read that 00:07:26.500 --> 00:07:28.680 out. A screen reader will literally read that 00:07:28.680 --> 00:07:34.250 out loud. IMG underscore four zero nine two dot 00:07:34.250 --> 00:07:37.670 JPG, which tells the student absolutely nothing. 00:07:37.870 --> 00:07:40.850 Right, that's useless. Good alt text translates 00:07:40.850 --> 00:07:43.529 the visual data into verbal data. So for your 00:07:43.529 --> 00:07:46.269 graphic it would say a diagram showing the water 00:07:46.269 --> 00:07:49.410 cycle, evaporation from the ocean, condensation 00:07:49.410 --> 00:07:52.439 into clouds, and precipitation as rain. Wow, 00:07:52.620 --> 00:07:54.639 okay. So when the screen reader hits that image 00:07:54.639 --> 00:07:57.519 code, it reads your description aloud, and suddenly 00:07:57.519 --> 00:08:00.399 that visual information is transformed into an 00:08:00.399 --> 00:08:03.259 audible format. The image becomes perceivable. 00:08:03.579 --> 00:08:05.839 That makes so much sense. You're giving the computer 00:08:05.839 --> 00:08:08.199 the script it needs to translate for the student. 00:08:08.560 --> 00:08:10.839 The same would go for video. Right? If I upload 00:08:10.839 --> 00:08:12.899 a video lecture, I have to add closed captions 00:08:12.899 --> 00:08:15.000 because the deaf student needs the audio translated 00:08:15.000 --> 00:08:17.300 into a visual format they can perceive. Precisely. 00:08:17.319 --> 00:08:19.420 You're providing multiple sensory avenues to 00:08:19.420 --> 00:08:21.740 the exact same information. OK, so I've added 00:08:21.740 --> 00:08:24.139 my alt text to the water cycle and I've captioned 00:08:24.139 --> 00:08:26.420 my video. The student can perceive it. But the 00:08:26.420 --> 00:08:28.699 second pillar says the material must be operable. 00:08:29.279 --> 00:08:31.480 If they can already see or hear it, what does 00:08:31.480 --> 00:08:34.419 operable actually mean? Operability is all about 00:08:34.419 --> 00:08:36.700 how the user interacts with the digital environment. 00:08:37.100 --> 00:08:39.639 The most common hurdle here involves navigation. 00:08:40.240 --> 00:08:42.019 Think about how you typically scroll through 00:08:42.019 --> 00:08:45.379 a web page or click a link. Just grab my mouse 00:08:45.379 --> 00:08:48.059 and click it. Right. But using a mouse requires 00:08:48.059 --> 00:08:51.120 a very specific type of fine motor control and 00:08:51.120 --> 00:08:54.220 hand -eye coordination. Many individuals with 00:08:54.220 --> 00:08:56.840 motor disabilities rely entirely on a keyboard 00:08:56.840 --> 00:08:59.500 to navigate a computer. Just the keyboard. Just 00:08:59.500 --> 00:09:02.580 the keyboard. Using the Tab key to jump between 00:09:02.580 --> 00:09:05.200 links, the Enter key to select, the arrow keys 00:09:05.200 --> 00:09:08.500 to scroll. if you design a custom digital quiz 00:09:08.500 --> 00:09:11.659 that requires a student to drag and drop answers 00:09:11.659 --> 00:09:14.220 using a mouse, and you haven't coded a way to 00:09:14.220 --> 00:09:16.879 do that using just the keyboard. Oh, you've completely 00:09:16.879 --> 00:09:18.440 locked them out? You've completely locked that 00:09:18.440 --> 00:09:21.019 student out. They can perceive the quiz, but 00:09:21.019 --> 00:09:23.820 they cannot operate it. Oh, wow. I wouldn't have 00:09:23.820 --> 00:09:26.379 even thought of that. If the software doesn't 00:09:26.379 --> 00:09:28.740 recognize a tab keystroke, the student is just 00:09:28.740 --> 00:09:30.960 stuck staring at a quiz they can't take. Hmm. 00:09:31.370 --> 00:09:33.929 And Ackerman also mentioned something under this 00:09:33.929 --> 00:09:37.970 pillar about flashing displays. Yes, this is 00:09:37.970 --> 00:09:41.070 a critical safety mechanism. Content must not 00:09:41.070 --> 00:09:43.669 be designed in a way that is known to cause seizures 00:09:43.669 --> 00:09:46.409 or physical reactions. Right. Rapid strobing 00:09:46.409 --> 00:09:49.090 effects or certain high contrast animations can 00:09:49.090 --> 00:09:52.090 trigger photosensitive epilepsy. Operability 00:09:52.090 --> 00:09:53.730 isn't just about being able to click a button. 00:09:53.830 --> 00:09:55.850 It is about ensuring the digital environment 00:09:55.850 --> 00:09:58.490 is physically safe to interact with. Which brings 00:09:58.490 --> 00:10:01.220 us to the third pillar. Yeah. Let's say the student 00:10:01.220 --> 00:10:03.919 can perceive my quiz and they can safely operate 00:10:03.919 --> 00:10:06.480 it using their keyboard. The third requirement 00:10:06.480 --> 00:10:10.000 is that the material must be understandable. 00:10:10.340 --> 00:10:13.240 This feels a bit, I don't know, redundant. If 00:10:13.240 --> 00:10:15.659 it's perceivable and operable, isn't it inherently 00:10:15.659 --> 00:10:17.700 understandable? Not necessarily. Think of it 00:10:17.700 --> 00:10:20.220 this way. Perceivable and operable deal with 00:10:20.220 --> 00:10:22.980 sensory and physical access. Understandable deals 00:10:22.980 --> 00:10:25.600 with cognitive access. It is about the logic 00:10:25.600 --> 00:10:27.379 of the user interface. Okay, give me an example. 00:10:28.090 --> 00:10:30.450 If your student is tabbing through that digital 00:10:30.450 --> 00:10:33.809 quiz using their keyboard, the order their cursor 00:10:33.809 --> 00:10:36.490 moves should be logical. It should go from question 00:10:36.490 --> 00:10:40.129 one to answer A, B, C, then to question two. 00:10:40.990 --> 00:10:44.149 If the focus jumps randomly from question one 00:10:44.149 --> 00:10:46.549 down to the footer of the page, then back up 00:10:46.549 --> 00:10:48.850 to question four. That would be incredibly confusing. 00:10:49.110 --> 00:10:51.169 Exactly. The operation isn't understandable. 00:10:51.389 --> 00:10:53.509 Oh, I see. It's about predictability. It's also 00:10:53.509 --> 00:10:55.990 about clear communication when things go wrong. 00:10:56.549 --> 00:10:59.690 If a student makes an error on a digital form, 00:11:00.070 --> 00:11:02.529 the error message needs to explicitly explain 00:11:02.529 --> 00:11:05.649 what went wrong and how to fix it. Just flashing 00:11:05.649 --> 00:11:08.769 a generic red X isn't understandable. Yeah, that's 00:11:08.769 --> 00:11:10.990 just frustrating. And the navigation of a class 00:11:10.990 --> 00:11:12.990 website should be consistent. You don't want 00:11:12.990 --> 00:11:15.590 the main menu on the left side on Monday and 00:11:15.590 --> 00:11:17.490 then hidden in a drop -down menu on the right 00:11:17.490 --> 00:11:20.250 side on Tuesday. Keep it logical. Keep the cognitive 00:11:20.250 --> 00:11:23.519 load low. I'm with you. But now we hit the fourth 00:11:23.519 --> 00:11:25.179 pillar, and I have to be honest, I need to push 00:11:25.179 --> 00:11:27.059 back on this one. Let's hear it. The fourth pillar 00:11:27.059 --> 00:11:30.080 is that materials must be robust. Ackerman notes 00:11:30.080 --> 00:11:32.379 this means materials must be compatible both 00:11:32.379 --> 00:11:34.879 forward and backward in time. That is the standard, 00:11:35.039 --> 00:11:37.940 yes. But technology changes at an absolutely 00:11:37.940 --> 00:11:40.679 lightning speed. Telling a busy teacher that 00:11:40.679 --> 00:11:42.899 the digital worksheet they're scrambling to finish 00:11:42.899 --> 00:11:45.860 on a Tuesday night needs to be compatible forward 00:11:45.860 --> 00:11:48.960 and backward in time sounds completely unreasonable. 00:11:49.159 --> 00:11:51.210 It does sound like a lot. I mean, I remember 00:11:51.210 --> 00:11:54.110 trying to code my MySpace page back in 2006, 00:11:54.389 --> 00:11:56.289 and if I put one bracket in the wrong place, 00:11:56.590 --> 00:11:59.629 the whole page got fire. How is an algebra teacher 00:11:59.629 --> 00:12:02.230 supposed to future -proof their lesson against 00:12:02.230 --> 00:12:04.289 whatever operating system Apple is going to release 00:12:04.289 --> 00:12:06.820 in 2030? What's fascinating here is that the 00:12:06.820 --> 00:12:09.139 requirement for robustness isn't actually asking 00:12:09.139 --> 00:12:11.860 teachers to be fortune tellers or master programmers. 00:12:12.259 --> 00:12:15.139 It is asking them to rely on clean, standard 00:12:15.139 --> 00:12:18.179 coding practices rather than chasing the newest, 00:12:18.519 --> 00:12:20.720 flashiest technological gimmick. OK, but how 00:12:20.720 --> 00:12:23.519 does standard code survive time better than new 00:12:23.519 --> 00:12:26.240 tech? Because assistive technologies like screen 00:12:26.240 --> 00:12:28.600 readers or specialized braille keyboards are 00:12:28.600 --> 00:12:31.379 often incredibly complex and highly customized 00:12:31.379 --> 00:12:34.379 for the user. Students in schools simply cannot 00:12:34.379 --> 00:12:36.820 afford to upgrade these expensive devices every 00:12:36.820 --> 00:12:39.179 time a software company releases a minor update. 00:12:39.539 --> 00:12:41.679 Oh, that makes sense. The hardware's a bottleneck. 00:12:41.899 --> 00:12:44.899 Right. If a teacher builds a document using standard 00:12:44.899 --> 00:12:47.440 HTML text and basic heading structures, which 00:12:47.440 --> 00:12:50.000 have been around for decades, it will be robust. 00:12:50.480 --> 00:12:52.419 A screen reader from five years ago can parse 00:12:52.419 --> 00:12:54.980 that standard code perfectly, and a screen reader 00:12:54.980 --> 00:12:56.960 five years in the future will still be able to 00:12:56.960 --> 00:12:58.899 parse it because it's the foundational language 00:12:58.899 --> 00:13:02.440 of the web. Ah. But if the teacher decides to 00:13:02.440 --> 00:13:06.019 use some proprietary, highly animated, flash 00:13:06.019 --> 00:13:08.919 -in -the -pan widget they found on a random education 00:13:08.919 --> 00:13:11.320 blog. That's where the material breaks. If that 00:13:11.320 --> 00:13:13.980 fancy widget only works on the absolute newest 00:13:13.980 --> 00:13:17.100 version of one specific web browser, it violates 00:13:17.100 --> 00:13:19.679 the robust pillar. Because as soon as that browser 00:13:19.679 --> 00:13:22.360 updates, or if the student is using an older 00:13:22.360 --> 00:13:25.179 assistive device, the code shatters. So it's 00:13:25.179 --> 00:13:28.340 about simplicity, really? Yes. Robustness simply 00:13:28.340 --> 00:13:31.259 means maximizing compatibility. by sticking to 00:13:31.259 --> 00:13:34.399 the basics. Without that unshakable foundation, 00:13:34.799 --> 00:13:37.440 educational equity is entirely at the mercy of 00:13:37.440 --> 00:13:39.539 the next random software update. Yeah, it completely 00:13:39.539 --> 00:13:41.779 flips my perspective. It's not about anticipating 00:13:41.779 --> 00:13:43.519 the future. It's about building a foundation 00:13:43.519 --> 00:13:46.000 so solid that it doesn't matter when the wind 00:13:46.000 --> 00:13:49.299 changes. Exactly. But let's take a step back, 00:13:49.820 --> 00:13:52.899 ensuring that every single digital material is 00:13:52.899 --> 00:13:56.340 perceivable with alt text, operable via keyboard, 00:13:57.100 --> 00:13:59.539 understandable in its layout, and robustly coded. 00:13:59.789 --> 00:14:03.629 That is a massive checklist, especially when 00:14:03.629 --> 00:14:06.029 traditionally we think of this effort as being 00:14:06.029 --> 00:14:08.710 for a relatively small subset of students who 00:14:08.710 --> 00:14:10.830 have documented disabilities. It sounds like 00:14:10.830 --> 00:14:13.509 a monumental heavy lift for a niche outcome, 00:14:13.769 --> 00:14:16.409 but this is the exact moment where the narrative 00:14:16.409 --> 00:14:18.789 around accessibility transforms. Here's where 00:14:18.789 --> 00:14:21.649 it gets really interesting. because Ackerman 00:14:21.649 --> 00:14:24.110 points out a massive unexpected payoff to all 00:14:24.110 --> 00:14:27.230 this work. While these WCAG standards were originally 00:14:27.230 --> 00:14:29.529 engineered to provide access for those with specific 00:14:29.529 --> 00:14:32.049 disabilities, educators are finding that resources 00:14:32.049 --> 00:14:33.889 meeting these standards actually improve the 00:14:33.889 --> 00:14:36.230 learning experience for all students, universally. 00:14:36.490 --> 00:14:38.830 It is a phenomenon that physical accessibility 00:14:38.830 --> 00:14:41.850 advocates have known about for decades, and seeing 00:14:41.850 --> 00:14:44.549 it map perfectly onto digital education is just 00:14:44.549 --> 00:14:46.610 incredible. It's the curb -cut effect. For anyone 00:14:46.610 --> 00:14:48.649 unfamiliar, the curb -cut effect comes from physical 00:14:48.649 --> 00:14:51.419 urban planning. Back in the day, sidewalks just 00:14:51.419 --> 00:14:53.500 dropped off sharply into the street at an intersection. 00:14:53.960 --> 00:14:56.879 Right, a literal step down. Yeah. Disability 00:14:56.879 --> 00:14:59.480 advocates fought incredibly hard for curb cuts. 00:15:00.039 --> 00:15:02.200 Those little ramps carved into the corner of 00:15:02.200 --> 00:15:04.759 the sidewalk, specifically so individuals in 00:15:04.759 --> 00:15:06.600 wheelchairs could cross the street independently. 00:15:07.419 --> 00:15:09.460 It was a targeted intervention for a specific 00:15:09.460 --> 00:15:11.909 group. But once those physical curb cuts were 00:15:11.909 --> 00:15:14.710 installed, society realized something unexpected. 00:15:15.009 --> 00:15:17.529 Right. Everyone started using them. Parents pushing 00:15:17.529 --> 00:15:19.409 heavy strollers didn't have to lift them over 00:15:19.409 --> 00:15:22.049 the curb. Travelers dragging rolling luggage 00:15:22.049 --> 00:15:24.750 could glide right into the crosswalk. Delivery 00:15:24.750 --> 00:15:27.370 workers with hand trucks, kids on skateboards, 00:15:27.909 --> 00:15:30.470 a design mandate intended for wheelchairs, ended 00:15:30.470 --> 00:15:32.549 up making the physical environment smoother and 00:15:32.549 --> 00:15:34.789 more efficient for the entire population. And 00:15:34.789 --> 00:15:37.029 that exact same dynamic occurs in the digital 00:15:37.029 --> 00:15:39.750 classroom. Let's look at those WKCAGA pillars 00:15:39.750 --> 00:15:42.370 again, but this time through the lens of the 00:15:42.370 --> 00:15:45.289 digital curb cut. Take closed captions on a video. 00:15:45.809 --> 00:15:48.049 The ADA mandates them so a student who is deaf 00:15:48.049 --> 00:15:51.070 can perceive the content. But who else uses closed 00:15:51.070 --> 00:15:53.450 captions? Oh, a student trying to watch a lecture 00:15:53.450 --> 00:15:55.710 in a noisy cafeteria who forgot their headphones. 00:15:56.789 --> 00:15:59.799 Or... a student whose first language isn't English, 00:16:00.419 --> 00:16:02.679 who heavily benefits from reading the words while 00:16:02.679 --> 00:16:05.460 hearing them spoken to reinforce their comprehension. 00:16:05.740 --> 00:16:09.019 Exactly. Or consider the requirement for structured 00:16:09.019 --> 00:16:12.919 digital text and clear navigation cues, the understandable 00:16:12.919 --> 00:16:16.419 and robust pillars, originally designed so screen 00:16:16.419 --> 00:16:18.940 readers could logically parse the code of a document. 00:16:19.519 --> 00:16:22.019 But who else benefits from a cleanly formatted 00:16:22.019 --> 00:16:25.059 document with clear, predictable headings instead 00:16:25.059 --> 00:16:27.679 of a giant wall of text? A student who's just 00:16:27.679 --> 00:16:31.019 exhausted. You know, running on coffee, studying 00:16:31.019 --> 00:16:32.879 at two in the morning on a tiny phone screen. 00:16:33.240 --> 00:16:35.179 They don't have the mental energy to hunt through 00:16:35.179 --> 00:16:37.500 a chaotic layout. The clear structure lowers 00:16:37.500 --> 00:16:39.700 the cognitive load for them too. That is the 00:16:39.700 --> 00:16:42.240 ultimate mechanism at play here. Cognitive load. 00:16:42.480 --> 00:16:44.980 When you design for the margins, for the extreme 00:16:44.980 --> 00:16:47.980 use cases, you inherently remove friction from 00:16:47.980 --> 00:16:49.840 the core experience. Wow, that's a great way 00:16:49.840 --> 00:16:52.860 to put it. And when you remove digital friction, 00:16:53.299 --> 00:16:55.379 the mental energy that a student was wasting 00:16:55.379 --> 00:16:58.139 just trying to access or navigate the material 00:16:58.139 --> 00:17:00.919 can be redirected toward actually understanding 00:17:00.919 --> 00:17:03.659 the concept. It transforms accessibility from 00:17:03.659 --> 00:17:06.900 a burden of compliance into a literal strategy 00:17:06.900 --> 00:17:09.970 for excellence. But even knowing that this curb 00:17:09.970 --> 00:17:12.569 cut effect benefits everyone, we are still asking 00:17:12.569 --> 00:17:15.569 our DIY weekend warrior teachers to write alt 00:17:15.569 --> 00:17:18.630 text, test keyboard operability, and audit their 00:17:18.630 --> 00:17:21.930 code for robustness. It's a lot to ask. That 00:17:21.930 --> 00:17:24.250 is a massive amount of technical overhead for 00:17:24.250 --> 00:17:26.269 someone whose primary job is teaching eighth 00:17:26.269 --> 00:17:28.769 grade history. They cannot be expected to manage 00:17:28.769 --> 00:17:31.170 this technical audit alone. Nor should they be. 00:17:31.529 --> 00:17:33.809 And this is where critical, often overlooked 00:17:33.809 --> 00:17:36.890 group steps into the spotlight. Ackerman explicitly 00:17:36.890 --> 00:17:39.750 calls out the vital role of school IT professionals 00:17:39.750 --> 00:17:41.809 in this ecosystem. I'm so glad he brought this 00:17:41.809 --> 00:17:43.609 up, because I think people often view school 00:17:43.609 --> 00:17:46.490 IT departments purely as the folks who unblock 00:17:46.490 --> 00:17:48.650 the jammed printer or, you know, reset the Wi 00:17:48.650 --> 00:17:50.609 -Fi router when it goes down. Right. It is a 00:17:50.609 --> 00:17:54.029 very real - perception of their role. But Ackerman 00:17:54.029 --> 00:17:57.650 argues that IT professionals must be the proactive 00:17:57.650 --> 00:18:00.170 infrastructure supporting teachers in this endeavor. 00:18:00.950 --> 00:18:04.049 If teachers are the DIY builders, IT professionals 00:18:04.049 --> 00:18:06.829 are the building inspectors providing the specialized 00:18:06.829 --> 00:18:09.750 tools. So what does that look like mechanically? 00:18:10.250 --> 00:18:13.170 How does an IT department audit thousands of 00:18:13.170 --> 00:18:15.700 documents created by hundreds of teachers? It 00:18:15.700 --> 00:18:17.819 starts by configuring the technical environment 00:18:17.819 --> 00:18:20.140 so that accessibility is the default setting, 00:18:20.279 --> 00:18:22.839 rather than an afterthought. For instance, most 00:18:22.839 --> 00:18:25.559 modern productivity suites, like Microsoft Office 00:18:25.559 --> 00:18:28.839 or Google Workspace, they have automated accessibility 00:18:28.839 --> 00:18:31.380 checkers built right in. Oh, really? Yeah. They 00:18:31.380 --> 00:18:33.519 work a lot like a spell checker, but for code. 00:18:33.880 --> 00:18:36.000 As a teacher types, the software scans the document 00:18:36.000 --> 00:18:38.660 and flags if an image is missing alt text or 00:18:38.660 --> 00:18:40.799 if the color contrast of a font is too low to 00:18:40.799 --> 00:18:42.680 be readable. Like a little red squiggly line. 00:18:42.880 --> 00:18:45.279 Exactly. The IT department's job is to deploy 00:18:45.279 --> 00:18:48.000 these tools domain -wide, ensure they are activated, 00:18:48.440 --> 00:18:50.440 and train the teachers on what those warnings 00:18:50.440 --> 00:18:52.599 mean. So it's about empowering the teacher with 00:18:52.599 --> 00:18:54.539 automated feedback right at the point of creation. 00:18:54.880 --> 00:18:58.400 Yes, but IT also carries a broader auditing responsibility. 00:18:59.059 --> 00:19:01.359 They use specialized software that acts almost 00:19:01.359 --> 00:19:04.460 like a search engine spider. This software crawls 00:19:04.460 --> 00:19:07.220 the school's internal network, scanning learning 00:19:07.220 --> 00:19:09.799 management systems and public websites, generating 00:19:09.799 --> 00:19:12.599 reports on compliance failures. Oh, wow. Yeah, 00:19:12.680 --> 00:19:15.539 they can instantly see, okay, 40 % of the videos 00:19:15.539 --> 00:19:17.859 uploaded this semester lack closed captions. 00:19:18.380 --> 00:19:20.619 They are the ultimate quality assurance team. 00:19:20.829 --> 00:19:23.329 If we connect this to the bigger picture, the 00:19:23.329 --> 00:19:25.829 IT department is really acting as the crucial 00:19:25.829 --> 00:19:28.650 bridge here. Think about the span of that bridge. 00:19:28.829 --> 00:19:31.230 On one side, you have a foundational civil rights 00:19:31.230 --> 00:19:34.289 law from 1990, the ADA. In the middle, you have 00:19:34.289 --> 00:19:36.890 a highly technical set of international web standards 00:19:36.890 --> 00:19:41.109 from 2018 WCAG G2 .1. And on the far side, you 00:19:41.109 --> 00:19:44.390 have the daily, messy, fast -paced reality of 00:19:44.390 --> 00:19:47.250 a teacher trying to deliver a lesson to 30 distracted 00:19:47.250 --> 00:19:51.240 kids on a Wednesday morning. translators. They 00:19:51.240 --> 00:19:53.660 take the heavy legal mandate and the dense technical 00:19:53.660 --> 00:19:56.220 code, and they build the invisible infrastructure 00:19:56.220 --> 00:19:58.720 that allows the teacher to actually deliver equitable 00:19:58.720 --> 00:20:01.599 education. Without IT running those domain -wide 00:20:01.599 --> 00:20:03.960 scans and setting up the automated checkers, 00:20:04.599 --> 00:20:07.740 the law is just words on a page, and the standard 00:20:07.740 --> 00:20:10.690 is just a theoretical ideal. They make the invisible 00:20:10.690 --> 00:20:13.509 infrastructure visible and functional. So let's 00:20:13.509 --> 00:20:15.009 bring this all together. We started with the 00:20:15.009 --> 00:20:18.230 isolated city and we've walked through how digital 00:20:18.230 --> 00:20:21.109 accessibility in education has evolved into this 00:20:21.109 --> 00:20:24.349 intricate shared ecosystem. You have civil rights 00:20:24.349 --> 00:20:27.490 laws setting the moral baseline. You have international 00:20:27.490 --> 00:20:29.430 web guidelines providing the technical manual. 00:20:29.529 --> 00:20:31.349 You have teachers doing the hard work of building 00:20:31.349 --> 00:20:33.890 the daily learning materials. And you have I 00:20:33.890 --> 00:20:36.589 .T. professionals acting as the backbone, ensuring 00:20:36.589 --> 00:20:38.710 the whole system holds together. It's a profound. 00:20:38.700 --> 00:20:41.700 shift in how we view the responsibility of digital 00:20:41.700 --> 00:20:43.940 creation. So what does this all mean for you? 00:20:44.079 --> 00:20:46.660 Even if you aren't a teacher or a school IT director, 00:20:47.079 --> 00:20:49.279 this applies to your life right now. Whether 00:20:49.279 --> 00:20:51.440 you are drafting a corporate memo to your team, 00:20:51.940 --> 00:20:53.819 designing a basic landing page for your small 00:20:53.819 --> 00:20:56.579 business, or just sending a highly complex email 00:20:56.579 --> 00:20:59.619 outlining a project plan, you are a digital creator. 00:20:59.779 --> 00:21:02.640 We all are, really. We are. And if you apply 00:21:02.640 --> 00:21:05.099 these four pillars, making sure your content 00:21:05.099 --> 00:21:08.910 is perceivable with descriptive text. operable 00:21:08.910 --> 00:21:11.690 without bizarre constraints, understandable with 00:21:11.690 --> 00:21:14.890 logical flow, and robust enough to work cleanly 00:21:14.890 --> 00:21:17.549 across devices, you will make your communication 00:21:17.549 --> 00:21:19.750 infinitely more effective for whoever receives 00:21:19.750 --> 00:21:22.910 it. You are building digital curb cuts in your 00:21:22.910 --> 00:21:25.450 own daily life. And that leads to a fascinating 00:21:25.450 --> 00:21:27.809 implication about the future of how we interact 00:21:27.809 --> 00:21:30.480 with information. We have spent this time talking 00:21:30.480 --> 00:21:32.759 about how accessible design makes information 00:21:32.759 --> 00:21:35.480 clearer and more robust for human minds, but 00:21:35.480 --> 00:21:38.180 consider what else relies entirely on clear, 00:21:38.519 --> 00:21:40.779 structured, digital data to learn and operate. 00:21:41.119 --> 00:21:43.160 Artificial intelligence. Artificial intelligence. 00:21:43.539 --> 00:21:45.759 Large language models and web crawlers read the 00:21:45.759 --> 00:21:47.579 internet in a way that is remarkably similar 00:21:47.579 --> 00:21:49.619 to how a screen reader operates. They don't have 00:21:49.619 --> 00:21:52.299 human eyes, they parse code, structure, and text 00:21:52.299 --> 00:21:54.619 descriptions. Wow, I never thought of that. This 00:21:54.619 --> 00:21:56.539 raises an important question for you to ponder. 00:21:56.799 --> 00:22:00.079 As we integrate AI deeper into our daily lives, 00:22:00.559 --> 00:22:02.640 could strictly following human accessibility 00:22:02.640 --> 00:22:06.579 standards like WCAG 2 .1 soon become the baseline 00:22:06.579 --> 00:22:09.140 requirement simply to ensure your content is 00:22:09.140 --> 00:22:12.359 visible to AI systems. We might soon find that 00:22:12.359 --> 00:22:14.700 designing for digital equity is also the ultimate 00:22:14.700 --> 00:22:17.160 strategy for digital survival in the AI age. 00:22:17.480 --> 00:22:19.779 That is an incredible thought to leave on. Designing 00:22:19.779 --> 00:22:21.799 for the margins might end up being the key to 00:22:21.799 --> 00:22:24.039 communicating with machines of the future. Thank 00:22:24.039 --> 00:22:26.650 you for joining us on this deep dive. Next time 00:22:26.650 --> 00:22:29.150 you encounter a blank digital wall, we hope you 00:22:29.150 --> 00:22:31.250 remember the power of the invisible infrastructure. 00:22:31.910 --> 00:22:32.609 Until next time.