Accessibility statement
Our commitment to an accessible website, what we've tested, and how to tell us about a barrier.
Last reviewed: October 2026
Our commitment
We are committed to improving the accessibility of our website and aim to conform with the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA. We want everyone to be able to use this website, including people who use screen readers, keyboard navigation, magnification, voice control or other assistive technologies.
Accessibility features
- Keyboard accessibility: every link, button, menu, accordion and form control can be used with a keyboard. A "Skip to main content" link appears first on every page.
- Screen reader compatibility: pages use semantic HTML, landmarks, a logical heading structure, labelled form fields and correct names, roles and states for interactive controls.
- Text alternatives: decorative images and icons are hidden from assistive technology; the logo has an accessible name.
- Colour and contrast: text meets at least 4.5:1 contrast, and interface components and focus indicators meet at least 3:1. Information is never conveyed by colour alone.
- Focus indicators: a thick, high-contrast outline shows keyboard focus, and the sticky header never covers the focused element.
- Responsive design: the layout adapts from 320-pixel-wide screens to large displays, and supports 200% and 400% zoom without loss of content.
- Forms: visible labels, autocomplete, clear instructions, an error summary and field-level error messages.
- User preferences: support for reduced motion and Windows High Contrast (forced colours). No autoplaying media, carousels, CAPTCHAs or time limits.
How we tested
- Automated testing of every page with axe-core (WCAG 2.0, 2.1 and 2.2 A and AA rules) at mobile and desktop sizes
- Keyboard testing with Tab, Shift+Tab, Enter, Space and Escape
- Layout checks at 320, 375, 768, 1024, 1280 and 1440 pixels wide, and in forced-colours mode
- Colour contrast calculations for every colour pair
Known limitations
- This website has not yet been tested with the NVDA, JAWS, VoiceOver or TalkBack screen readers on real devices. We plan to complete this testing and will update this statement.
- Some About page content is still being prepared and is marked as a placeholder.
- If JavaScript is turned off, forms use the browser's built-in error messages instead of our error summary.
Feedback and reporting an accessibility issue
If you find any barrier on this website, please tell us. Describe the page, what you were trying to do, and the device, browser and assistive technology you used.
- Email: hariharasatish@inclusafetech.com
- Contact form: contact us
We aim to reply within 2 working days and to fix confirmed issues as quickly as possible. If you need information from this website in a different format, ask and we'll provide it.