RBI Guidelines for Accessibility Testing in Banking: The 2026 Compliance Playbook

According to 2024 research data cited by Deque Systems, only 15% of Indian banks fully comply with WCAG standards — leaving 85% of the sector exposed to regulatory action, legal liability, and exclusion of 27 million citizens with disabilities. The accessibility standards and guidelines for the banking sector underwent a seismic shift in 2025: the Supreme Court declared digital access a fundamental right, RBI issued new Digital Banking Channels Authorisation Directions effective January 1, 2026, and SEBI mandated compliance deadlines stretching into mid-2026. For banking CTOs, compliance officers, and IIBF exam candidates, this guide provides the complete regulatory picture, WCAG 2.2 transition roadmap, testing tools, penalties framework, and a 90-day compliance action plan.

What You'll Learn

• The 6 accessibility touchpoints mandated by the Ministry of Finance for every Indian bank
• How the April 2025 Supreme Court ruling and RBI's 2026 Directions change compliance obligations
• WCAG 2.1 vs WCAG 2.2 differences that directly affect banking login, OTP, and authentication flows
• Which accessibility testing tools work best for RBI compliance — and why automated tools alone are not enough
• IIBF exam prep with MCQ-style questions on banking accessibility standards
• A phased 90-day roadmap to achieve compliance before your next regulatory audit

Metric	Value	Source
Indian banks WCAG-compliant	15%	Deque Systems, 2024
Persons with disabilities in India	27 million	Deque Systems, 2024
Automated tools WCAG coverage	30-40%	Inclly, 2026
WCAG 2.2 new success criteria	9	AllAccessible, 2025
SEBI audit completion deadline	April 30, 2026	Deque Systems, 2025
SEBI remediation deadline	July 31, 2026	Deque Systems, 2025

What Are the RBI's Accessibility Standards and Guidelines for the Banking Sector?

The Ministry of Finance, Government of India, issued the "Accessibility Standards and Guidelines for Banking Sector" document on February 2, 2024. This document defines six distinct touchpoints where banks must ensure barrier-free access for persons with disabilities. The RBI's Digital Banking Channels Authorisation Directions, 2025 (PR no. 2025-2026/1589, issued November 28, 2025, effective January 1, 2026) explicitly reference this Ministry of Finance document as a mandatory compliance requirement for all authorized banks.

The six touchpoints cover the full spectrum of banking interactions. First, accessibility to branch premises requires ramps, tactile paths, accessible counters, and signage in Braille. Banks must ensure that their physical infrastructure does not create barriers for customers using wheelchairs, walking aids, or those with visual impairments.

Second, ATM accessibility mandates Talking ATMs with audio guidance, tactile keypads with Braille markings, and wheelchair-accessible placement. According to Inclusion.in (2025), Union Bank of India has deployed Talking ATMs as part of its award-winning Union Access initiative, setting the benchmark for public sector banks.

