Skip to main content
Skip to Main Content
Skip to main content
Navigation

Best Practices to Reach All Learners in Our STEM Classrooms

In this keynote presentation from the 2025 VEX Robotics Educators Conference, Jason McKenna, VP of Global Educational Strategy for VEX Robotics, explores how to make STEM education truly accessible to every student. Moving beyond viewing STEM as just another subject, this talk demonstrates how thoughtful accessibility in STEM education benefits all learners. Watch this video to learn about practical solutions and innovative approaches that are transforming STEM classrooms into inclusive spaces where every student can thrive.

A PDF version of this keynote presentation’s slides is linked below the video.
 

VEX Robotics Educators Conference. I'm going to get started on today's keynote, and we're going to talk about Best Practices to Reach Learners in STEM Classrooms. So, if you don't know by now, I am Jason McKenna. I'm the Vice President of Global Educational Strategy for VEX Robotics, and we're going to talk about accessibility here today. We're going to talk specifically about the work that we've done here at VEX for the last approximate year to build accessibility into all of our products. When I say products, I'm going to show you examples from hardware. I'm going to show you examples from software. I'm going to show you examples from websites and also our curriculum. Okay? So let's start first of all talking about why. Okay? Now, I am not going to weigh deeply into politics here, but you know, but there's obviously been a lot of stuff in the news about DEI, so on and so forth. But accessibility is the law. If you don't believe me, try to open an apartment building and not include something like a wheelchair ramp. Okay? Accessibility is the law, all right? Access. This is the law right here, okay? Accessibility is the law, okay? Accessibility is the law of the land. Specifically what we are talking about, and what I'm going to be talking about here and what impacts all of you as teachers is Title two of the Americans With Disabilities Act.

This applies to state and local government entities, including public schools. It addresses web and mobile accessibility issues. Okay? This has been very challenging for us, okay? Because when you talk about web and mobile accessibility issues, how does this affect things like the touch screen on an AIM robot? Is that a website? Is that a mobile site? What about things like that, like on, on like a VEX IQ robot or the VEX IQ brain, right? The screen on that, is that a website? Okay? Is that a mobile site? So these are kind of, these are all the things that we really had to dive into when we were thinking about these things. How does Title two and the American With Disabilities Act, how does that affect a thing like a robot? All right? How does that affect us?

I, what does it actually mean? Right? What does this actually mean? Okay? A public entity, that's you, schools, shall ensure that the following are readily accessible and usable by individuals with disabilities, web content, that a public entity provides or makes available directly or through contractual licensing or other arrangements. So stuff like Code.org, VEXcode, Scratch, okay?

All those particular things. Mobile apps. So all the apps that you use, right? For your school, all the apps that you use, okay? That a public entity provides or makes available directly or through contractual licensing or other arrangements. Here's the key thing right here.

Level of compliance is WCAG 2.1 AA. WCAG stands for the Web Content Accessibility Guidelines. Okay? Web Content Accessibility Guidelines. In my office, we are experts on the web content accessibility guidelines. I'm going to give you examples of that here in a moment. So what this essentially means is if you are, for example, delivering curriculum to your students, okay? If you're delivering curriculum to your students through web content, okay? Using a third party service, obviously, or through mobile apps, it has to reach this threshold. Has to reach this threshold. Web Content 2.1 AA. This is the law. Now, where is the levels of compliance? Government entities larger than 50,000 students, April 24th, 2026. Government entities smaller than 50,000 students. So the government wants to give smaller schools, obviously, more time to reach levels of compliance is April 27th, 2027. Some states have pursued this more aggressively, specifically the states of Maryland and Colorado. So, states of Maryland, anyone here from Maryland and Colorado? Yeah. So you know this very, very well. You're nodding your heads, yes. So states of Maryland and Colorado, it's right now. So in the states of Maryland and Colorado, they are saying right now, if you are delivering content, web content to your students, it has to reach WCAG 2.1 compliance.

It has to. If it is not, you are violating the law. And the people liable is the school.

So it's the school's responsibility to make sure that if you are using a vendor, that service that you are using is reaching this particular threshold. The school's liable. So they're not coming after VEX, they're coming after you, just so you know. Okay?

Then there's this other part, also, section 508. What is section 508? In '98, Congress amended the Rehabilitation Act of 1973 to require federal agencies to make their electronic and informational technology accessible to people with disabilities. So, again, when you start talking about this stuff, electronic and informational technology accessible to people with disabilities. Does that mean a robot?

