The commitment
Useful technology must remain usable under real conditions.
Accessibility includes permanent, temporary, and situational needs: keyboard use, screen magnification, screen readers, reduced motion, high contrast, limited bandwidth, touch input, small displays, cognitive load, and changing environments.
Every important interaction should have a semantic, readable fallback, and visitors should remain in control of motion and visual intensity.
Implemented support
What the current experience is designed to provide.
- StructureSemantic headings, landmarks, lists, fieldsets, legends, labels, and ordinary links/forms.
- NavigationSkip link, visible keyboard focus, logical source order, and no pointer-hover-only path.
- Touch and zoomPrimary controls target at least 44 CSS pixels and layouts reflow for tablet and mobile.
- ColorApproved text/action contrast, redundant status language, and forced-color opt-in for key surfaces.
- MotionSystem reduced-motion support plus a device-local explicit Reduce Motion preference.
- RecoveryNative validation, visible errors/status, truthful empty states, and no destructive action hidden behind animation.
Visitor control
Experience controls travel with the public and client experience on this device.
Respects the operating system’s reduced-motion choice where supported.
Explicitly suppresses decorative transitions and animated movement.
Uses the approved restrained depth and signal treatment.
Removes nonessential glow, gradients, and atmospheric background intensity.
These preferences are stored only in this browser’s local storage. They are not an account setting or analytics identifier.
Honest limitations
Automated checks help; they do not replace people using assistive technology.
The codebase includes semantic, contrast, responsive, reduced-motion, forced-color, rendered-route, and keyboard/touch contracts. Before production release, Dhivora still requires manual VoiceOver and NVDA review, 200% and 400% zoom, operating-system high contrast/forced colors, physical mobile input, orientation, virtual-keyboard, and browser-matrix testing.
No WCAG conformance certification or independent accessibility audit is claimed on this page.
Report a barrier
Describe the blocked outcome, not private personal details.
Email contact@dhivora.com and describe the page, what you were trying to do, and the device or assistive technology you were using. A barrier is treated as a defect, because it is one.
Anonymous reporting is no longer possible: the intake that offered it was retired, and email necessarily carries your address. If that matters to you, use any address you like — nothing is verified and nothing is stored beyond the mailbox itself.
A reply is not promised and there is no remediation date.