Our Commitment

SunnyPharma® is committed to making our health education content accessible to all users, including those with disabilities. Access to accurate health information should not depend on a person’s ability to use a standard browser interface. We are working toward conformance with the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA, and we treat accessibility as a core design requirement rather than an afterthought.

This statement describes the accessibility practices we apply, the limitations we are currently aware of, and how to reach us if you encounter a barrier.

Accessibility Practices We Apply

In building and maintaining this website, we aim to apply the following practices:

• Semantic HTML: Pages are built using a logical heading hierarchy (H1 → H2 → H3), landmark regions (header, nav, main, footer), and ARIA roles where appropriate
• Keyboard navigation: Interactive elements — links, navigation items, and form inputs — are intended to be operable by keyboard
• Focus indicators: Visible focus states are applied to interactive elements
• Alternative text: We aim to provide descriptive alt attributes for meaningful images, and empty alt="" for decorative images
• Color contrast: Text and background color combinations are chosen with the WCAG contrast targets in mind (4.5:1 for normal text, 3:1 for large text)
• Responsive design: Pages are designed to be responsive across common viewport sizes, from small mobile screens to desktop, without requiring horizontal scrolling at standard widths
• Text scaling: Layouts are designed to accommodate browser text scaling without loss of content or functionality
• Input font sizes: Form inputs use a minimum font size intended to prevent unwanted mobile auto-zoom
• Descriptive link text: Links are written to identify their destination rather than relying on phrases like “click here” or “read more”
• Language declaration: A lang attribute is set on each page to assist screen readers with pronunciation
• Tables: Data tables use header cells (<th>) and are placed in scrollable containers to reduce overflow on narrow screens

Current Status & Known Limitations

We are working toward WCAG 2.1 AA conformance, but we want to be transparent about where we are:

• This website has not yet undergone formal accessibility testing or an independent third-party audit. The practices above describe our design approach, not a certified conformance result.
• We have not yet completed systematic testing with assistive technologies such as screen readers. Until we do, some barriers may exist that we are not aware of.
• Some PDF documents linked from our pages may not fully conform to PDF accessibility standards.
• Third-party embedded content (such as externally delivered fonts) may introduce variations outside our direct control.
• Some complex data tables may benefit from additional labeling, which is under ongoing review.

We review accessibility when new page templates are introduced and when significant content changes are made, and we review this statement at least annually. As we complete assistive-technology testing, we will update this statement to reflect what has been verified.

Technical Approach

The accessibility of this website relies on the following technologies:

• HTML5
• CSS3 (without relying on CSS alone to convey critical information)
• JavaScript (where used, pages are intended to remain functional without it)
• ARIA attributes where native HTML is insufficient

Assistive Technologies

We design our pages with common assistive technologies in mind, including screen readers such as NVDA, JAWS, VoiceOver, and TalkBack used with mainstream browsers. As noted above, we have not yet completed systematic testing across these tools; if you use assistive technology and encounter a barrier, we would value hearing from you.

Reporting Accessibility Barriers

We take accessibility barriers seriously. If you encounter content on this website that you cannot access due to a disability, or a page that does not meet the standards described above, please contact us via the contact page and include, where you can:

• The URL of the page where you encountered the barrier
• A description of the issue
• The assistive technology you are using, if applicable

We aim to acknowledge reports within 5 business days and to resolve confirmed issues within 30 business days where technically feasible.

Enforcement & Complaints

Accessibility requirements differ by country. If you are not satisfied with our response to an accessibility report, you may contact the accessibility enforcement authority in your own jurisdiction — for example, authorities responsible for the Americans with Disabilities Act (United States), the European Accessibility Act (European Union), the Accessible Canada Act (Canada), or equivalent legislation where you live.