Does that mean a construction site? This is the, these are the things that we've been struggling with. I say struggle, I'm not sure if struggle is the right word, but this is what we've been thinking about very, very deeply, right? To ensure that our stuff is reaching, when I say stuff, I'm talking about our software, our hardware, our curriculum, making sure that all of our things, okay? Reach this threshold to make sure that we are essentially in adherence to the law, okay? So, again, I don't wanna weigh deeply into politics, but I want to be clear with you, this is the law, okay? This is the law. This is the American With Disabilities Act. Okay? This is the law, okay? Now, but beyond the law, what we've learned going through this process, and I'll talk about specifically what we've learned from VEX as we've gone through this, is when you prioritize accessibility, you create a better learning experience for everyone. Okay? Now, I talked about, when I started off this presentation, that we've recorded all the different presentations that we've done, and I would highly encourage you to, if you did not get a chance to watch the presentation from Andreas Stefik. So I'll be the first to admit, I am not the smartest person in this room.

So, when we face challenges like this, like how do we get our web content to reach WCAG 2.1? How do we get VEXcode to reach WCAG 2.1? We don't try to figure this stuff out on our own, right? We go and we talk to experts. And in this field, when we talk about accessibility, Stefik is an expert in this. He's been thinking about this for the last 10 to 15 years. This is what he does, right? These are the research questions that he's been exploring for the last 10 years, okay? And his view on accessibility is not limited to people with disabilities. And in his talk, when he spoke about this, he talked about, if you have a student that just broke up with his boyfriend or girlfriend during lunch and you're teaching him that very next class, guess what? They're going to have a barrier to learning, okay? You have to address that as a teacher. If you have a student that comes to your class hungry, that's a barrier to learning. If you have, and I had this one I taught, if you had students that rode a bus for two hours coming to your school, and they had to get up at 5:00 in the morning, and they're tired as a of that, that's potentially a barrier to learning, right? So oftentimes, I was guilty of this when I taught, when we think about accessibility, we think about students with disabilities, right?

But we all have different barriers to learning. We all have different barriers to learning, okay? So when we think about it in that context, and as a result of that, as teachers, when we think about learner variability first in that context, and as a product company, when we think about accessibility in that same context, we are actually able to benefit all learners as a result of that. And I'll talk about a couple different examples of that when we go through our examples of how we've implemented this through our products and through our solutions. Here's a great example is, I talked about this yesterday when I talked about the VEX Continuum. How many of you use voice when you send text messages? Show of hands? Yeah. That's an accessibility feature. That is an accessibility feature that I'm assuming by the show of hands here, that many of you do not have a disability use that, right? I think, Tim, can correct me if I'm wrong, I think every one of our software developers uses dark mode. Yes. Dark mode is an accessibility feature, okay? That many people without a disability use. They find it easier on their eyes. I personally hate dark mode. It's a running joke in the office, but many people use it even though they don't have a disability, okay?

And there are many, many, many other examples of it. But when you think about accessibility, again, when you think about accessibility, it actually ends up benefiting many different people. So, along that line, when you think about the problem of accessibility, again, thinking about this from both a teaching perspective, but also from a product company perspective, oftentimes we view the tip of the iceberg, right? We view all these different things. Ah, I don't have the right curriculum. I don't have the right PD, I don't have the right resources. I don't have the right instruction. And yes, these are all problems, right? These are all issues, but it's not the real problem, right? It's not the real problem.

The real problem is stuff like this, the blueberry muffin analogy. I learned this from CAST. So CAST is a nonprofit that developed the Universal Design for Learning Standards. And you have this great analogy, it's the blueberry muffin analogy, right? So if you're going to make a blueberry muffin, you start with the blueberries, right? Then you put the blueberries in the batter, okay? You mix it all together and you get this great muffin. Right? But oftentimes in education, and also when you create a product, what do you do with accessibility? Right? You make the muffin, and then here's the accessibility part. You shove it in at the end, right? I did this all the time when I taught, right? I was guilty. I did this for 20 years when I was in the classroom. I would have it, I would, okay, I'm going to teach a unit on, you know, pick something, the water cycle, World War II, you know, whatever, solving simple equations, right? Whatever it was, I'm going to, I sit down there and I create the unit, you know, whatever instructional design process you wanna think about, I sit down there, I create the unit, I design the lessons, go through the whole thing, make the assessment, do the whole thing.

And at the very end, I'm like, okay, here's little Johnny with his learning disability. Now I'll just adjust the test at the very end. That was me shoving the blueberries in at the end, right? And I did that for 20 years when I was in the classroom. And I didn't think about learner variability at the very beginning. Okay? That is the real problem. Other problem is this, right? The other problem is this.

This is something that unfortunately I see literally all over the world, okay?

