Dyslexia 301: Assistive Technology Training for a District Moving to Blended Learning


A one-hour Canvas course that asked teachers to learn one free assistive technology tool well enough to install it, use it, and plan how to teach it to a student.

  • Project Type: Asynchronous online professional development course
  • Audience or Client: Rapid City Area Schools (RCAS) teachers across all grade levels and subjects, with the district’s Dyslexia Task Force as client
  • Timeline: Designed fall 2021; delivered to staff in August 2022
  • Role: Instructional designer
  • Collaborators: RCAS Dyslexia Task Force
  • Format or Deliverables: One-hour Canvas course (“Dyslexia 301”) with a mastery-gated pre-assessment, five interactive Canvas Studio videos (one per tool), a feature comparison chart, an accessible-LMS job aid, and a written implementation plan as the final task

The Situation

RCAS teachers were about a year into a district push toward blended learning, and most of what they were building in Canvas was text, since videos and graphics take far longer to make. That shift landed hardest on students with dyslexia and other struggling readers, who were now meeting more text, more often, outside of class. The district already had two one-hour dyslexia courses, but Dyslexia 201 leaned on supports inside StudySync and Wonders, which only some classrooms used and which didn’t carry over into Canvas. When I polled the Task Force, they rated teachers’ understanding of how to use dyslexia supports in Canvas at about a 2 out of 5, and they rated the need for training at 4.4.

The Approach in Brief

The course had to fit inside one hour during back-to-school week, for about 400 teachers who were already stretched thin. So instead of surveying every tool, I asked each teacher to pick one of five free assistive technology tools and learn it well. The course opened with a five-question pre-assessment on dyslexia basics, and anyone who scored under 80% was routed to review the Dyslexia 201 material first. Each tool had its own short Canvas Studio video with questions that paused the video and asked teachers to do the next step, not just recall it. The course ended with each teacher writing a plan to introduce the tool to one of their own students.

What Came Out of It

The Task Force tested a prototype on November 9, 2021. On the eleven feedback forms, clarity and navigation were rated mostly 4s and 5s out of 5, and the discussion afterward produced four changes. RCAS then adopted the course as the third in its yearly series of hour-long online dyslexia trainings and assigned it to staff in August 2022. I don’t have completion or evaluation data from after that, so the testing session is the clearest evidence I can point to.

Key Takeaway

When teachers have one hour, depth on one tool they will actually use is worth more than a tour of five they won’t. The narrowing also made it possible to ask for a real plan at the end instead of a quiz score.


Deeper Context

The course started as the final project for an instructional design course in my master’s program. The Task Force had a real need and offered to act as the client, so the project had to work as an actual district training and not only as coursework.

The district’s history shaped several choices. The 101 and 201 courses had drawn two common complaints: the first had little teachers could apply right away, and the second recommended tools that most secondary teachers didn’t have. I wanted every tool in 301 to be free, to work in Canvas and on Chromebooks, and to be usable without much background in the platform. Feedback from the district’s Teacher Advisory Council that fall described staff as overwhelmed, and I designed for the teachers who were furthest from enthusiastic about blended learning. Some of the tools had to be very easy to set up. For the teachers who were further along, a separate job aid covered how to make a Canvas course more accessible in general.

The Journey

I worked in a spiral, circling back through the learners, outcomes, activities, assessment, and evaluation in each phase rather than finishing one before starting the next. I sent the Task Force a short poll early, and their answers set the course’s ingredients: videos, job aids, simulation-style questions, mastery quizzes, and chances to apply what they learned right away. The poll also showed they wanted a mix of assessment types instead of a single quiz.

The scope narrowed twice. The original plan had teachers learn two tools, but completion data from 101 and 201 showed the average teacher took about 45 minutes, with the slowest closer to an hour. Two tools wouldn’t fit, so I cut it to one. While building the comparison chart, I also dropped Helperbird and Read&Write, both of which put key features behind a paywall. I didn’t want the course to read as pressure on the district to buy something. Google Docs dictation and the OpenDyslexic font extension took their place.

The sequence diagram below is the version I took to the Task Force. Teachers moved through an overview and the pre-assessment, then pages on what assistive technology is, how it helps, what its limits are, and how to choose a tool. Then came the video branch, where each teacher picked one tool, and a final module on introducing the tool to students and building routines around it.

Flowchart of the Dyslexia 301 course as taken to testing. An overview leads to a five-question pre-assessment, with a branch to review Dyslexia 201 material for anyone under 80%. An assistive technology module covers what AT is, how it helps, its limits, and selecting a tool, linked to an accessible-LMS job aid. An installation and usage module branches to five interactive videos (Read Aloud, Microsoft Immersive Reader and Dictation, Google Docs Dictate, Mercury Reader, and OpenDyslexic) with 80% mastery quizzes. A training-learners module covers introducing the tool and building routines, ending in an exit writing plan and a survey.

At the testing session, I explained the aims and what was ready to try, then watched as Task Force members worked through the prototype. I stopped people one at a time to ask what they were thinking and where they got stuck. After the forms, the group talked it through together. Four changes came out of that session: 1) a short “why” video at the start showing what assistive technology looks like in practice, 2) more detail on the tool-selection page, including Canvas integration, Chromebook support, and suggested age ranges, 3) replacing OpenDyslexic with Google Lens, after a member pointed out that dyslexia fonts lack research support and can reinforce the myth that dyslexia is a visual problem, and 4) a closer look at elementary classrooms. One member put that last point this way:

“I’m wondering how assistive technology would work at the elementary level. Elementary classrooms don’t have specific content areas or textbooks. Some read-aloud features are available within the Wonders curriculum. Assistive technology may look very different at the elementary level.”

The Work Itself

The two images in this case come from the planning document. The sequence diagram is in the Journey above. The page prototype below shows the template every content page followed: a short “How to Complete This Page” section at the top, then the content, with links out for anyone who wanted more.

Prototype of the course page "What is Assistive Technology?" It opens with a "How to Complete This Page" section telling learners to read the items and click next, defines assistive technology with examples like wheelchairs, hearing aids, and closed captioning, links to NIH and AUSPELD for more, and lists technologies the course leaves out, such as spell checkers, word prediction, reading pens, Google Lens, and text simplifiers, with a short reason for each.

What I’d Change

I’d start prototyping sooner. The interactive video was the riskiest piece of the design, and I tested it with the Task Force only after the design was mostly set. Putting a rough version of one video in front of a few teachers in the first weeks would have surfaced the font question and the elementary question earlier.

I’d also widen the needs analysis beyond the Task Force. The Task Force knew dyslexia well, but I learned about the classroom mostly through them. Interviews with a mix of teachers, and time watching students who already used assistive technology, would have grounded the tool choices in what students actually found useful. The elementary feedback was the clearest sign of that gap.

Finally, I’d carry the evaluation through. The plan included a survey at the end of the course and a review with the Task Force after it launched, but I don’t have those results. A next version would decide up front who looks at the data, when, and what would change because of it. I’d also build the course in pieces the district could reuse in later trainings rather than as a single hour.

Connections

For a later case about making online PD easier to use, see Applying User Research to Online K-12 Professional Development. For another training built around teachers working in their own Canvas courses, see Canvas Design Workshop in Edgemont, South Dakota.

If you’re planning assistive technology training for your own staff, you can reach me at licht.education@gmail.com, and there are more tools, articles, and resources at bradylicht.com.


Discover more from Brady Licht

Subscribe to get the latest posts sent to your email.