Home / Services / Cloud, cost and accessibility

Digital accessibility that works for every user, not just the checklist

By Mirav Labs, led by Deepak MittalUpdated
Short answer

Digital accessibility means people with disabilities can use your website or app on their own: by keyboard, with a screen reader, with captions, at high zoom. We audit against WCAG 2.2, rank the issues by severity and user journey, fix them in your code and design system, test with assistive-technology users, then add CI checks so new releases stay accessible.

Key takeaways

  • WCAG 2.2 is the current W3C Recommendation and the practical yardstick for web and app accessibility.
  • In India, the RPwD Act, its Rule 15, GIGW 3.0, IS 17802 and SEBI's 2025 circulars each cover different organisations, so map what applies to you.
  • Automated scanners find only part of the problem; keyboard, screen-reader and real-user testing find the rest.
  • Fix once in the design system and every screen built from it improves.
  • Accessibility holds only if CI checks, design rules and training stop regressions.

Accessibility is easy to talk about and hard to see from inside your team. Your developers use a mouse and a large screen. Your users include people who navigate by keyboard alone, listen to the page through a screen reader, read at 200% zoom, watch videos with the sound off, or use a phone with one hand. If a single button has no label or a form traps focus, that user cannot finish the task, and there is no workaround.

We are an engineering team. We find what blocks real users, fix it in your code and design system, and set up the checks that keep it fixed. We do not give legal opinions; we help your team meet the technical standard your counsel and regulators point to.

What accessibility means in practice

Most accessibility work comes down to a handful of everyday behaviours. These are the areas we check on every audit.

  • Keyboard. Every link, button, menu, date picker and modal can be reached and operated with the keyboard, in a sensible order, with no traps.
  • Visible focus. You can always see where you are. Focus is not hidden behind sticky headers or cookie banners.
  • Screen readers. Headings, landmarks, labels and roles tell a screen-reader user what each element is and what it does. Images carry useful text alternatives, and dynamic changes such as error messages are announced.
  • Contrast and zoom. Text and controls have enough contrast, and the layout still works when text is enlarged or the page is zoomed.
  • Captions and transcripts. Video has captions, audio has transcripts, and nothing important depends on sound or colour alone.
  • Forms. Every field has a label, errors say what went wrong and how to fix it, and sign-in does not depend on solving a puzzle or remembering a code.
  • Mobile. Accessible mobile apps have labelled controls, touch targets large enough to hit, alternatives to complex gestures, and support for the platform's own screen reader and text-size settings.

WCAG 2.2: the standard we test against

The Web Content Accessibility Guidelines are published by the W3C. WCAG 2.2 is a W3C Recommendation, organised under four principles with success criteria at three levels: A, AA and AAA. We usually test to Level AA. WCAG 2.2 adds nine success criteria to WCAG 2.1 and removes one, 4.1.1 Parsing. Because the guidelines are written to be technology-neutral, we apply them to websites, web apps, mobile apps and documents alike.

WCAG principleWhat it asksTypical failures we find
PerceivableUsers can perceive the content, whatever their senses.Images without text alternatives, low contrast, video without captions, meaning carried by colour only.
OperableUsers can operate every control and move through the page.Keyboard traps, missing or hidden focus, tiny touch targets, drag-only interactions, timeouts with no warning.
UnderstandableContent and behaviour are clear and predictable.Unlabelled fields, vague error messages, asking for the same data twice, sign-in that relies on memory tests.
RobustContent works with current and future assistive technologies.Custom widgets with no name, role or state; status messages screen readers never announce.

The Indian rules: who each one covers

