Saavutettavuus: WCAG, monikielisyys ja EU-direktiivi

Saavutettavuuden kaksi ulottuvuutta — vammaissaavutettavuus (WCAG 2.1 AA) ja kielellinen saavutettavuus (FI/SV/EN läpileikkaavasti) — ja miksi molemmilla on merkitystä laillisesti ja kaupallisesti.

Accessibility is two things at once: making your site usable by people with disabilities, and making it usable by people who don't share the same first language. The Long Way takes both seriously. Every site we build meets WCAG 2.1 AA at minimum, and every multilingual site we build is properly localised — not Google-Translated.

Disability accessibility (WCAG 2.1 AA)

The Web Content Accessibility Guidelines define what an accessible site looks like. The AA conformance level is the practical floor for a public commercial website. It covers four principles, each of which we treat as a default, not an extra:

Perceivable. Sufficient colour contrast (4.5:1 for body text); meaningful alt text on every image; captions on video; text that resizes without breaking the layout.
Operable.Full keyboard navigation, with a visible focus ring and a "skip to content" link at the top of every page. No animations that flash; no time-limited interactions where the user can't request more time.
Understandable. Plain-language labels on every form field. Predictable navigation. Error messages that say what went wrong and how to fix it.
Robust. Semantic HTML so assistive technology can interpret the page. ARIA where strictly needed — never as a substitute for native semantics.

We test with screen readers (NVDA on Windows, VoiceOver on macOS), with keyboard-only navigation, and with the browser zoomed to 200%. The accessibility tree is part of the design review, not a post-launch audit.

The legal floor in the EU

The European Web Accessibility Directive (EU 2016/2102) already requires public sector sites to meet WCAG 2.1 AA. The European Accessibility Act (EAA, 2019/882) extends comparable obligations to many private-sector services from June 2025 — including e-commerce, banking, transport booking, and digital media. If your site sells anything online to EU customers, this almost certainly applies to you.

Linguistic accessibility

Finland is a bilingual country. A serious public-facing site should be available in both Finnish and Swedish; one targeting an international audience should add English. We use next-intl to make the locale a first-class part of every URL — visitors always know which language they're reading and can switch between them without losing their place.

Two pieces of this matter and often get skipped:

Translated content, not just translated UI chrome. The header navigation isn't a translation — it's a token dictionary. The body content (case studies, blog posts, policy texts) is the actual translation work. Both have to happen.
Cultural sensitivity in the translation itself. Swedish in Finland is different from Swedish in Sweden — we use Finland-flavoured Swedish throughout. English on a Finnish site can be neutral, but the tone should match how the brand speaks in Finnish, not be machine-translated breeze.

Examples in the portfolio: millalahdenpera.fi is FI/SV throughout for a parliamentary candidate; saarijameri.fi is FI/SV/EN with locale-keyed Payload fields all the way down.

Why this matters commercially

Accessibility expands the audience: roughly one in six people lives with a disability, and many more benefit from accessible design even if they don't consider themselves disabled (try reading a low-contrast site in bright sunlight). Multilingual support roughly doubles your addressable market in Finland. Both also help SEO, because the signals search engines use overlap heavily with the signals assistive technology uses.

What we won't do

We don't install "accessibility overlay" widgets — those third-party scripts that promise WCAG compliance with one line of JavaScript. They are widely shown to make accessibility worse, not better, and they don't hold up in a real legal challenge.