Accessibility statement.

FintechPays Editorial Co., UK LLP (Companies House #OC4451x) is committed to making fintechpays.com usable for everyone, including readers who navigate by keyboard, screen reader, magnifier, or assistive input. This statement describes the current accessibility state of the site, how we tested it, and where we know we still have work to do.

Scope

This statement covers all pages published under https://fintechpays.com, including the English default (/), Arabic (/ar/, right-to-left), and Hindi (/hi/) locales. It applies to editorial articles, comparison tables, regulator references, methodology pages, and the site chrome shared across them.

It does not cover third-party destinations linked from our content. Affiliate partners, regulator portals, and external sources maintain their own accessibility postures.

Conformance status

The Web Content Accessibility Guidelines (WCAG) define requirements for designers and developers to improve accessibility for people with disabilities. They define three levels of conformance: Level A, Level AA, and Level AAA.

fintechpays.com substantially conforms to WCAG 2.2 Level AA as of 28 May 2026.

"Substantially conforms" means the site has been audited against every applicable Level AA success criterion, all critical and major findings have been remediated, and the remaining gaps are documented below in Known limitations. We do not claim Level AAA conformance, and we do not claim conformance with EN 301 549 — the site is independent editorial publishing, not a public-sector service.

How we tested

The May 2026 audit combined automated tooling with structured manual review:

• axe-core static analysis was run against the production build. The current build reports zero violations across all 147 pages.
• Manual specialist review was conducted by a coordinated set of accessibility agents, each focused on a single dimension: colour contrast, ARIA semantics, keyboard navigation, heading structure, link purpose, SVG and graphics, and right-to-left parity for the Arabic locale.
• Localised chrome verification was performed on built pages across English, Arabic, and Hindi to confirm that signature captions, byline metadata, masthead defaults, and the language switcher render with correct lang attributes and native-script labels.
• Screen reader spot checks were carried out with NVDA (Windows) and VoiceOver (macOS and iOS). JAWS coverage is partial; see Known limitations.

Remediation from the audit was shipped across five pull requests covering i18n chrome leaks, hreflang and sitemap hygiene, locale landing pages and the language switcher, social-card and favicon assets, and a contrast and semantics pass that lifted two critical tokens to pass SC 1.4.3 and SC 1.4.11, alongside eleven major fixes including focus-ring layering over sticky table columns, sortable-header SC 2.5.3 compliance, breadcrumb separator hiding, Devanagari typography overrides, and a Safari-compatible skip link.

Known limitations

We are honest about what is not yet fixed. Two items are tracked for the next remediation cycle.

Focus persistence across the mobile/desktop dual tree

Hub pages render both a desktop sortable table and a stacked mobile-card view in the DOM, swapping visibility by viewport. If the viewport changes during keyboard navigation, focus can land in the subtree that is now visually hidden. We plan to apply the inert attribute to the inactive subtree, which will remove it from the focus order and the accessibility tree. Target: Q3 2026.

JAWS smoke test for the payout-reliability meter

The payout-reliability meter used in the program comparison table is implemented with role="meter" and an aria-valuetext fallback. NVDA and VoiceOver announce the value correctly through aria-valuetext. We have not yet completed a JAWS smoke test, and JAWS support for role="meter" is uneven across versions. The aria-valuetext string is the authoritative announcement and is read by all three engines, so the value is conveyed regardless. Target: Q3 2026.

Feedback

If you encounter an accessibility barrier on fintechpays.com, please tell us. We treat accessibility reports as production bugs, not feature requests.

• Email: editorial@fintechpays.com
• Response commitment: we will acknowledge your report within five business days and tell you whether we can fix it, when, or why not.

Please include the page URL, the assistive technology and browser you were using, and a brief description of what went wrong.

Compatibility

The site is tested against current versions of Chrome, Firefox, Safari, and Edge, paired with NVDA, VoiceOver (macOS and iOS), and — partially — JAWS. It does not rely on JavaScript for content; all editorial pages are statically rendered.

Standards referenced

• Web Content Accessibility Guidelines (WCAG) 2.2, Level AA

Dates

• Statement prepared: 28 May 2026
• Last reviewed: 28 May 2026
• Next scheduled review: 28 May 2027, or sooner if substantial changes are shipped