Accessibility Statement

We believe health information — and the tools to manage family health — should be accessible to everyone, regardless of ability. Accessibility is not a checkbox exercise for us; it is an ongoing engineering practice that we apply to every new feature and content update.

We follow the Web Content Accessibility Guidelines (WCAG) version 2.1, level AA, as our baseline. These guidelines explain how to make web content accessible to people with a wide range of disabilities, including visual, auditory, motor, and cognitive impairments.

Our website is designed and tested against:

• WCAG 2.1 Level AA: The internationally recognized standard for web accessibility.
• Indian RPwD Act 2016 (Rights of Persons with Disabilities Act): Specifically the accessibility guidelines for government and public-facing digital services.
• Section 508 (US): For federal-compliance alignment where applicable.
• EN 301 549: European accessibility standard, used as a reference for procurement-grade accessibility.

We use automated testing (axe-core, Lighthouse, WAVE) on every page template and conduct manual keyboard-only navigation tests on critical user flows (contact form, blog navigation, menu toggle).

• Semantic HTML: Pages use proper heading hierarchy (H1 → H2 → H3), landmark elements (header, nav, main, footer), and ARIA labels where needed.
• Keyboard navigation: All interactive elements (links, buttons, form fields, menu toggle) are reachable and operable via keyboard alone, in logical tab order.
• Skip-to-content link: A "Skip to content" link appears at the top of every page for keyboard and screen-reader users to bypass the navigation.
• Color contrast: Body text meets WCAG AA contrast ratios (minimum 4.5:1 for normal text, 3:1 for large text). We test in both light and dark modes.
• Form labels: All form fields (contact form, comment form, search) have associated label elements and clear error messaging.
• Image alt text: Decorative images use empty alt attributes; informational images use descriptive alt text. Screenshots of the app include alt text describing what the screen shows.
• Dark mode: A toggle is available in the header; respects system preference when no user choice is set. Reduces eye strain for users with light sensitivity.
• Responsive design: All pages reflow for screen sizes from 320px (small phones) to 1920px+ (large desktops). No horizontal scrolling at any width.
• Readable typography: Body font size is 16px minimum; line height is 1.6 for paragraphs; paragraphs are limited to ~75 characters wide for readability.

Despite our best efforts, some areas of the website may have accessibility limitations:

• Third-party embedded content: Google AdSense ads, YouTube embeds, and social media share buttons are governed by their providers' accessibility practices. We cannot always guarantee they meet WCAG AA. We minimize their use and place them in ways that do not block primary content.
• PDF attachments: Some blog articles may link to external PDFs (e.g., IRDAI circulars, government guidelines). We do not control the accessibility of those PDFs.
• Older blog articles: Articles published in the early days of the site may not meet current accessibility standards. We are gradually updating them; if you encounter a problem, please report it.
• Mobile keyboard traps: The mobile menu, on rare older Android browser versions, may have keyboard focus issues. We are working on a fix.

If you encounter any accessibility barrier not listed here, please report it via our contact page with the subject "Accessibility Issue".

The VitalNadi Android app follows Google's Material Design accessibility guidelines:

• All interactive elements have content descriptions for TalkBack screen reader users.
• Touch targets meet the 48dp minimum recommended by Material Design.
• Color is never the sole indicator of state (e.g., error states include icon and text, not just red color).
• Text scaling respects the user's system font size settings.
• The app supports both light and dark themes, following the system theme by default.

If you encounter an accessibility issue in the Android app, please contact us with: device model, Android version, the screen or feature affected, and the assistive technology you are using (TalkBack, switch access, etc.).

We take accessibility reports seriously and aim to respond within 5 business days. To report an issue:

1. Visit our contact page.
2. Use the subject line "Accessibility Issue".
3. Include: the URL or screen name, the specific problem, the device and browser/Android version you are using, and any assistive technology in use.
4. If possible, attach a screenshot or short recording.

If the issue is critical (e.g., a keyboard trap that prevents you from completing a task), we will prioritize a fix and aim to ship it within 30 days. For non-critical issues, we batch fixes into our regular release cadence.

Accessibility is not a one-time audit — it is an ongoing practice. We:

• Run automated accessibility tests on every code change before deployment.
• Conduct quarterly manual reviews of high-traffic pages with keyboard-only and screen-reader testing.
• Train new content contributors on accessible writing practices (heading hierarchy, alt text, link text).
• Review this statement annually and update it with new improvements and known limitations.

We test the website with the following assistive technologies:

• Screen readers: NVDA (Windows), VoiceOver (macOS and iOS), TalkBack (Android).
• Browser zoom: Up to 200% without horizontal scrolling, on Chrome, Firefox, Safari, Edge.
• Keyboard-only navigation: Tested on Windows and macOS.
• High-contrast mode: Windows High Contrast mode and macOS Increase Contrast.
• Speech recognition: Basic testing with Windows Voice Access.

If your preferred assistive technology is not on this list and you encounter issues, please let us know — we will add it to our test matrix.

For accessibility questions, reports, or feedback, contact us with the subject "Accessibility". Our accessibility lead reviews all such messages personally.