Accessibility statement

Our commitment to accessibility.

EquitableDocs exists to make documents accessible. Our own website must meet the same standards we apply to the documents we process. This page sets out the standards we follow, how we test against them, and how to report a problem if you find one.

01 Standards we follow

Three layers.

  • WCAG 2.2 Level AA (Web Content Accessibility Guidelines, October 2023). The international standard for web accessibility. The site is tested against the full 2.2 AA rule set, including the four new success criteria added in 2.2 (Focus Not Obscured, Dragging Movements, Target Size minimum, Redundant Entry, Accessible Authentication).
  • W3C COGA cognitive accessibility guidelines, ensuring the site works for people with learning disabilities, ADHD, dyslexia, and low digital literacy. COGA is not yet a formal WCAG conformance criterion, but it informs our design choices.
  • PDF/UA (ISO 14289) for all documents we produce. This is the standard for the documents we deliver to readers, not for the website itself.

02 What this means in practice

Concrete commitments.

  • Every page works with screen readers: NVDA, JAWS, VoiceOver, TalkBack.
  • Every page is fully navigable by keyboard alone, with a visible focus indicator on every interactive element.
  • All text meets minimum contrast ratios: 4.5 to 1 for body text, 3 to 1 for large text. Most palette pairs on this site exceed those minima.
  • All interactive targets are at least 24 by 24 CSS pixels (the WCAG 2.2 minimum).
  • All form fields have visible labels and associated for/id attributes. Required fields are marked in plain language, not by colour alone.
  • No content relies on colour alone to convey meaning.
  • No flashing content, no auto-playing media, no time limits.
  • Plain language throughout, at a Grade 6 to 8 reading level on body copy.
  • The site respects your browser settings for zoom, font size, and high-contrast mode. It uses system fonts, so any font preferences you have set (for example, a dyslexia-friendly font) are honoured.
  • A prefers-reduced-motion media query disables non-essential animation.
  • A forced-colors media query lets your operating system's colour scheme replace the page palette when high-contrast mode is on.

03 How we test

Four-layer testing strategy.

Documented in the testing playbook used across the project. Every page is checked against all four layers before it goes live.

  1. 01

    Static automated audit

    Pa11y CI against WCAG 2 AA, on every public page, every time a change is committed. Zero findings is the bar; pages do not ship with open issues.

  2. 02

    Keyboard scenarios

    Playwright keyboard tests cover tab order, focus visibility, skip-link target, form-field reachability, and submit-button position.

  3. 03

    Structural HTML audit

    Python checks for page-title uniqueness, viewport zoom support, tabindex misuse, link-text consistency, and CSS contrast pair sweep across the whole site.

  4. 04

    Real screen reader walk-through

    NVDA on Windows for periodic spot-checks. VoiceOver on Mac for the same. The thing automated tools cannot catch is what an assistive technology actually announces; only a real screen reader walk surfaces that.

04 Report a problem

If you find anything difficult to use, tell us.

We continuously test and improve. If any part of this website is difficult to use with your assistive technology, contact us. We respond within seven working days, fix the issue, and let you know when it is resolved.

Email: deepa@equitabledocs.org
Phone: +91 91100 41713

05 Last updated

12 May 2026.

This statement is reviewed and updated whenever the site's accessibility posture changes. The date above reflects the most recent review. Major changes since the previous review are recorded in the site repository's commit history.