CareGridCalendo Health

Accessibility

Accessibility statement.

Calendo Health is a public marketing website for therapy clinics. The site is built to be usable across devices, input methods, and assistive technologies while the live product remains separate.

Prepare feedback

Keyboard-friendly paths

The public site includes a skip link, visible focus states, standard links and buttons, and keyboard-operable disclosure panels.

Semantic page structure

Pages use headings, landmarks, breadcrumbs, list structures, labels, and descriptive link text to support scanning and assistive technologies.

Readable visual system

The interface uses restrained color, clear spacing, high-contrast interactive states, and stable layouts across desktop and mobile widths.

Form guidance

The demo, purchase, and updates forms use explicit labels, validation messages, error associations, live status feedback, receipt links, and clear contact paths.

Scope

A practical statement for this website.

This statement covers organosi.com.gr public marketing pages, demo request forms, resource pages, search, and public static assets. It does not describe the live Calendo Health product app.

Responsive access

Pages are designed to work on mobile and desktop screens without requiring a separate mobile app. Installed-app metadata is available for supported browsers.

Known limitations

Some public visuals are illustrative product mockups. If an image, interaction, or route blocks access, contact us so it can be reviewed and improved.

Review habits

Accessibility should stay visible as the site grows.

Future CareGrid products, launch materials, and product visuals should keep the same public-site accessibility expectations.

  • Navigate core pages and forms with only the keyboard.
  • Keep focus outlines visible on buttons, links, inputs, and disclosure controls.
  • Use privacy-safe image alt text, labels, and descriptions for public assets.
  • Avoid relying on color alone for validation, status, or selected states.
  • Retest responsive layouts when adding new routes, cards, or navigation items.

Accessibility feedback

Email hello@organosi.com.gr with the page URL, browser or device, assistive technology if relevant, and a short description of the issue.

Prepare feedback

Feedback reporter

Turn public website issues into clear reports.

Capture the page, issue type, environment, safe reproduction questions, and public-only details before opening a feedback email.

Website feedback reporter

Prepare a useful public-site issue report.

Capture the affected page, issue type, environment, and safe reproduction questions before sending feedback to the Calendo Health team.

51%

Report clarity

Accessibility barrier

Keyboard, screen reader, contrast, focus, label, motion, or layout issue.

Not sure

Use this when the affected page or feature is hard to classify.

Questions to answer

Generated report

Public website feedback report

Public website feedback report:
Issue type: Accessibility barrier
Affected area: Not sure
Page URL or route: Not provided
Environment: Not provided
Reply email: Not provided

Questions:
- Which page URL or route showed the issue?
- What were you trying to do before the issue happened?
- Can the issue be reproduced without including private clinic, patient, or account details?

What happened:
Not provided

Safe report boundaries:
- Use this reporter for public marketing website issues only.
- Do not include patient data, clinical notes, private access details, private screenshots, contracts, or live app records.
- Use public page URLs, browser/device details, and general steps instead of private examples.
- Security vulnerabilities should use the disclosure contact in /.well-known/security.txt or the security page.
Open feedback email

Safe report boundaries

  • Use this reporter for public marketing website issues only.
  • Do not include patient data, clinical notes, private access details, private screenshots, contracts, or live app records.
  • Use public page URLs, browser/device details, and general steps instead of private examples.
  • Security vulnerabilities should use the disclosure contact in /.well-known/security.txt or the security page.

Privacy preferences

We use optional first-party analytics to understand page visits and demo interest. The site works normally if you decline.