Accessibility Statement
Last reviewed:
Binclusive was founded by a team of disabled people. Accessibility is the thing we sell, so binclusive.io has to hold up to the standard we ask of everyone else. This statement sets out where the site stands today, what we know is still missing, and how to reach a person when something gets in your way.
Conformance status
binclusive.io is partially conformant with the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA. Partially conformant means most of the site meets the standard, while some content, listed further down, does not yet.
We do not claim full conformance. Parts of this site are rendered by third-party services whose code we cannot change, and we will not sign off on something we do not control.
Standards we follow
- WCAG 2.2, Level AAThe international benchmark for accessible web content, and the basis of the conformance claim above.
- EN 301 549The European standard for accessible ICT, which adopts WCAG and adds requirements for software, documents and hardware.
- European Accessibility ActEU Directive 2019/882, which has required accessible digital products and services on the EU market since 28 June 2025.
- Turkey Digital Accessibility CircularThe Turkish circular on digital accessibility, published in the Official Gazette.
How we keep the site accessible
- Disabled testers on our team work through this site by keyboard and with the screen readers they use every day.
- We run our own scanner over this codebase and our own agentic audits against this site — the same tooling we sell.
- Our own video is captioned and audio-described with our own tooling.
- Accessibility defects go through the same route as any other bug: tracked in the repository, reviewed, shipped.
- When we cannot fix something, we write it down on this page instead of leaving it unsaid.
Known limitations
We would rather tell you than have you find out. As of the date above, we know about the following:
Third-party embeds
Pop-ups and interactive product demos load from third-party services whose code we do not write. Their keyboard and screen reader behaviour can change without warning, and the fix is not always ours to make.
Embedded video players
Our own video is captioned and audio-described. Where a blog post embeds a video through a third-party player, the player's controls are not our code. If you need a transcript or a described version of anything on this site, ask us and we will send you one.
Content published continuously
Blog posts and success stories go up often. Despite our review step, a missing image description or a heading out of order can slip through. Tell us and we will usually have it fixed within a few days.
If any part of this site blocks you, email us and we will get you the same information in a form that works for you: plain text, a transcript, or a conversation.
Report a barrier
If you run into something on binclusive.io you cannot use, we want to hear about it. The page address and what happened is enough. You do not need to describe it in technical terms.
Email: info@binclusive.io
We reply within five working days. If a fix will take longer than that, we will tell you when to expect it and give you another way to get what you came for in the meantime.
If you are not satisfied with our response
Write back and ask for the matter to be escalated to our management. Users in the European Union can also contact the national authority responsible for enforcing the European Accessibility Act in their country.
How this site was evaluated
This statement is based on a self-evaluation by Binclusive, combining three methods: manual testing by disabled testers on our team, our own scanner run over this codebase, and our own agentic audits run against this site. We review this statement at least once a year, and after any significant change to the site.