WINBD App Accessibility Statement

WINBD is committed to improving access to its digital services for users across Bangladesh.

We recognize that people interact with mobile applications in different ways. Some users may navigate with a screen reader, keyboard or switch-access technology, voice controls, magnification, high-contrast settings, captions, or other assistive technologies. Other users may benefit from simple language, predictable navigation, larger touch targets, clear error messages, or reduced visual and motion effects.

For this reason, accessibility is considered throughout the design, development, testing, and improvement of our digital products.

Bangladesh’s digital-service guidance specifically recognizes the importance of disability-inclusive websites, mobile applications, and digital services and recommends compatibility with screen-reading software and following WCAG guidance or its updated version.

WINBD therefore aims to apply recognized accessibility principles to the extent technically and commercially practicable, while continuing to identify and address barriers that may prevent users from accessing our services.

Scope of This Statement

This Accessibility Statement applies primarily to:

• The WINBD mobile application.
• WINBD’s mobile-friendly digital interfaces.
• Account and profile-related interfaces.
• Registration and login experiences.
• Navigation menus and interactive controls.
• Forms and user-input fields.
• Help and support interfaces.
• Notifications and informational content.
• Other digital services operated and controlled by WINBD where accessibility improvements are applicable.

Some third-party websites, applications, payment services, advertising services, operating-system features, or external content may not be fully controlled by WINBD. Accessibility issues originating from third-party services may therefore require cooperation with the relevant provider.

 Accessibility Standards

WINBD uses recognized accessibility principles as a reference when designing and improving its digital experiences.

Where appropriate, our development and testing approach is informed by the Web Content Accessibility Guidelines (WCAG) and established mobile accessibility practices. WCAG provides internationally recognized guidance for making digital content more perceivable, operable, understandable, and robust.

Our objective is to work toward a digital experience that follows the four fundamental accessibility principles:

1. Perceivable – information should be presented in ways users can perceive.
2. Operable – controls and navigation should be usable through different interaction methods.
3. Understandable – information and interfaces should be clear and predictable.
4. Robust – content should work with a reasonable range of browsers, devices, operating systems, and assistive technologies.

Accessibility standards evolve over time. We may update our technical practices as WCAG and mobile accessibility recommendations develop.

Features We Aim to Support

WINBD aims to provide accessibility features and design practices that help users interact with the application more effectively.

Screen Reader Compatibility

We aim to structure important interface elements so that commonly used screen-reading technologies can identify and communicate buttons, labels, headings, forms, notifications, and other meaningful content.

Interactive controls should have descriptive names wherever technically possible. Images that communicate important information should also have meaningful alternative descriptions when appropriate.

Clear Navigation

We aim to maintain consistent navigation throughout the application.

Menus, buttons, account sections, forms, and other major functions should use recognizable labels and predictable layouts. Users should not be required to understand complicated visual designs simply to locate essential controls.

Text and Readability

We aim to make written information easier to read by using:

• Clear fonts and appropriate text sizes.
• Adequate spacing between content elements.
• Readable contrast between text and backgrounds.
• Descriptive headings.
• Short and understandable instructions where possible.
• Clearly identified links and buttons.

Where the operating system provides text-size or display settings, we aim to avoid unnecessarily preventing users from benefiting from those settings.

Color and Contrast

WINBD does not intend to rely exclusively on color to communicate important information.

For example, an important status, warning, error, or confirmation should ideally be communicated through text, an icon, or another identifiable method in addition to color.

We also aim to maintain sufficient contrast between important foreground and background elements.

Touch Controls

Mobile users may have different levels of precision when interacting with touchscreens.

We aim to provide appropriately sized and adequately separated touch targets so that buttons and controls can be selected without unnecessary difficulty.

Forms and Error Messages

Forms should provide understandable labels and instructions wherever possible.

When an error occurs, we aim to identify the affected field or action and provide information that helps the user understand what needs to be corrected.

Error messages should avoid unnecessary technical terminology.

Audio and Video Content

Where WINBD publishes multimedia content, we aim to consider accessibility features such as captions, text alternatives, transcripts, or other appropriate formats when reasonably applicable.

Accessibility requirements can differ depending on the purpose and format of the content.

Motion and Animation

Some users may experience difficulty with excessive animation, flashing effects, or rapidly changing visual elements.

We aim to use motion responsibly and avoid unnecessary animation that could interfere with usability. Where platform-level controls are available, users may also be able to reduce motion through their device accessibility settings.

Compatibility With Assistive Technology

WINBD understands that accessibility depends not only on the application itself but also on the device, operating system, browser, and assistive technology being used.

We therefore aim to test important user journeys across commonly used environments where reasonably practicable.

Testing may include consideration of:

• Screen-reading software.
• Device text-size settings.
• Display magnification.
• Voice-control features.
• Keyboard or alternative input methods where applicable.
• High-contrast or visual accessibility settings.
• Common Android and iOS accessibility features.
• Different screen sizes and resolutions.

Actual compatibility can vary between operating-system versions, devices, assistive technologies, and application releases.

Accessibility for Users in Bangladesh

WINBD is intended to serve users in Bangladesh, where people may access digital services through a wide variety of smartphones, network conditions, operating systems, and levels of digital literacy.

We recognize that accessibility is not limited to disability-related technology.

A user may experience difficulty because of a small screen, limited connectivity, unfamiliar terminology, temporary injury, age-related changes, low vision, hearing loss, limited dexterity, or another circumstance.

For this reason, we aim to keep important interactions simple, clear, and consistent.

Where appropriate, we also consider language and communication needs relevant to users in Bangladesh. Important instructions should be written as clearly as possible, avoiding unnecessary jargon or complicated technical language.

 Accessibility and Account Security