Third, digital banking channels — websites, mobile applications, internet banking portals, USSD, and SMS banking — must comply with WCAG 2.1 Level AA and IS 17802 (India's national ICT accessibility standard). This is the most testing-intensive touchpoint and the primary area where accessibility testing services deliver measurable compliance outcomes.

Fourth, issuance of debit and credit cards to visually impaired persons requires cards with distinguishing features such as notches, Braille markings, or tactile elements that allow blind and low-vision customers to identify card types by touch.

Fifth, accessible bank statements and documents must be available in Braille, large print, ePUB, and tagged PDF formats. According to DigitalA11Y (2025), RBI guidelines require banks to provide bank statements in accessible digital formats including Braille and ePUB.

Sixth, customer service and grievance redressal channels must accommodate persons with speech and hearing disabilities through sign language interpreters, video relay services, accessible complaint portals, and dedicated helpline options.

Key Finding: "Only 15% of total banks in India meet WCAG compliance standards" — Deque Systems, 2024

These six touchpoints form the foundation of every banking accessibility audit. Banks that address only their website or mobile app risk partial compliance, because the RBI framework evaluates the entire customer journey from branch entry to grievance resolution.

Which Document Outlines Accessibility in the Digital Banking Interface?

This is one of the most frequently searched questions — and a common IIBF exam topic. The answer involves multiple regulatory documents that together form India's banking accessibility framework.

The primary document is the "Accessibility Standards and Guidelines for Banking Sector" issued by the Department of Financial Services, Ministry of Finance, Government of India, on February 2, 2024. This document establishes the six touchpoints discussed above and sets the policy framework for inclusive banking. It is the document most commonly referenced in IIBF exam questions about banking accessibility standards.

The RBI Digital Banking Channels Authorisation Directions, 2025 (issued November 28, 2025, effective January 1, 2026) are the enforcement mechanism. These directions require all authorized banks — commercial banks, small finance banks, payments banks, and cooperative banks — to comply with the Ministry of Finance accessibility standards as part of their digital banking authorization. Banks that fail to meet these requirements risk their digital banking channel authorization itself.

IS 17802 (Indian Standard for ICT Accessibility) is India's national standard for ICT accessibility requirements. Published by the Bureau of Indian Standards, IS 17802 provides the technical specification for how digital products and services must be made accessible. RBI requires IS 17802 compliance alongside WCAG 2.1 Level AA as the minimum standard for all digital banking platforms.

GIGW 3.0 (Guidelines for Indian Government Websites, Version 3.0) applies specifically to public sector banks and government-affiliated financial institutions. GIGW 3.0 mandates accessibility compliance for all government-facing digital platforms and is referenced by both RBI and SEBI in their respective accessibility directives.

The Rights of Persons with Disabilities (RPwD) Act, 2016 provides the overarching legal framework. Section 46 of the RPwD Act mandates that all service providers — including banks — ensure accessibility of their services, products, and information. For a comprehensive overview of how these laws intersect, see our guide on digital accessibility laws in India.

Together, these documents create a multi-layered compliance obligation: the Ministry of Finance defines what banks must do, the RBI Directions enforce it through the banking authorization framework, IS 17802 and WCAG 2.1 define how to do it technically, and the RPwD Act provides the legal penalties for non-compliance.

How Does WCAG 2.2 Change Accessibility Requirements for Indian Banks?

WCAG 2.2 was officially approved as ISO/IEC 40500:2025 in October 2025, according to ADA QuickScan (2026). This ISO designation gives WCAG 2.2 formal international legal weight. Since both RBI and SEBI guidelines reference "WCAG 2.1 or latest version," banks must now plan their transition to WCAG 2.2 compliance.

WCAG 2.2 adds 9 new success criteria to the existing 78 criteria in WCAG 2.1, bringing the total to 87 criteria across Levels A, AA, and AAA. The new standard is backward-compatible: meeting WCAG 2.2 automatically satisfies WCAG 2.1 requirements. According to AllAccessible (2025), the 9 new criteria include 3 at Level A and 6 at Level AA/AAA.

For banking applications, two new criteria stand out as particularly impactful.

Criterion 3.3.8 — Accessible Authentication (Minimum, Level AA) prohibits cognitive function tests as the sole authentication method. In banking terms, this means image-recognition CAPTCHAs, memory-based puzzles, and pattern-recognition challenges used during login or OTP verification must provide accessible alternatives. Banks must allow password managers, biometric login, or copy-paste OTP entry as alternatives to cognitive-test-based authentication.

Criterion 2.5.8 — Target Size (Minimum, Level AA) requires interactive elements to be at least 24x24 CSS pixels with adequate spacing. For mobile banking apps — where UPI payment buttons, fund transfer confirmation buttons, and navigation elements are frequently undersized — this criterion demands significant UI remediation.

Aspect	WCAG 2.1	WCAG 2.2
ISO Status	ISO/IEC 40500:2012 reference	ISO/IEC 40500:2025 - approved October 2025
Total Success Criteria	78	87
RBI Baseline Requirement	Yes - Level AA mandatory	Yes - "WCAG 2.1 or latest version"
Authentication Rules	No specific criterion	3.3.8 Accessible Authentication - no cognitive tests without alternatives
Target Size Rules	No minimum size criterion	2.5.8 Target Size - 24x24 CSS pixels minimum
Dragging Movements	Not addressed	2.5.7 - single-pointer alternatives required for drag-based actions
Focus Visibility	Basic requirements	2.4.11 Focus Not Obscured - sticky headers cannot hide focus indicators
Redundant Entry	Not addressed	3.3.7 - multi-step forms must not re-ask for previously entered data
Help Consistency	Not addressed	3.2.6 Consistent Help - help mechanisms in same relative location

Pro Tip: Start your WCAG 2.2 transition with the two highest-impact banking criteria: 3.3.8 Accessible Authentication and 2.5.8 Target Size. Audit every login flow, OTP screen, CAPTCHA, and payment confirmation button on your mobile banking app and net banking portal. These two criteria alone will resolve the majority of authentication and mobile usability complaints from assistive technology users.

What Did the 2025 Supreme Court Ruling Mean for Banking Accessibility?

On April 30, 2025, the Supreme Court of India delivered a landmark judgment in the case of Pragya Prasun & Ors. v. Union of India. The bench of Justice JB Pardiwala and Justice R Mahadevan declared that digital access is an integral part of the fundamental right to life under Article 21 of the Indian Constitution. According to Moneylife (2025), the Court mandated that "persons with disabilities must be given equal, barrier-free access to financial services."

This judgment transformed digital accessibility from a compliance checkbox into a constitutional obligation. The Supreme Court specifically directed banks and NBFCs to provide accessible KYC processes, home visits for customers who cannot reach branches, screen-reader-friendly digital platforms, and assistive technology support across all banking channels.

Following this ruling, the RBI issued a compliance circular on August 14, 2025 (RBI/2025-26/75) to all regulated entities — commercial banks, cooperative banks, NBFCs, and payment banks — mandating immediate compliance with the Supreme Court order. According to Moneylife (2025), the RBI circular stated that "failure to implement the order will attract supervisory action and penalties."

The August 2025 RBI circular introduced several specific requirements. Banks must develop standard operating procedures for KYC for persons with disabilities. According to CourtKutchehry (2025), banks must now provide non-biometric KYC alternatives for customers unable to use facial recognition — including video KYC, OTP-based verification, and assisted digital KYC. Screen-reader-friendly portals and voice-enabled apps are now required, not optional.

The RBI also mandated quarterly compliance reports from all regulated entities, creating a structured reporting framework that ensures ongoing accountability rather than one-time compliance.

Watch Out: Many banks treat the Supreme Court judgment as a future obligation. It is not. The RBI's August 14, 2025 circular mandates "immediate compliance." Banks that have not yet audited their digital platforms for accessibility are already operating in violation of an active RBI directive. The quarterly compliance reporting requirement means the RBI will actively track whether banks are making progress.

The SEBI parallel is equally important. SEBI issued Circular No. SEBI/HO/ITD-1/ITD_VIAP/P/CIR/2025/111 on July 31, 2025, according to DigitalA11Y (2025), mandating digital accessibility for all SEBI-regulated entities (stock exchanges, mutual funds, brokers, depositories). While SEBI-regulated entities are distinct from RBI-regulated banks, the combined regulatory pressure signals that India's entire financial sector is now under accessibility mandates.

How Are Indian Banks Implementing Accessibility Testing in 2025-2026?

While 85% of Indian banks remain non-compliant with WCAG standards, several institutions have emerged as accessibility leaders. Their implementations provide a practical blueprint for banks planning their compliance journeys.

Union Bank of India launched its "Union Access" initiative on May 19, 2022 (Global Accessibility Awareness Day) and has since built one of India's most comprehensive banking accessibility programs. According to Inclusion.in (2025), Union Access is compliant with WCAG 2.1 Level AA and IS 17802. The initiative includes Union Sparsh Braille Cards, Talking ATMs, an accessible Digital Rupee (CBDC) app, UVConn WhatsApp banking in 7 languages, and voice-operable banking. Union Bank's digital platforms are compatible with NVDA, JAWS, VoiceOver, and TalkBack screen readers. The bank won the 16th NCPEDP Mphasis Universal Design Award 2025 in the Role Model Organizations category, and notably employs IAAP-certified professionals, including persons with visual impairment, in development roles.

ICICI Bank has committed to WCAG 2.1 Level AA compliance with a target deadline of December 31, 2025. The bank provides accessible branches with talking ATMs and Braille-enabled services. ICICI maintains a published accessibility statement outlining its compliance commitments.

These case studies highlight a critical pattern: accessibility is not a single project but an ongoing program. Union Bank's success stems from a board-level Accessibility Committee, IAAP-certified team members, and a formal digital accessibility policy — not just a one-time audit. Banks that approach accessibility as a regulatory checkbox rather than a sustained program consistently fail subsequent audits.

For banks operating in India's mobile-first banking landscape, mobile application testing services are particularly critical. With Android holding over 94% of the Indian smartphone market, TalkBack screen reader testing for mobile banking apps is the single most impactful accessibility testing investment a bank can make.

Which Accessibility Testing Tools Should Banks Use for RBI Compliance?

Selecting the right accessibility testing tools is essential for banking compliance, but understanding their limitations is equally important. According to Inclly (2026), "all automated accessibility tools share the same fundamental limitation: they catch approximately 30-40% of WCAG issues. The remaining 60-70% require manual testing by humans."

This limitation is critical for banking. RBI compliance audits demand comprehensive coverage, not just automated scans. Banks that rely solely on automated tools will miss the majority of accessibility violations — particularly those related to screen reader compatibility, keyboard navigation flow, and cognitive accessibility.

Tool	Type	Cost	WCAG Coverage	Best For	CI/CD Integration
axe DevTools	Automated scanner	Free tier available; paid plans for enterprise	WCAG 2.0, 2.1, 2.2 - A, AA, AAA	Developers in CI/CD pipelines; zero false positives	Yes - axe-core npm package
WAVE	Visual overlay tool	Free for web; paid API	WCAG 2.1 - A, AA	Non-technical content editors; visual feedback	Limited - API only
Lighthouse	Automated audit	Free - built into Chrome DevTools	~30 accessibility checks only	Quick audits; better for performance/SEO	Yes - Lighthouse CI
JAWS	Screen reader	$95/year or enterprise license	Manual testing - full WCAG coverage	Enterprise banking accessibility testing	No - manual testing
NVDA	Screen reader	Free and open-source	Manual testing - full WCAG coverage	Cost-effective screen reader testing	No - manual testing
Pa11y	Automated scanner	Free and open-source	WCAG 2.1 - A, AA	CI/CD automation; scheduled monitoring	Yes - CLI and npm

For RBI compliance, the recommended approach combines automated and manual testing. Automated tools (axe DevTools integrated into CI/CD pipelines) catch regressions during development. Manual screen reader testing with JAWS and NVDA validates the real-world experience of users with disabilities on net banking portals. For mobile banking apps, VoiceOver (iOS) and TalkBack (Android) testing is essential. For a comprehensive comparison of testing tools, see our guide on top accessibility testing tools.

Integrating axe-core into your CI/CD pipeline through test automation services enables continuous accessibility monitoring — catching regressions before they reach production. This is critical for banks that release frequent updates to mobile apps and net banking portals.

What Is the IIBF Exam Syllabus on RBI Accessibility Guidelines?

IIBF (Indian Institute of Banking and Finance) exam candidates preparing for CAIIB and JAIIB modules frequently encounter questions on banking accessibility standards. The Ministry of Finance "Accessibility Standards and Guidelines for Banking Sector" document (February 2, 2024) is the authoritative source for these exam questions. Below are common exam-style questions with detailed explanations.

Q1: Which document outlines accessibility in the digital banking interface?

Answer: The "Accessibility Standards and Guidelines for Banking Sector" issued by the Department of Financial Services, Ministry of Finance, Government of India, on February 2, 2024. This document covers six touchpoints for accessibility across banking services and is the primary regulatory reference for digital banking accessibility in India.

Q2: What are the touchpoints for accessibility standards and guidelines in the banking sector?

Answer: The six touchpoints are: (1) Accessibility to Branch Premises, (2) ATM Accessibility, (3) Digital Banking Channels (websites, mobile apps, internet banking), (4) Issuance of Debit/Credit Cards to visually impaired persons, (5) Accessible bank statements and documents, and (6) Customer service and grievance redressal channels. All six touchpoints must be addressed for full compliance with the Ministry of Finance guidelines.

Q3: What is the key objective of accessibility standards in banking?

Answer: To ensure persons with disabilities (PwD) have equal, barrier-free access to all banking services and facilities, in compliance with the Rights of Persons with Disabilities (RPwD) Act, 2016. The objective extends beyond digital channels to include physical branch access, ATM usability, document formats, and customer service channels.

Q4: What WCAG level do RBI guidelines require for digital banking platforms?

Answer: WCAG 2.1 Level AA is the minimum compliance standard required by RBI, along with India's IS 17802 national standard for ICT accessibility. Since WCAG 2.2 became the ISO/IEC 40500:2025 international standard in October 2025, banks should also prepare for WCAG 2.2 compliance as it is now the "latest version" referenced in regulatory directives.

Q5: Which regulator issued mandatory digital accessibility requirements for the financial sector in July 2025?

Answer: SEBI issued Circular No. SEBI/HO/ITD-1/ITD_VIAP/P/CIR/2025/111 on July 31, 2025, mandating digital accessibility for all SEBI-regulated financial entities. For RBI-regulated banks specifically, the mandate comes from the RBI Digital Banking Channels Authorisation Directions, 2025 (effective January 1, 2026), which references the Ministry of Finance Accessibility Standards as a mandatory requirement.

TL;DR: For IIBF exam preparation, remember these five anchor points: (1) Ministry of Finance document dated February 2, 2024 is the primary accessibility standards document, (2) six touchpoints cover the full banking journey, (3) WCAG 2.1 Level AA + IS 17802 are the technical standards required, (4) RPwD Act 2016 provides the legal framework, and (5) the Supreme Court's April 30, 2025 judgment elevated digital access to a fundamental right under Article 21.

What Are the Penalties for Non-Compliance with RBI Accessibility Guidelines?

The penalty framework for banking accessibility non-compliance operates across three distinct regulatory channels: the RPwD Act 2016, RBI enforcement actions, and SEBI enforcement for capital market entities.

Under the Rights of Persons with Disabilities (RPwD) Act, 2016, Section 89 prescribes a fine of Rs 10,000 for the first offense of non-compliance with accessibility mandates. Repeated offenses can attract penalties up to Rs 5,00,000 (Rs 5 lakh). The Chief Commissioner for Persons with Disabilities is the designated enforcement authority. In February 2025, the Chief Commissioner imposed Rs 10,000 penalties on 155 establishments — including government ministries and private organizations — for failing to make websites, mobile apps, and digital platforms accessible. This enforcement action signals that the penalty mechanism is actively operational, not merely theoretical.

RBI enforcement operates through supervisory action and monetary penalties. Following the August 14, 2025 circular, the RBI explicitly stated that "failure to implement the order will attract supervisory action and penalties," according to Moneylife (2025). RBI enforcement in the financial sector is substantial: the RBI imposed 353 penalties totaling Rs 54.78 crore in FY 2024-25 across various compliance categories. While these specific penalties were for KYC, cyber security, and other violations, the enforcement infrastructure exists and is being actively applied. With the August 2025 circular mandating quarterly compliance reports on accessibility, the RBI now has a reporting mechanism to identify and act against non-compliant banks.

SEBI enforcement applies to capital market entities (stock exchanges, mutual funds, brokers, investment advisors). According to DigitalA11Y (2025) and Deque Systems (2025), SEBI-regulated entities face an audit deadline of April 30, 2026 and a remediation deadline of July 31, 2026. Entities that miss these deadlines face SEBI enforcement actions including regulatory warnings and fines.

Beyond regulatory penalties, the reputational risk of accessibility non-compliance is significant. A banking customer with a disability who is denied access to digital services can now approach the courts citing the Supreme Court's April 2025 fundamental rights ruling — transforming what was previously a regulatory matter into a constitutional rights case. For a deeper dive into the legal landscape, see our post on why accessibility testing is important for your digital platforms.

Enforcement Channel	First Offense Penalty	Maximum Penalty	Enforcer	Active Enforcement
RPwD Act 2016	Rs 10,000	Rs 5,00,000	Chief Commissioner for PwD	Yes - 155 establishments penalized Feb 2025
RBI Supervisory Action	Monetary penalty + supervisory action	Case-specific	RBI	Yes - quarterly compliance reports mandated
SEBI Enforcement	Regulatory warning	SEBI enforcement action + fines	SEBI	Deadlines: Apr 30, 2026 audit; Jul 31, 2026 remediation
Supreme Court - Article 21	Contempt of court	Court-directed penalties	Judiciary	Active since April 30, 2025

How Can Banks Build a 90-Day Accessibility Compliance Roadmap?

Achieving banking accessibility compliance requires a structured, phased approach. The following 90-day roadmap provides a practical framework for banks that need to demonstrate compliance progress in their quarterly RBI reports.

Phase 1: Audit and Gap Analysis (Days 1-30)

The first phase focuses on understanding the current state of accessibility across all digital touchpoints. Banks should conduct a comprehensive WCAG 2.1 Level AA audit of their primary digital platforms: net banking portal, mobile banking app (Android and iOS), customer-facing website, and any USSD or SMS-based banking interfaces.

Key activities during this phase include automated scanning using axe DevTools and WAVE to identify programmatic violations, followed by manual screen reader testing with NVDA (Windows), VoiceOver (iOS), and TalkBack (Android). Banks should also audit document accessibility — specifically PDF bank statements, loan agreements, and KYC forms — against tagged PDF standards.

The output of Phase 1 is a prioritized gap analysis report that maps every identified violation to the specific WCAG criterion it violates, assigns a severity level (critical, major, minor), and estimates the remediation effort required. This report becomes the foundation for the Phase 2 remediation plan.

Phase 2: Remediation and Re-Testing (Days 31-60)

Phase 2 focuses on fixing the highest-priority violations identified in the audit. Banks should address critical violations first — keyboard traps, missing form labels, inaccessible authentication flows, and screen reader incompatibilities — before moving to major and minor issues.

During this phase, accessibility testing services provide the combination of automated scanning and manual assistive technology testing required for comprehensive remediation validation. Banks should integrate axe-core into their CI/CD pipeline during this phase to prevent new violations from being introduced during development.

Each fix should be re-tested using the same methodology (automated scan + manual screen reader validation) to confirm the violation is resolved and no new violations have been introduced. Banks should maintain a remediation log documenting each fix for regulatory reporting purposes.

Phase 3: Validation, Documentation, and Continuous Compliance (Days 61-90)

The final phase validates the overall accessibility posture and produces the documentation required for RBI quarterly compliance reports. Banks should conduct a full re-audit to verify that all critical and major violations have been resolved, and document the remaining minor issues with planned remediation timelines.

Banks must publish a public accessibility statement on their website — a requirement under both WCAG best practices and RBI expectations. This statement should declare the WCAG level targeted, the date of the most recent audit, known limitations, and contact information for accessibility-related feedback.

Appoint a nodal officer at both branch and head office levels for accessibility management, as required by RBI guidelines documented by DigitalA11Y (2025). Establish a board-level or senior-management-level accessibility committee that includes at least one person with disabilities. This governance structure ensures accessibility is maintained as an ongoing program, not a one-time project.

How Does Vervali Approach Banking Accessibility Testing?

Vervali Systems brings battle-tested accessibility testing frameworks specifically designed for India's BFSI sector. Vervali's methodology combines automated scanning tools (Axe, WAVE) with manual testing by accessibility experts using JAWS, NVDA, VoiceOver, and TalkBack — providing the comprehensive coverage that RBI compliance audits demand.

Vervali's accessibility testing services follow a six-step methodology: Accessibility Audit and Scoping, Automated Scan and Manual Review for 360-degree validation, Assistive Tech Compatibility testing across real devices and screen readers, Issue Categorization and Prioritization by WCAG level and business impact, Remediation Guidance with developer-friendly references, and Re-Testing with Continuous Compliance monitoring.

Vervali has a proven track record across the BFSI sector. For Motilal Oswal Financial Services, Vervali built an award-winning tech-first platform with 2,000+ active users post-launch. Across accessibility testing engagements, Vervali has achieved results including reduced WCAG failures by 90%, improved assistive tech usability by 85%, and achieved 100% ADA and Section 508 conformance for clients requiring international compliance standards.

As Muhammad Raheel from Emaratech noted: "Vervali Systems Pvt Ltd's work has increased test coverage by 70% to 80%, shortened regression testing time from multiple days to a few hours, and reduced manual regression effort by over 50%."

For banks operating under the January 1, 2026 RBI Digital Banking Channels Authorisation Directions, Vervali provides the end-to-end audit-remediation-retest cycle that maps directly to the six Ministry of Finance touchpoints, WCAG 2.1 Level AA, IS 17802, and GIGW 3.0 requirements.

TL;DR: Indian banking accessibility compliance in 2026 requires attention to five regulatory pillars: (1) the Ministry of Finance's 6-touchpoint framework, (2) RBI Digital Banking Channels Authorisation Directions effective January 1, 2026, (3) the Supreme Court's April 30, 2025 fundamental rights ruling, (4) WCAG 2.2's 9 new criteria (especially 3.3.8 Accessible Authentication and 2.5.8 Target Size), and (5) RPwD Act penalties actively being enforced. Automated tools catch only 30-40% of WCAG issues — manual screen reader testing with JAWS, NVDA, TalkBack, and VoiceOver is mandatory for compliance-grade audits.

---

Ready to Make Your Banking Platform Accessible and Compliant?

Vervali's accessibility testing experts help Indian banks and financial institutions achieve WCAG 2.1/2.2, IS 17802, and GIGW 3.0 compliance with battle-tested frameworks refined across 200+ product launches. From automated WCAG scanning to manual JAWS/NVDA/TalkBack testing, Vervali delivers the comprehensive accessibility audits that RBI compliance demands. Explore our accessibility testing services or get in touch to discuss your banking accessibility compliance roadmap.

Frequently Asked Questions

What are the accessibility standards and guidelines for the banking sector in India?

The accessibility standards and guidelines for the banking sector in India are defined by the Ministry of Finance document titled "Accessibility Standards and Guidelines for Banking Sector," issued on February 2, 2024. This document covers six touchpoints: branch premises, ATMs, digital banking channels, card issuance for visually impaired persons, accessible documents and statements, and grievance redressal. Banks must comply with WCAG 2.1 Level AA and IS 17802 as minimum technical standards, enforced through the RBI Digital Banking Channels Authorisation Directions, 2025.

Which document outlines accessibility in the digital banking interface?

The primary document is the "Accessibility Standards and Guidelines for Banking Sector" issued by the Department of Financial Services, Ministry of Finance, Government of India, on February 2, 2024. This document is supplemented by the RBI Digital Banking Channels Authorisation Directions, 2025 (effective January 1, 2026), which mandates all authorized banks to comply with these accessibility standards. IS 17802 (India's ICT accessibility standard) and GIGW 3.0 provide the technical compliance frameworks.

What is the difference between WCAG 2.1 and WCAG 2.2 for banking?

WCAG 2.1 has 78 success criteria and is the current RBI-mandated baseline (Level AA). WCAG 2.2, approved as ISO/IEC 40500:2025 in October 2025, adds 9 new criteria totaling 87. The two most impactful additions for banking are 3.3.8 Accessible Authentication (prohibiting cognitive-test-only login methods like image CAPTCHAs) and 2.5.8 Target Size (requiring 24x24 CSS pixel minimum for interactive elements). Since regulators reference "WCAG 2.1 or latest version," banks should plan for WCAG 2.2 compliance.

Can automated accessibility testing tools achieve full RBI compliance?

No. According to a 2026 Inclly comparison study, automated accessibility tools catch only 30-40% of WCAG issues. The remaining 60-70% of violations require manual testing by humans — including screen reader testing with JAWS and NVDA, keyboard navigation testing, and cognitive accessibility evaluation. For RBI compliance, banks must combine automated scanning tools (axe DevTools, WAVE) with manual assistive technology testing to achieve comprehensive coverage.

What are the penalties for banks that fail accessibility compliance in India?

Under the RPwD Act 2016, first-time non-compliance attracts a Rs 10,000 fine, with repeated offenses escalating to Rs 5,00,000 (Rs 5 lakh). In February 2025, 155 establishments were penalized by the Chief Commissioner for Persons with Disabilities for failing to make digital platforms accessible. Additionally, the RBI's August 14, 2025 circular states that failure to comply will attract "supervisory action and penalties." The Supreme Court's April 2025 ruling further elevates non-compliance to a fundamental rights violation under Article 21.

How often should banks conduct accessibility audits?

Banks should conduct comprehensive accessibility audits at least quarterly to align with the RBI's quarterly compliance reporting requirement mandated in the August 14, 2025 circular. Additionally, banks should run automated accessibility scans in their CI/CD pipeline for every code deployment to catch regressions before they reach production. Annual full audits by IAAP-certified professionals are recommended as a best practice, and SEBI mandates annual accessibility audits for SEBI-regulated entities starting April 30, 2027.

What is IS 17802 and why is it important for banking accessibility?

IS 17802 is India's national standard for ICT accessibility requirements, published by the Bureau of Indian Standards. It provides the technical specification for how digital products and services must be made accessible in the Indian context. RBI requires IS 17802 compliance alongside WCAG 2.1 Level AA as the minimum standard for all digital banking platforms. IS 17802 is referenced in the SEBI July 2025 circular and the RBI Digital Banking Channels Authorisation Directions, making it a regulatory requirement for all Indian financial institutions.

What assistive technologies must banks support for RBI compliance?

Banks must support screen readers (JAWS, NVDA for Windows; VoiceOver for iOS/macOS; TalkBack for Android), voice control systems, screen magnifiers, speech recognition software, and alternative input devices. With Android holding over 94% of the Indian smartphone market, TalkBack testing for mobile banking apps is the most critical assistive technology investment. Union Bank of India's Union Access initiative, which won the NCPEDP Universal Design Award 2025, demonstrates compatibility with NVDA, JAWS, VoiceOver, and TalkBack as the benchmark.

How does the Supreme Court's April 2025 ruling affect banking accessibility obligations?

The Supreme Court's April 30, 2025 judgment in Pragya Prasun & Ors. v. Union of India declared digital access a fundamental right under Article 21 of the Indian Constitution. This means inaccessible banking platforms are not merely regulatory violations but constitutional rights violations. The ruling directed banks to provide accessible KYC processes, home visits for persons who cannot reach branches, screen-reader-friendly platforms, and assistive technology support. The RBI followed with an August 14, 2025 circular mandating immediate compliance from all regulated entities.

What should IIBF exam candidates know about banking accessibility?

IIBF exam candidates should focus on five key concepts: (1) the Ministry of Finance "Accessibility Standards and Guidelines for Banking Sector" document (February 2, 2024) is the primary reference, (2) six touchpoints cover the full banking accessibility spectrum, (3) WCAG 2.1 Level AA and IS 17802 are the technical standards, (4) the RPwD Act 2016 provides the legal framework with penalties ranging from Rs 10,000 to Rs 5 lakh, and (5) the Supreme Court's April 30, 2025 judgment declared digital access a fundamental right. Common exam questions focus on identifying the six touchpoints, the issuing authority (Ministry of Finance), and the required WCAG compliance level.

Sources

1. Deque Systems (2024). "Insight into the current state of digital accessibility in the Indian banking sector." https://www.deque.com/blog/insight-into-the-current-state-of-digital-accessibility-in-the-indian-banking-sector/
2. Deque Systems (2025). "SEBI sets a new standard for digital accessibility in finance in India." https://www.deque.com/blog/sebi-sets-a-new-standard-for-digital-accessibility-in-finance-in-india/
3. DigitalA11Y (2025). "SEBI Mandates Digital Accessibility Across Financial Industry in India." https://www.digitala11y.com/sebi-mandates-digital-accessibility-across-all-regulated-platforms-for-financial-industry/
4. Moneylife (2025). "Supreme Court Mandates Barrier-Free Banking for Disabled Persons; RBI Issues Compliance Circular." https://moneylife.in/article/supreme-court-mandates-barrierfree-banking-for-disabled-persons-rbi-issues-compliance-circular/77987.html
5. DigitalA11Y (2025). "RBI Digital Accessibility Guidelines for Banks: A Complete Implementation Guide." https://www.digitala11y.com/rbi-digital-accessibility-guidelines-for-banks-a-complete-implementation-guide/
6. CourtKutchehry (2025). "Digital KYC for Persons with Disabilities: Supreme Court & RBI Issue Inclusive Banking Guidelines." https://www.courtkutchehry.com/pages/blog/digital-kyc-guidelines-persons-with-disabilities-supreme-court-rbi-2025/
7. ADA QuickScan (2026). "WCAG 2.2 Is Now an ISO Standard: What Changes for 2026 Compliance." https://adaquickscan.com/blog/wcag-2-2-iso-standard-2025
8. AllAccessible (2025). "WCAG 2.2: Complete Compliance Guide 2025 — All 9 New Success Criteria." https://www.allaccessible.org/blog/wcag-22-complete-guide-2025
9. Inclusion.in (2025). "Union Bank of India's Union Access Initiative Redefines Inclusive Banking." https://inclusion.in/article/2025/11/no-indian-left-behindunion-bank-of-indiasunion-access-initiative-redefines-inclusive-banking/
10. Inclly (2026). "Best Free Accessibility Testing Tools Compared: axe vs WAVE vs Lighthouse vs Pa11y." https://inclly.com/resources/accessibility-testing-tools-comparison
11. LEGlobal (2025). "India: SEBI Mandates Digital Accessibility for all Regulated Entities." https://leglobal.law/2025/09/19/india-sebi-mandates-digital-accessibility-for-all-regulated-entities/