We have schools and they'll be like, okay, you know what? We're going to start our students in something like Scratch Junior. We'll have a really good experience with them with Scratch Junior, and then we'll go to Regular Scratch, and then we will go to Code.org, or maybe we'll do VEXcode at that point, because we have some kids that are interested in the competition. So we'll do VEXcode, but in the regular classroom, we'll do Code.org. And then after that we'll do text-based. We'll do a little bit of Python, and then we'll do excuse me. And also we're going to do, we want kids to make apps, so we'll do App Academy and something else like that. And we got this collaboration of stuff that we're going to have our kids do in computer science.

And then from a hardware perspective, we'll get some bee bots for the kids in kindergarten and first grade. And then after that, maybe we'll get some Spheros for them after that. And yes, we want to do competition. So we'll get some VEX set cues for them. After that, we'll go from there. And then maybe also we'll get some Micro:Bits for them, because we want to do a little bit with electronics and so on and so forth. And then we'll end up with something else after that when they're in high school, right?

And there's no, and I see that everywhere, right? And there's no thought process given to the transitions that students have to go to as they transition from different coding paradigms, and as they transition from different hardware paradigms. There's no thought given to the cognitive load the students have to overcome as they transition between them. And there's no thought given to how that impacts the actual student learning as that, the transition between those different things. We would never do this in a core academic subject, okay? We would never do that. If I was teaching sixth grade language arts, and I spent the entire semester having my students work in Google Docs, and then for one essay, I told them to do it in Microsoft Word, just because, I would never have my students do that.

But we do it in STEM and computer science all the time. We get captivated by optionality.

And we never think about the impact of that optionality on student learning. But there is an impact, okay? There is an impact on it. And there's a lot of research to talk about the fact that there is an impact on it. Okay? And we're going to talk about that research a little bit. The first bit of research that we did, and really what got us at VEX kind of started on this path thinking about accessibility was this particular piece of research. And this is on research.vex.com, or if you can't find it, you can just send me an email, I'll be happy to, to share it with you. But this is a, this was a study that we had done with Dr. Maya Israel. She did the workshop on Wednesday, the first day of the conference, in a partnership with her in the University of Florida. And you see the name over here, Joanne Barrett. She was, or Jean Barrett, excuse me, that was from, or Dr. Kelly Thomas, excuse me. Deborah, Deborah Thomas from Broward County, Florida. It was a partnership with us, University of Florida and Broward County, Florida. It was around VEX 123. And it was a way to evaluate the accessibility of VEX 123 with students with disabilities using this POUR Framework and using the POUR Guidelines.

Okay? Stefik talked about POUR in his presentation also, the one that he gave also on Wednesday. But POUR is an acronym that stands for perceivable, operable, understandable and robust. The reason why the POUR Framework exists is so that you as educators don't have to dig through WCAG like we did, okay? It's a friendlier way to assess educational products, specifically hardware products so you don't really have to dig into things like WCAG, okay? And what this paper goes through is how you could look at a piece of educational technology and decide, is it perceivable for your students? Is it operable for your students? Is it understandable for your students? And is it robust for your students? Okay? And that's what we did. I don't have time to get into what each of those things means. It talks about it in the paper, okay? But if you have a question about that, I'd be more than happy to chat with you about it after this conference. You can also watch Stefik's presentation. He goes into detail about it. But what the teachers did in Broward County under the guidance of Dr. Israel, is they went through and they evaluated VEX 123 according to each of these parts of this framework. And this is what really got us thinking again about all these issues around accessibility.

So let's start talking about the solutions. Okay? So I've kind of framed the problem for you, framed our thinking around it. Talked about what got us started thinking about all this. Let's get into our solutions now. Okay? So the first solution is obviously the VEX Continuum. Okay? This is, so the part that I talked before about making sure that students have a scaffolded solution as they move throughout their academic journey, this is why we tried to create a STEM continuum and also a computer science continuum. So, let me spend a moment talking about why we're so passionate about this and why we feel like this is so important. Okay? Couple reasons. Number one, we talked about this a little bit yesterday.

How do you reach, first of all, students from marginalized communities? How do you reach more young women in STEM education? How do you get, how do you broaden participation widely in STEM education? The research is very clear, you have to start early, okay? Which is why we like to say STEM and coding starts early, okay? It's very, very important to start your students early. Again, students as young as six years old form an opinion about their proficiency or their ability to do STEM and computer science. Once that opinion forms, it's very, very difficult to change. So our job is to try to provide them with meaningful and impactful learning experiences when they are young to try to give them a positive impression and improve their self-efficacy towards STEM and computer science. That's why we built those tools and solutions for very young students. That's reason number one for the VEX Continuum. Reason number two is that there's a lot of controversy around educational research, what works and what doesn't works. But what we can very, very, very confidently say, works is the number one predictor of success for a student when they walk into a classroom is the amount of background knowledge that they know about a concept when they walk into that classroom.

