Accessibility

Built to be usable by everyone.

Financial planning shouldn't be gated behind a screen you can't navigate. We build planbend to be operable with a keyboard, readable with a screen reader, and legible at any zoom — and we treat accessibility as part of finishing a feature, not a later cleanup.

This statement reflects current practices and is updated as the product evolves. Last updated: June 2026.

Our target

We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA across the planbend marketing site and application. WCAG 2.1 AA is the standard most widely referenced by accessibility law and the benchmark we hold new work to.

What we've built in

Keyboard operability. Interactive controls are reachable and operable with a keyboard alone, and a visible focus ring (a high-contrast outline) shows where you are as you move through the page.
Labeled controls. Form fields, buttons, and inputs carry programmatic labels so screen readers announce what each control does, not just that it exists.
Charts have text alternatives. Every chart in the app is paired with a data table that is always present for screen readers, plus a "show data table" toggle for sighted users — so the numbers behind a projection are never locked inside an image.
Readable contrast. Body text is designed to meet the 4.5:1 contrast ratio AA requires against our dark background.
Zoom and reflow. Pages allow pinch-zoom and browser zoom — we do not lock scale — so you can enlarge text without breaking the layout.
Reduced motion. We respect the operating-system "reduce motion" preference and limit non-essential animation for users who ask for it.
Skip links and structure. Pages provide a "skip to content" link and use headings and landmarks so assistive technology can navigate the structure quickly.

Where we're still improving

Accessibility is ongoing, not a finished checkbox. planbend is a large, evolving application, and some areas are stronger than others. We are continually testing with keyboard and screen-reader workflows and fixing barriers as we find them. If you hit something that doesn't work for you, telling us is the fastest way to get it fixed — see below.

Reporting a barrier

If any part of planbend is difficult or impossible to use with assistive technology, please email hello@planbend.com with the page or feature, what you were trying to do, and the assistive technology or settings you use. We take these reports seriously and will work with you toward a fix or an accessible alternative.

A note on third-party content

Some parts of the experience — such as the payment form — are provided by third parties (for example, Stripe's checkout). We choose providers that take accessibility seriously, but their interfaces are outside our direct control. If you encounter a barrier in a third-party component, let us know and we'll help you complete the task another way.