Accessibility statement

• //Every interactive element is keyboard operable, with a visible focus ring in the active accent colour.
• //Text contrast is checked to at least 4.5:1, and against images we apply a scrim rather than hoping.
• //Accordions, dialogs and comparison sliders use native elements where they exist, so platform semantics come for free.
• //All motion is disabled under prefers-reduced-motion, with elements rendering in their final state instantly.
• //Headings follow a single logical outline; one h1 per page.
• //Icons that sit beside a text label are hidden from assistive technology so labels are not announced twice.

Automated axe-core checks run in CI against key pages. Automated testing catches perhaps 40% of real barriers, so we also do keyboard-only walkthroughs of the main journeys.

We would rather list these than claim they do not exist:

• //Screen-reader testing so far is with VoiceOver on macOS and iOS. NVDA and JAWS testing on Windows is not yet complete.
• //The architecture diagrams collapse to an ordered list below tablet width. The list is accurate but conveys the sequence rather than the full topology.
• //Long spec tables scroll horizontally inside their own container on narrow screens.

Email sales@vconnectservices.co.in with the page and what happened. We treat access barriers as defects, not enhancement requests, and will tell you a fix date rather than thanking you for the feedback.