Commitment and target
This is a working draft. The website is designed toward WCAG 2.2 Level AA, including keyboard access, visible focus, semantic structure, labelled forms, clear status messages, sufficient colour contrast, reduced-motion support and reflow on small screens. This wording is a goal, not a certification of conformance. Before launch, representative pages and every form path should be checked with automated tools, keyboard-only use, screen-reader sampling, text zoom and mobile reflow. Any known limitation should be recorded here with a practical alternative and expected review date. People who encounter a barrier may use the published contact route; the owner must confirm the accessible, monitored mailbox and response process before publication.
The design and engineering target is the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA across every public page and enquiry path. That target is a product requirement, not a statement that an external assessor has certified this pre-launch build.
Measures included in this build
- semantic page landmarks, logical heading structures, descriptive page titles, and a skip link;
- keyboard-operable navigation, accordions, links, controls, and visible focus styles;
- labelled form fields with inline instructions, field errors, and live status messages;
- minimum 44 by 44 CSS-pixel primary targets and layouts intended to reflow at 320 CSS pixels;
- contrast-aware colour roles that do not rely on colour alone for meaning;
- reduced-motion support, no autoplay media, no essential carousel, and no hover-only task;
- plain English, meaningful link labels, and captions for representative product diagrams; and
- system-font fallbacks that include Bangla-capable families for a future reviewed edition.
Compatibility
The site is intended to work with current versions of major browsers, keyboard-only input, browser zoom, and common screen-reader/browser combinations. Public content remains present as semantic HTML if JavaScript is unavailable; JavaScript adds form status and validation convenience but is not the only submission path.
The final acceptance baseline must record the actual browser, operating-system, device, and assistive-technology versions tested. Older software should degrade to readable content rather than a blank application shell.
Known limits and testing still required
At this pre-launch stage, the implementation has not completed the full WCAG Evaluation Methodology process, representative-user validation, NVDA testing on Windows, or a formal audit by an independent accessibility specialist. Production CMS authentication is also not active, so its accessibility has not been accepted.
Before public launch, every unique component and complete form process should receive automated checks plus manual keyboard, VoiceOver, NVDA, 200% zoom, 320-pixel reflow, high-contrast, reduced-motion, and slow-connection testing. Any confirmed barrier must be fixed or listed here with an accessible alternative and review date.
Report an accessibility barrier
If something prevents you from reading content or completing a task, email arnish.cse.sdcs@gmail.com with “Accessibility feedback” in the subject. If possible, include the page, what you were trying to do, the browser or assistive technology used, and the format that would work better. Do not include sensitive personal information.
This mailbox is a provisional direct route. The owner must confirm that it is monitored and publish a realistic response target before launch. You can also use the general contact route.
Preparation of this statement
- Statement version
- Pre-launch working draft
- Last reviewed
- 2026-09-09
- Assessment method
- Implementation review and automated build checks to date; formal WCAG-EM audit pending
- Responsible organisation
- To be confirmed with the final Impact Sol. legal identity