When I started my first job in IT, a senior colleague asked me to check a web form I had built. She did not open it in a browser. She put her hand over the mouse, pressed Tab and watched. The cursor vanished after the second field, and I could not tell where I was on the page. “Imagine this is the only way you can use a computer,” she said. That moment taught me more about web accessibility than any slide deck. This primer is for beginners who want to start in the same place: a few big ideas, and a mini-glossary you can keep beside your keyboard.
The big idea in one sentence
Accessibility means building things so that people with different abilities, devices and situations can use them to do the same job. It is not a separate product. It is a quality of ordinary good work, and the same habits help people who have never thought of themselves as having any special need.
Who are we building for?
Think about a spread of real people. A student who is blind and uses a screen reader. A grandfather with trembling hands who finds small buttons impossible. A new arrival who reads the language slowly. A programmer with a repetitive strain injury who avoids the mouse. A commuter using a cheap phone with a flickering signal. If your page works for all of them, it will almost certainly work for the person you originally imagined as well.
Mini-glossary of web accessibility terms
- Screen reader: software that reads the page aloud or sends it to a braille display. It depends on well-built headings, labels and text alternatives.
- Alt text: a short written description of an image, so someone who cannot see it still gets its meaning. Skip it when the image is purely decorative.
- Contrast: the difference in brightness between text and its background. Higher contrast means easier reading, especially in bright light or for low vision.
- Focus: the control currently selected by the keyboard. It must always be visible, or keyboard users get lost.
- Keyboard navigation: moving through a page with Tab, Enter and the arrow keys instead of a mouse.
- Captions and transcripts: text versions of audio and video. They serve people who are deaf, in noisy rooms, or who simply prefer reading.
- Semantic headings: real heading tags in a logical order, which let people skim and jump rather than wade through everything.
- Plain language: short sentences and familiar words, with each new term explained the first time it appears.
- Reflow: a layout that rearranges itself when text is enlarged, instead of forcing sideways scrolling.
Your first five habits
- Tab through your own work. If you cannot see where you are, neither can anyone else.
- Zoom to double size. Check that nothing overlaps, vanishes or needs side-to-side scrolling.
- Name every control. Replace “click here” and bare icons with words that say what happens.
- Describe images that carry meaning. One honest sentence is usually enough.
- Read it aloud. If you stumble, so will your reader.
A story about a small fix
A learner I mentored once built a sign-up form for a volunteer group. Every field was grey text on a slightly lighter grey background, and errors appeared as a faint red outline. It looked sleek in his design tool. Two volunteers, both over seventy, quietly stopped signing up. When he enlarged the text, darkened the colours and wrote a message that said “Please enter a phone number we can reach you on”, sign-ups from older volunteers rose within weeks, and the younger ones said it felt easier too. He had not set out to change anything except readability. That small, humane edit taught him the point of the whole subject.
Where this fits in your learning
Accessibility belongs beside the rest of your practical learning, not after it. If you are mapping a self-study plan, a resource such as this step-by-step approach to learning a technical field from scratch shows how to build skills in layers, and inclusive habits are one more layer worth adding early. For a view of what employers expect from IT professionals more broadly, this overview of skills a modern IT professional needs gives helpful context.
Learning from teams that publish their standards
One good way to learn is to read how real teams describe their own commitments. Many organisations now publish an accessibility statement saying what they support and how to report a barrier. The web development and SEO team cmsGalaxy has an accessibility statement for its own site, and reading a short example like that helps you see what honest, specific wording looks like. Notice how it names limits as well as strengths.
Common beginner mistakes
- Relying on colour alone to show errors or status.
- Hiding the keyboard outline because it looks untidy.
- Writing alt text such as “image” or repeating a file name.
- Assuming an automated checker will catch everything.
- Leaving the work for a final polish that never happens.
A tiny practice project
Choose one page you already know, perhaps your portfolio or a school project. Spend an hour on it. Tab through every control, enlarge the text, read the copy aloud, add real labels and descriptions, and ask a friend who is not technical to find one piece of information on it. Write down what you changed and how it felt before and after. That one hour tends to teach what days of reading cannot, and the result is a finished example you can talk through with an interviewer. Then pick another page next month and keep going.

