Accessibility Statement
Last updated: 2026-07-12
Robic Rufarm India Private Limited is committed to making the CAMARON platform accessible to everyone. This statement outlines our accessibility standards, features, known limitations, and how to get help.
Audit status
Display Preferences
Persist on this device. Defaults follow your OS settings when supported.
Suppress non-essential animation.
Boost foreground / border contrast.
Our Commitment
Robic Rufarm India Private Limited is committed to ensuring that the CAMARON aquaculture intelligence platform is accessible to all users, regardless of ability or disability. Our conformance target is WCAG 2.2 AA — the Web Content Accessibility Guidelines, Level AA — which provide a framework for making web content more accessible to people with disabilities including visual, auditory, motor, and cognitive impairments. This is a target we measure continuously rather than a certification we claim. The audit status below states exactly what is measured, how often, and what is not yet covered.
Accessibility Features
CAMARON incorporates the following accessibility features: • Semantic HTML: We use proper heading hierarchies, landmarks (header, nav, main, footer), and ARIA attributes throughout the platform. • Keyboard Navigation: All interactive elements are accessible via keyboard. Our keyboard shortcuts panel (press "?" on any page) shows available shortcuts. • Screen Reader Support: ARIA labels on all interactive elements, live regions for dynamic content updates, and descriptive alt text on images. • Color & Contrast: Our design system uses high-contrast color tokens that meet WCAG AA contrast ratios in both light and dark modes. • Text Scaling: The platform supports browser-level text scaling up to 200% without loss of content or functionality. • RTL Support: Full right-to-left language support for Arabic, Urdu, Sindhi, and Kashmiri users. • Reduced Motion: Animations respect the prefers-reduced-motion media query. • Focus Indicators: Visible focus rings on all interactive elements for keyboard users.
Conformance & Audit Status
Statement last reviewed: 2026-07-12. 2026-Q2 audit — Tier-1 external-style sweep (8 routes, Loop Q); all Serious findings remediated and re-gated in CI. Automated gates that run on every pull request: • Lighthouse accessibility gate — every Tier-1 public route must score at or above 95/100 on both desktop and mobile presets. A route that drops below the floor fails the build; the per-route score table is published with each run. Routes in the gate: home (/), sign-in (/auth), pricing, contact, help, onboarding, and this statement page. • axe-core via Playwright — Tier-1 (npm run a11y) and Tier-2 (npm run a11y:tier2) sweeps. The npm run a11y:diff gate blocks merges that introduce a new critical or serious violation against the stored baseline. • eslint-plugin-jsx-a11y is enforced on every commit, and a contrast audit compares every design-system colour pair in both light and dark themes. Coverage: • Tier 1 (8 routes) audited and remediated: home, authentication wizard, onboarding, farmer dashboard, pricing, contact, help, and this statement. Zero critical or serious axe-core findings. • Tier 2 (13 in-app routes) covered: technician / doctor / exporter / lab-tech dashboards, My Crop Site, My Crop Score, Aqua Trading Hub, Field Mode, Marketplace, and the calculator entry points. Zero critical or serious findings. • Shared shells hardened first — DashboardLayout, NavbarFull, Footer, FloatingCTA, and the shadcn UI wrappers — so fixes cascade across all role dashboards. • Severity signals (ticket priority, alert chips) carry a non-colour glyph alongside colour, so they stay readable without colour perception. • Skip-to-content is present on both the public and authenticated shells, targeting main content and sidebar navigation. A manual assistive-technology pass (VoiceOver on macOS/iOS plus NVDA on Windows) by a third-party reviewer is planned and has not yet been performed. Until it is, every claim on this page comes from automated tooling.
Known Limitations
We publish open items rather than implying full conformance. Known gaps as of 2026-07-12: • IoT Sensor Charts: Real-time visualisations may not convey every data point to screen-reader users. A tabular alternative is available via "View as Table" on each chart. • AI Disease Detection: Image-based analysis requires visual input; text-based symptom entry is provided as an alternative pathway. • PDF Export Reports: Some generated PDFs do not yet meet PDF/UA. Work is in progress. • Third-Party Components: Embedded payment checkout and video conferencing carry their own accessibility limitations beyond our direct control. • Tier-3 surfaces — the calculator suite and internal admin consoles — inherit the same component library and lint rules but are not individually audited route-by-route. • Remaining moderate-severity items from the current audit backlog (icon-button labelling on a small number of secondary controls, duplicate section headings in the Help Center) are queued for the next remediation wave. If a barrier blocks you today, report it below and we will treat it as a priority rather than waiting for the next sweep.
Multilingual Accessibility
CAMARON supports 31 languages to serve our global user base across 26+ countries. Accessibility features are maintained across all supported languages, including: • Translated ARIA labels and screen reader text • Language-specific font scaling adjustments for mobile devices • Right-to-left (RTL) layout support with proper content reflow • Locale-aware date, number, and currency formatting If you encounter accessibility issues in a specific language, please let us know so we can address them promptly.
Feedback & Assistance
We welcome feedback on the accessibility of CAMARON. If you encounter a barrier, need assistance using the platform, or want to suggest an improvement, contact us: • Email: accessibility@robicrufarm.com • Phone: +91 9642549416 • In-app: the support chat (available to signed-in users) We aim to respond to accessibility enquiries within 2 business days. If you need content in an alternative format — large print, audio, or otherwise — tell us and we will accommodate the request. Review cadence: this statement is reviewed at least quarterly and re-reviewed whenever the automated gates report a change in conformance. It was last reviewed on 2026-07-12.
Report an accessibility issue
Found a barrier? Send us the details below — your report routes to the same support inbox as /contact, prefixed for accessibility triage.
Guidance & Resources
Inside CAMARON
- Press "?" anywhere to open the keyboard-shortcuts panel.
- Use the language switcher in the top nav to change one of 31 supported languages (RTL supported).
- On any chart, use the "View as Table" toggle for a screen-reader-friendly tabular view.
- Enable Reduced Motion in your OS — CAMARON respects prefers-reduced-motion and disables non-essential animation.
Related pages
- Help CenterQuick-start guides, calculator formulas, FAQ.
- Contact SupportReach a human — accessibility-related queries triaged within 2 business days.
- Privacy PolicyHow we handle your data, including assistive-tech telemetry.
- Data Processing AddendumEnterprise-grade data handling guarantees.
- All PoliciesFull legal & operational policy library.
External standards & guides
- WCAG 2.2 AA Quick ReferenceW3C's official Web Content Accessibility Guidelines — our conformance target. Verified · Externalwww.w3.orgVerified external destination — opens www.w3.org in a new tab
- WebAIM ArticlesPractical screen-reader and assistive-technology guides. Verified · Externalwebaim.orgVerified external destination — opens webaim.org in a new tab
- Chrome Accessibility SettingsBrowser-level accessibility controls. Verified · Externalsupport.google.comVerified external destination — opens support.google.com in a new tab
- Safari Accessibility FeaturesBuilt-in accessibility tools on macOS / iOS. Verified · Externalsupport.apple.comVerified external destination — opens support.apple.com in a new tab
- Firefox Accessibility FeaturesMozilla's browser accessibility documentation. Verified · Externalsupport.mozilla.orgVerified external destination — opens support.mozilla.org in a new tab
Deep dives
Six long-form guides covering how accessibility actually works on this platform — what is enforced, how it is measured, and where the gaps still are.
Keyboard navigation across CAMARON dashboards
Every dashboard, wizard and drawer is reachable without a mouse. Here is the shortcut map, the focus rules we hold ourselves to, and where the gaps still are.
Read the guideScreen reader support: landmarks, live regions and honest gaps
What a screen reader actually encounters on CAMARON — the landmark structure, the live regions that announce alerts, and the surfaces that are not there yet.
Read the guideColour, contrast and theme parity
CAMARON ships light and dark themes from one semantic token set. This is how contrast is measured, gated in CI, and kept at parity across both themes.
Read the guideAccessibility on mobile and in the field
Pond-side logging happens one-handed, in sunlight, sometimes offline. Tap targets, Field Mode, offline states and what that means for accessible design.
Read the guideMultilingual and right-to-left accessibility
31 languages, four of them right-to-left. How language attributes, mirrored layouts and per-script font scaling keep the platform readable everywhere.
Read the guideHow we audit accessibility (and what we do not claim)
The exact gates that run on every pull request, how routes are tiered, what the baseline allowlist does, and the manual assistive-technology pass we have not done yet.
Read the guide