Let me start with an uncomfortable truth: your website is probably excluding people. Not intentionally, almost nobody does it on purpose. But if you haven’t actively thought about web accessibility, there are people who literally cannot use your site. Blind people who rely on screen readers. People with motor disabilities who can’t use a mouse. Colour-blind users who can’t distinguish your carefully chosen colour scheme. Elderly people whose vision isn’t what it used to be.
And here’s the thing that should really get your attention if you’re a business owner in Spain: it’s becoming a legal requirement, and the deadlines are closer than you think.
I’ve been building websites for small businesses across Spain for years, and accessibility is the topic that gets the biggest gap between “yeah, that’s important” and actually doing something about it. So let me give you the practical, no-nonsense guide to what accessibility means, what the law requires, and what you can actually do about it without rebuilding your entire website.
What Web Accessibility Actually Means (Skip the Jargon)
Web accessibility means making your website usable by everyone, including people with disabilities. That’s it. No complicated definition needed.
In practice, it covers four main areas:
Visual: People who are blind (use screen readers), have low vision (need larger text), or are colour-blind (can’t rely on colour alone to convey meaning).
Motor: People who can’t use a mouse, they navigate using keyboards, voice commands, or specialised devices. If your site requires mouse hovering or precise clicking, they’re stuck.
Hearing: Deaf or hard-of-hearing users who can’t access audio content. If you have videos without captions, they miss out.
Cognitive: People with dyslexia, ADHD, or cognitive disabilities who need clear layouts, simple language, and consistent navigation.
The international standard for web accessibility is called WCAG (Web Content Accessibility Guidelines). It has three levels: A (minimum), AA (the standard everyone aims for), and AAA (aspirational). For legal compliance and general good practice, WCAG 2.1 Level AA is the target.
The Legal Reality in Spain and Europe
This is where it gets serious. The European Accessibility Act (EAA) was adopted in 2019 and EU member states, including Spain, have until June 28, 2025 to transpose it into national law, with businesses needing to comply by June 2025.
In Spain specifically, we already have:
- Real Decreto 1112/2018: Requires public sector websites and apps to meet WCAG 2.1 Level AA. This is already in force.
- The European Accessibility Act (transposed as Ley de Accesibilidad): Extends requirements to private sector businesses providing certain services, including e-commerce, banking, and transport services.
- LSSI (Ley de Servicios de la Sociedad de la Información): Spain’s general e-commerce law, which increasingly intersects with accessibility requirements.
“But I’m a small business,” I hear you say. “Does this really apply to me?”
Currently, the strictest requirements apply to public sector websites and larger businesses. But the direction of travel is unmistakable: accessibility requirements are expanding, not shrinking. Microenterprises (fewer than 10 employees and under 2 million euros turnover) have some exemptions under the EAA, but this doesn’t mean your website can be completely inaccessible.
More practically: even if you’re technically exempt right now, an inaccessible website is a liability. Discrimination complaints can be filed regardless of business size, and the reputational risk alone should concern you.
The Business Case (Beyond Compliance)
Legal requirements aside, there’s a compelling business argument for accessibility:
It expands your audience. In the EU, roughly 87 million people have some form of disability. In Spain, that’s over 4.3 million people. On the Costa del Sol, with its significant retired population, the numbers are even more relevant. Many of these people have money to spend and actively prefer businesses that accommodate their needs.
It improves SEO. This is the secret weapon. Many accessibility best practices, proper heading structure, alt text on images, descriptive link text, clean HTML, are also SEO best practices. I’ve seen websites improve their search rankings simply by fixing accessibility issues. Google’s algorithms increasingly reward accessible, well-structured content.
It improves everyone’s experience. Captions don’t just help deaf users, they help anyone watching a video in a noisy cafe. Good colour contrast doesn’t just help colour-blind users, it helps anyone using their phone in sunlight. Keyboard navigation doesn’t just help motor-impaired users, it helps power users who prefer keyboards.
The Most Common Problems (And How to Fix Them)
After running website audits for dozens of small businesses, I see the same accessibility issues over and over. Here’s what they are and how to fix them:
1. Missing alt text on images
The problem: Screen readers can’t describe images without alt text. Blind users hear “image” or worse, the filename (“IMG_3847.jpg”).
The fix: Add descriptive alt text to every meaningful image. “Front view of our restaurant terrace overlooking Marbella beach”, not “restaurant” or “photo1.” Decorative images (backgrounds, dividers) should have empty alt text (alt=””) so screen readers skip them.
2. Poor colour contrast
The problem: Light grey text on a white background looks elegant to you but is unreadable for users with low vision. WCAG requires a contrast ratio of at least 4.5:1 for normal text.
The fix: Use a contrast checker tool (WebAIM’s Contrast Checker is free). Adjust your text colours to meet the 4.5:1 ratio. This usually means making text darker than you’d aesthetically prefer, but readability trumps aesthetics every time.
3. No keyboard navigation
The problem: Users who can’t use a mouse navigate with the Tab key. If your interactive elements (menus, buttons, forms) don’t work with keyboard navigation, these users are locked out.
The fix: Test your site by unplugging your mouse and trying to navigate with Tab and Enter only. Can you reach every link? Open every menu? Submit every form? If not, you have keyboard navigation issues. The most common fix is ensuring focusable elements have visible focus indicators (that glowing outline when you Tab to something, don’t remove it with CSS).
4. Forms without labels
The problem: If your contact form uses placeholder text instead of proper labels, screen readers don’t know what each field is for. The user hears “edit text” instead of “email address.”
The fix: Add visible labels to every form field. Placeholders are not labels, they disappear when you start typing and aren’t reliably read by screen readers. Every input field needs a corresponding label element.
5. Missing heading structure
The problem: Screen reader users navigate pages by headings (H1, H2, H3). If your headings are actually just bold text or styled divs, the page has no navigable structure for these users.
The fix: Use proper HTML heading tags in a logical hierarchy. One H1 per page (your main title), H2 for main sections, H3 for subsections. Never skip levels (don’t go from H2 to H4).
6. Auto-playing video or audio
The problem: Auto-playing media is disorienting for screen reader users and can be distressing for users with cognitive disabilities or PTSD.
The fix: Never auto-play video or audio. Always let users choose to play media. If you absolutely must auto-play (hero videos), mute it by default and provide a clear play/pause button.
Testing Tools You Can Use Right Now
You don’t need to hire an expert to do an initial accessibility check. These free tools will catch the most common issues:
WAVE (wave.webaim.org): Paste your URL and get a detailed breakdown of accessibility issues. It’s the gold standard for free testing.
Lighthouse (built into Chrome DevTools): Press F12, go to the Lighthouse tab, and run an accessibility audit. Quick and actionable.
axe DevTools (browser extension): More detailed than Lighthouse, catches issues other tools miss.
The keyboard test: No tool needed. Unplug your mouse and try to use your website with only Tab, Enter, and Escape. If you get stuck anywhere, that’s an accessibility barrier.
Colour Contrast Analyzer: Free desktop app that lets you pick any colour on your screen and check its contrast ratio.
A word of caution: automated tools catch roughly 30-40% of accessibility issues. The rest require human testing. But fixing the issues these tools find is a massive improvement over doing nothing.
The WordPress-Specific Guide
Since most of the small business websites I build are on WordPress, here are WordPress-specific tips:
Choose an accessible theme. WordPress.org marks themes that pass accessibility review with an “Accessibility Ready” tag. If you’re picking a new theme, filter for this. If you’re on an existing theme, check if it has accessibility issues using WAVE.
Use the right plugins. WP Accessibility (free) adds several fixes automatically. One Click Accessibility adds an accessibility toolbar. But don’t rely on overlay plugins that promise to “make your site accessible” with one click, they don’t work and can actually make things worse.
Be careful with page builders. Some popular page builders (looking at you, early versions of Elementor) generate HTML that’s terrible for accessibility. If you use a page builder, test the output with WAVE to see what it’s actually generating.
If you’re building a new site, starting with accessibility in mind from day one is dramatically cheaper than retrofitting. This is something we factor into every web design project at Fork IT.
The Quick Win Checklist
If you’re overwhelmed, start here. These changes take a few hours and fix the most critical issues:
- Add alt text to all images (start with your homepage and main landing pages)
- Check and fix colour contrast on text (use WebAIM Contrast Checker)
- Add visible labels to all form fields
- Ensure your site has a logical heading structure
- Make sure all links have descriptive text (no more “click here” links)
- Add captions or transcripts to any video content
- Test keyboard navigation on your main pages
- Remove any auto-playing media
These eight fixes alone will take your site from “totally inaccessible” to “reasonably accessible”, and they’re all things you can do yourself without any coding knowledge.
When to Get Professional Help
DIY accessibility gets you a long way, but there are times when you need professional help:
- Your website handles transactions (e-commerce, bookings), accessible checkout flows are complex
- You’re in a regulated industry where legal compliance is non-negotiable
- You have complex interactive features (maps, calculators, dynamic content)
- You want a proper WCAG 2.1 Level AA audit with a compliance statement
A professional web design approach that includes accessibility from the start is always cheaper than fixing an inaccessible site after launch.
The Bottom Line
Web accessibility isn’t just a legal checkbox, it’s a fundamental aspect of building a website that works for everyone. The EU and Spain are making it increasingly non-optional, but even if the law weren’t involved, it’s the right thing to do. And unlike many “right things to do,” it also happens to be good for your business, your SEO, and your bottom line.
Start with the quick wins. Use the free testing tools. Fix the obvious issues. Then, when you’re ready for a thorough review, get in touch, we’ll make sure your site works for everyone.