> For the complete documentation index, see [llms.txt](https://docs.blacksky.community/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.blacksky.community/blacksky-community-guidelines/blacksky-accessibility-statement.md). # Blacksky Accessibility Statement Effective Date: October 2026 Blacksky Algorithms is building the future of self-governable online communities with tools that make complex infrastructure simple to deploy. Most social platforms control what users see, how communities operate, and who gets to feel safe online. Blacksky changes that by providing one-click infrastructure for independent, self-governed digital spaces. Our platform lets communities create safe spaces on their terms, pool resources democratically, and govern collectively—without needing technical expertise to deploy algorithms, moderation tools, or data servers. Accessibility is something we work on continuously rather than something we consider finished. This document describes how we approach that work and where we currently stand. *** #### 1. How we think about it Accessibility barriers are bugs. When something doesn’t work with a screen reader, a keyboard, magnification, or voice control, that is an issue with our product, not a limitation of the person using it. We fix those the way we fix anything else. At Blacksky Algorithms, we value self-governance and including the community within our designs. Our Head of Community also serves as our disability advisor to ensure that we work closely with organizations and scholars to ensure that Blacksky is aware of what accessibility online looks like. *** #### 2. What we’re doing * We are committed to doing QA for features and are working towards ensuring that our app becomes more accessible with each update. * We involve disabled community members in design and testing, and we pay them for their time. * Reported barriers are escalated through our Head of Community, who works closely with our Head of Product to address this need within the design. *** #### 3. Some things we build for specifically * Alternative text on images, with support for authors adding it. * Moderation labels and content warnings exposed as text, so they’re announced by screen readers rather than communicated by color or icon alone. * Respect for the operating system’s reduced-motion setting. * Text that stays readable and functional when zoomed or reflowed. *** #### 4. What we are still working on * We're building toward other compliance steps, including audits. * Content on the network isn’t all ours. Blacksky operates in a federated ecosystem. Posts, images, and video come from people across the AT Protocol, and much of it lacks alt text or captions. We prompt authors to add alt text on our web and mobile apps, and we surface when it’s missing, but we can’t retroactively describe other people’s images. \ Third-party clients are outside our control. Blacksky feeds and our moderation labels can be displayed in apps we don’t build. How accessible those apps are is up to them. *** If you run into a barrier, we want to know. Email us at . It helps if you can tell us the screen or page, what you were trying to do, and what device and assistive technology you’re using. Screenshots or a recording are useful but not necessary. We read every report. If you need something from us in a different format, ask, and we’ll get it to you.