BhaiBahini Logo

Accessibility Statement

Access to guidance should not depend on a person’s vision, hearing, mobility, cognition, language, device, or internet speed. 

  1. Our commitment

    BhaiBahini is committed to making its website, application, forms, learning resources, and remote mentorship experience usable by people with diverse disabilities, devices, languages, literacy levels, and connection speeds. Accessibility is part of our promise of fair access, not a one-time compliance exercise.

  2. Our accessibility target

    We aim to design and improve our digital services toward conformance with the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA. Until a qualified audit is completed, this statement should not be read as a claim that every page or feature fully conforms.

  3. What we are working to provide

    • Keyboard access with a visible and logical focus order.
    • Clear page titles, headings, landmarks, labels, instructions, and error messages.
    • Text alternatives for meaningful images and accessible names for controls and icons.
    • Readable color contrast without relying on color alone to communicate meaning.
    • Support for browser zoom, text resizing, responsive layouts, and common assistive technologies.
    • Captions, transcripts, or equivalent alternatives for important audio and video content.
    • Controls for motion, animation, time limits, and content that could cause distraction or physical reactions.
    • Plain-language content and clear explanations of unfamiliar terms.
    • Accessible forms that identify required fields, preserve entered information where practical, and explain how to correct errors.
    • Low-bandwidth and mobile-friendly paths for participants in Nepal where feasible.
  4. Remote mentorship access

    BhaiBahini mentorship takes place through approved remote channels. We will work to choose tools that support keyboard use, screen readers, captions, and other accessibility features. Participants may request a reasonable alternative such as live captions, a transcript, accessible documents, additional processing time, or a different approved communication format when feasible and safe.

  5. Known limitations 

    Some third-party tools, older documents, pilot features, or user-submitted content may not yet meet our accessibility target. We will prioritize barriers that prevent someone from expressing interest, completing onboarding, reporting a safety concern, joining a session, or accessing essential information.

    Third-party accessibility may change outside our control. We will seek alternatives or reasonable accommodations when an external tool creates a significant barrier.

  6. Request help or report a barrier

    If you cannot access content or complete a task, contact [ACCESSIBILITY EMAIL]. Please include, if you are comfortable doing so:

    • The page, form, document, or feature involved.
    • What you were trying to do and what happened.
    • Your browser, device, and assistive technology, if relevant.
    • The format or accommodation that would help.

    You do not need to disclose a diagnosis. We will acknowledge requests as soon as possible and work toward an accessible response or alternative. Accessibility requests will be handled respectfully and will not reduce eligibility for mentorship.

  7. Service providers and partners

    Before a provider handles personal information, BhaiBahini should assess the provider’s purpose, data access, security, retention, child-privacy implications, location, subcontractors, incident-notification terms, deletion support, and ability to assist with rights requests. Agreements should require confidentiality and use only for authorized purposes.

    High-risk providers include identity or background-check services, video and messaging tools, analytics, AI services, payment services, and systems storing safeguarding records. 

  8. International transfers and distributed teams

    BhaiBahini may operate across Nepal and the United States and use providers in other countries. Cross-border access must be limited to legitimate duties, protected by appropriate contracts and security measures, and documented in a data inventory. The team must confirm where each material system stores and backs up data.

  9. Continuous improvement

    Our process includes accessibility requirements during design and development, automated checks, keyboard and screen-reader review, content checks, and testing with people who have disabilities when possible. We welcome feedback from participants, families, schools, mentors, and disability communities.

  10. Compatibility and formal review

    The experience is intended to work with current versions of widely used browsers and operating systems. Before making a formal conformance claim, BhaiBahini should complete an independent WCAG 2.2 AA audit, publish known exceptions, assign an accessibility owner, and establish a remediation schedule.

Follow the BhaiBahini Journey

Receive occasional updates about our pilot, founding community, learning resources, and upcoming opportunities to participate.