Accessibility

Ringfully targets WCAG 2.2 Level AA across this website, the browser softphone, the administrator console and the Windows desktop application. That is the standard referenced by accessibility law in Canada and the United States, and the one we measure against.

A phone system is a communications tool, so this is not decoration. Someone who cannot use a mouse, or who reads with a screen reader, or who needs a much larger interface, has to be able to answer a call.

On this website:

1. a skip link to the main content, and proper landmarks on every page;
2. one heading structure per page with no skipped levels, checked by an automated test;
3. a visible focus outline on every link and button — restored specifically for the public pages, because the signed-in product suppresses it on inputs;
4. text colours whose contrast ratios are computed rather than assumed, with a test that recalculates them on every build and fails below 4.5:1;
5. full respect for a reduced-motion preference, handled in two independent places so a failure in one cannot leave content invisible;
6. no images at all — the illustrations are text and vector shapes with proper labels — so there is no missing alternative text;
7. content that renders fully with JavaScript disabled; and
8. no horizontal scrolling at a 390-pixel width, tested per page.

These are enforced by a test suite rather than a checklist, which is the difference between an accessibility statement and an accessibility claim.

Being specific, because a statement claiming full conformance would not be true:

1. The product has not been audited independently. The public site is tested automatically; the signed-in softphone and console are not held to the same standard yet.
2. The call-flow builder is a drag-and-drop canvas. Building a flow by dragging blocks is not currently operable by keyboard alone. This is the largest known gap and the hardest to fix.
3. Some newer WCAG 2.2 criteria have not been verified across the product — in particular minimum target sizes and focus visibility where content overlaps.
4. No screen-reader testing report exists. We have not published results against specific assistive technologies, so we do not claim compatibility with any.
5. No VPAT or accessibility conformance report. If your procurement needs one, tell us and we will say honestly how long it would take.

If any part of Ringfully is difficult or impossible for you to use, write to us and we will answer. Contact [TBD] — or [TBD], or by post to [TBD], in whichever way is easiest for you. You do not have to use a particular format, name a standard, or explain the technology.

Tell us what you were trying to do and what stopped you. We will:

1. acknowledge within five business days;
2. tell you what we found and whether we can fix it, within thirty days;
3. offer another way to do the thing while a fix is outstanding; and
4. record it, so a barrier reported once is not reported into a void.

Feedback may be given anonymously, and we will publish nothing that identifies you.

Tell us and we will do it with you or for you. Setting up a call flow, configuring hours, adding agents and changing routing can all be done by us on request rather than through the interface. That is not a substitute for fixing the interface, and we are not treating it as one — but nobody should be blocked from using their phone system while we do.

Accessibility enquiries, feedback and complaints: [TBD], addressed to [TBD], [TBD], [TBD]. Our security page and privacy policy take the same approach of naming what is missing rather than only what is present.