Back to the blog
accessibilityweb developmentlegal

Web Accessibility (WCAG): Why It's No Longer Optional

Gatium csapatSeptember 6, 20263 min read

It's not just an issue for big government websites. Who accessibility actually affects, the most common mistakes, and why a fixed site is better for everyone.

Web Accessibility (WCAG): Why It's No Longer Optional

Accessibility has long been a topic most SME leaders thought of as "more of a big, government-website thing." That picture has changed by now: the European Union's accessibility directive is gradually affecting more and more digital service providers, and regardless of legal obligation, more and more customers are arriving with devices or needs that a non-accessible site simply can't respond to. This article isn't legal advice — it's about why it's worth treating this with a business mindset, not just as compliance.

Who this actually affects — more than you'd think

When we talk about accessibility, most people picture a blind user with a screen reader. That's indeed an important case, but far from the only one. This also includes someone with reduced vision trying to read in bright sunlight on a low-contrast screen; someone with shaky hands who clicks imprecisely and misses tiny buttons; someone temporarily navigating with just one hand and a keyboard because of a broken arm; or simply someone in a noisy environment trying to understand a video without sound, with no captions. This realization is what flips the question from a legal obligation into the exclusion of a real, measurable customer base — because these people today simply leave your site, and end up at a competitor who thought about them better.

The other, often underrated point is that many accessibility fixes give a better experience to everyone, not just the targeted group. Good contrast is more readable for everyone, a bigger clickable area is more comfortable for everyone on mobile, well-structured content broken into subheadings is quicker for everyone to scan. This is exactly why accessibility isn't worth treating as an "extra layer" tacked onto a finished site at the end of a project — but as a baseline quality expectation built into every step of design and development.

The most common, cheaply fixable mistakes

Most websites' accessibility problems aren't complex technical shortcomings — they're a handful of relatively easy-to-fix basic mistakes. Missing text descriptions for images is one of the most common: for a screen-reader user, an image with no description simply doesn't exist, even if it conveys important information (a price, a chart). Poor color contrast — a trendy but pale gray text on a white background — is barely readable for many, even with normal vision, in bright light.

The lack of keyboard navigability is another common problem: many interactive elements (a custom dropdown, a custom card) can only be clicked with a mouse, and can't be reached with a keyboard at all — meaning anyone who can't use a mouse is simply excluded from that functionality. Finally, missing video captions excludes not just hearing-impaired users, but everyone browsing without sound in a public place — which today, given mobile usage rates, is a surprisingly large group.

How to get started if you're facing this now

Accessibility doesn't need to — and shouldn't — be treated as one giant project you "do once and it's done." The approach that works in practice is to first use an automated checking tool (several are available for free) to uncover the most glaring, technically easy-to-detect mistakes — missing image captions, weak contrast, missing labels on form fields — and fix these one by one. This covers a significant share of the problems, with relatively little work.

Accessibility isn't expensive because it's a lot of work — it's expensive if you try to bolt it onto an already-finished, complex site at the very end. If you think about it as part of the design, most of it comes naturally.

Automated tools don't catch everything, though — the real, deeper problems (logical navigation order, understandable error messages, actual usability with a screen reader) are best uncovered through human testing. If this feels like too big a step right now, start with the most important conversion paths — the contact form, the purchase flow — because there, exclusion means direct lost revenue too, not just a matter of principle.


If you'd like to know where your website currently stands on accessibility, request a quick audit — we'll tell you what's worth fixing first.

Ready to talk through your project?

Let's discuss how to build an experience that not only looks great, but drives real growth for your product.

Website Accessibility for SMEs — WCAG Basics | Gatium