Several instruments touch digital accessibility in India. They do not all apply to everyone, so the first step is to map which ones apply to your organisation. Here is what each one covers, in plain terms.

  • Rights of Persons with Disabilities Act, 2016. The Act requires the Central Government to make rules laying down accessibility standards, including for information and communication technology (section 40). Section 46 gives service providers, both government and private, two years from the notification of those rules to provide services in line with them.
  • Rule 15 of the RPwD Rules, 2017. Rule 15(1) sets the accessibility standards. For ICT it points to the guidelines for Indian government websites, requires documents on websites to be in ePUB or OCR-based PDF format, and, after later amendments, refers to IS 17802 for ICT products and services, as set out in the Supreme Court's judgment below.
  • Rajive Raturi v. Union of India. On 8 November 2024 the Supreme Court held that Rule 15(1) is ultra vires the RPwD Act because it relied on guidelines rather than a baseline of mandatory rules. It directed the Union Government to frame mandatory rules within three months, in consultation with stakeholders, and said progressive compliance with the existing standards must continue. The Department of Empowerment of Persons with Disabilities has since run a public consultation on draft accessibility standards for the ICT sector.
  • GIGW 3.0. The Guidelines for Indian Government Websites apply to government websites and apps at any organisational level, central and state, including district administrations and local governments. Their accessibility guidance is based on WCAG 2.1. If you build or run a portal for a government body, this is your baseline.
  • IS 17802. The Bureau of Indian Standards publishes IS 17802 (Part 1):2021, Accessibility for the ICT Products and Services: Requirements, with Part 2 covering how conformance is determined.
  • SEBI-regulated entities. SEBI's circular of 31 July 2025 requires its registered intermediaries and market infrastructure institutions to make their digital platforms meet WCAG 2.1 or later, GIGW, IS 17802 and the RPwD Act. It calls for an audit by IAAP-certified accessibility professionals that includes usability testing by persons with disabilities, a remediation plan, annual audits, and accessibility requirements in procurement. SEBI has issued compliance guidelines and later clarifications.
  • RBI payment systems. The RBI's guidelines of 11 October 2024 ask banks and non-bank payment system providers to review their payment systems and devices for accessibility and make the changes needed, without compromising security.

If you are a private company outside these regulated groups, treat WCAG 2.2 AA as your technical target and ask your counsel how the RPwD Act and any new rules apply to you. Our job is to make the product meet the standard, and to give your team evidence of what was tested and fixed.

How an audit and fix programme runs

We run accessibility as an engineering programme in five steps. Each step produces something your team can use, even if you stop there.

How we make websites and apps work for everyoneAudit to keep it accessible
Step 1Audit

Automated, manual and screen-reader checks

Step 2Prioritise

By severity and by user journey

Step 3Fix

In code, design system and content

Step 4Test with people

Users of assistive technology

Step 5Keep it accessible

Checks in CI, rules, training

Now:

1. Audit

We agree a sample: your key templates and the journeys that matter most, such as sign-up, KYC, search, checkout, booking or a claim form. We run automated scans across the sample, then check each journey by hand against WCAG 2.2: keyboard only, at high zoom, with contrast tools, and with screen readers on desktop and mobile. Screen reader testing is where most of the serious blockers surface, so we do it on every journey, not as an extra.

2. Prioritise

A long list of issues helps nobody. We rank each finding by severity (does it block the task, slow it down or just annoy?) and by user journey, so a missing label on the payment button comes before a decorative image on the About page. Each issue gets the WCAG criterion, the affected screens, a recording or screenshot, and a suggested fix.

3. Fix

We fix in three places. In code, we correct semantics, labels, focus handling and announcements. In the design system, we repair shared components such as buttons, modals, tabs and form fields, so every screen built from them improves at once. In content, we work with your editors on alt text, headings, link text, captions and accessible documents. Your developers can make the fixes with our guidance, or we can pair with them and raise pull requests.

4. Test with people

Tools and expert reviewers cannot stand in for lived experience. We run task-based sessions with users of assistive technology, such as screen-reader users, people with low vision and people who use keyboard or switch access, on the fixed journeys. What they find goes back into the fix list.

5. Keep it accessible

Accessibility decays with every release unless something stops it. We add automated accessibility checks to your CI pipeline, write accessibility rules into the design system and its documentation, add accessibility to your definition of done, and train designers, developers, testers and content editors on what to look for. A periodic re-audit confirms the work is holding.

What you get

