Accessibility Statement

01 — The standard we target, pinned to a version

We target WCAG 2.2 Level AA — the Web Content Accessibility Guidelines published by the W3C, version 2.2, conformance level AA. We name the version on purpose. "WCAG AA" with no version silently shifts every time the standard moves, and a promise that changes without telling you isn't a promise.

Some context on how that lines up with European law. The harmonised standard the European Accessibility Act leans on is EN 301 549, and its web chapter — clause 9 — currently incorporates WCAG 2.1 Level AA. WCAG 2.2 keeps every Level A and AA criterion of 2.1 except 4.1.1 Parsing, which the W3C retired as obsolete, and adds new ones on top. Targeting 2.2 AA therefore covers what clause 9 asks for and goes a step beyond it.

And the claim we do not make: WCAG 3.0 is a W3C working draft. Nobody can conform to it yet, including us. If you're ever offered a "WCAG 3.0 ready" website, that is a sales line, not a standard.

02 — Conformance status: partially conformant

websites.kalebtec.com is partially conformant with WCAG 2.2 Level AA. "Partially conformant" is the standard's own vocabulary, and it means: some parts of the site may not fully conform, or we cannot yet evidence that they do.

Here's what it does not mean. It doesn't mean we know of a barrier and have left it there — every defect our audit found is fixed in production and re-measured, and the numbers are in section 03. It means a claim of full conformance would need more evidence than we hold today: an independent audit we have not commissioned, the same depth of coverage on every part of the site (our signed-in customer console has had a lighter pass), a recorded assistive-technology test, and an automated check that keeps the result true between releases.

If we could honestly write "fully conformant" we would — it reads better and it sells better. We'll upgrade this wording the day the evidence supports it, and not one day before.

03 — What we found, and what we fixed

We audited this site on 24 July 2026 and it did not conform: one Level A failure and a set of Level AA contrast failures. We're publishing them rather than quietly patching them, because a statement that only lists successes tells you nothing. All of the following are fixed in production and re-measured:

• Contrast (1.4.3). The "Perfect for" label on the featured pricing card measured 1.71:1 in dark mode — effectively invisible. Now 5.85:1.
• Contrast (1.4.3). Case-study body text measured 2.29:1. Now 7.68:1.
• Contrast (1.4.3). The status code on our 404 page measured 2.58:1. Now 8.62:1.
• Contrast (1.4.3). The final call-to-action row now measures 5.34:1, in both the light and the dark theme.
• Keyboard traps and obscured focus (2.1.2, 2.4.11). The mobile navigation drawer and the pricing chooser both leaked keyboard focus to controls sitting behind the sticky buy bar while the page was scroll-locked. Both now cycle focus inside the open dialog and hand it back where it came from when you close them.
• Page titled (2.4.2). Our 404 page had no title. That is a Level A failure — the most basic tier there is — and it is fixed.

For reference, Level AA asks for 4.5:1 on normal text and 3:1 on large text and user-interface components. The figures above are the measured values after each fix, quoted in the theme where the element was worst.

04 — What we know is still short, and the plan for each

• No independent audit. Everything on this page is our own measurement. Plan: commission a third-party review before we upgrade the status in section 02 beyond "partially conformant".
• The signed-in customer console. The console where you follow your order, see your site and find your invoices went live recently, for our first customers, and has had a lighter pass than the public pages. Plan: a full keyboard, contrast and structure pass on the console, and this statement updated with the result, before it opens more widely.
• The automated guard is real, and it is not everything. Every public page is checked automatically on every build, at two screen widths in both the light and the dark theme, and a serious or critical finding stops the release. What that check cannot see is a good deal of Level AA: it cannot judge focus order, a misleading label, a keyboard trap it never opened, or the contrast of a control's outline. Plan: keep widening what is checked, and keep saying which parts are machine-checked and which are not.
• Our own staff console. The operator console is part of this site and came inside the automated check on 27 July 2026, in both languages, at both widths, in both themes. Nobody outside Kalebtec can reach it and it is not a customer surface, but it is on this domain, so we count it and record what we find here on the same terms as everything else.
• Control outlines in the signed-in console (1.4.11). The border that identifies a text field, a dropdown or a secondary button inside the console measured 1.81:1 in the light theme and 2.15:1 in the dark theme, against the 3:1 that Level AA asks for on user-interface components. Fixed on 27 July 2026 and re-measured at 18.46:1 and 3.54:1. It never affected the public pages, and never a website we build for a client.
• No assistive-technology test on file. Our manual testing was keyboard-based. We have not recorded a pass with a screen reader (NVDA, VoiceOver). Plan: run one and record the result at the next review.
• Coverage is page-by-page, not exhaustive. We checked the criteria that apply to each public page; we have not verified every 2.2 AA criterion on every page. Where we haven't measured something, we say "not measured" — never "passes".