Okay? That's why Big Bird is so effective, right? So students watch "Sesame Street", they go into kindergarten, they know how to count, they know how to read, how to do all those particular things. That's why public broadcasting did, does "Sesame Street". It was to help prepare students when they went into kindergarten, especially students, and have parents that read to them. All right? So that's why we did that. So if we're able to provide this continuum, that means that students don't, if we feel that STEM is really important, students do not start learning STEM just in middle school. But instead, we have a continuum that students can learn from year to year to year, and build that background knowledge in a scaffolded way that does not ask them to transition between different products, different development environments and different curriculum. Third of all, teacher capacity. If you go back and think about that slide I talked about before, right? If one teacher is coding with a Sphero robot, another teacher's coding with a VEX robot and a third teacher's coding with a Micro:Bit robot, all in the same school district, how do those teachers collaborate? They don't. That's exactly right.

They do not collaborate. Teachers learn best from other teachers. When I was teaching sixth grade math and my students struggled, what did I do? I walked out my classroom, I went down the hall, and I went to talk to Jeff Delman, who was the eighth grade algebra teacher. Sadly, that analogy oftentimes doesn't exist in STEM. Why? Because maybe you just have one STEM teacher. Because your school's not implementing a continuum, or you are doing STEM, but again, everyone's doing something different. So you do not have that opportunity to collaborate. So you feel like you're on an island because you are on an island, and you do not have that opportunity to collaborate because everyone is doing something different. So you do not have an opportunity to build that capacity amongst your teachers. Okay? Yesterday we had a great presentation from Henry County, Jamal sitting up front right here. That's what they did. They built capacity amongst their teachers and allowed their teachers to have their own professional learning community. They can learn from one another. Okay? And same thing with computer science.

And we've actually researched it. So I talked about the fact that there is research to support the fact that students, this is how we lose students in STEM. You talk about the STEM leaky pipeline, right? So students get involved in STEM in elementary and middle school. Why do they not go on and pursue STEM majors in college? Why do they not? Why do they drop outta STEM as they continue to get older? It's because we ask these students to transition between different platforms, because we ask these students to transition between blocks and text-based coding, and we do not provide them with the proffer scaffolds. I mean, this is just common sense. This is why we buy K-8 language arts curriculum, right? This is why we buy nine to 12 science curriculum. It's why we do that. It's to avoid these transitions, okay? It's to avoid it. It's because, it's so that everything is well scaffolded. All right? That's the same thing that we're trying to do in STEM. I shared these yesterday. These are examples of those scaffolds. Okay? Had a great question, he's sitting in the back right now, from this gentleman in the back yesterday, how do I get my high school students to do engineering notebooks? Right?

Yeah. It's hard to get high school students to start at anything, right? Try to get a 16-year-old to start anything, that's hard to do. If you can figure that out, you're gonna be a billionaire. I got news for you, right? It is hard to get high school students to start anything. The answer, unfortunately, for that gentleman that asked it, is to start them in first grade. That's the real answer.

That is the real answer. You start them when they are young. Again, go back to what I said before. If this is not something that they can see themselves doing, if it is not something they can see themselves successful at, then you're going to have a very difficult time convincing them to do it, especially when they're 16 years old and they've never done it before. So what's the answer? Start them early. This is an engineering notebook. Obviously not the engineering notebooks you're going to see downstairs, but I will fight you in the parking lot if you think this is not engineering notebook. Right? This is an engineering notebook right here, okay? And these are kindergarten and first grade students doing it with VEX 123. Okay? But this is how you get them started. This is how you get them started and you scaffold it all the way up. Okay?

Again, this is the power of a continuum. This is the power of a continuum. You find the right solution for the students at their instructional level. You have, this is a great example here. You have a middle school or a high school student that obviously cannot use a computer to use computer science to do computer science, or they can't manipulate a physical robot. You can have the student with the aide, tell them the coder, which coder cards to put in the coder, and they can still have them participate with the other students in a computer science classroom, okay? In a computer science classroom. It's an amazing thing. It's an amazing thing. But, and you can also have those teachers work together because again, you are in the same ecosystem. You're in the same ecosystem.

Some more examples. We spent a lot of time, okay? So now we're going to get into the nitty gritty of WCAG. Okay? So hold onto your hats now. We're get to the nitty gritty of WCAG. So we talk about what does WCAG mean? Okay? WCAG 2.1, Web Content Accessibility Guidelines. All right? So a lot of this pertains to students that are visually impaired. Now, let me be very clear with you upfront. We are not all the way where we need to be yet in certain areas. I don't wanna stand up here and make you think that we have everything solved. We do not. We still have work that we have to do, okay? But we are working very hard at it. But if you think about this, right? If I have a visually impaired student, a visually impaired student, okay? And I want that visually impaired student to code, what can that visually impaired student not use?

