Picture the person who works in space. Most of us see the same image: a fit, young, fast-talking engineer who hears every radio call perfectly, reads dense briefing sheets at a glance and climbs a ladder without a second thought. That picture is wrong in ways that matter, and it quietly decides who gets invited into space careers and who gets left at the door. Here are six myths about space careers and space communication, and what happens when we drop them.
Myth 1: “Space is only for a narrow type of person”
Launch teams, mission planners, ground controllers, data analysts, technical writers and trainers all keep a mission running. Very few of them ever wear a flight suit. Yet job posts and outreach events are often written as if every candidate has identical eyesight, hearing, mobility and first language. When a careers page lists ten “must-haves” that have nothing to do with the work itself, capable people simply never apply. Plain descriptions of what each role really involves, and what the physical or sensory demands truly are, widen the pool without lowering any standard.
Myth 2: “A technical briefing has to sound technical”
A briefing exists so that everyone in the room knows what is about to happen. Jargon-heavy language does not prove expertise. It just makes people with a different first language, or a different training background, work twice as hard to follow. Compare that with how a beginner-friendly walk through the nearest orbit band introduces its terms: one idea per sentence, each new word explained the first time it appears. Pilots and controllers have used standard phrases for decades precisely because clarity beats cleverness. The same habit works for written material too.
Myth 3: “Accessibility is a favour for a small group”
Large text, captions, high-contrast diagrams and short paragraphs were first demanded by people who could not do without them. Then everyone else noticed they were simply easier. Think about reading a launch-day checklist on a phone in bright sunlight, or following a livestream in a noisy hall with the sound off. Captions and strong contrast help a person with a hearing or vision difference, and they also help the tired volunteer at the back of the crowd. Design for the hardest case and the middle gets easier on its own.
Myth 4: “One route to the information is enough”
A diagram with no written description shuts out anyone using a screen reader. A video with no transcript shuts out anyone on a patchy connection or in a quiet library. A form that only works with a mouse shuts out anyone who relies on a keyboard. Offering two or three routes to the same fact, such as a picture plus a short text explanation, is not duplication. It is how you make sure the explanation of, say, why some satellites seem to hover over one spot reaches the student who cannot see the figure and the one who cannot hear the narration.
Myth 5: “People will tell us if something is hard to use”
Most will not. They leave quietly. The curious teenager who could not find the register button, the retired technician who gave up on a tiny-print schedule, the career changer who could not decode an acronym-packed role description: none of them write in to complain. The only way to catch these exits is to ask people directly, watch them try the page or the briefing, and treat each stumble as information. A two-sentence “tell us what was confusing” box at the end of a guide is cheap and surprisingly productive.
Myth 6: “Making things inclusive is a one-time project”
Pages get edited, new diagrams get added, new rules appear, and each change can quietly break what worked before. Teams that do this well treat accessibility like maintenance on a vehicle: small regular checks rather than one grand inspection. Some web development and SEO teams go as far as publishing an accessibility statement for their own site, which is a useful habit to borrow. cmsGalaxy does exactly that, putting in writing what its pages aim to support so visitors know what to expect and where to report a problem. A short public statement of that kind keeps a team honest long after the launch excitement fades.
What a practical fix list looks like
You do not need a new budget to start. Pick one public page or one briefing document this week and run through the following.
- Words: replace abbreviations on first use, and keep sentences short enough to read aloud in one breath.
- Type: make the body text comfortable to read at arm’s length, with clear space between lines.
- Labels: name every button, link and diagram so its purpose is obvious without surrounding context.
- Alternatives: pair each image or video with a text version, and offer a keyboard-only way through every step.
- Access: for events and tours, state plainly whether entrances are step-free, where seating is, and how to ask for adjustments.
The payoff for space careers
The field needs more problem-solvers than any single stereotype can supply. A careers page that describes roles in plain language, an open day with captioned talks and step-free routes, and a briefing note anyone can read in one pass: these are small choices that turn “not for people like me” into “maybe I could do this”. None of them costs anything in rigour. They simply stop treating an imagined average person as the only visitor, and the real visitors, with all their differences, tend to notice and stay.
Start with one page, one document, one event. Ask three people who are not like you to try it, listen to where they hesitate, and fix that first. Then do it again next month. That is how a field that looks outward gets better at looking around at who is actually in the room.