Passed the Tests, But No One Can Use It.
I watched a store employee try to download a required training module on his phone during a break once. The screen was cracked. The shop was so noisy that noise was useless. He was wearing work gloves, so each tap was about half an inch. He gave up about four screens and marked it as complete later from a friend’s account, telling you exactly how much was attached. That course passed all the accessibility checks it was given. Screen reading labels were fine. Color contrast is up to standard. Even the person who was built for it still cannot use it, because the checks he passed were not equal to the things that prevent him. Designing the floor is important, too.
Accessibility Compliance is Necessary and Not Sufficient
I want to be careful here, because the work to reach my route and I am not willing to talk about standards. The Web Content Accessibility Guidelines (WCAG) exist for good reasons, and a screen reader user who can’t read your tutorial is a real failure you need to address. None of this is in question. Meeting those standards is the ground you build on, it’s not something to skip.
But “accessibility” is quietly reduced somewhere along the way to “bypass automatic scanning.” And on the shop floor, that definition leaves out most of the people you’re actually trying to reach. Level is required. It’s not all work. Designing down means accounting for real-world conditions.
Conditions Course Did Not Meet
Think about who is actually taking the training from the frontline and where. Most of them are learning English as a second language (ESL), and a module written at a college reading level loses them in vocabulary long before the content becomes difficult. Many of them do not have a computer at work and will only see the lesson on a phone, usually an old one with a small screen. The store has a dot signal, so the heavy video module that takes the hard connection ladders and buffers to stop.
And there’s usually no quiet place to do it. The course is designed by someone sitting at a desk, in a quiet room, on a large monitor, with a fast connection, and no one waiting for them. It is eaten standing still, with noise, on a cracked phone, in the ten minutes stolen between tasks. Almost none of the design guesswork exists in the journey from table to store.
None of those ideas are wrong in themselves. They are not visible to the person doing them, because they are the conditions in which a person works every day. The problem is that all of them are small bets on the student’s place, and when the work happens that bet quietly loses. A module that requires a strong connection breaks when the signal is weak. The careful tapping that you think is out the window under the gloves, and the quiet moment it was stepped on doesn’t come to a sound. The design didn’t account for the actual reading area, so it falls apart there.
Design for a Floor, Not a Desk
Many adjustments that help design the floor are not uncommon. Write down the learning rate of the people on the ground, not the people who signed the contract, and look at the real worker ahead of the guesswork. Take the phone first, small screen, and gloves, which means larger tapping targets and less precision required. Assume that the connection drops, so the module works in short bursts that don’t lose progress when the signal does. Think about the sound, so nothing serious lives only in sound.
For ESL practitioners specifically, simple language does more good than any other feature you can add to it. Keep sentences short and common words, and put one idea in front of someone at a time. Be clear about what plain language means here, though, because it’s easy to get it wrong. Simplifying what you do in sentence structure and connective tissue around words is necessary. The conditions themselves remain. The coatings worker still needs to read “pot life” and the actual product names, because that’s the language the job and safety data are written in. Nouns carry precision, as does the logic around them, “if only,” “before you,” the order in which the steps must occur. Simplifying the language should not blur those into something vague, because in the work done safety can hurt “someone” quickly. Lowering the learning curve should never come at the expense of technical accuracy. He makes sentences follow easily while leaving out both definite terms and conditions.
And by crossing the language gap, the most accessible movement often stops making words the only way in. I want to be precise about that, because the tempting shortcut is to replace the text with the text, and that’s a step backwards. A user who reads a screen, anyone who searches for a word, a reader who processes written steps better than visual ones, all still need words. So you keep the words and pair them with a clear picture or a short illustration, so the meaning has more than one route to the human head. A worker recording a second language under time pressure can depend on the image; the student who needs the text still has it. Showing up with soliloquy beats more often than people expect. And the simple language work under it helps everyone, in the same way that the road cuts ended up helping far more people than they were drawn to.
Actual Test
There is one check that catches almost all of this, and it’s not a scanner. Put the finished module in a cheap phone, take it to the real place where it will be used, sound and gloves and spot signal included, and try to go out yourself. You’ll find problems in about five minutes, and they won’t be any automated tool flagged. This is an important test for successful design on the ground.
Passing the scan tells you that the course can be opened with assistive technology, which is important and worth pursuing. Whether a person doing the job can get through it under real-world conditions is a different question, and currently most of the industry is only answering the first one. Answer both, and build something your front line can use.
