Legal
Accessibility Statement
This document is provided as-is and is not legal advice. Consult counsel before relying on it.
Last updated 2026-08-24. Pocket-CFO describes its accessibility commitments, standards, known limitations, and feedback process.
Our Commitment
Pocket-CFO aims to conform to WCAG 2.2 Level AA across web, iOS, and Android, and we are actively remediating known gaps. This is a goal we work toward, not a guarantee — we do not represent that every part of the service currently meets that standard, and we do not claim certification or full conformance. We target the latest stable versions of Safari, Chrome, and Firefox, and we aim to support assistive technologies including VoiceOver (macOS and iOS) and NVDA (Windows). We are still formalizing a documented pre-release accessibility review; rather than overstate our process, we describe our current methods and their limits below.
Standards and Methods
We use WCAG 2.2 Level AA, Title III of the Americans with Disabilities Act, Section 508 of the Rehabilitation Act, and EN 301 549 (the European accessibility standard) as reference points for our work, without asserting certification or compliance with any of them. Accessibility requirements vary by jurisdiction, and not every standard referenced here applies to every user or market. Our accessibility checks combine automated and manual methods: every release build runs an automated axe-core scan over our public pages as part of the build pipeline, together with accessibility linting of our templates — these catch structural issues such as missing labels, names, and ARIA misuse, but not visual properties like color contrast, which automation cannot judge reliably — and we perform manual keyboard-only navigation and screen-reader passes over the areas we change. Barriers that are reported to us, or that we find ourselves, are triaged on a rolling basis, and we prioritize those that block access to information or the completion of a task.
Known Limitations
Some parts of the service are harder for us to fully control. Third-party embedded content — including the Paddle checkout iframe and any analytics or session-replay tooling we use when enabled — follows the accessibility practices of that third party rather than ours. Complex financial data tables and charts may need an accessible text alternative; we provide summary figures in adjacent text where practical, but coverage is not yet complete everywhere. Exported report output, including the dashboard's PDF export action, may not fully match the accessibility of the in-app experience. Some date-picker controls also inherit Ionic framework defaults that may have minor focus-order inconsistencies. We track these items in our backlog, address them on a rolling basis, and will update this statement as they are resolved.
Report an Issue
If you encounter an accessibility barrier or need content in an alternative format, contact us at accessibility@rippre.com; we aim to acknowledge your message within 5 business days. If a barrier prevents you from accessing information or completing a transaction, we will provide that information or transaction through an accessible alternative means — for example by phone or email — while we work to fix the underlying barrier. This statement is reviewed periodically and was last reviewed on 2026-08-24.
