Our commitment
আমাদের প্রতিশ্রুতি
help@tenderpulse.com.bd; আমরা ৭ দিনে response করব।TenderPulse aims to provide a service that meets the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA standard. WCAG 2.1 AA We treat accessibility as a feature requirement on every shipped change, not as a polish pass at the end of a quarter.
We are aware that AA compliance is a moving target — both because the standards evolve (WCAG 2.2, EN 301 549) and because our product evolves. The accuracy of this statement is aspirational on the day it is published; the gap analysis below is honest about where we fall short.
What works well today
যা ভালো কাজ করে
The areas where we currently meet or exceed WCAG 2.1 AA:
- Keyboard navigation — every interactive element is reachable and operable from the keyboard alone. Skip-to-main-content links are present at the top of every page.
- Screen reader compatibility — tested on NVDA (Windows), VoiceOver (macOS / iOS), and TalkBack (Android). Form fields have explicit labels, ARIA landmarks structure each page, and live-region announcements report asynchronous state changes.
- Color contrast — body text and UI controls meet the 4.5:1 contrast ratio. Critical actions meet the 7:1 enhanced ratio.
- Focus indication — visible focus rings are preserved on every interactive element with sufficient contrast against the background.
- Reflow and zoom — content remains usable at 320 CSS pixel width without horizontal scrolling, and scales up to 200% without loss of content or functionality.
- Bilingual labelling — Bangla translations sit alongside English labels using the
lang="bn"attribute so screen readers pronounce them correctly.
Known issues and remediation timeline
জানা সমস্যা ও remediation
help@tenderpulse.com.bd)। আমরা list-এ যোগ করব।The accessibility issues we are currently tracking, with target remediation dates:
| Surface | Issue | Severity | Target |
|---|---|---|---|
| /tenders/[id]/copilot | Streaming AI response does not announce intermediate chunks to screen readers; user only hears the final message. | Medium | 2026-Q3 |
| /tenders/upload (drag-drop) | Drag-and-drop ZIP upload has a keyboard-accessible fallback (file picker) but the drop zone’s success state is not announced via live region. | Medium | 2026-Q3 |
| /pricing (tier comparison) | Comparison table lacks scope attributes for column- level header association; works visually but is harder for screen readers in linear table mode. | Low | 2026-Q4 |
| Bangla pdf exports | Generated PDF exports contain Bangla glyphs but lack proper PDF/UA tagging — screen readers can read English metadata but not the body. | High | 2026-Q4 |
| /onboarding (date picker) | Custom date picker uses keyboard navigation but does not announce selected date in some screen readers (NVDA + Firefox combination). | Medium | 2026-Q3 |
Severity classifications follow a four-tier scale. Critical (the surface is unusable for the affected technology) is patched within 30 days as an in-quarter override. High (the surface is usable but with significant friction) is targeted for the current quarter. Medium and Low follow normal roadmap planning.
Conformance audit and methodology
Audit methodology
Our internal pipeline runs axe-core and Pa11y automated checks on every pull request affecting frontend code. Findings labelled critical or serious block merge until resolved. Automated tools catch only a fraction of accessibility issues — typically 30-40% — so we layer additional manual review on top.
Annually, we engage an independent accessibility consultancy to conduct a full WCAG 2.1 AA audit covering the marketing site and the authenticated application. The most recent audit was completed in 2026-02. The next is scheduled for 2027-02. Audit reports are not published in full (they list specific attack-surface details that we treat as security-relevant), but enterprise customers under NDA can request a copy.
User-research sessions with assistive-technology users are conducted at least twice per year. Findings from these sessions feed directly into the issue list in §3.
Surfaces explicitly out of scope
যা scope-এ নয়
Some surfaces are explicitly out of the scope of this statement:
- Customer-uploaded files — tender ZIPs, PDFs, spreadsheets uploaded by the customer. We render these as faithfully as we can but cannot retrofit accessibility into arbitrary third-party content.
- Third-party external links — links to CPTU, Bangladesh Bank, EPS, donor agencies. We are not responsible for the accessibility of pages we do not control.
- Archived versions of legal documents — earlier versions in our changelog history are preserved for audit purposes; the current version is the one we maintain to AA standard.
- Beta features labelled as such in the UI may ship with known accessibility gaps that are documented as part of the beta-release notes; we hold beta features to AA within 30 days of general availability.
Alternative formats and direct help
Alternative format
If a TenderPulse surface presents an accessibility barrier you cannot work around, we will provide the underlying information in an alternative format on request:
- Phone walkthrough by a TenderPulse support representative (Bangla or English)
- Email-based document review with descriptions of any visual content
- Audio recording of the relevant document or page content
- Plain-text export of any UI surface where the visual structure is the barrier
- One-on-one onboarding session by video call with screen- reader-friendly walkthrough
These services are free and unconditional. Email help@tenderpulse.com.bd and we will arrange.