Accessibility statement
Accessibility at Ripple
Ripple should work for as many people as possible.
Last updated
We are building Ripple with accessibility in mind from the beginning. Our goal is to meet the Web Content Accessibility Guidelines version 2.2 at Level AA.
This is a goal, not a claim of certified conformance. Ripple has not yet had an independent accessibility audit or comprehensive testing with people who use a wide range of assistive technologies.
What we are working toward
We aim to make Ripple:
- perceivable, so important information is available in more than one visual form;
- operable with a keyboard as well as a pointer or touchscreen;
- understandable on a first visit, with plain language and predictable actions; and
- robust enough to work with current browsers and assistive technologies.
What we have designed for
Ripple currently includes:
- semantic headings, landmarks, labels and link text;
- a skip link to move past repeated navigation;
- visible keyboard focus;
- keyboard access to interactive controls;
- touch targets designed to be at least 44 by 44 pixels;
- text and interface contrast designed toward WCAG AA requirements;
- status labels that do not rely on colour alone;
- responsive layouts that reflow for narrow screens and enlarged text;
- clear validation and status messages;
- reduced-motion behaviour that removes or simplifies non-essential animation;
- still, complete content when reduced motion is requested; and
- written information alongside important charts and network graphics.
Blue, coral and neutral colours carry meaning in Ripple’s design, but colour should never be the only way a state or action is communicated.
Animation and motion
Ripple uses restrained animation to help explain movement, progress and connection.
Most animation runs once or responds directly to scrolling or interaction. Ripple does not currently use autoplaying video.
If your device or browser requests reduced motion, animated scenes should appear in a complete, still state. Core information and actions should remain available without depending on an animation.
Charts and the Ripple Tree
The Goal page contains charts and visual progress indicators. Their important totals, labels and explanations should also be available as text.
The private Ripple Tree is an interactive picture of confirmed connections. Direct connections are also presented in a written list. The visualisation supports pointer and keyboard interaction, but it has not yet been tested with every screen-reader and browser combination.
If either experience prevents you from finding information or completing an action, email hello@rippleau.com. We can provide the relevant information in a simpler format.
Known limitations
Ripple is still in its first version. At this stage:
- it has not had an independent accessibility audit;
- it has not been comprehensively tested by people with disabilities;
- testing across screen readers, voice-control tools, magnification software, browsers and operating systems is not yet complete;
- complex animated or interactive visualisations may be less usable in some assistive-technology combinations; and
- very old browsers may not provide the same experience as current browsers.
These limitations are not intended to excuse barriers. We want to know when something does not work so we can prioritise the right improvements.
Compatibility and technology
Ripple is designed for current versions of commonly used browsers on desktop and mobile devices.
The service uses HTML, CSS and JavaScript. Some visualisations use SVG or canvas. JavaScript is needed for parts of the signed-in experience and for some interactive visualisations.
We use standard browser controls and semantic HTML wherever practical, adding accessible names and states when custom interaction is necessary.
How we assess accessibility
Our current assessment is an internal self-evaluation. It includes:
- automated browser checks for keyboard focus, responsive layouts, reduced motion and important workflows;
- keyboard testing;
- responsive testing at desktop and mobile sizes;
- focus, validation and loading-state checks;
- reduced-motion checks; and
- browser-based journey tests for important workflows.
Automated tests cannot establish that a service is accessible by themselves. Independent review and testing with disabled users remain future work.
Tell us about a barrier
If something in Ripple is difficult or impossible for you to use, email: hello@rippleau.com
It helps if you tell us:
- the page or action you were using;
- what you expected to happen;
- what got in the way;
- your browser and device, if you know them;
- any assistive technology you were using; and
- the format or adjustment that would help.
Only include information you are comfortable sharing. Do not send passwords, sign-in links, confirmation links or unnecessary sensitive information.
We will acknowledge your message, investigate the issue and work with you on an accessible alternative where reasonably possible.
You can also ask for information from Ripple in another accessible format.
If your concern is not resolved
We would like the opportunity to address an accessibility concern directly.
You can also learn about disability discrimination and making a complaint through the Australian Human Rights Commission: humanrights.gov.au/complaints
Seeking information or making a complaint will not affect your ability to use Ripple.
Ongoing improvement
Accessibility is ongoing work. We will review this statement as Ripple changes, record known limitations honestly and update the “Last updated” date when the statement materially changes.