What can't they use? Mouse. They can't use a mouse. That's exactly right. They cannot use a mouse. Now, if you're using Scratch blocks or Code.org blocks or VEXcode blocks, what do those kids have to use?

A mouse. It's all drag and drop. They have to, that there's the rub. There's the problem right there. You've just uncovered the major violation of WCAG 2.1 right there. Okay? That's the problem. If I'm a visually impaired student, I obviously can't click and drag with a mouse. Okay? So here are some of the things that we've built in, right?

Move forward for 200 millimeters. Okay, the ability to read blocks, and I still have to use a mouse to do that, so we're not all the way there yet. Turn right for 90 degrees. But we're making progress there, obviously. Okay?

We do have keyboard. We do have keyboard shortcuts in VEXcode. Why? Because we need that. Okay? No mouse. Okay? These are the things that we wanna build in to make things more accessible according to WCAG 2.1. Okay? So keyboard shortcuts that we've built in.

You've noticed if you've gone over and you've seen any of the AIM demos that we've had over, or you've been in AIM workshops, you've noticed the color of the blocks. You've noticed that these high contrast blocks, we actually don't call them high contrast blocks are just the AIM blocks because this is the, quote, unquote, default, right? This is for students, obviously not, you know, blind students, but students that might have, you know, different levels of impairment what they're seeing. This is to make sure that students can easily distinguish the blocks. We will work over the course of the next few months to propagate this to all of our different platforms, okay? But it's an AIM right now, and this'll be in all the rest of our platforms. Like I said, we'll be working over that over the course of the next few months. So if you have different degrees of colorblindness or visual impairment, we wanna make sure that it is easy for you to distinguish between all of our blocks. This was a mode in like EXP and other blocks right now, but it's going to be the default moving forward.

Switch blocks, I'm going to talk about Switch blocks in a lot more detail here, upcoming, but this is something that we developed first for VEXcode VR. This is what Dr. Jimmy Lin, our Director of Computer Science Education put a dissertation on, but I'll talk about that here in a minute in a little bit more detail.

So our websites. PD+. So again, if you think about it, being able to make it screen reader-adaptable, or screen, being able to be read by a screen reader, excuse me. So making sure that all of your content can actually be read by a screen reader. And also, I can navigate it with a keyboard. Again, if I am visually impaired, I cannot use a mouse. So we had to essentially rebuild our websites so that number one, everything could be read by a screen reader, screen reader. And number two, I'm able to tab through everything and I can navigate everything via keyboard shortcuts, or as you see here, just kind of tapping everything. But we basically had to redo all of our websites to be able to do that. Now, when we talk about navigating, excuse me, be able to read with a screen reader, you may say to yourself, well, that's not that big of a deal. Well, it was because all throughout our websites we had screenshots of stuff like this.

And guess what? Screen readers can't read screenshots.

Okay? So we had to go through and replace all of our screenshots with, what are the SVG? Well, that got it right. SVG files, so we had to create SVG files and replace in all of our curriculum, in all of our PD and everything with SVG files so that they can be read by a screen reader. We have a lot of curriculum. We have a lot of PD. It took a lot of work to be able to do that. And then when we built our API site, okay? Api.vex.com, all of the block examples that we have in that also are SVG files and they're not screenshots. Why? Again, so we can do that, and then the same thing with the Python code snippets that you have right here. None of these are screenshots. None of these are screenshots because they cannot be read by a screen reader. And it's really cool feature, you can copy and paste it into your code with the, from the API sub, which is really cool. Now, the cool feature about this with AIM with the API site, okay? Is that API site is built into the help of AIM.

So all those cool features I just talked about are right here in AIM. So all of this in AIM right now is able to be read by a screen reader, and I'm able to move through it without a mouse, okay? And again, just like I talked about with the block colors, we'll be moving, we'll be doing the same with all the rest of our platforms. So IQ, VXP. We'll eventually be moving that, so all the help here is also coming from the API site also. All right?

This was the hardest one, okay? This is also the best example about thinking about accessibility, about how it helps all learners. All right? We do all the direct instruction in our curriculum, okay? So if we're going to teach you like to code with a conditional block, or if we're going to teach you how to build a drive train on a VEX IQ robot in a particular lesson, we're going to, we're going to actually do the teaching, right? And so we do that so that you can be the facilitator, okay? So as to teach, you can be a facilitator and you can go and you can do whatever. And we asked you the direct instruction of it. But according to WCAG, in order for those direct instruction videos to be WCAG 2.1 compliant, they had to, they had to be, they had to be usable for a non-sighted person, all right? So they had to be, so a non-sighted person had to be able to gather the same meaning from that video as a sighted person. So we had to put what's the scripted audio in the video. Have to include that in there. So here's an example of that.