05 — Third-party content we don't control

Two parts of the experience are not ours to fix directly, and pretending otherwise would be the easy way out:

• Stripe Checkout and Stripe payment links. Payment happens on Stripe's own pages, under Stripe's accessibility conformance, not ours. We chose Stripe and we own that choice: if you hit a barrier at payment, tell us and we'll take your order another way — by email, with a person — and we'll raise it with Stripe.
• PostHog. We use PostHog for analytics and error tracking. It renders nothing you interact with. The cookie choice you see is our own component, on our own pages, and it sits inside the same review as the rest of the site — declining is exactly as easy as accepting.

06 — How we assessed this

Self-assessment, carried out by Kalebtec Studio S.C on 24 July 2026. No external body audited this site, and we hold no accessibility certification. What the assessment consisted of:

• Automated contrast analysis of the rendered pages, alpha-composited, in both the light and the dark theme.
• Automated structural analysis: image alternatives, accessible names on links and controls, landmark regions, heading order, duplicate ids, positive tabindex, the skip link, and the page language attribute.
• Manual keyboard testing at 390px and 1280px viewport widths, in both themes: tab order, visible focus, focus cycling inside dialogs, and escape behaviour.
• Re-measurement of every defect after its fix — that is where the figures in section 03 come from.

What the assessment did not include: a screen-reader or other assistive-technology pass, a cognitive-accessibility review, and any form of external audit. Those are the gaps in section 04, and they are the reason this page says "partially conformant".

07 — Tell us when something doesn't work

Write to hello@kalebtec.com. Tell us the page, what you were trying to do, and what happened — and, if you can, the browser or assistive technology you use. You don't need to name a success criterion or know any of the jargon on this page: "I can't read this" is a complete and useful report.

• We acknowledge you within two business days.
• We give you a substantive answer within 15 calendar days: either it's fixed, or the date it will be — and if the fix will take longer than that, a way to get what you needed in the meantime, from a person, by email.
• We tell you the outcome, and where it turns out to be a real defect we record it on this page at the next review.

If you need something from this site in a different form — a document, a price, the Terms — ask us and we'll send it in a format that works for you, at no cost.

08 — If we don't put it right

Accessibility of products and services in Spain is governed by Ley 11/2023, de 8 de mayo, which transposes the European Accessibility Act. It gives you routes that don't depend on our goodwill:

In practice that means: the supervisory authority designated by your autonomous community, the consumer route — for us in Galicia, the OMIC de Vigo, the Instituto Galego do Consumo and the Junta Arbitral de Consumo de Galicia, all listed in our Terms — or the courts. None of it costs you anything to start.

One thing we will not do is point you at the EU Online Dispute Resolution platform: the European Commission shut it down on 20 July 2025. Any site still linking to it is sending you to a dead page, and we're not going to be one of them.

Terms & Conditions →

09 — Who is responsible for this statement

Kalebtec Studio S.C — CIF J26989384 — Avenida do Alcalde Portanet 20, 4º J, 36210 Vigo (Pontevedra), Spain. hello@kalebtec.com. Spanish law applies.

A note on scope, since it would be easy to imply more than is true. The European Accessibility Act exempts microenterprises that provide services from its accessibility requirements, and we are one. That exemption is not why this page exists. We sell "Accessibility to WCAG 2.2 AA" as a commercial promise about the websites we build, and this statement is us holding our own site to the same line we sell. Our clients' sites are a separate question: where a client's service is itself in scope of the Act, an accessible build is part of what they're buying from us.

10 — Dates and how often we review this

• Prepared: 24 July 2026.
• Last reviewed: 24 July 2026.
• Applies to: websites.kalebtec.com, including the signed-in customer console.

We review this statement at least every six months, and additionally whenever we ship a change that touches layout, colour or an interactive component, or whenever someone reports a barrier. Every review moves the date at the top of this page. If that date is more than six months old, we are late — and you're entitled to say so.

This page exists in English and Spanish, with the same content in both. Where the two differ in a legal reading, the Spanish version prevails.