♿ Accessibility at Supar Bazaar Finance

We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA — the internationally recognised standard for web accessibility published by the World Wide Web Consortium (W3C).

The Four WCAG Principles (POUR)

• Perceivable: Information and user interface components must be presentable in ways users can perceive (e.g., alt text, captions).
• Operable: UI components and navigation must be operable via keyboard and other input methods.
• Understandable: Information and operation of the UI must be understandable to all users.
• Robust: Content must be robust enough to be reliably interpreted by assistive technologies.

Applicable Legal Frameworks (India)

• Rights of Persons with Disabilities (RPWD) Act, 2016 — mandates accessibility in digital services
• Information Technology Act, 2000 — governs digital accessibility obligations
• National Policy for Universal Electronic Accessibility, 2013
• RBI Guidelines on Accessibility for financial services apps and websites

The following accessibility features are implemented across suparbazaar.online:

• ⌨️ Full Keyboard Navigation: All interactive elements — menus, forms, buttons, modals — are accessible and operable without a mouse.
• 🔊 Screen Reader Compatible: Our pages use semantic HTML and ARIA landmarks so screen readers can navigate content logically.
• 🖼️ Alt Text on Images: All meaningful images include descriptive alt attributes. Decorative images use alt="".
• 📐 Semantic HTML Structure: We use proper HTML5 elements: <header>, <nav>, <main>, <section>, <article>, <footer>.
• 🏷️ ARIA Labels & Landmarks: Interactive components include appropriate aria-label, aria-expanded, aria-controls, and role attributes.
• ⏭️ Skip-to-Content Link: A hidden skip link appears on focus to allow keyboard users to bypass navigation.
• 🔍 Resizable Text: Text scales correctly up to 200% zoom without loss of content or functionality.
• 🎨 Colour Contrast: Text-to-background contrast ratios meet the WCAG 2.1 AA minimum of 4.5:1 for normal text and 3:1 for large text.
• 📋 Form Labels & Error Messages: All form fields have visible labels. Validation errors are descriptive and programmatically associated with inputs.
• 🔗 Consistent Navigation: Navigation structure is consistent across all pages, making it predictable for assistive technology users.
• 📱 Responsive Design: The site adapts across devices (desktop, tablet, mobile) without loss of accessibility.
• 🚫 No Content Relying Solely on Colour: Information is never conveyed by colour alone — we always use text, icons, or patterns as well.

Screen Readers

• NVDA (NonVisual Desktop Access) — Windows, free
• JAWS (Job Access With Speech) — Windows
• VoiceOver — macOS and iOS (built-in)
• TalkBack — Android (built-in)
• Narrator — Windows (built-in)

Supported Browsers

• Google Chrome (latest 2 versions)
• Mozilla Firefox (latest 2 versions)
• Microsoft Edge (latest 2 versions)
• Apple Safari (latest 2 versions)
• Samsung Internet (Android)

Input Methods

• Standard keyboard and mouse
• Touch screens (smartphones and tablets)
• Switch access devices
• Voice control software (e.g., Dragon NaturallySpeaking, Voice Control on iOS/macOS)

Our entire website can be navigated using a keyboard alone. Here is a quick reference for common keyboard shortcuts:

Colour Contrast

We test all text-to-background colour combinations to meet WCAG 2.1 AA requirements: a minimum ratio of 4.5:1 for normal text and 3:1 for large text (18pt+). Our primary text on white background achieves a ratio of approximately 7:1.

Typography & Readability

• We use the Inter typeface — a humanist sans-serif optimised for screen readability.
• Base font size is 16px; line height is at least 1.6 for body text.
• Text can be enlarged to 200% in browser settings without horizontal scrolling or content overlap.
• We avoid justified text alignment (which creates uneven spacing) for body content.

Focus Indicators

All interactive elements display a visible focus outline when accessed via keyboard. We use high-contrast focus rings (blue outline on light backgrounds) that meet WCAG 2.1 Success Criterion 2.4.7 (Focus Visible).

No Reliance on Colour Alone

Status indicators, error messages, and data visualisations always include text labels or icon patterns in addition to colour coding, ensuring users with colour vision deficiencies receive the same information.

Our platform is designed mobile-first, ensuring full accessibility across smartphones and tablets:

• Touch Target Size: All buttons, links, and interactive elements are at least 44×44 CSS pixels — meeting WCAG 2.5.5 (Target Size) best practices.
• Responsive Layout: Content reflows at all viewport widths without requiring horizontal scrolling (WCAG 1.4.10 Reflow).
• Mobile Screen Readers: Fully compatible with VoiceOver (iOS) and TalkBack (Android).
• Gesture Alternatives: All actions performed by swipe or complex gestures also have equivalent button or link equivalents.
• Orientation: Content is accessible in both portrait and landscape orientations (WCAG 1.3.4).
• No Motion Auto-play: We respect the user's "prefers-reduced-motion" system setting — animations are disabled for users who prefer it.

• No Auto-Playing Media: Our site does not auto-play any audio or video content. Any media must be explicitly played by the user.
• Promotional Videos (if applicable): Any video content on our platform includes closed captions (subtitles) and, where feasible, a text transcript.
• No Flashing Content: We do not use content that flashes more than 3 times per second, preventing potential triggers for photosensitive users (WCAG 2.3.1).
• Audio Controls: Any audio that plays for more than 3 seconds includes mechanisms to pause, stop, or mute (WCAG 1.4.2).
• Icon Buttons: All icon-only buttons (e.g., notification bell, user avatar) include accessible aria-label attributes so screen readers can announce their purpose.

