Skip to content

Accessibility

BlindPay should work for everyone who moves money with it, including people who use a keyboard, a screen reader or screen magnification. This page covers where we stand against WCAG 2.2 AA, what still falls short and how to tell us about a barrier.

Partially conformant
WCAG 2.2 Level AAUpdated
Report a barrier
See known limitations

Our commitment

We design and build BlindPay to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA, the W3C standard for accessible web content.

Accessibility fixes go through the same code review as every other change. The barriers we know about and have not fixed yet are listed on this page.

Conformance status

blindpay.com is partially conformant with WCAG 2.2 Level AA. Partially conformant means some parts of the content do not fully meet the standard yet. Each gap we know about is under known limitations.

  • Website

    blindpay.com

    Status
    Partially conformant
    Details
    Automated scans of 32 pages and keyboard testing.

  • Documentation

    blindpay.com/docs

    Status
    Partially conformant
    Details
    Automated scans and keyboard testing of navigation, search and code tabs.

  • Dashboard

    app.blindpay.com

    Status
    Partially conformant
    Details
    Code review against WCAG 2.2 AA and browser checks of the shared dialogs and form fields. Not yet tested with assistive technology.

  • Card checkout

    Hosted checkout and pay.blindpay.com

    Status
    Not yet assessed
    Details
    The card number, expiry date and security code fields come from our card processor. 3-D Secure screens come from the cardholder's bank.

Not covered: the BlindPay API, which has no interface of its own, and the pages partners build with it.

What we built

Our last WCAG 2.2 AA pass covered the website, the docs, the dashboard and our component libraries. This is what it put in place.

  • A Skip to content link is the first keyboard stop on the website, the docs and the dashboard.
  • Each page has one main region and named navigation landmarks, so a screen reader lists the page the way it looks.
  • Buttons, menus, tabs, switches and form fields work with a keyboard and show a visible focus ring.
  • Form fields have labels, and error messages are tied to the field they describe.
  • Text and links on the website and docs pages we scan meet the 4.5:1 contrast minimum.
  • The dashboard's shared dialog shows its close button to keyboard users.
  • Decorative icons are hidden from screen readers. Icon-only buttons have names.
  • Copy buttons and status messages in the docs are announced to screen readers.
  • Code tabs in the docs follow the WAI-ARIA tabs pattern: arrow keys, Home and End.
  • Most animations respect the reduce motion setting in your operating system.

How we test

  • Automated scans with axe-core against the WCAG 2.2 A and AA rules, on 32 website pages, the docs and the API reference. In the last run, the only failures left were two exempt items on the website: the Y Combinator logo in the footer and a color sample on our design system page.
  • Keyboard walkthroughs of the skip link, the main menu, the mobile menu, docs search and code tabs.
  • Keyboard and focus checks of the dashboard's shared dialogs and form fields in a browser.
  • Code review on every change before it ships.

Known limitations

These are the barriers we know about. If you run into one that is not listed, tell us.

  • Light gray focus ring on buttons

    WCAG 1.4.11

    Website and docs

    Buttons, pill selectors and checkbox cards show a light gray ring when you tab to them. Against the page it measures under the 3:1 minimum. Text fields and checkboxes use a blue edge that passes.

  • Dashboard colors not yet measured

    WCAG 1.4.3
    WCAG 1.4.11

    Dashboard

    We darkened the placeholder text, error text and focus outlines we found by reading the dashboard code, and checked the shared dialogs and form fields in a browser. We have not measured the signed-in dashboard yet.

Report a barrier

If something on blindpay.com, the docs or the dashboard gets in your way, email support@blindpay.com. Include the page address, what you were trying to do, and the browser and assistive technology you use. If you need something from this site in another format, ask in the same email.

Running a procurement or security review? Email compliance@blindpay.com.

About this statement

Standard
WCAG 2.2 Level AA
Status
Partially conformant
Prepared
November 4, 2026
Last tested
October 30 to November 4, 2026
Method
Self-assessment by the BlindPay team
Relies on
HTML, WAI-ARIA, CSS and JavaScript

One API.
Multiple payment rails.

Get a Demo
Go to Docs

Blind Pay, Inc. (“BlindPay”) is a United States-based financial technology and payments infrastructure company, incorporated in the State of Delaware on May 2, 2024. BlindPay is duly registered as a Money Services Business (“MSB”) with the Financial Crimes Enforcement Network (“FinCEN”) under registration number 31000277566153. BlindPay is not a state-licensed money transmitter and does not, in its own capacity, engage in regulated money transmission services. All such regulated activities are conducted exclusively through, and under the licenses of, duly authorized financial institution partners. BlindPay's role is limited to providing financial technology, virtual account management, payment processing, and related payments infrastructure services that facilitate payment flows and account functionalities. These services are provided in coordination with its licensed partners and in compliance with applicable federal MSB requirements and relevant state regulatory frameworks.

Blind Pay, LLC (“BlindPay”) is a Delaware limited liability company formed on June 24, 2025. BlindPay is duly registered as a Money Services Business (“MSB”) with the Financial Crimes Enforcement Network (“FinCEN”) under registration number 31000318334247 and is listed in the Nationwide Multistate Licensing System (“NMLS”) under NMLS ID #2745309.

BLIND PAY SOCIEDADE PRESTADORA DE SERVIÇOS DE ATIVOS VIRTUAIS LTDA. (“BlindPay”) is a Virtual Asset Service Provider (“VASP”) operating in Brazil. The company is presently completing the regulatory adaptation process required of Virtual Asset Service Provider Companies (SPSAV) under Central Bank of Brazil Resolution No. 520/2025, and remains subject to the transitional regime set forth in Article 88 of that Resolution. Registered address: Avenida Princesa Isabel, nº 15, Sala 1405, Edifício Martinho de Freitas, Centro, Vitória/ES, 29010-361.

Backed by
Combinator
All systems operational
AICPA SOC 2 badgeGDPR badgeDORA badge

BlindPay is a stablecoin API that enables individuals and businesses to move money worldwide.

© BlindPay 2026.

Privacy PolicyTerms of ServiceTrust PageAML Policy Statement