Accessibility
PointBagel is a dense financial tool. It should still work if you drive it from the keyboard or read it with a screen reader. Below is what we build to, what works, what does not, and where to write when something is broken.
Last updated: August 2, 2026
The standard we build to
We build PointBagel to meet WCAG 2.1 Level AA. That is the target we design and test against. It is not a certificate, and we are not telling you every page already meets every criterion.
This statement covers pointbagel.com and the signed-in app. We have not commissioned an independent audit. We test with the keyboard and with screen readers as we build, and automated checks run on every change. Automated checks catch a minority of what matters, so we treat them as the floor. When we find something we cannot fix that week, it goes on the list below instead of going quiet.
What works today
- Skip to content
- Every page starts with a "Skip to main content" link, so you can jump past the navigation instead of tabbing through it on each new page.
- Keyboard operation
- Menus, dialogs, and the Application Calendar plan builder are all operable from the keyboard, including reordering cards without a mouse.
- Visible focus
- Whatever you have focused carries a visible outline, rather than being left to whatever the browser happens to draw.
- Screen reader support
- Form fields are labeled programmatically, validation errors are announced where they occur, and changes like a finished sync or a saved balance are read out through polite live regions. Pages declare their language and use real headings and landmarks.
- Tap target floor
- Our floor for interactive targets is 44 by 44 pixels, above the 24 pixel WCAG minimum. Small icon buttons get the larger hit area without the icon growing.
- Reduced motion
- If your system asks for reduced motion, our animations turn off rather than shrinking.
- Contrast checking
- Color pairs on our public pages are held to a 4.5:1 minimum, checked by an automated test rather than by eye. A pair that fails blocks the change from shipping.
- One light theme
- We ship a single light theme instead of a dark mode. One set of colors is one set of contrast values to verify, which we would rather do well than do twice.
What is not fixed yet
Known problems, written down here rather than left for you to discover:
- Our offer history chart is read through hover tooltips. Its data is not yet available to a screen reader or reachable by keyboard. A fix is in progress.
- Some wide comparison tables scroll sideways, and that scrolling cannot be done from the keyboard alone.
- The notifications menu in the signed-in header does not announce whether it is open or closed.
- A few small labels use fixed pixel sizes, so raising your browser default font size will not enlarge them. Page zoom works everywhere.
- In the signed-in app, some secondary text on tinted backgrounds sits just under our 4.5:1 contrast target.
That list is current as of the date at the top. If you hit something that is not on it, that is a bug and we want to hear about it.
No accessibility overlay
We do not run an overlay, a toolbar, or a widget that promises to fix the site once it loads. Those products tend to fight with the assistive technology you have already set up, and they leave the underlying pages exactly as broken as they were. We would rather fix the pages.
Tell us what broke
Email [email protected]. Tell us the page, what you were trying to do, and which browser and assistive technology you use. That detail is usually the difference between a fix this week and three rounds of questions first.
We aim to reply within five business days. Reports go to the person who writes the code, not into a queue nobody reads. If an accessibility problem is blocking you from something you pay for, say so, and we will find you another way to get it done while we fix the page.