Our platform integrates with several third-party services. While we aim to partner with accessible providers, we cannot guarantee the accessibility of content or tools provided by third parties:

• Razorpay (Payment Gateway): The payment checkout interface is provided by Razorpay. We encourage users experiencing accessibility issues with the checkout to contact us for alternative payment arrangements.
• Google Analytics: A server-side analytics tool — adds no user-facing UI barriers.
• Facebook Pixel: A background tracking script — no user-facing accessibility impact.
• UIDAI (Aadhaar KYC): KYC widgets are provided by UIDAI. Users who cannot use the eKYC interface may contact us to arrange alternative identity verification.
• Font Awesome & Google Fonts: Icon library and web fonts loaded via CDN — tested for accessibility impact.

Accessibility is a continuous commitment, not a checkbox. Here's how we actively work to improve:

• Regular Audits: We conduct periodic accessibility reviews using both automated tools (Axe, WAVE, Lighthouse) and manual testing with assistive technologies.
• User Testing: We engage users with disabilities to test our platform and provide feedback on their real-world experience.
• Developer Training: Our development team receives regular training on WCAG guidelines, ARIA best practices, and inclusive design principles.
• Design Reviews: All new features and design changes undergo an accessibility review before deployment.
• Feedback Driven: Accessibility issues reported by users are prioritised in our development backlog and tracked to resolution.
• Third-Party Monitoring: We review the accessibility compliance of our third-party service providers annually.

We are transparent about areas where our platform does not yet fully meet WCAG 2.1 AA. Below are known gaps and our planned resolution timeline:

• Third-Party Payment Widget: The Razorpay checkout widget may have limited screen reader support for certain form interactions. Workaround: Contact our support team for assisted payment processing. Expected fix: Q2 2026 (pending vendor update).
• Complex Data Tables: Some financial statement tables may lack full header associations for screen reader row/column navigation. Fix timeline: Q1 2026.
• PDF Documents: Downloadable statements may not be fully tagged for screen reader access. Fix timeline: Q2 2026 — transitioning to accessible HTML statements.
• Legacy Admin UI: Internal administrative pages (not user-facing) currently have partial accessibility support. These are not part of the user-facing product.

Your feedback helps us make our platform more accessible for everyone. If you experience any barriers, please reach out:

• Email: shaport.suparbazaar.xyz (preferred — response within 48 business hours)
• Contact Form: suparbazaar.online/contact.php
• Website: https://suparbazaar.online/

When Reporting an Issue, Please Include:

• The page URL where you encountered the barrier
• A description of the accessibility issue
• The assistive technology and browser you are using
• Your preferred format for our response (email, phone call, etc.)

If you are not satisfied with our response to an accessibility concern, you may pursue the following escalation path:

1. Step 1 — Contact Us Directly: Email shaport.suparbazaar.xyz with "Accessibility Complaint" in the subject line. Include all relevant details.
2. Step 2 — Escalation Review: If unresolved within 10 business days, request escalation to our senior management team via the same email.
3. Step 3 — External Bodies (India): You may contact the Department of Empowerment of Persons with Disabilities (DEPwD) under the Ministry of Social Justice & Empowerment, Government of India, for formal complaints under the RPWD Act 2016.
4. Step 4 — Ombudsman / Consumer Forum: You may also approach the appropriate Consumer Disputes Redressal Commission if the matter relates to service denial based on disability.

Guidelines & Standards

• W3C Web Accessibility Initiative (WAI) — primary resource for web accessibility
• WCAG 2.1 Guidelines — full specification
• WebAIM — accessibility guides and contrast checker
• DEPwD India — Department for Persons with Disabilities

Free Screen Readers

• NVDA (Windows) — free, open-source screen reader
• VoiceOver — built into macOS/iOS (no download needed)
• TalkBack — built into Android (no download needed)
• Narrator — built into Windows (no download needed)

Browser Accessibility Settings

• Google Chrome Accessibility Features
• Firefox Accessibility Features
• Apple Accessibility Support

We review and update this Accessibility Statement regularly to reflect our ongoing improvements and any changes to our platform, services, or applicable standards.

• The "Last Updated" date at the top of this page is revised with every update.
• Significant changes (e.g., changes to our conformance level or known limitations) will be communicated via a notice on our platform.
• We aim to review this statement at least once every 6 months or after any major platform update.

We encourage you to bookmark this page and check back periodically. If you have questions about any recent changes, contact us at shaport.suparbazaar.xyz.

This Accessibility Statement is published in accordance with our legal obligations under the following Indian legislation and guidelines:

• Rights of Persons with Disabilities (RPWD) Act, 2016 — Section 46 mandates accessibility of ICT services
• National Policy on Universal Electronic Accessibility, 2013
• Information Technology (Intermediary Guidelines and Digital Media Ethics Code) Rules, 2021
• RBI Guidelines on Accessibility of Banking Services
• Web Content Accessibility Guidelines (WCAG) 2.1 by W3C — our technical benchmark

We are committed to making reasonable adjustments to ensure our financial services are accessible to persons with disabilities as required by law, and beyond — because inclusion is a core value, not merely a compliance obligation.