Keeping the Accessibility Promise
A week with my first 3D printer, and the difference between learning a lesson and translating one.
Before my first 3D printing class even began, one sentence convinced me I had signed up for something special.
100% Accessible Classes for Everyone.
As a blind student, I didn’t read those words as marketing.
I read them as a promise.
Not a promise that nothing would ever go wrong. Technology has a funny way of humbling everyone. Printers jam. Software crashes. Lessons run long. Schedules change.
The promise I expected was something different.
I expected that accessibility would be built into the learning experience itself.
After spending a week assembling my first 3D printer, who now proudly answers to the name Robot, I realized something.
This article isn’t really about 3D printing.
It’s about what it means to promise accessibility.
More than compatible
When people hear the word accessibility, they often think about software compatibility.
Can JAWS read it?
Does VoiceOver work?
Is the button labeled?
Those questions matter.
But accessible education goes much further than that.
Accessibility isn’t simply making sure a disabled student can open the software.
It’s making sure they can spend their energy learning the subject instead of translating the lesson.
That’s a very different goal.
A sighted student should leave class thinking about 3D printing.
A blind student shouldn’t leave class thinking about how to decode what everyone else just watched happen.
When the promise was kept
Throughout the week, I experienced moments that showed me exactly what accessible teaching can look like.
The course wiki was beautifully organized. Headings were structured correctly, alternative text was present, and navigating the documentation with a screen reader felt effortless.
During the printer assembly, the instructor intentionally crinkled different plastic bags while describing what each one contained.
The paperwork.
The screws.
The filament.
That tiny decision told me something.
Instead of assuming I could identify the bags visually, the lesson had been translated into sound.
Later, while explaining manual bed leveling on the original Ender 3 printers, the instructor described something I never would have thought to compare.
He asked students to imagine the grippiness of sandpaper on a scale from one to ten while sliding a piece of paper beneath the nozzle.
If the paper felt extremely grippy, the nozzle was too close to the bed.
If it barely gripped at all, the nozzle was too far away.
Aim for somewhere around a five.
He also explained that if the nozzle was too close during printing, you’d hear it scraping against the print bed.
Those weren’t simply colorful descriptions.
They gave me independent ways to evaluate my own work through touch and sound.
The same thing happened while assembling the printer.
One of the aluminum rails kept giving me trouble.
Eventually, I discovered something the instructor hadn’t explicitly said but that became one of the most useful tactile checks of the entire week.
If the rail is seated correctly, it supports itself before you install the screws.
If it isn’t…
It flops over.
That one discovery taught me something much larger than printer assembly.
Accessible instruction doesn’t just explain what success looks like.
It teaches students what success feels like.
When I stopped learning and started translating
Accessibility isn’t measured by its best moments.
It’s measured by what happens when a student can no longer follow the lesson the same way everyone else can.
One afternoon, I sat down expecting to learn Tinkercad Codeblocks.
Instead, I spent nearly three hours sitting through a lesson built around visually manipulating shapes: moving them across the workspace, resizing them, grouping them together, cutting holes, and watching designs evolve on the screen.
Those are valuable skills.
If your primary way of understanding a design is by watching it take shape visually, that lesson makes perfect sense.
But I hadn’t enrolled in the course because I wanted to become a digital sculptor.
I had enrolled because I wanted to learn the coding interface.
For nearly three hours, I wasn’t learning Codeblocks.
I was waiting for them.
Somewhere during that lesson, I realized I wasn’t really learning 3D modeling anymore.
I was translating a visual workflow while hoping the lesson would eventually arrive at the part I could engage with in the same way as everyone else.
That realization has stayed with me far longer than anything I learned about Tinkercad.
What stays with me is how small the fix might have been. Every visual manipulation in that lesson has a Codeblocks equivalent, that’s the entire point of Codeblocks. When the demo cut a hole into a cube by dragging one shape into another, that operation also exists as blocks you can arrange and read. Teaching both versions side by side wouldn’t have derailed the lesson. It would have given every student a second way in, and it would have given me a first one.
Though I should admit something. Everything I just described is my best guess about how Codeblocks actually works, because I still haven’t been taught it.
There’s a difference between including a disabled student in the classroom and including them in the lesson.
Curiosity is an accessibility skill
That afternoon didn’t happen because anyone was careless. It happened because no one had sat with the lesson the way I would have to.
One of the biggest misconceptions about accessibility is that instructors need to become experts in assistive technology before they can teach disabled students.
I don’t believe that’s true.
I don’t expect every instructor to master JAWS.
I don’t expect them to memorize every VoiceOver gesture.
I do hope they’ll become curious.
If you’re teaching Cura, spend a few minutes navigating it with only the keyboard.
Listen to what the screen reader announces.
Then compare that to what you’re seeing on the screen.
If you’re teaching Tinkercad, do the same thing.
Not because you’ll become an accessibility expert in half an hour.
Because you’ll begin to understand how your students experience the software you’re teaching.
That comparison matters.
You already know what the interface looks like.
Now you’ll have a better understanding of what your student hears.
That makes it much easier to recognize when a visual explanation needs to become a verbal one, or when a demonstration needs a tactile checkpoint instead of another gesture toward the screen.
Curiosity leads to preparation.
Preparation leads to independence.
And independence builds confidence.
The question that changed everything
As the week went on, I found myself asking a question over and over again.
If my printer starts printing…
How do I know whether Robot is producing perfect calibration squares…
…or a pile of spaghetti…
…or dragons…
…or monkeys?
A sighted student can glance across the room and immediately answer that question.
I can’t.
So what replaces vision?
Is there a sound I should be listening for?
A vibration?
A tactile clue after the first layer?
An AI description?
Those aren’t just questions about 3D printing, they’re questions about teaching.
Every lesson contains information that sighted students absorb automatically.
Good accessible instruction asks how that same information can be communicated through another pathway.
Sometimes the answer is touch.
Sometimes it’s sound.
Sometimes it’s thoughtful language.
Sometimes it’s technology.
The pathway doesn’t have to be identical.
It simply has to lead to understanding.
Keeping the promise
When I look back on that week, I don’t remember frustration first.
I remember possibility.
I assembled my first 3D printer.
I learned how slicing software fits into the printing process.
I discovered a hobby I’m genuinely excited to continue exploring.
Most importantly, I learned that accessibility isn’t magic.
It isn’t perfection.
It isn’t a checklist.
It’s a series of thoughtful decisions made before class even begins.
So, was the promise kept?
Yes and no.
I left that week with Robot fully assembled, a new hobby I genuinely love, and a head full of sandpaper scales and crinkling bags.
I also left without the one lesson that would let Robot actually print.
He’s sitting beside me as I write this. Assembled. Ready. Waiting.
The gap between those two outcomes is exactly the distance between including a student in the classroom and including them in the lesson.
The crinkle of a plastic bag.
The grippiness of sandpaper.
The sound of a scraping nozzle.
A rail that flops over when it isn’t seated correctly.
Each one answered the same question in a different way.
Each one helped replace information that would otherwise have been available only through sight.
Every instructor who promises accessibility owes their students one question before class begins:
What information are my sighted students getting automatically… and how can I teach that another way?