Legal
Accessibility Statement
Last updated
An accessible site is simply a better-engineered one, so accessibility is built into how we work — not audited in at the end. Here is what we commit to, where we stand today, and how to tell us if we have missed something.
Our commitment
We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA across every page of this site, in all three languages we publish — English, Türkçe, and Arabic — including a genuine right-to-left experience, not a mirrored afterthought.
This matters to us for three reasons: it is the right thing to do, it is increasingly a legal expectation in the markets we serve, and a site that is fast, robust, and usable by everyone is exactly the kind of engineering we are selling. Our accessibility is part of our proof.
Where we stand today
In June 2026 we audited this site against every WCAG 2.2 Level A and Level AA success criterion — 55 criteria in all, 31 at Level A and 24 at Level AA. The audit produced a per-page record for every page in every language, and its checks re-run automatically on every change we ship, so this statement cannot quietly drift from what is actually true.
- 33 criteria are verified automatically on every build — page structure, contrast, keyboard wiring, forms, motion, and language markup are checked by deterministic tooling across all three languages, and a failure blocks the release.
- 13 criteria do not apply to this site — for example, we publish no audio or video and require no login — and each is recorded with its reason rather than silently claimed.
- 9 criteria are satisfied in our testing but still await their final recorded human verification pass — named openly in "What is still in review" below.
The audit found one Level AA failure: focused content could settle behind the sticky page header when following an in-page link (success criterion 2.4.11, Focus Not Obscured). It was fixed the same day, and a regression check now keeps it fixed. No known unresolved WCAG 2.2 Level AA failures remain on this site.
How we verify it
Accessibility here is enforced by engineering, not assured by a paragraph:
- Deterministic checks in our build pipeline verify semantic structure, focus order, form labeling, color-independence, reduced-motion behavior, and right-to-left correctness on every page, in every language, before any change can ship.
- Automated accessibility testing (axe) and Lighthouse audits run against the real pages.
- Color contrast is computed from our design tokens — every combination the system can paint meets the AA thresholds, and no stylesheet can bypass them.
- Real-browser passes exercise what automation cannot judge: keyboard walkthroughs, screen-reader announcements — including Arabic — and touch-device behavior. Each pass is recorded, and whatever has not yet been recorded is listed openly below.
What this covers
This statement covers every page of this website in all three languages, including the right-to-left Arabic experience. It does not cover our internal content-management screens, which are not part of the public site.
Where we link to third-party sites, we cannot always guarantee their accessibility — though we choose partners carefully.
What is still in review
We would rather name what remains than overstate conformance. These 9 success criteria pass our testing but still await their final recorded human verification — a real screen-reader, keyboard, or device pass rather than an automated check:
- 2.1.1 Keyboard, 2.5.2 Pointer Cancellation, and 3.2.1 On Focus — the recorded end-to-end keyboard walkthrough.
- 1.3.3 Sensory Characteristics and 1.4.12 Text Spacing — the recorded screen-reader and content-review pass.
- 2.5.8 Target Size (Minimum) and 3.2.2 On Input — the recorded touch-device and forms pass.
- 1.3.4 Orientation and 1.4.10 Reflow — the recorded mobile and reflow device pass.
A native-speaker review of the Türkçe and Arabic translations — including this statement — is scheduled as part of the same pre-launch pass. Until every recorded pass is in, we deliberately make no blanket conformance claim; we state exactly what is verified and how.
Tell us about a barrier
If any part of this site is hard to use with assistive technology, or you hit a barrier we have not caught, we want to know — we treat it as a defect, not a complaint. Tell us what happened, the page, and the assistive technology or browser you were using, and we will look into it and aim to reply within one business day.
Reach us through our contact page. If you need this information or any page in a different format, ask and we will do our best to provide it.
