Accessibility Statement

Our conformance target, an honest account of where we currently fall short of it, and a way to tell us when we have got it wrong.

1. Our commitment

DECTIFY builds systems that people rely on at work, often under time pressure and often at night. An interface that excludes an operator is a safety problem before it is a compliance problem. We treat accessibility as part of engineering quality rather than as a remediation exercise.

This statement covers the DECTIFY website at dectify.in and the DECTIFY HUB web application. It does not cover third-party content embedded from other providers, which we identify in section 5.

2. Conformance status

We target Web Content Accessibility Guidelines (WCAG) 2.2 Level AA.

Our current status is partially conformant: most of the standard is met, but some content does not yet fully conform. "Partially conformant" is the accurate description and we prefer it to a claim we cannot substantiate. The specific gaps are listed in section 4.

3. What we have built in

• Keyboard operation. All interactive controls are reachable and operable by keyboard, with a visible focus indicator meeting the WCAG 2.2 focus appearance criteria, and a skip link to main content on every page.
• Structure. Semantic headings in order, landmark regions, labelled form controls, and tables with proper header associations.
• Names, roles and values. Custom components expose accessible names and states to assistive technology; live regions announce alerts and status changes.
• Contrast. Body text and interface controls meet at least 4.5:1, and large text at least 3:1, against their backgrounds in both the default and high-contrast themes.
• Not by colour alone. Alert severity, match confidence and system status are conveyed by shape, label and position in addition to colour.
• Reduced motion. The site and application respect prefers-reduced-motion; every transition, reveal and parallax effect is disabled when it is set.
• Resize and reflow. Content reflows to a 320 CSS pixel viewport width without loss of function and supports 200% text scaling and 400% zoom.
• Time limits. Session timeouts warn before expiry and can be extended. No essential task is under a timer that cannot be adjusted.
• Target size. Interactive targets meet the 24 by 24 CSS pixel minimum introduced in WCAG 2.2.

4. Known limitations

These are the areas where we do not currently meet our target. We publish them because a conformance claim without a gap list is not informative.

5. Third-party content

Some content is supplied by third parties and is outside our direct control — embedded video, map tiles, and certain documentation widgets. We assess these before adoption, raise defects with the vendor, and will replace a component that cannot be remediated. Where a third-party component blocks a task, tell us and we will provide the information another way.

6. Assessment approach

We combine automated testing in continuous integration (axe-core on every pull request, blocking on new violations), manual keyboard-only testing of each release, screen reader testing with NVDA on Windows, VoiceOver on macOS and iOS, and TalkBack on Android, and periodic review by an external specialist. Findings are tracked in the same backlog as functional defects, with accessibility defects triaged at the same severity as functional ones.

7. Compatibility

The website and HUB are designed to work with current versions of Chrome, Edge, Firefox and Safari, together with NVDA, JAWS, VoiceOver, TalkBack, Dragon NaturallySpeaking, and operating system magnification and high-contrast modes. They are not tested against browsers more than two major versions old.

8. Feedback, and what we will do with it

If you meet a barrier, tell us at accessibility@dectify.in. Include the page or screen, what you were trying to do, and the assistive technology and browser you were using, if you know them.

• We acknowledge within 2 business days.
• We give a substantive response, including whether we can fix it and by when, within 10 business days.
• If we cannot fix it quickly, we provide the information or function another way in the meantime, at no cost to you.

If you are not satisfied with our response, escalate through Grievance Redressal. Country-specific statutory routes are set out at India Accessibility and Inclusion and Australia Accessibility and Inclusion.

9. Formal approval and review

This statement was prepared following the W3C Accessibility Statement Generator model, is approved by [named officer and title], and is reviewed at least quarterly and on every major release. The version and effective date at the top of this page reflect the most recent review.