WCAG - what it is and why your website should be accessible
A client asks: "Why can't my mother read our website properly?"
She is 67 and has poor eyesight. She zooms the browser to 150%. On half the websites she visits, text overlaps, buttons disappear behind edges, and menus stop working. The site works. But for her - it does not exist.
This is an accessibility problem. And it affects far more people than you think.
What is WCAG
WCAG (Web Content Accessibility Guidelines) is a set of rules for building websites that work for everyone - including people with visual, hearing, motor, or cognitive disabilities.
The current standard is WCAG 2.1. The most common level is AA (double A). There are three levels - A (minimum), AA (industry standard), AAA (maximum). Most regulations and public tenders require AA.
The guidelines are built on 4 principles. A website must be:
Perceivable - users must be able to see or hear the content. Alt text on images, sufficient color contrast, captions in videos.
Operable - it must work with a keyboard, not just a mouse. Visible focus, logical navigation, no traps (elements you cannot Tab out of).
Understandable - content and interface must be clear. Declared page language, labeled form fields, meaningful error messages.
Robust - the site must work across different technologies. Screen readers, older browsers, assistive devices.
Who does this affect
Globally, 1.3 billion people live with some form of disability - 16% of the population. On top of that, there are people with temporary limitations: a broken arm, an eye infection, noise in the background, bright sunlight on a phone screen.
And older people. Your target audience ages with you. Eyesight fades, hand motor skills decline, and phone screens do not get any bigger.
But accessibility also helps people without any limitations at all. Good text contrast is easier to read in direct sunlight. Large buttons are easier to tap on a phone. Video captions help when you are on a train without headphones.
The legal side
In the EU, the European Accessibility Act is extending requirements to the private sector - e-commerce, banking, telecommunications. In many countries, accessibility lawsuits against businesses are increasing year over year.
For private companies, WCAG may not be legally required everywhere yet. But more and more corporate clients demand it from their vendors. Public tenders already include WCAG in their specifications.
The direction is clear: accessibility is becoming a standard, not an option.
Why it makes business sense
Setting ethics aside (because you should not need convincing that people deserve to use your website):
- Wider reach - 16% of the population is a segment you lose when your site is inaccessible
- Better SEO - Google rewards accessible sites. Alt text, proper heading structure, semantic HTML - the same things SEO requires
- Fewer complaints - a contact form that works for everyone means fewer "I can't submit the form" phone calls
- Reputation - a company that cares about accessibility is seen as professional. Not because it is trendy - because it is honest
Where to start
You do not need to rebuild your site from scratch. Start with four things:
- Check text contrast. Minimum 4.5:1 for regular text, 3:1 for large text. Free tool: WebAIM Contrast Checker
- Add alt text to images. Describe what is in the photo. Not "image" or "photo_01.jpg"
- Test with a keyboard. Press Tab and navigate the page. Focus must be visible and move logically
- Zoom to 200%. Ctrl/Cmd + a few times. If anything breaks - you have a problem
At dede.agency we implemented WCAG 2.1 AA - from color contrast, through keyboard navigation, to an accessibility widget that lets users increase contrast, enlarge text, or pause animations. It did not require a site rebuild. It required a conscious approach to details that were previously invisible.
In the next post I will show you specific tools and tests to check your website accessibility in 10 minutes.