Text VEX Classroom Series.

Text, Aimee Defoe, MAT, Senior Curriculum Developer and Former Principal and Teacher. Aimee stands at a desk behind a field of VEX Tiles upon which an EXP BaseBot and a red Buckyball sit on opposite sides of the desk, set a red EXP bundle and a laptop. Behind her are VEX EXP posters and a whiteboard that reads Castle Crasher Lesson 3 Practice. Hello, I'm Aimee, and welcome back. So you see what it did there. It described the entire scene before Aimee started talking. Why? Because if a non-sighted person was watch, if a blind person was watching this video, it is describing the entire scene to them, right? Before they actually start with, it's going to say, this is who it is, this is who she is, this is where she is, and this is the environment that she's in. Okay? And then the captions, the captions below her as she's talking aren't just going to be the words that she's saying. This is like, we started going through this process, so my daughter has autism, right? So she has auditory processing issues. So we would watch a movie together, we'd always watch with the closed captioning, right? So we're watching a movie and someone opens a can of Coke and the closed captioning goes, effervescent sounds.

And it was literally like that Leonardo DiCaprio meme where he's pointed the TV. That was me, because we just had to do that. We were just, we're just on a call with that where they were talking about with the closed captioning, you just can't do the words, you have to describe all the sounds that were going on. And I was like, "We just did that. We just had to do that for some of our videos for our thing." Because that's WCAG 2.1. So the closed caption is not just what they're saying on there, right? It is all of those particular things. So, but what this has done, we don't wanna have to, that's not a good, so if you're a, when I show this video, the question I always get is, well, what about for the sighted kids though? Does that make it a little bit clunky for them, for them to watch? And that's, that's correct. Right? So what we have to do now is we think about this before we film a video. So how, when we film these videos, how can we film the video to avoid that little intro that I just played for you? And guess what? When you think about that, before you film the video, you actually make the video better for all learners. Now think about that for a minute. We have filmed, I don't know, hundreds of videos, right?

We have filmed hundreds of videos. Before we went down this process to go back and talk about the real problem again, before we went down this process, we never thought, how do we film this video to make sure it works for all learners?

We would think about, okay, how am I going to teach this? How am I going to talk about this? I gotta make sure I talk about conditional statements right. I gotta make sure I attach this wheel on correct. I wanna make sure I talk about these learning outcomes right. I wanna make sure I say this at the end. We know all that stuff great, fantastic. We never thought about how do I make sure a student that might be visually impaired understands this video just as well as a student that has no visual impairment? And how do I set the scene, for lack of a better term, to ensure that that happens?

But now we do that, and because of that, our videos are much better, and they're actually better for all learners as a result of that. And in our AIM curriculum, they actually show that. So one thing I want to talk about here is all basically the examples of us from a product company of shoving the blueberries and at the end, we've tried to correct those mistakes with AIM. So I just talked about that from creating the videos and from a curriculum standpoint, but also from a product standpoint with AIM. So one of the things that we wanted to make sure that we did with AIM is we wanted to make sure that we included multiple modalities for students to interact with the robot, because we learned that with VEX 123. So being able to use the coder with VEX 123 we found was really important. So we wanted to make sure we included that also with AIM was having those multiple modalities. But the real key thing was touch button coding. So with that POUR assessment, biggest piece of feedback that we got was when the students touched the buttons with 123, it wasn't loud enough. So you didn't get as much of that auditory feedback. So we wanted to make sure with AIM, as you see, we're trying to show the animation there.

It really did make sure that it was loud enough for the students, okay? And that's what you see here. And also counting the steps here. That was the other bit of feedback that we got from Maya's study with POUR. So really taking that feedback that we got from Dr. Israel and the teachers from Broward County and put, and also, one more thing to highlight on that, the feedback on the LEDs. So you could see here when we're touching the buttons, we're also getting the visual feedback down here. So auditory feedback, visual feedback, all these different types of feedback for the haptic feedback. All these different type of feedback for the students as they're using AIM. This was the examples, again, that we used as a result of that study.

