An Accessibility Pass on an Existing Site

I’ve lost count of how many “accessibility consultants” have tried to sell me a monthly subscription for a software suite that supposedly handles everything for them. It’s the same old song: they make the process sound like you need a PhD in computer science just to ensure a screen reader can navigate your homepage. Honestly, the industry has turned how to make a site accessible into this expensive, convoluted mystery, when in reality, it’s mostly just about common sense and decent structure. You don’t need a massive budget or a team of specialists; you just need to stop building digital barriers for people.

I’m not here to sell you a shiny new plugin or a certification course that costs more than my first server rack. My plan is much simpler: I’m going to show you the practical, manual steps to get your content in front of everyone without the unnecessary fluff. We’ll talk about alt text, contrast, and keyboard navigation—the actual essentials—so you can get it done in an afternoon and get back to your life. No upselling, no nonsense, just the facts.

Semantic Html Best Practices the Foundation of Inclusion

Back when I was building circuits, if you didn’t label your components correctly, the whole system was a mess. Web development is no different. People try to make things look “pretty” using endless nested `

` tags, but to a machine, that’s just a wall of noise. If you want real screen reader optimization, you have to use the right tools for the job. Use a `

` for your menu and a `

` for your primary content. It sounds basic, but it’s the difference between a user actually finding your info or getting lost in a digital void.

I’ve seen plenty of developers try to bypass this by throwing a bunch of complex ARIA roles and attributes at a broken layout, hoping it fixes the problem. That’s just band-aid engineering. You don’t need a complicated workaround if your underlying structure is sound. Stick to semantic HTML best practices from the jump. If you build your site on a logical, meaningful foundation, you’ve already done eighty percent of the heavy lifting for accessibility without spending an extra dime on fancy plugins.

Mastering Wcag Compliance Guidelines Without the Bloat

Now, when you start looking into the official WCAG compliance guidelines, it’s easy to feel like you’re drowning in a sea of technical jargon designed to make you hire a consultant. Don’t fall for it. You don’t need a certification seminar to get the basics right; you just need to respect how people actually use the web. For instance, pay attention to your color contrast ratios. If your text is a light grey on a white background, you aren’t being “minimalist”—you’re just making your site unreadable for anyone with even slight visual impairments.

The same goes for how a person moves through your pages. I’ve spent many an evening testing sites using nothing but the Tab key, and it’s a wake-up call. If you can’t navigate your entire menu using only a keyboard, your keyboard navigation accessibility is broken. You don’t need fancy plugins to fix this; you just need to ensure your focus states are visible and logical. Avoid the temptation to layer on complex ARIA roles and attributes unless you actually know what they do. Most of the time, if you’ve stuck to solid, clean code, the browser handles the heavy lifting for you.

Five things that actually matter (and the rest is just noise)

Check your colour contrast. It sounds simple, but I’ve seen far too many “modern” sites use light grey text on a white background. If you can’t read it while squinting at a screen in a bright room, it’s not good design, and it’s certainly not accessible.
Don’t go overboard with animations. A little movement is fine, but if your site flashes or slides every time someone scrolls, you’re going to give people headaches. Keep it steady; people are here for information, not a light show.
Labels for your forms. There is nothing more frustrating than a contact form where you click a box and have no idea what you’re supposed to type in it. Make sure every input field has a clear, permanent label. Don’t rely on placeholder text that disappears the moment you start typing.
Keyboard navigation is your litmus test. Put your mouse aside for a minute and try to use your site using only the Tab key. If you get stuck in a loop or can’t reach the menu, your site is broken for anyone who can’t use a mouse.
Write decent alt text for images. You don’t need a poetic description of every pixel, but if an image conveys information, describe it. If it’s just a decorative line or a bit of fluff, just leave the alt attribute empty so the screen readers know to skip it.

The Bottom Line

Don’t let agencies talk you into expensive “accessibility audits”—if you’ve used proper semantic tags and kept your code clean, you’ve already done 90% of the heavy lifting.

Accessibility isn’t a premium add-on you buy later; it’s just good, logical engineering that should be baked into the site from the first afternoon you spend on it.

Stick to the basics: high contrast, clear navigation, and readable text. You don’t need a bloated plugin suite to make a site usable for everyone.

Cutting Through the Noise

At the end of the day, making a site accessible isn’t about buying a premium “accessibility suite” or hiring a consultant to run a thousand-dollar scan. It comes down to the basics we’ve discussed: using proper semantic HTML so the machines actually understand your structure, and following the WCAG guidelines without letting the technical jargon paralyze you. If you’ve got your alt text sorted, your color contrast is readable, and your navigation doesn’t require a PhD to figure out, you’ve already done more than most. You don’t need a bloated toolkit; you just need to build with intent and respect the way different people interact with a screen.

I’ve seen plenty of flashy, expensive websites that are essentially digital brick walls for anyone using a screen reader. Don’t fall into that trap. Building an accessible site shouldn’t be an exhausting marathon or a massive line item in your budget; it should be a standard part of your afternoon workflow. Just remember that the web was meant to be a level playing field. If you focus on the fundamentals of usability, you aren’t just ticking a compliance box—you’re actually making the internet work the way it was designed to. Now, go get that site live.

About Halvard Boateng

A first website needs a domain, a host and an afternoon. The rest is upselling.