Our commitment
ajaykajla.in is committed to ensuring digital accessibility for people with disabilities. We are continually improving the user experience for everyone and applying relevant accessibility standards.
We take a practical approach: where a standard can be met without compromising the design, we implement it. Where design and accessibility trade-offs exist, we resolve them in favour of accessibility — a visually impaired user missing a feature is not an acceptable compromise.
This site targets WCAG 2.1 Level AA conformance. We review our accessibility status every six months and after any major redesign.
What we've built in
The following accessibility features are intentionally designed into this site:
Keyboard navigation
All interactive elements — links, buttons, forms, menus — are reachable and operable using a keyboard alone. Focus order follows a logical visual sequence.
Focus indicators
Visible focus rings are shown on all interactive elements. We do not suppress :focus-visible styles.
Colour contrast
Body text and interactive labels meet a minimum 4.5:1 contrast ratio against their background. Large headings meet 3:1.
Semantic HTML
We use landmark roles (nav, main, footer), heading hierarchy, and descriptive link text throughout.
Reduced motion
All animations and transitions are suppressed when prefers-reduced-motion: reduce is set in the visitor's system preferences.
Resizable text
Text can be resized up to 200% using browser zoom without loss of content or function. We use relative units throughout (rem, em, clamp).
Technical approach
This site is built with standard HTML, CSS, and vanilla JavaScript — no heavy framework dependencies that could interfere with assistive technology parsing.
- ARIA attributes — used judiciously for dynamic components (navigation menus, expanded/collapsed states) where native HTML semantics are insufficient.
- Alt text — all meaningful images carry descriptive
altattributes; decorative elements usearia-hidden="true". - Form labels — every form input is explicitly labelled. Error messages are programmatically associated with their fields.
- Link purpose — links are descriptive in context. We avoid ambiguous labels like "click here" or "read more" without surrounding context.
- Language declaration —
lang="en"is set on the HTML element on every page.
We test using keyboard-only navigation and with VoiceOver (macOS/iOS) and NVDA (Windows). We run periodic automated checks using axe-core.
Known limitations
Despite our efforts, some areas do not yet fully meet WCAG 2.1 Level AA. We document them honestly here:
Decorative page-transition animations+
The animated page transition (the brand overlay that plays between pages) plays even when prefers-reduced-motion is respected for content animations but not yet for this specific transition layer. Fix is in progress — target: Q3 2026.
Navigation submenu on mobile+
The "Services" dropdown submenu in the navigation is fully keyboard-accessible on desktop but requires improvement on touch-only devices where hover-intent is not available. We are exploring a tap-to-expand approach.
Animated hero graphics+
Some decorative animated elements on service pages (ticker tapes, floating cards) have ARIA roles but may announce redundant information to screen readers on certain browser/AT combinations. These are being audited page by page.
Embedded maps and third-party content+
Where third-party embeds are present, we cannot guarantee their conformance. We provide text-based alternatives (address, coordinates) adjacent to any map visual.
Feedback & contact
If you experience an accessibility barrier on this site — a page you cannot navigate, a form you cannot complete, content you cannot read — we want to know immediately.
We also welcome positive feedback and suggestions. Accessibility improvements often come from the people who rely on assistive technology every day.
Report a barrier or ask for help
We aim to respond within 4 working hours and provide an accessible alternative within 2 working days if we cannot fix the issue immediately.
Formal complaint process
If you have reported an accessibility issue and are not satisfied with our response, you may escalate through the following steps:
- Step 1 — Email hello@ajaykajla.in with "Accessibility complaint" in the subject line. Include the page URL, the issue, and the assistive technology you are using.
- Step 2 — We will acknowledge within 24 hours and provide a resolution timeline. Complex issues will be escalated internally.
- Step 3 — If unresolved within 30 days, you may contact the Ministry of Electronics and Information Technology (India) or the relevant accessibility authority in your jurisdiction.
This statement was prepared on 21 May 2026 and will next be reviewed by November 2026.