last updated · 11 September 2026

Accessibility

What RollGuard does to be usable with iOS's accessibility features — and what we haven't done.

In the app

RollGuard is built with the standard iOS interface components, so it inherits the system's accessibility behaviour rather than reimplementing it. Specifically:

On this website

The site is plain HTML with no third-party scripts. Text scales with your browser's text-size setting, the film is click-to-play rather than autoplaying, and animation is suppressed when your browser reports a Reduce Motion preference.

What we haven't done

We have not carried out a formal accessibility audit, and we don't claim conformance to a particular standard or level. RollGuard is made by one person, and stating a conformance level we haven't independently tested against would be a claim we can't support. What's described above is what the app and site actually do; it isn't a certification, and it isn't exhaustive.

We also know of no way to make one part of the app fully accessible: reviewing a flagged photo means looking at the photo. VoiceOver will read the category, the reason and the masked fragment RollGuard stored, and the Keep, Hide and Delete controls are fully labelled — but the image itself is not described, because RollGuard never analyses image content beyond the checks it runs on your device.

Telling us about a problem

If something in RollGuard or on this site doesn't work with an accessibility feature you rely on, please email support@rollguard.app and say which feature and which screen. It goes to the person who wrote the app. We'll tell you honestly whether we can fix it and roughly when.