Accessibility

Accessibility at Roll Call

Roll Call aims to meet WCAG 2.2 level AA. That target is stated on our Ring Appstore listing, so this page records what we actually do about it and where we know we fall short.

What is built in

Every page is ordinary HTML that works without JavaScript, including sign-in, so the service stays usable in a screen reader or a restricted in-app browser. Every form control has a real label. Keyboard focus is always visible. A skip link comes before the header on every page.

Nothing in the product relies on colour alone to carry meaning. A missed visit is marked by its word and its shape as well as its colour, so the four verdicts stay distinguishable in greyscale and on a printed page. The monthly service record is built to print in black and white for the same reason.

What we check automatically

Every page the product serves is checked on every build for the structure a screen reader navigates by: one first-level heading, no skipped heading levels, a skip link that comes first and actually lands, a single main landmark, a real label on every field, a name on every link and button, headers with scope on every data table, and nothing jumping the keyboard order. A page added without being checked fails the build rather than slipping through.

Colour contrast is computed from the palette itself, not judged by eye. Every text and boundary pairing in use meets WCAG 2.2 AA, and no colour is redefined at any screen width, so a ratio measured once holds at every viewport. That audit found and fixed three real failures: form field edges and button outlines shared a token with decorative hairlines and sat at 1.21:1 against the page, and the marking for an unverified visit sat at 2.82:1.

What we know is not done

Nobody has yet driven the visit log or the printable record with VoiceOver or NVDA from start to finish. The automatic checks above cover the structure those tools rely on, but they cannot tell us whether the result is pleasant to listen to, whether our wording makes sense read aloud, or whether the order things are announced in matches how the page is meant to be read. We would rather say that than imply a machine check settles it.

Telling us about a problem

Write to support@rollcall.homes and say which page and what happened. An accessibility problem is treated as a bug, not a feature request.

See also Privacy, Terms and Support.