Accessibility statement

We design, build, and maintain this website with the goal of providing equivalent access to everyone, regardless of disability, assistive technology, or browsing context. Accessibility is treated as a design constraint at the component level — not as a post-launch audit pass.

Where a feature is genuinely incompatible with assistive technology, we surface an alternative path so the underlying functionality is still reachable.

We target conformance with:

• Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA— the international standard developed by the W3C’s Web Accessibility Initiative.
• Section 46 of the Rights of Persons with Disabilities Act, 2016 (India) — which requires accessible information and communication technology.
• Indian government accessibility guidelines issued by the Department of Empowerment of Persons with Disabilities.

AAA conformance is aspirational for certain content surfaces. Where we fall short, the “Known limitations” section below documents what and when we plan to fix it.

Our website implements the following accessibility features:

Keyboard navigation

• All interactive elements are reachable via keyboard alone.
• A “Skip to content” link is available at the top of every page for screen-reader and keyboard users.
• Focus indicators are visible and high-contrast on every focusable element.

Screen readers

• Semantic HTML — landmarks, headings, lists, and forms are properly labeled.
• ARIA attributes are used where native HTML doesn’t fully express the intended behavior (e.g., accordion expansions, dropdown menus).
• Images include descriptive alternative text. Decorative images are marked as such so screen readers don’t announce them.
• Form fields have visible labels and accessible name associations. Error messages are programmatically associated with the relevant field.

Visual design

• Text contrast meets WCAG AA minimums on all interactive elements and body copy.
• Color is not used as the sole means of conveying information — meaningful distinctions are also expressed through text, iconography, or position.
• Type sizes are responsive and scale with browser zoom up to 200% without loss of content or functionality.

Motion

• We respect the prefers-reduced-motion media query. Users who have indicated a preference for reduced motion see static or minimally animated versions of components that otherwise include motion effects.
• No content auto-plays sound or video without user initiation.
• Carousel and tab components do not auto-advance in a way that prevents user interaction.

Forms

• All form inputs have visible labels.
• Required fields are marked both visually and via the required attribute.
• Validation errors are announced to assistive technology, not just visually indicated.
• Inline help text is associated with its field via aria-describedby.

We’re transparent about gaps so you know what to expect:

• Embedded Cal.com scheduler: the discovery-call iframe is rendered by Cal.com. We have limited control over its internal accessibility characteristics. If you encounter a barrier while scheduling, use one of our alternative contact methods.
• Map embed: the static map on the contact page may not be fully navigable by screen readers. The full postal address is provided as text alongside the map for equivalent access.
• PDF lead magnets: where we offer downloadable PDFs, we generate them with structural tagging where possible. Older PDFs may have limited tagging — contact us for an alternative format if needed.
• Third-party widgets: chat widgets, social media embeds, and similar third-party content carry their own accessibility characteristics. We choose vendors with documented accessibility support but cannot guarantee full conformance.

We update this list as we fix gaps and as new ones are identified through testing.

Accessibility is tested through multiple methods:

• Automated testing — axe-core, Lighthouse, and Pa11y are run on key pages during development.
• Manual testing — keyboard-only navigation, screen reader verification (NVDA, JAWS, VoiceOver), and zoom behavior at 200%+ are checked on the home page, contact page, and primary conversion paths quarterly.
• User feedback — reports from users with assistive technology are treated as priority bugs.

Audits are not currently performed by an external accessibility specialist on this site. As the site matures, we plan to commission an independent audit at least annually.

If you encounter content or functionality on this website that is not accessible, please tell us. We treat accessibility reports as priority bugs and aim to acknowledge within 2 business days.

Email: hello@medigrow.co.in

Please include:

• The URL where you encountered the barrier.
• A description of the barrier and what you were trying to do.
• Your operating system, browser, and (if applicable) assistive technology you were using.

If our website is inaccessible to you for any reason, you can reach us via:

• Email: hello@medigrow.co.in — typical response within 4 business hours.
• Phone: +91 9742820226 — Mon–Sat 09:30–19:00 IST.
• WhatsApp: +91 9742820226 — same-day response during business hours.

We are happy to provide information, schedule consultations, and complete inquiries through any of these channels — accessibility is not a prerequisite for engaging with us.

Accessibility is treated as a continuous improvement track, not a one-time milestone. Current priorities:

• Commission a third-party accessibility audit and publish the findings with remediation timelines.
• Improve color contrast on lower-emphasis labels (currently meets AA but with margin we’d like to increase).
• Add transcripts for any video content we publish, even when captions are present.
• Test with users who use assistive technology and incorporate their feedback directly.

Status updates and changes will be reflected in the “Last reviewed” date and in the “Known limitations” section above.