VEX AIM with the Python coding, we totally redid the toolbox here for Python. Totally redid all of this in here to try to make it easier for the students so they weren't so overwhelmed, but all the different commands. I can actually collapse all of these, so I can just focus on the ones that I wanna be able to see. So again, really focused on some of the feedback that we got from our users going through that. And lastly, I wanna spend about five minutes talking about Switch blocks, and then I'll open up for questions that you have. But with Switch blocks, one of the big things I talks earlier about was students transitioning, and one of the biggest headaches in transitioning is that transition from block to text-based coding. So this, again, this is what Jimmy wrote his dissertation on. It's also what Jimmy's PhD advisor, Dr. David Weintrop from University of Maryland, wrote his dissertation on. But you know, again, blocks like this turn right for 180 degrees, it abstracts out a lot of that messiness of text-based coding for students. Like why is this dot here between robot and screen? Why is this under store between show and emoji? Why is happy in all caps? Why is there a comma there?

Why is there parentheses there? Stefik in his presentation actually goes through and spends a lot of time talking about really why there's no rhyme and reason behind a lot of these things for text-based coding, right? There's no, there's, scientifically, there's no evidence to show as to why these things exist in text-based coding. And as a result of that, it makes it very, very difficult for students to learn it, right? So blocks abstracts all of that out, but then in the text, we just kind of throw our students into the deep end and ask them now to do all of this. So the whole idea behind Switch is to make that transition easier for students by keeping, as you see here, the structure of blocks while allowing them to explore text-based coding. But Switch actually does a lot more than that because Switch actually gives students different ways that they can do it. So what Jimmy's dissertation showed is that students initially began their exploration to Python by using block.

So I can right-click on a block, okay? And I can begin to change, I can just begin by changing parameters inside of a block, excuse me. And I can convert it to switch. Just that simple. So I don't have to know any commands. I don't have to type. I don't have to do anything. Okay? I can change parameters and then I can just use the convert function that we build into VEXcode. I can convert it to a Switch block, okay?

Or I can compose with blocks. I can convert the Switch mode and then mainly input what they saw converted into a Switch block shown here to convert the switch, see what I had there, okay?

And now good and type it in.

So now I don't have to have anything memorized, right? So now I don't have to have anything memorized what I'm doing.

I can type, I can convert and then I can reference, okay?

So there's all these different message. There's a, this is, this is actually my favorite way to do it, by the way. So I drag a block in, I convert it, oh, that's what I do. And then I can write it in there. So the great thing about this with Switch blocks is that there's just not one way to do it. Okay? I have multiple ways that I can do this. And this is totally up to the students. So the students can do this scaffolding on their own. So we don't tell the students, use this one method to use Python. They can use whichever method that they want.

So I can modify and Switch mode right here. So I can go right into Switch, I can modify the Switch blocks right there. Okay?

I can use auto complete and switch.

So all these different methodologies, I think there's eight total, but all these different methodology that students utilize when they use Switch mode that they could scaffold on their own. And the other great thing about this is when you think about, if you think about your own school, if you're teaching computer science in your own school, when do you introduce Python? Someone, a curriculum coordinator, a principal, a computer science teacher, someone just decided we are going to learn Python or C or C++ whatever. We are going to learn text-based coding here.

But why? Why did we pick intro to Python in ninth grade? Why do we pick intro to text-based coding, and what, like why did we choose that particular age and grade? How do we determine our students were ready for text-based coding at that particular time? The beautiful part about Switch is it allows students to do text-based coding when they're ready to do it. You notice on some of those different examples there, you had blocks and text, did not have to be all text. So students can switch on their own and they can scaffold it on their own and they can use whatever methodology that they want on their own. And what we do then is we give the power to the students. We allow them to activate their own voice and allow them to choose when they are actually ready to really dive deeper into text-based coding. And at the end of the day, and that's a good way to kind of wrap this up and I'll open up for questions, that's what accessibility is all about. It's removing barriers for our students and allowing them and putting the ability in their own hands to take control of their educational journey, right? At the end of the day, what we all want as teachers is we wanna be able to empower our students to really find their own passion and to explore things and to be able to really find what motivates them as students.

That's what we want to be able to do. We all got into education because we love that light bulb moment from our students. We love those aha moments from our students. That's what we want to be able to do. So our job at VEX is to try to provide you as best as we possibly can with the tools and the resources so that all of your students, all of your students, okay? Whether they have disabilities or not, all of your students can have as many of those aha moments as they possibly can. Okay? So with that, I'll go ahead and open up to whatever questions that you may have. Thank you.

First off, I'd like to thank you for your presentation. It was very enlightening. Thank you. The question that's been kind of nagging my mind is, I don't know what the statistics are about this kind of student in the world today, but have you guys figured out a situation with a sort of like a Helen Keller situation where they're both blind and deaf? So we've thought about things like... So if we're able to like figure out the no mouse problem, right? So I am able to, I'm, a blind student, I'm able to code the robot, how do I know the robot went to where I wanted to go? Right? So like, do we have the robot give some type of auditory feedback to allow, okay, like, like every time I make a a nine degree right turn, it's two beeps, I make a nine degree left turn, it's three beeps, stuff like that? We've had those types of conversations. But if I'm both a blind and a deaf student, we've kind of explored that a little bit, but I don't have a good answer for you right now, but we've had those conversations. Yes. Yeah. Right.

