Accessibility infrastructure for web, mobile, and media — find, fix, and gate a11y issues across your stack, and produce the described video, tagged PDFs, and alt text that go with it.
Accessibility is not one surface and not one method, so the platform is not either.
Web — source scans of JSX/TSX, Astro, and Liquid, plus live-DOM scans that drive a real
browser against rendered pages, crawls, and Storybook stories.
Mobile — source scans of iOS (SwiftUI, UIKit, Interface Builder), Android
(Jetpack Compose and XML layouts) and React Native against Apple’s and Google’s platform accessibility guidelines,
plus audits that drive the real TalkBack on an Android device or emulator and the real VoiceOver
on an iOS Simulator.
Games and other surfaces — source scans of Unity scenes.
Manual audits — outcome-based journeys run with a real screen reader, through a browser for
web projects, on an Android device with TalkBack for Android apps, or on an iOS Simulator with
VoiceOver for iOS apps, answering whether a person can finish the task rather than whether the
markup parses clean.
Content — the accessibility work that is not code: audio description and captions for video,
tagged and remediated PDFs, and alt text for images.
Products
Documentation is organized by product. Pick the one you’re working with.
CLIb8e — scan web and mobile source for accessibility findings, run screen-reader audits, fix what they find, and gate regressions in CI, all from your terminal.
MCPConnect Claude Code, Cursor, or any MCP client to your Binclusive data — projects, pages, journeys, audits, and tickets — and let your coding agent read and file accessibility work.
AuditsCloud audits that drive a real screen reader through your journeys — and what to do when a run can't reach your site.
Content StudioAudio description and captions for video, PDF accessibility remediation, and bulk image alt text — with organizations, credits, and an API.
More coming
Widget and the API get their own sections here as their docs land.
About the CLI docs
The CLI docs follow the Diátaxis framework — four quadrants, each answering
a different question.
Tutorials — learning-oriented lessons. Start here to run your first scan end to end.
How-to Guides — task-oriented recipes for scanning locally, gating a pull request, and more.
Reference — the precise b8e command surface, exit codes, environment, and output formats.
Explanation — the concepts behind the CLI: the scanning model, component-to-host resolution, and blast-radius ranking.
About the MCP docs
Same four quadrants, for the hosted MCP server at mcp.binclusive.io.
Tutorials — connect an agent and work a real ticket end to end.
How-to Guides — connect a client, run a cloud audit, file a finding from an agent.
Reference — every tool, the HTTP endpoints, and the shared vocabularies.
Explanation — what the server serves, how authentication works, and why audits are asynchronous.
About the Audits docs
Cloud audits run your journeys with a real screen reader, in a browser Binclusive hosts.
How-to Guides — let the audit runner through your firewall or WAF.
About the Content Studio docs
Same four quadrants, for producing accessible media.
Tutorials — create an account, describe your first video, remediate your first PDF.
How-to Guides — generate audio descriptions, refine captions, fix PDF issues, bulk alt text.