For everyone

Accessibility

Last reviewed August 18, 2026 · Maison Mason LLC d/b/a AroundBack

An app whose premise is that everyone deserves closeness without exposure had better be usable by everyone. We want aroundbackapp.com and the AroundBack app to work for people using screen readers, keyboard navigation, magnification, reduced motion, and every other way people actually use their devices.

Our standard

We aim for conformance with the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA on this website, and we build the iOS app against Apple's accessibility frameworks — VoiceOver labels on interactive elements, Dynamic Type, and system reduced-motion and contrast settings. We have not yet commissioned a formal third-party audit; this statement describes what we've done ourselves, honestly, and will be updated as that changes.

What this site does

  • Semantic HTML with a logical heading structure, landmark navigation, and descriptive link text. Every page opens with a skip link so a keyboard user can jump past the navigation straight to the content.
  • Text alternatives on meaningful images, including the app screenshots; decorative graphics are hidden from assistive technology.
  • Color contrast measured rather than assumed: every text colour on the page against the colour actually behind it, and every control's border against its surroundings. The one place it fell short was the form on the sponsorship page, where the field borders sat at 1.5:1 against a required 3:1, so a separate control-boundary colour was added to reach it. Information is never conveyed by color alone.
  • Full keyboard operability with visible focus states; no keyboard traps; no time limits.
  • Motion respects you: all entrance animations, ambient background movement, and hover effects are disabled when your system requests reduced motion, and the home page carries a Pause motion control that stops its looping animation. Every page reads completely with JavaScript off; the two forms need it, and without it they stay switched off rather than send anything.
  • Responsive layout that supports 200% zoom and text scaling without horizontal scrolling; no autoplaying media, no flashing content.

What the app does

The website is the smaller half of the job. Here's where the app stands, including the parts that aren't finished:

  • VoiceOver. Labels, traits, and values are written throughout the app — the tab bar, the grid, chat, and the safety controls. Each profile tile on the grid reads as a single element rather than a scatter of fragments: name, age, distance band, presence, what the person is looking for, and any status, in one pass.
  • Distance is never precise, so it can't be announced precisely. On the grid the app never receives another member's coordinates or exact distance, so VoiceOver reads exactly what the screen shows: a band like "Nearby," "Same neighborhood," or "1 to 3 mi." On the Now map, a Now posted where few people are nearby appears as a marker within an area about 1 km across, never at the poster's own position.
  • Reduce Motion changes behavior, not just duration. The launch animation never starts, the Now map's zone pulse rests still, typing dots stop cycling, the loading shimmer doesn't sweep, and a mutual match becomes a quiet cross-fade instead of a burst of particles (the haptic still fires).
  • Status is carried by shape, not only color. Verification, intent, distance band, matches, sparks, and saved profiles each have their own symbol that is always drawn, with color as a second signal — and VoiceOver speaks each state in words.
  • Dynamic Type is only partly done. Most text uses scaling text styles, and scaled metrics keep icons sized to the text around them. But on the grid's profile tiles only the name and age scale, and only up to 35 percent larger; the distance and status chips and the badges stay a fixed size. Our latest audit at the larger text sizes, in September 2026, found that layouts start to lose their balance at the largest standard size and that many screens stop working at the accessibility sizes: button labels break mid-word or wrap one letter per line, labels truncate, and on a small phone some controls fall off the first screen.
  • What we haven't done. A handful of icon-only buttons still announce as their symbol name, photos on the profile screen carry no descriptive text, and we have not yet run a VoiceOver traversal on a physical device — the annotations above are written and reviewed, not yet heard end to end. We also don't currently read iOS's "Differentiate Without Color" setting, because the symbols are drawn either way.

Known limitations on this site

  • The five product screenshots are images of the app's interface; their alt text summarizes each screen but cannot convey every on-screen detail. The surrounding text carries the substance.
  • Our legal documents are long; we've added in-page headings and anchors, but we know length itself is a burden and provide summaries where we can (each policy leads with a short version).
  • The site has not yet had a formal external audit. We have measured contrast, checked that every control has a real name, that every error message is tied to the field it describes, that focus is always visible, and that nothing overflows sideways at 200% zoom. What we have not done is listen to it. Systematic testing with VoiceOver and other screen readers is still ahead of us, and this page will say so when it is done rather than before.

Tell us what's broken

If any part of this site or the app is hard to use with your assistive technology, that's a bug — report it like one: support@aroundbackapp.com with "Accessibility" in the subject. We read these with the same priority as security reports, and you don't need an account to write to us.