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) and Android
(Jetpack Compose and XML layouts) against Apple’s and Google’s platform accessibility guidelines.
Games and other surfaces — source scans of Unity scenes.
Manual audits — outcome-based journeys run through a real browser and a real screen reader,
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.
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.
Content StudioAudio description and captions for video, PDF accessibility remediation, and bulk image alt text — with organizations, credits, and an API.
More coming
Widget, Audit, and the API get their own sections here as their docs land.