Commitment

Accessibility Statement

Last updated: 19 April 2026

Secure IT Technologies is committed to making secure-it.tech accessible to everyone, including people with visual, auditory, motor, or cognitive differences. This statement describes our current status, known gaps, and how to reach us if you encounter an accessibility barrier.

1. Conformance target

We aim for conformance with the Web Content Accessibility Guidelines 2.1, Level AA (WCAG 2.1 AA), and for compliance with India's Rights of Persons with Disabilities Act, 2016 and related government accessibility guidelines.

2. Current status

At the date above, the Site is partially conformant with WCAG 2.1 AA. Core content is navigable by keyboard, screen readers receive meaningful structure (semantic landmarks, form labels, and aria-label / aria-hidden where relevant), colour contrast meets AA for body copy, and motion-rich effects respect prefers-reduced-motion.

3. Known limitations

  • Hero canvas animation. The network graph, attack arcs, shield, and radar on the homepage are decorative; they are marked aria-hidden="true" and are automatically disabled for users with prefers-reduced-motion: reduce.
  • SOC dashboard rotator. The multi-slide SOC card auto-rotates. Screen readers skip it (marked decorative). Mouse and touch users can click the pagination dots to navigate manually; keyboard navigation of the rotator is on our roadmap.
  • Form validation. Error and status messages use role="status" and aria-live="polite" so screen readers announce them. We continue to improve inline validation granularity.
  • Embedded third parties. Cloudflare Turnstile renders inside an <iframe> controlled by Cloudflare; its accessibility is determined by Cloudflare.

4. What we do

  • Test pages with WAVE, axe DevTools, and manual keyboard navigation on a regular cadence.
  • Verify colour contrast with automated tooling on every design change.
  • Respect user preferences: prefers-reduced-motion, prefers-color-scheme (coming), and system font sizing.
  • Use semantic HTML first, ARIA only where native semantics aren't enough.

5. Assistive technology we test against

  • VoiceOver (macOS Safari, iOS Safari)
  • NVDA (Windows Chrome, Firefox)
  • Keyboard-only navigation
  • 200% browser zoom

6. Reporting accessibility issues

If you encounter a barrier on the Site or need content in an alternative format, please let us know:

Please tell us the page, the issue, the assistive technology you're using, and any error messages. We aim to respond within 5 business days and to fix qualifying issues within 30 days.

Accessibility is an ongoing effort. Thank you for helping us improve.