01The standard we build to
We build to the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA, published by the W3C. It is the standard referenced by India's Guidelines for Indian Government Websites (GIGW 3.0) and by the European standard EN 301 549.
02What we do to meet it
Semantic structure
One heading hierarchy per page, landmarks, labelled regions, a skip link, and tables with header cells.
Contrast and type
Text colours drawn from a token set chosen for AA contrast; no text below 11px; layouts that reflow at 320px and 200% zoom.
Keyboard and focus
Every control is a real button or link, operable by keyboard, with a visible focus ring; tabs follow the ARIA pattern.
Motion and JavaScript
Reduced-motion preferences show finished states without loops; every page is complete and readable with JavaScript off.
Alternatives
Images carry text alternatives; decorative interface mock-ups are hidden from screen readers and described in a sentence instead.
Touch targets
Tap targets are at least 44 by 44 pixels, above WCAG 2.2's 24-pixel minimum (2.5.8).
03Conformance status
This website is partially conformant with WCAG 2.2 AA: we build and test to it, but some content may not yet fully conform, and it has not been independently audited.
| Check | How | Status |
|---|---|---|
| Automated checks | Browser tooling on every page before release | In place |
| Keyboard-only use | Manual pass on every template | In place |
| Screen readers | NVDA, VoiceOver on a sample of pages | Partial |
| Independent audit | Third-party WCAG 2.2 AA audit | Planned |
04Known limitations
These are the limitations we know about. We list them so you are not surprised by them.
- Animated demonstrations. Some service pages show looping interface mock-ups. They pause off-screen and stop under reduced motion, but there is not yet a pause control on every one (WCAG 2.2.2).
- Wide tables and diagrams. On phones some scroll sideways inside their own box rather than reflowing.
- Documents we link to. Third-party pages and any PDFs we did not produce may not meet the standard.
- Language. The site is in English only; we do not yet offer Hindi or Punjabi versions.
05Report a barrier
If anything on this site is hard to use, tell us. Fill in what you can — the button opens your email app with the report written. Without it, email connect@xterraedze.com.
If you need content from this site in another format — large print, plain text, or read aloud on a call — ask and we will provide it.
06How and when we review this
This statement was prepared on 24 September 2026 from our own testing. We will review it at every major release and at least every six months.
- Next review
- March 2027
- Method
- Self-assessment; independent audit planned