DeliverableWhat it containsWho uses it
Applicability mapWhich standards and rules apply to your organisation and products, with sources, for your counsel to confirm.Compliance, legal, leadership
Audit reportFindings mapped to WCAG 2.2 criteria, by journey and screen, with evidence and suggested fixes.Product, engineering
Prioritised backlogIssues ranked by severity and journey, ready to import into your tracker.Engineering managers
Fixed components and codePull requests or pairing on components, templates and pages.Developers, design system team
User testing summaryWhat assistive-technology users could and could not do, and what changed.Product, UX
CI checks and design rulesAutomated tests in your pipeline, component accessibility notes, and a definition of done.Engineering, design
Accessibility statement draftA plain-language statement of what conforms, known gaps and how users can report problems.Product, compliance

Accessibility and the rest of your stack

Accessibility work often touches the same flows as your privacy and security work: consent screens, sign-in, KYC and third-party scripts. Consent notices need to be accessible too, which our privacy engineering team checks. Third-party widgets for chat, payments or captcha are a common source of accessibility failures, and we review them alongside the API and supply-chain inventory.

Where teams usually go wrong

  • Relying on an overlay or a scanner score. A green score from an automated tool does not mean a screen-reader user can pay a bill. Test the journeys.
  • Fixing pages, not components. If the modal component traps focus, fixing it on one page leaves it broken on forty others.
  • Leaving mobile out. Many Indian users reach you first through an app. Audit the app with the same care as the website.
  • Forgetting documents and media. Scanned PDFs, image-only circulars and uncaptioned videos block users as surely as a broken button.
  • Treating it as a one-off project. Without CI checks and training, the next redesign undoes the work.

How to start

Pick the two or three journeys that matter most to your users and your regulators. We will scope an audit around them, agree the sample and timeline, and share findings journey by journey as we go. From there you can fix in-house with our backlog, or have us work alongside your developers until the journeys pass and the checks are in CI. Tell us about your websites and apps and we will suggest a starting scope.

Frequently asked questions

Is WCAG compliance mandatory in India?

It depends on who you are. Government websites and apps follow GIGW 3.0, which is based on WCAG 2.1. SEBI-regulated entities must meet WCAG 2.1 or later, GIGW and IS 17802 under SEBI's July 2025 circular. Other organisations should look at the RPwD Act, 2016 and Rule 15 of its rules with their own counsel, since the Supreme Court has directed the government to frame mandatory accessibility rules.

What is the difference between WCAG 2.1 and WCAG 2.2?

WCAG 2.2 adds nine success criteria to 2.1, covering areas such as focus that is not hidden, target size, dragging movements, redundant entry and accessible authentication. It also removes 4.1.1 Parsing. W3C states that content conforming to WCAG 2.2 also conforms to 2.1 and 2.0, though teams bound by a 2.1 policy may still need to test 4.1.1.

How long does a website accessibility audit take?

For a typical site or app, we scope an audit around a sample of templates and your key user journeys rather than every page. The time depends on how many journeys, platforms and languages are in scope, and a large portal with several apps takes longer than a single site. We agree the sample and timeline with you before we start.

Can automated accessibility testing tools make my site compliant?

No. Automated scanners catch issues such as missing alt text, low contrast and empty labels, but they cannot judge whether alt text is meaningful, whether focus order makes sense or whether a screen-reader user can finish checkout. You need manual and assistive-technology testing as well.

How do you test a mobile app for accessibility?

We test on real devices with the built-in screen readers on iOS and Android, with large text and display zoom, with switch and keyboard access, and in both orientations. We check labels, touch target sizes, gesture alternatives and focus order on each key screen, and map findings to WCAG.

What is GIGW 3.0?

GIGW 3.0 is the current version of the Guidelines for Indian Government Websites, published on guidelines.india.gov.in. It applies to Indian government websites and apps at central, state, district and local levels, and its accessibility requirements are based on WCAG 2.1.

Scope it with us

A 30-minute call to understand your systems and what good looks like. We aim to send a written, fixed-scope proposal within three working days.

Talk to us

Related services

This page describes engineering and security services. Where it mentions laws, rules or standards, it is general information, not legal advice.

Talk to us