Kindness should be easy for everyone to share.

What works

• Everything in the member app, the console for Circle organisers and this site can be used with a keyboard alone, and every stop shows a focus ring.
• Text, focus rings and the edges of fields meet the WCAG AA contrast ratios in both the light and the dark theme, and tests hold them there on every change.
• Pages reflow to 320 pixels wide without scrolling sideways, and text can be zoomed to 200%.
• Menus, dialogs and sheets take focus when they open, close with Escape, and give focus back. Every sheet has a Close button.
• Form errors say what went wrong, are announced, and leave you where you can fix them.
• The ripple animation stops by itself within five seconds, and nothing moves if your device asks for reduced motion.
• The Ripple Map has a list of its places as well as the map, and every place on it is a named button.
• There is no sound or video, and nothing depends on colour alone.

What is not right yet

RippleCore partly meets WCAG 2.1 AA. These are the problems we know about, and what we are doing about each one.

• Photos members attach to a moment are announced as "Photo 1 of 2" and so on: there is not yet a way for a member to describe what a photo shows.

  We will decide how members can add a description by the end of December 2026.

• With extra letter and line spacing turned on, some single-line names are cut short sooner. The full name is on the page each one links to.

  To be fixed by the end of January 2027.

• Inside a date field, the focus ring is the browser’s own rather than the field’s.

  To be fixed by mid-December 2026.

• RippleCore has not yet been tested with a screen reader in use. Its markup and automated checks are built for one, but we have not confirmed it with VoiceOver or NVDA.

  A session with both is planned by the end of January 2027.

Tell us about a problem

If something stops you or gets in your way, email jk@ripplecore.co. It helps to say which page, what you were trying to do, and the device and any assistive technology you use. We reply within 10 working days with what we will do and by when, and if you could not finish something, we tell you another way to do it in the meantime.

How we checked

On 23 October 2026 we ran the automated WCAG 2.1 A and AA rules on 66 screens in both themes, walked every one with a keyboard, opened all 88 menus, dialogs and sheets, and checked every screen at 320 pixels wide. Contrast is held by tests that run on every change. We check again before each major release and at least once a year. This was our own assessment: RippleCore has not yet been audited by a third party.

Universities can ask for our Accessibility Conformance Report (VPAT 2.5, WCAG edition) at the same address.