Languages

We want Cleave CRM to be usable by as many people as possible, including users with disabilities. While we’re still early in our product journey, accessibility is on our roadmap from the start—not an afterthought. Here’s our current approach: • Design with accessibility in mind – We’re standardizing on clear typography, strong color contrast, and consistent layouts. – Interactive elements (buttons, links, forms) are being designed to be obvious and easy to use. • Keyboard and screen reader compatibility – Our goal is for all core workflows to be usable with a keyboard, without relying on a mouse. – We’re working toward better support for screen readers by using semantic HTML, ARIA labels where appropriate, and predictable focus states. • Target standards – As the product matures, we are aiming to align with widely recognized web accessibility guidelines (such as WCAG 2.1 AA) and best practices followed by ADA-conscious SaaS products. – This will be an ongoing effort, not a one-time checkbox. • Continuous improvement – Accessibility work will continue alongside new features, visual refinements, and performance improvements. – When we find issues, we’ll log them, prioritize them, and address them as part of our regular development process. If accessibility is critical for your team, we want to hear from you. Please share your needs and any specific barriers you encounter through our feedback board so we can prioritize changes that make Cleave CRM more inclusive and usable for everyone.

At launch, Cleave CRM will focus primarily on the U.S. and English-speaking markets. Our first priority is to make sure the core product is fast, stable, and genuinely useful for the businesses that rely on it every day. That said, we know many of our users work with teams and clients who speak other languages—and we absolutely have that in mind as we build. Our current plan is: • Launch: – Full support for U.S. English throughout the app and documentation. • Within the first year after launch: – Add Spanish language support for the Cleave CRM interface. – Begin updating key help articles and resources for Spanish-speaking users. As we get closer, we’ll share more specifics around timelines and which parts of the product are included in each language phase. If language support and a particular language is important for your team, we’d love to hear from you. Use our public feedback board to share your needs and help us prioritize future language expansions in a way that best supports you and your customers.