Accessibility statement

Our commitment

Idcare Digital is committed to making idcarefinder.com usable by as many people as possible, including people who navigate by keyboard, use a screen reader or a magnifier, need larger text, or prefer less motion on screen.

Finder is bought largely by public libraries and universities, which are themselves bound by accessibility duties. It would be an odd product to sell from an inaccessible website.

Conformance status

This site is partially conformant with the Web Content Accessibility Guidelines (WCAG) 2.2 level AA.

“Partially conformant” is chosen deliberately, and it is the honest label rather than the flattering one. Every criterion we can test automatically passes on every page, on every change. But automated testing reaches only part of WCAG — roughly a third of the success criteria can be checked by a machine at all — and this site has not had an independent audit or been tested with people who use assistive technology daily. Until it has, claiming full conformance would be claiming more than we have evidence for.

How we test

Accessibility is a build gate on this project, not a review stage. A change that breaks it cannot be merged.

On every change, automatically:

• axe-core runs against every page in two viewports — 1440 × 900 and 390 × 844 — which is 82 page-and-viewport combinations. The build fails on any violation rated critical or serious. There are currently none.

• Structure is asserted rather than eyeballed: exactly one h1 per page, heading levels that descend without skipping, the expected landmark regions and no more, and the first focusable element on every page being the skip link.

• Horizontal overflow is measured at every page and viewport, because a page that scrolls sideways at 320px is a failure a screenshot hides.

• Layout is measured at seven widths in all three languages — 60 assertions — because Spanish and German run 30–40% longer than English and a component that fits in one language is not a component that fits.

• Contrast is computed arithmetically from the design tokens, not judged by eye. The brand orange carries dark ink rather than white for exactly this reason: white on it measures 3.64:1 and fails, dark ink measures 4.93:1 and passes.

By hand, on the two components with moving parts:

• The home page demonstration is tested with JavaScript disabled, with prefers-reduced-motion: reduce set, and with its pause control operated — including that pausing settles it on a complete frame rather than freezing it mid-animation.

• The floating buttons are tested for target size, for keeping a visible focus ring, for never covering a link in the footer, and for working with no JavaScript at all.

The evidence from each run is kept for 30 days.

What we have deliberately done

Some of these are the reason for a design decision, so they are worth stating:

• Nothing moves unless you allow it. The animation beside the headline runs only where prefers-reduced-motion is not set to reduce. Where it is, the sequence shows its final frame — a record, its shelf, and the route to it — immediately and permanently. This is written as motion being added for readers who accept it rather than removed for readers who do not, so the failure mode is a still picture rather than an empty box.

• The animation can be stopped. It loops for longer than five seconds, so WCAG 2.2.2 requires a way to pause it. There is a button beside it. It works with a keyboard, it names what it does, and it reports its own state.

• Everything works without JavaScript. The enquiry forms submit and are answered. The animation shows its finished frame. The floating buttons work. Nothing on this site requires a script to be usable.

• No motion is triggered by scrolling into view except the appearance of the two floating buttons, which is a fade rather than movement across the screen.

• Focus is always visible, on a 2.5px ring in the brand colour, and it is never removed.

• The interactive displays described on this site have their own accessibility characteristics — reachable height, a large-target interface, screen-reader support on the device — which are documented in the product datasheet rather than here. This statement covers the website.

What we know is not yet right

If you find something not on this list, we would rather know than not.

Tell us about a barrier

If any part of this site stops you doing something, write to info@idcaredigital.com.

Please tell us the page, what you were trying to do, and — if you can — what you are using to read the site. That last detail is usually what turns a report into a fix.

We aim to reply within five working days. If a barrier is straightforward, we would rather fix it than answer a message about it.

If you are not satisfied

Idcare Digital is a private company, and this is a commercial website. Spain’s Royal Decree 1112/2018, which gives a formal complaint route for inaccessible websites, applies to public-sector bodies rather than to a supplier’s own site — so there is no statutory reclamación route here.

That is a description of the law rather than a way out of the obligation. If you have raised something with us and are not satisfied with the answer, say so and it will be looked at again by someone else.

[TO CONFIRM: whether your adviser wants a named escalation contact — a person or a role — rather than the same shared mailbox. A route that leads back to the same inbox is not much of an escalation, and public-sector customers ask about this.]

About this statement

• Prepared: 8 September 2026

• Method: self-assessment, with the automated and manual testing described above

• Last evaluated: 8 September 2026. The automated part runs again on every change to the site, so the evaluation date is never far behind what you are reading

• Standard applied: WCAG 2.2 level AA. For public-sector procurement, the corresponding European standard is EN 301 549; the WCAG criteria above are the web content part of it