Accessibility
Blink is meant to work for the whole room — including the people in it who use a screen reader, who navigate by keyboard, who need larger text, or who can't tolerate motion. This page says where we are, honestly, and how to reach a person if something blocks you.
On the website and web app at joinblink.me we aim to meet WCAG 2.2 Level AA, the current version of the Web Content Accessibility Guidelines. That goes beyond WCAG 2.1 Level AA, the version the U.S. Department of Justice adopted for public bodies in 2024, which is the benchmark usually applied under the Americans with Disabilities Act.
In the iPhone and Android apps, and the Apple Watch app if you use it, we aim to follow each platform’s accessibility guidance: labels for VoiceOver and TalkBack, text that follows your Dynamic Type or font-size setting, animation that respects Reduce Motion, and colour contrast that meets the same AA levels as the web.
We are not claiming we fully meet any of this. No independent auditor has reviewed Blink, and no screen-reader user has tested it under controlled conditions. Saying otherwise would be easy and untrue. What follows is what we have actually built and checked, and what we know is still missing.
Everything at joinblink.me — the site, the host dashboard, the guest join flow, the camera, and the album where the night arrives — and the Blink apps: the iPhone app with its App Clip, widgets and Live Activities, the Android app, and the Apple Watch app if you use it.
On the website: tap targets on guest screens are at least 44 × 44 pixels. Text and controls were measured against the backgrounds they actually sit on rather than assumed — several hints and labels that were too faint to read have been corrected. If your device asks for reduced motion, the landing page honours it: nothing pins, nothing scrubs, and the page reads straight down as ordinary sections. Interactive elements show a visible focus ring for keyboard navigation, headings and landmarks are marked up semantically, and forms surface errors in text rather than disabling a button with no explanation.
In the apps: buttons and controls on the main screens carry spoken labels for VoiceOver and TalkBack, screen titles are marked as headings, and a tab with a dot says what the dot means. The apps make no sounds by design; what a sound would tell you is said instead. On iPhone, VoiceOver announces each photo taken and how many are left, when the roll is finished and when the photos are revealed, along with errors and confirmations; on Android, TalkBack hears status changes as they happen.
Text grows with your system text size, and buttons grow with it rather than cutting their labels off; the largest headings stop growing at a set size. In the dark night look, the main button, the create button and the tab dot meet 3:1 contrast against their background, and text on them meets 4.5:1. With Reduce Motion on, sheets and counters cross-fade instead of sliding or springing. The reveal is a press-and-hold gesture with a moving progress bar; with Reduce Motion or a screen reader on, it becomes a plain Reveal button that does the same thing. On Apple Watch, the shutter announces its result (“Saved on iPhone”).
A guest needs no password — which removes a category of barrier before anything else has to work.
Taking the photo is visual. Blink’s core action is framing a picture, and there is no meaningful screen-reader equivalent for composing a shot. We won’t pretend to solve that with a label.
But receiving the night does not depend on it. Every guest gets the whole roll — in the app, by link, and by email if they asked for it — without taking a single photo. You can view it, download it, and ask for any photo of you to be removed. If someone at the party can’t use a camera, they still get everything the camera produced.
The camera and the reveal move. While a video clip records, a ring fills around the shutter to show the time left. That ring keeps moving under Reduce Motion, because it is the only clock for the clip. The reveal’s hold-to-reveal animation is replaced by a button only when Reduce Motion or a screen reader is on.
Some camera text doesn’t grow. The photo counter and a few labels over the viewfinder stay a fixed size so they don’t cover the picture, so they don’t follow larger text settings.
Silent means no sound cues. The shutter, the last photo and the reveal are felt as vibrations and, on iPhone, spoken by VoiceOver, but there is no sound for someone who would rely on one rather than on a vibration or a screen reader.
Less tested: the App Clip, the widgets and the Apple Watch app are newer and have had less accessibility checking than the main app, and TalkBack on Android has had less than VoiceOver; the spoken photo count is made for VoiceOver and is not yet read out the same way by TalkBack. On the website, some secondary labels are set in small uppercase type that is harder to read than it should be; that is under review. Our background video carries no captions because it has no audio — a text description is provided in its place.
This is the part of the page that actually matters. If any part of Blink is unusable for you, email support@joinblink.me with “accessibility” in the subject, or write to Chariot Archive, Inc., 195 East Main Street, Columbus, Ohio 43215, USA. Tell us the page or screen, the device, what you were trying to do, and what got in the way — including the assistive technology you use, if you’re comfortable sharing it.
We reply within 5 business days, and we will tell you plainly whether we can fix it, when, or if we can’t. If the fastest route is a person doing it for you — pulling your photos, removing one, closing an account — we’ll just do that.
To have a photo of you taken down you don’t need this page or an account: report a photo works for anyone, including people who were never at the event.