So this might be slightly off topic, but it popped to my mind when we're talking about the legality of, what was again? WCAG? Yes. The acronym. So I was in one of your workshops on AI and Computational Thinking, the use of the AI vision and whatnot. And your trainer really stressed that, "Oh, don't worry, there's nothing being uploaded to the cloud of, you know, images the students faces. We don't want to mess with the legality and things like that." Yes. Well, what about AIM though? Because if I have a student like checking their answer with the bot there and then in the background, oh, there's a student's face, okay, it's gotta communicate with the cloud, that image to, you know, is this correct to this problem or not here? How is that squared? Yeah, so AIM is the same if like, if you were in like, like an EXP AI vision sensor workshop, AIM is the same way. So all the processing is is happening on the device. We're not sending anything to the cloud for any of those products yet. Yeah, thank you for the question. I believe Sony's done a lot to do the same kind of conversational idea. And I don't know if you've gone down that road, but Sony specifically in some of their hardware and some outside of that too for learning, they have a lot of hardware that's accessible for specifically handicapped wheelchair specific options.

And a lot of those have ability for a incorporation into other environments and coding. Specifically, one of their joystick that's a optional 3D printed button kind of, in fact it's a round label. So I didn't know if the next step within that construct as this conversation becomes more, for lack of a better term, more accessible to everybody, is that something then that as we, you know, take them out of our circle and everybody starts overlapping within that, that we share those other ideas? Yeah, so-- Ecosystem? Yeah, so I'm not sure if Sony's one that we have, but it might be Microsoft, but we have what's called the Bridge App. We actually have a demo of it in our Educators Lounge, in which we, it was with Broward again, but we worked with their inclusion teacher because they had a student that wanted to be on the VEX IQ team, but they couldn't operate our controller. So we created what we call the Bridge App and it mapped the controller functionality to one of the accessibility controllers. So that student was able to use an accessibility controller, I'm not sure if it was Sony, but they were able to use an accessibility controller to drive and use a VEX IQ Robot. So that's actually where the Educators Lounge.

You can go and see that. I think Becks over there, one of our software devs demoing that over there, there. So we we've started down that road. Yes.

Other questions? Have you thought about having filters on your block code so that some of the more complicated code blocks aren't available to students? So that way, I like a lot of program, design programs, you can have a primary way of looking at it? So it just, because they're so complicated, we first look at them, so that way perhaps be a little bit more scaffolding to students and then you can reveal more as they grow up in their sophistication with that product. Yeah, we do that now somewhat. So for like VEX GO, for example, if you do not have like a motor connected in the drivetrain, we don't expose the motor blocks to you. If you don't have a sensor connected in the driver config, we don't have those sensor blocks exposed to you. So we do do that now to a certain extent. You know, there's a yin and a yang to it. We still get support tickets because people are like, I can't find the motor blocks. Where are they? Your software's broke. You know, so we still get that. So we still struggle with that a little bit also, but yes, we do try to scaffold it so they're not so overwhelmed so it, for it. Even like with VEX 123, we have all the coder cards, and in our PD we always say, never give all the coder cards to the kids.

Like we say, like they take a cup, and then if the coder, if the assignment requires like four or five particular coder cards, give those to the students, then they have to think about the correct sequence. And then if they get done, then you can throw one or two more cards in the cup and say, okay, explore these cards, not like that type of thing. So we're intentional about that also.

I think we have time for one more question, if there is one.

No? Oh, one more. One more, Nicole. Just within our state and school district, we're pretty mindful right now of a new a DA if we get stuff coming down. So you kind of alluded to this, do you have a more specific timeline of when high contrast blocks are available across the continuum? And when I understand how huge converting a whole API taking out and taking out all those pictures, do you have any sort of timeline that I can bring back to the people that are going to ask? If you send me an email, I can get back to you on, I don't have anything. I can't, I don't wanna quote something to you right now, but if you send me an email, I'll be able to follow up with you on that, yeah. Great, thank you. Sure. All right, I think that's, yeah, I think we have workshops starting at 10:10. Tim, is that right? Yes, we have other workshops beginning in about 10 minutes. So just in time for you to grab some coffee, use the restroom, but thank you very much, appreciate you.

VEX Robotics Educators Conference.

Share

Like this video? Share it with others!

Additional Resources

View the full presentation slides here.

Continue the conversation in the VEX Professional Learning Community!

Learn more about the VEX Robotics Educators Conference at conference.vex.com