Startup and fintech teams tend to move fast, and accessibility often ends up on the "we'll get to it eventually" pile. The problem is, for fintech products, the stakes are higher than for most digital products: people are putting their money into your app, and an accessibility barrier there isn't just an inconvenience, it can mean someone can't access their own funds.

There's also a regulatory angle that often gets overlooked. OJK Regulation No. 6/POJK.07/2022 on Consumer and Community Protection in the Financial Services Sector (later refined by POJK No. 22 of 2023) requires financial service providers to ensure equal access for all consumers, including dedicated services for consumers with disabilities and elderly consumers. So accessibility in this sector isn't just an ethical or reputational matter, it's also part of regulatory compliance.

The checklist below isn't a complete list of every WCAG criterion, but it's a practical starting point you can check today without needing to become an expert first.

Text and color

  • Make sure there's enough contrast between text and its background, especially for transaction amounts and balances, which are often displayed in lighter or thinner text than regular content.
  • Don't rely on color as the only indicator. Profit/loss or up/down status that's only distinguished by green and red will be unreadable for colorblind users. Add an arrow icon or a plus/minus sign next to it.
  • Make sure text can still be zoomed or enlarged without breaking the layout or cutting off content.

Forms and onboarding (KYC)

  • Every input field has a clear label that's properly associated with it, not just a placeholder that disappears the moment the user starts typing.
  • Error messages are specific and actionable. "Invalid data" doesn't help anyone; "ID number must be 16 digits" is far clearer.
  • Required fields are clearly marked, and that marking is explained, not just an asterisk with no indication of what it means.
  • Document upload flows (ID card, selfie, etc.) come with clear instructions on what's expected, and tell users specifically what went wrong if there's an issue, instead of just "upload failed."

Authentication and security

  • If there's a visual CAPTCHA, provide an alternative that doesn't rely on the ability to see a specific image.
  • Give users enough time to enter an OTP code, and if there's a time limit, provide an option to request a new code without restarting the entire process.
  • Make sure login and verification can still be completed using keyboard only or with a screen reader active.

Navigation and interaction

  • Every critical function, such as transfers, payments, and transaction confirmations, can be completed using a keyboard alone, with no mouse or touch required.
  • Clickable buttons and elements are large enough and spaced apart, so they're hard to mis-tap, especially key buttons like "Confirm" or "Send."
  • When navigating with a keyboard, the currently focused element is clearly visible and isn't hidden behind something else, like a header or a pop-up.

Visual content and data

  • Investment performance charts or transaction history have a text or table-based alternative, not just a graphic that a screen reader can't read.
  • Transaction category icons (shopping, transport, food, etc.) have alt text, rather than being plain icons with no label.
  • Tutorial or product explainer videos have captions, especially for content that walks through important features or steps.

Notifications and transaction status

  • Transaction status (success, failed, pending) is shown using a combination of color, icon, and text, not color alone.
  • Important notifications, like failed payments or insufficient balance, remain accessible and understandable to screen reader users, rather than only appearing as a brief visual pop-up.

Customer support

  • There's an alternative support channel beyond text-based live chat, such as a phone line, for users who have difficulty typing or using certain technology.
  • An accessibility statement is published openly, explaining your commitment and how users can report accessibility issues.

How to verify all of this

Automated testing tools like axe DevTools or Lighthouse can quickly catch some of the issues above, but most items on this checklist, especially anything related to the screen reader experience and keyboard navigation, require hands-on manual testing.

If you want a broader picture of your organization's readiness before diving into technical specifics, our Accessibility Maturity Assessment is a good place to start. For a more specific evaluation of your product, our accessibility audit service can help uncover concrete barriers this checklist alone might not catch.

This checklist won't make your product 100% accessible overnight, but working through a few of these items this week is already a lot better than waiting for "someday" that might never come.