WCAG 2.2 AA

What WCAG 2.2 Actually Requires

WCAG 2.2 is published by the W3C Web Accessibility Initiative and serves as the global standard for web accessibility. When SEBI and RBI reference accessibility requirements, they point to WCAG. Level AA is the conformance level regulators expect — not the minimum Level A, and not the aspirational Level AAA.

The standard organizes its 87 success criteria under four principles. Here is what each means for financial platforms.

Perceivable

Information and interface components must be presented in ways users can perceive, regardless of their sensory abilities.

• Stock charts, NAV graphs, and asset allocation pie charts need descriptive text alternatives
• Tables containing holdings data, transaction histories, and fee schedules need proper th/td structure and scope attributes
• Color-coded trade indicators (red for sell, green for buy) must also use text labels or icons
• Content must adapt to different viewport sizes without horizontal scrolling up to 400% zoom

Operable

Every function must be accessible through keyboard-only navigation and standard assistive technology inputs.

• Tab order must follow a logical sequence through order entry forms, portfolio filters, and navigation menus
• Session timeouts must warn users and allow extension — particularly critical for complex trading workflows
• No content should flash more than three times per second
• Drag interactions (like rearranging watchlist items) must have keyboard alternatives

Understandable

Content must be readable, predictable, and provide input assistance.

• Form error messages must identify the specific field and describe the error clearly
• Page language must be programmatically determinable
• Navigation must be consistent across pages
• Labels must clearly describe the purpose of each input field

Robust

Content must work reliably with current and future assistive technologies.

• Custom UI components need proper ARIA roles, states, and properties
• Dynamic content updates must announce to screen readers via live regions
• Status messages must be programmatically determinable without receiving focus

New in WCAG 2.2

WCAG 2.2 adds nine criteria that weren’t in 2.1, several of which directly impact financial platforms:

• Focus Not Obscured: Sticky headers and floating toolbars must not hide the keyboard focus indicator
• Dragging Movements: Drag-and-drop interactions need click alternatives
• Target Size: Interactive elements must be at least 24×24 CSS pixels
• Consistent Help: Contact information and help mechanisms must appear in consistent locations
• Redundant Entry: Users should not need to re-enter information already provided in the same session

Getting to Compliance

Start with a professional accessibility audit to establish your current conformance level. Our four-phase methodology maps every finding to specific WCAG criteria, giving your team a clear remediation roadmap. For teams building internal capability, our Training Fellowship covers WCAG implementation patterns in depth.