Our Accessibility Goal
Basis uses the Web Content Accessibility Guidelines (WCAG) 2.2 Level AA as its working accessibility target for public pages and product experiences. This is an ongoing product and engineering commitment, not a representation that every part of Basis is already fully conformant.
Current Status
Basis is an early-stage product. We have not completed a formal third-party accessibility audit or verification, and some areas may still need improvement. We review accessibility as part of product development and prioritize issues that affect core account, budgeting, planning, billing, privacy, and connected-account workflows.
Accessibility Practices
- Use semantic HTML and recognizable controls as the default approach.
- Keep keyboard access and visible focus states available for interactive controls.
- Provide text labels or accessible names for icon-only actions.
- Support reduced-motion preferences for custom interface animations.
- Review high-impact flows, including sign-in, settings, billing, account connection, budgeting, planning, and data controls.
Known Limitations
Basis includes interactive models, charts, dashboards, and financial visualizations. We are continuing to improve keyboard behavior, screen-reader summaries, chart alternatives, and contrast across these surfaces. Some externally hosted or embedded flows, such as Plaid account connection and Stripe checkout or billing portals, may also have accessibility characteristics controlled by those providers.
If a visualization or workflow is difficult to use, contact us and we will work to provide the information or help complete the task in an accessible way where reasonably feasible, even if full remediation takes longer.
Feedback and Assistance
If you experience an accessibility barrier or need help using Basis, contact us at accessibility@basis-financial.com.
Helpful details include the page or feature involved, the device and browser you are using, the assistive technology involved if any, and what you were trying to do. We aim to acknowledge accessibility messages within 5 business days and prioritize barriers that affect core product access.