Accessibility

Instaloops is a place people meet, learn and work, and that only holds if everyone can get in. Hubmind LLC is committed to making the Service usable by people with disabilities — including people who use screen readers, magnification, speech input, switch devices, or a keyboard alone.

We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA. We treat WCAG 2.2 AA as the bar for new work and as the yardstick when we revisit older screens.

In practice that means we build for:

• full keyboard operation, with a focus indicator you can always see and no keyboard traps;
• semantic structure — real headings, landmarks, lists and labelled form fields — so assistive technology can navigate the page;
• text alternatives for meaningful images, and decorative images marked as decorative;
• colour contrast that meets AA for text and interface components, and never colour alone to carry meaning;
• layouts that reflow to 320 px and survive 200% zoom without loss of content;
• touch targets large enough to hit reliably, and status messages announced to assistive technology;
• respect for the prefers-reduced-motion setting, so animation is reduced when you ask your device for less of it.

Instaloops is partially conformant with WCAG 2.2 AA: most of the Service meets the standard, and some parts do not yet. We are honest about the gaps rather than claiming a clean bill of health.

Known areas we are still working on:

• some rich-media and live-session screens have incomplete keyboard and screen-reader support;
• a few older screens carry heading structures and contrast values that predate this standard;
• captions and transcripts depend on what a creator uploads, so coverage varies by community.

Much of what you see on Instaloops is created by community owners and members — their posts, uploads, videos and embedded tools. We give creators the means to make that content accessible, including alt text and caption support, but we cannot guarantee material we did not author. If you hit an accessibility barrier in a specific community, tell us and we will work with its owner.

We test with current versions of Chrome, Safari, Firefox and Edge, paired with VoiceOver on macOS and iOS, NVDA on Windows, and TalkBack on Android. We also run automated checks in development and review new interfaces by keyboard before they ship. Automated tools catch only part of the picture, so manual review is part of the process.

If any part of Instaloops is hard or impossible to use, we want to hear about it — that feedback is how this list gets shorter. Write to [email protected] with “Accessibility” in the subject line, and if you can, include:

• the page or feature, and its web address;
• what you were trying to do and what happened instead;
• your browser, operating system and any assistive technology you use.

We aim to acknowledge accessibility reports within 2 business days and to give you a plan or a fix within 10 business days. If a fix will take longer, we will tell you why and offer a way to get what you need in the meantime.

While we fix a barrier, we will help you get the same result another way — walking you through a task, providing content in a different format, or completing an action on your behalf with your permission. Ask at [email protected].

We review this statement when the Service changes materially, and at least once a year. The effective date at the top of the page reflects the last review.