Accessibility at CercaClaro

In short: we want anyone to be able to search for and contact professionals on CercaClaro without barriers, whether or not they use assistive technology. Our target is level AA of WCAG 2.2: we already use semantic HTML, full keyboard navigation, a visible focus indicator, sufficient colour contrast and text alternatives throughout the site. We are still working through known gaps, mainly around some third-party images and the map, which isn’t live yet.

Our accessibility target

We design and build CercaClaro to reach level AA of the Web Content Accessibility Guidelines (WCAG) 2.2, the W3C’s international reference standard for digital accessibility. It’s a target rather than a certification: some parts of the site already meet it, others we’re still reviewing. It sits inside our methodology, not bolted on afterwards.

What we do

• Semantic HTML. Headings, lists, buttons and links are used for what they actually are, not disguised <div>s, so screen readers and other assistive tools can follow each page’s real structure.
• Full keyboard navigation. Everything you can do with a mouse — searching, filtering, opening a contact form, moving through the menu — works with a keyboard alone, in a sensible order.
• Visible focus. When you navigate by keyboard, you can always see which element has focus: a clear outline with enough contrast, never removed for the sake of style.
• Colour contrast. Text keeps a contrast ratio of at least 4.5:1 against its background, in line with the WCAG AA criterion.
• Text alternatives. Meaningful images carry a descriptive alt in the page’s own language; purely decorative ones are marked so screen readers skip them.
• Correct lang attribute. Every page declares its language (en or es) so assistive tools use the right pronunciation and rules.
• Reduced motion. If your system has “reduce motion” switched on, we respect that preference and skip animations that aren’t necessary.
• Nothing relies on colour alone. A “verified” badge, an error message or a required form field is never shown by colour alone — there’s always text, an icon or a label alongside it.

Known limitations

We don’t have everything right yet:

• Some third-party images (for example, freely licensed city photos — see credits) may carry a more generic alt text than the ones we write ourselves, because we’re relying on the original source’s own description.
• The interactive map isn’t live yet. When we launch it, it will always come with a list or table alternative — never a map on its own.
• Some pages built in the early stages of the project may not fully meet AA level yet. We’re working through them in order of traffic.

If you spot any other barrier, tell us — it’s the quickest way for us to fix it.

The legal picture in Spain

Two separate Spanish laws deal with digital accessibility, and it’s worth keeping them apart:

• Royal Decree 1112/2018 (Real Decreto 1112/2018), transposing EU Directive 2016/2102, requires public-sector websites and apps to meet the UNE-EN 301549 technical standard. It doesn’t apply to us directly — CercaClaro is a private service — but we use that same standard as a technical reference point.
• Law 11/2023 (Ley 11/2023), transposing Directive (EU) 2019/882 — the European Accessibility Act — sets accessibility requirements for certain private products and services (e-commerce, banking, passenger transport, e-books, among others) from 28 June 2025. Its exact scope depends on the type of service and the size of the business; we follow how it applies to services like ours and work towards it where it does.

In both cases, the underlying technical standard (UNE-EN 301549) is built on WCAG 2.1 level AA. Our own WCAG 2.2 AA target goes a step further than that baseline.

How to report a barrier

If you run into an accessibility barrier on CercaClaro — a button that won’t respond to the keyboard, contrast that’s too low, an image with no description — get in touch through the contact details on the legal notice page. Please tell us:

1. Which page it happened on (the URL, if you have it).
2. What you were trying to do and what went wrong.
3. Whether you use a screen reader, screen magnifier or other assistive technology, and which one.

We look at every report and prioritise it by how many people it affects.

Last reviewed

This statement was last reviewed on 24 September 2026, the same day it was published. We’ll update it as our practices or the applicable legal framework change.

---

Related: methodology, verifying professionals, image credits, legal notice, privacy, cookies.