Security features can sometimes create accessibility challenges. For example, authentication procedures, verification steps, timed sessions, or security notifications may be difficult for some users to complete.

WINBD aims to balance accessibility with the need to protect accounts and user information.

Where an accessibility barrier occurs during registration, login, verification, or account recovery, users are encouraged to contact our support team for assistance.

Users should never be required to disclose passwords, PINs, authentication codes, or other confidential security credentials through an accessibility complaint.

Third-Party Services

Some functions associated with a digital application may depend on third-party technologies or services.

These can include payment providers, analytics services, authentication systems, operating-system services, embedded content, customer-support technologies, or other external platforms.

WINBD does not necessarily control the accessibility of third-party services.

Where a third-party component creates an accessibility barrier, we will seek to understand the issue and, where possible, work with the relevant provider or identify a practical alternative.

 Known Accessibility Limitations

Digital accessibility is an ongoing process, and no application should be considered permanently accessible simply because it has passed a particular test.

Depending on the version of the WINBD App, device, operating system, or third-party technology being used, some users may encounter limitations.

Potential issues may include:

• Incomplete labeling of certain controls.
• Compatibility differences between screen readers.
• Third-party content that does not fully support accessibility.
• Difficulty with certain dynamic or interactive elements.
• Differences in accessibility behavior between mobile operating systems.
• Newly introduced features that have not yet completed accessibility testing.

When we identify accessibility barriers, we aim to assess their impact and prioritize improvements according to severity, frequency, and the importance of the affected function.

 Accessibility Testing and Continuous Improvement

Accessibility is not a single project with a final completion date.

We aim to incorporate accessibility considerations into product development and quality assurance processes.

Where appropriate, our improvement process may involve:

1. Reviewing interface designs before development.
2. Conducting automated accessibility checks.
3. Performing manual accessibility testing.
4. Testing important user journeys with assistive technologies.
5. Reviewing reports submitted by users.
6. Prioritizing significant barriers.
7. Implementing corrective changes.
8. Re-testing affected functionality after updates.

User feedback is particularly valuable because automated testing cannot identify every real-world accessibility problem.

Research and policy work concerning Bangladesh’s digital ecosystem has also highlighted the importance of regular accessibility audits, user-centered design, and stronger accessibility practices across digital services.

 Feedback and Accessibility Assistance

If you experience difficulty using any part of the WINBD App because of an accessibility barrier, we encourage you to contact our support team.

When reporting an issue, please provide as much of the following information as you are comfortable sharing:

• The part of the application where the problem occurred.
• What you were trying to do.
• What happened.
• What you expected to happen.
• Your device type.
• Your operating-system version.
• The assistive technology you were using, if applicable.
• Any relevant screenshots or recordings, provided they do not contain confidential information.

You do not need to provide sensitive personal information simply to report an accessibility problem.

Accessibility Support: [Insert official WINBD support email]

Customer Support: [Insert official WINBD support channel]

Support Hours: [Insert current support hours]

We aim to review accessibility feedback and determine the appropriate next step as efficiently as reasonably possible.

 Alternative Ways to Access Information

If a particular feature or piece of information is not accessible to you, please contact our support team.

Where reasonably possible, we will consider providing an alternative way to obtain the relevant information or complete the relevant non-sensitive process.

An alternative method may not always be identical to the standard digital experience, but our objective is to reduce unnecessary barriers and provide meaningful assistance.

Privacy and Accessibility Complaints

Accessibility feedback may contain information about a user’s disability or assistive technology. Users should therefore avoid including unnecessary sensitive information in a support request.

WINBD will handle accessibility-related communications in accordance with its applicable privacy and data-handling practices.

An accessibility complaint should not be used to submit passwords, payment credentials, authentication codes, or other confidential account-security information.

 Accessibility Governance

Responsibility for accessibility should be shared across product design, engineering, quality assurance, content, customer support, and management teams.

WINBD aims to improve accessibility by:

• Considering accessibility during product planning.
• Training relevant teams where appropriate.
• Reviewing significant accessibility feedback.
• Prioritizing high-impact barriers.
• Including accessibility in quality assurance processes.
• Updating this statement when significant changes are made.
• Monitoring developments in accessibility standards and digital-service practices.

Legal and Regulatory Considerations in Bangladesh

WINBD recognizes the importance of disability inclusion and accessibility within Bangladesh’s broader digital environment.

Bangladesh’s disability-rights framework includes accessibility considerations for information, communication, and information and communication technology, while government digital-service guidance specifically addresses accessible websites, mobile applications, and digital services.

This statement is intended to describe WINBD’s accessibility approach and should not be interpreted as a legal opinion or a representation that every part of the application currently satisfies every applicable legal or technical requirement.

WINBD will continue to review its accessibility practices as applicable Bangladeshi laws, regulations, government guidance, technical standards, and industry practices develop.

Updates to This Accessibility Statement

We may update this Accessibility Statement when:

• New accessibility features are introduced.
• Significant changes are made to the WINBD App.
• Accessibility standards or guidance change.
• We identify new accessibility limitations.
• Our feedback and testing processes are improved.

The “Last Updated” date at the top of this statement indicates when the document was most recently reviewed or updated.

Our Accessibility Goal

Our goal is simple: people should not be unnecessarily excluded from digital services because of a disability or accessibility barrier.

We understand that accessibility is an ongoing responsibility. Technology changes, devices change, assistive technologies change, and the needs of users are diverse.

For WINBD, accessibility therefore means continuously listening, testing, learning, and improving.

We welcome feedback from users in Bangladesh and from anyone who interacts with the WINBD App using assistive technology.

If you encounter an accessibility problem, please let us know. Your feedback can help us identify barriers that automated testing or internal reviews may not detect and can contribute directly to making future versions of the WINBD App more inclusive.