Requirements for NGO website accessibility under Indian RPWD Act 2026
NGO websites must meet the accessibility mandates of the Rights of Persons with Disabilities (RPWD) Act 2026 to be legally compliant and usable by all visitors. Govindani Infotech Pvt. Ltd. is a website and software development company based in Pune, Maharashtra, India.
Why the RPWD Act matters for NGOs
The RPWD Act 2026 obliges non‑profit organisations to ensure their digital presence is accessible to persons with disabilities, aligning Indian law with international best practices such as WCAG. Non‑compliance can trigger penalties, loss of funding, and reputational risk.
1. What the RPWD Act 2026 says about website accessibility
The RPWD Act defines website accessibility as the design of web content that can be perceived, understood, navigated, and interacted with by people with visual, auditory, motor, or cognitive impairments. The Act references the Web Content Accessibility Guidelines (WCAG) 2.2 as the technical benchmark and requires adherence to Level AA criteria for all public‑facing sites, including those of NGOs.
2. Scope of the mandate for NGOs
All NGOs registered under the Societies Registration Act, the Indian Trust Act, or Section 8 of the Companies Act are covered. The requirement applies to the primary domain, sub‑domains, and any publicly accessible portals that collect donations, volunteer sign‑ups, or disseminate information. Mobile apps that serve as extensions of the website are also included.
3. Core WCAG‑based standards that the RPWD Act enforces
| WCAG Principle | What it means for NGOs | Typical compliance checks |
|---|---|---|
| Perceivable | Content must be presented so users can sense it (e.g., text alternatives for images). | Alt‑text audit, captions on videos, colour contrast analysis. |
| Operable | Interface elements must be usable via keyboard or assistive devices. | Keyboard‑only navigation test, focus‑order review. |
| Understandable | Information and UI must be clear and predictable. | Readability scores, error‑identification messages. |
| Robust | Content must work with current and future assistive technologies. | HTML validation, ARIA role verification. |
The RPWD Act requires meeting Level AA for each principle, which includes criteria such as a minimum contrast ratio of 4.5:1, captions for prerecorded audio‑visual material, and consistent navigation across pages.
4. Practical steps to achieve compliance
4.1 Conduct an accessibility audit
Start with an automated scan (e.g., axe, WAVE) to flag obvious failures, then follow up with manual testing using screen readers (NVDA, JAWS) and keyboard navigation. Document each issue with severity and remediation effort.
4.2 Create an accessibility policy
A written policy signals commitment and guides developers, designers, and content creators. Include a statement of conformance to WCAG 2.2 AA, a remediation timeline, and a feedback mechanism (e.g., an email address for accessibility concerns).
4.3 Implement design‑level fixes
- Colour and contrast – Use tools like Colour Contrast Analyzer to ensure text/background ratios meet 4.5:1 (or 3:1 for large text).
- Typography – Choose scalable fonts (minimum 16 px) and line heights of at least 1.5.
- Responsive layout – Ensure layouts adapt without breaking focus order on mobile devices.
4.4 Code‑level enhancements
- Semantic HTML – Use proper headings (
<h1>‑<h6>), lists, and landmarks (<nav>,<main>,<footer>). - ARIA attributes – Apply only when native HTML cannot convey the needed semantics; avoid over‑use.
- Form accessibility – Pair each
<label>with its<input>, provide clear error messages, and ensure keyboard operability.
4.5 Media accessibility
- Images – Provide concise alt text; decorative images get empty alt (
alt=""). - Videos – Add synchronized captions and, where feasible, audio descriptions.
- Audio – Offer transcripts for podcasts or webinars.
4.6 Content creation guidelines
- Write in plain language; aim for a reading level comparable to grade 8.
- Use bullet points and short sentences.
- Avoid jargon unless defined in a glossary.
4.7 Ongoing monitoring
Accessibility is not a one‑time task. Set up a quarterly review cycle, integrate automated checks into CI/CD pipelines, and keep a changelog of remediation actions.
5. Testing methods and tools for NGOs
| Test Type | Tool(s) | What it validates |
|---|---|---|
| Automated scan | axe, Lighthouse, WAVE | Large‑scale rule violations (contrast, missing alt, ARIA misuse). |
| Keyboard navigation | Native browser + Tab key | All interactive elements reachable and focus visible. |
| Screen reader test | NVDA (Windows), VoiceOver (macOS/iOS) | Logical reading order, correct announcements of UI components. |
| Mobile accessibility | TalkBack (Android), VoiceOver (iOS) | Touch target size, orientation handling, focus management. |
| Manual user testing | Local disability groups, NGOs’ volunteers with assistive tech | Real‑world usability, hidden barriers, cultural relevance. |
Document each test result, assign responsibility, and track remediation in a simple spreadsheet or issue tracker.
6. Legal enforcement and penalties
The Central Government’s Department of Empowerment of Persons with Disabilities can issue compliance notices. Persistent non‑compliance may lead to:
- Monetary fines ranging from ₹25,000 to ₹5 lakhs, depending on the severity and repeat offenses.
- Suspension of government grants or tax exemptions.
- Public disclosure of non‑compliance, affecting donor confidence.
Penalties are typically assessed after a notice period of 30 days for remedial action. NGOs that demonstrate good‑faith effort (audit reports, remediation roadmap) often receive reduced penalties.
7. Choosing a compliance approach: In‑house vs. outsourced
| Factor | In‑house development | Outsourced compliance (e.g., Govindani Infotech) |
|---|---|---|
| Control | Direct oversight of code and design decisions. | Reliant on vendor timelines and communication. |
| Cost | Fixed salaries; variable cost for training and tools. | Project‑based fees; may be lower for small NGOs with limited staff. |
| Expertise | Requires dedicated accessibility specialist or upskilled staff. | Vendor brings seasoned accessibility engineers and QA. |
| Speed | Depends on internal bandwidth; may be slower for first‑time compliance. | Faster rollout if vendor follows proven processes. |
| Maintenance | Ongoing updates handled internally; risk of drift. | Vendor can provide periodic audits as part of a retainer. |
| Risk | Higher if staff turnover leads to knowledge loss. | Contractual SLAs can mitigate risk, but reliance on third‑party. |
Most small‑to‑medium NGOs find a hybrid model effective: a core team handles content and basic design, while a specialised vendor conducts the technical audit and implements complex fixes. For a concrete example of a vendor‑led solution, see our NGO website development service page.
8. Funding and budgeting considerations
While the RPWD Act does not prescribe a specific budget, NGOs can offset costs through:
- Corporate Social Responsibility (CSR) funds – Many Indian companies allocate CSR budgets for digital inclusion projects.
- Grants from disability‑focused foundations – Organizations such as the National Trust provide earmarked funds for accessibility.
- Government schemes – The Ministry of Electronics and Information Technology offers subsidies for small entities adopting accessible technology.
When preparing a budget, allocate roughly 10‑15 % of the total website development cost for accessibility work, plus a modest annual reserve for re‑audits and updates.
9. Common misconceptions about Indian accessibility law
- “Only large NGOs need to comply.” – The law applies to any registered NGO with a public website, regardless of size.
- “Adding alt text is enough.” – Alt text addresses only the perceivable principle; operable, understandable, and robust criteria must also be met.
- “Compliance is a one‑off task.” – Accessibility is an ongoing process; new content and features must be evaluated continuously.
- “Screen readers are the only assistive technology to test.” – Users also rely on voice input, switch devices, and magnifiers; each presents unique requirements.
Frequently Asked Questions
How does the RPWD Act define “public‑facing website”?
A public‑facing website is any domain or sub‑domain that any internet user can access without authentication, including donation pages, event calendars, and resource libraries.
Do mobile apps need to follow the same WCAG level as the website?
Yes. The RPWD Act treats mobile apps as extensions of the website and requires them to meet WCAG 2.2 AA criteria, especially for touch targets and screen‑reader compatibility.
What is the minimum contrast ratio required for text?
The Act mandates a contrast ratio of at least 4.5 : 1 for normal text and 3 : 1 for large text (18 pt or 14 pt bold). Tools like the Colour Contrast Analyzer can verify compliance.
Can I use a third‑party template and claim it is accessible?
Using a template reduces development effort, but you must still test the final site for accessibility. Templates often need customisation to meet Level AA, especially for colour contrast and ARIA usage.
How long do I have to fix a compliance notice?
The standard notice period is 30 days, after which penalties may be imposed if remediation is not demonstrated.
Is there a certification for Indian website accessibility?
There is no government‑issued certification, but NGOs can obtain third‑party accessibility statements from recognised auditors, which can be displayed on the site as proof of due diligence.
Where to Start
- Run an initial audit using a free tool like Lighthouse to identify high‑priority gaps.
- Draft an accessibility policy that references WCAG 2.2 AA and outlines a remediation timeline.
- Prioritise fixes that affect navigation and perception (alt text, colour contrast, keyboard focus).
- Engage a specialist—either upskill your team or partner with a vendor such as Govindani Infotech for a detailed audit and implementation plan.
- Set up a quarterly review to keep the site compliant as content evolves.
If you need a partner to walk you through the technical details, feel free to reach out to our team on WhatsApp.