Building LenGrowth so more people can use it with confidence.
Last updated: May 15, 2026
Accessibility is part of how we think about useful software. LenGrowth is still growing, and our commitment is to improve the public website and the product deliberately, honestly, and in conversation with the people who use it.
Our intention
We want people with different bodies, devices, assistive technologies, and working conditions to be able to understand LenGrowth, navigate it, and complete important workflows.
Our accessibility goals
Our goal is to make LenGrowth easier to perceive, navigate, understand, and operate. That applies to our public pages, authentication flows, dashboards, company workspaces, task surfaces, reports, and collaboration features.
We are working toward practical alignment with the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA. We treat that standard as a baseline for product decisions, not as a one-time checkbox.
LenGrowth platform
LenGrowth helps teams manage growth work across strategy, tasks, assets, integrations, reporting, and specialist collaboration. Because those workflows can be dense, accessibility work on the platform focuses first on core paths people need to complete their work.
- Clear keyboard paths through navigation, forms, dialogs, task actions, and settings.
- Visible focus states and interface states that do not rely on color alone.
- Readable labels, headings, helper text, validation messages, and status messages.
- Screen reader-friendly structure for dynamic product areas where content changes after user actions.
- Support for browser zoom, responsive layouts, dark mode, and contrast-sensitive UI decisions.
We know this work is ongoing. New product surfaces should carry accessibility expectations from design through implementation, review, and testing.
Public website
The public LenGrowth website is available without an account. We aim for visitors to learn what LenGrowth does, compare options, read legal and trust information, and contact us without avoidable barriers.
Keyboard access
We aim for menus, links, buttons, forms, dialogs, and account actions to be reachable and usable from the keyboard.
Readable structure
We use headings, labels, descriptive link text, and page structure that help people scan content visually or with assistive technology.
Visual clarity
We design for clear focus states, sufficient contrast, resizable text, reduced ambiguity, and dark interfaces that still preserve legibility.
Responsive experiences
We check core public pages and product workflows across viewport sizes so navigation and content remain usable on small screens.
Standards and testing
We use modern web standards and React/Next.js patterns to support semantic markup, responsive layouts, and accessible interaction states. Our intended accessibility coverage includes keyboard navigation, screen reader compatibility, focus visibility, alternative text for meaningful images, descriptive links, sufficient contrast, and form labels and errors that can be understood by assistive technology.
As LenGrowth changes, we will continue improving our review process so accessibility issues are caught earlier and corrected with the same seriousness as usability, security, and reliability issues.
Contact us
If you encounter an accessibility barrier on LenGrowth, please tell us what happened, the page or workflow involved, and the assistive technology, browser, or device you were using if you are comfortable sharing it.