Accessibility statement

Finatha is built for people managing complex financial lives across countries, currencies, and income types. Clarity is the product. That commitment extends to everyone who uses Finatha, including users who rely on assistive technology, prefer reduced motion, read at large text sizes, or navigate by keyboard.

We design and build Finatha to be perceivable, operable, understandable, and robust. We test as we ship and we publish the gaps we know about.

Finatha targets Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA, with selected Level AAA criteria adopted where they materially improve a financial product (notably contrast, focus appearance, and accessible authentication).

WCAG is published by the W3C and is the standard cited by the European Accessibility Act (EAA), UK accessibility regulations, US Section 508, and most national accessibility laws.

This statement reflects the state of the product on the date below. We re-review quarterly and after material design or platform changes.

Finatha is tested on the latest two major versions of:

• Google Chrome, Apple Safari, Microsoft Edge, Mozilla Firefox on macOS, Windows, iOS, and Android.
• VoiceOver on macOS and iOS, TalkBack on Android, NVDA on Windows, JAWS on Windows.
• Keyboard-only navigation, including Tab, Shift+Tab, Enter, Space, Arrow keys, Escape, and Home/End.

We honour the operating system prefers-reduced-motion setting and disable non-essential animation. We honour the operating system colour scheme (light or dark). Arabic and right-to-left layouts use logical CSS properties so direction follows the user's locale.

• Skip to main content link on every page (revealed on first focus).
• Visible keyboard focus ring with at least 3:1 contrast against adjacent surfaces.
• Reduced motion support: animation and transitions are minimised when the operating system requests it.
• Semantic forms: labels are always present, helper text is wired with aria-describedby, errors are announced.
• Screen reader announcements for save and status events via polite live regions.
• Financial numbers use tabular figures and currency codes so amounts read predictably.
• Light and dark themes with token-level contrast control.
• Bilingual English and Arabic with right-to-left layout and Arabic typography.
• Cookie consent that allows granular per-category choice, refusable, and withdrawable.

We track gaps openly. The current backlog targeted for the next release cycle:

• Privacy mode (mask balances): a persistent toggle and a redacted state for amounts is in active development.
• Session timeout warning: a 60-second warning before inactivity logout is in active development.
• Re-authentication for sensitive actions: required for data export and account closure, in active development.
• Banner and tooltip primitives: replacing ad-hoc title attributes with accessible patterns, in active development.
• Form input semantics: enforcing autocomplete and inputmode on every input across the app, in active development.
• Chart text alternatives: adding screen-reader summaries beside data visualisations, planned.
• Error summary on submit: top-of-form error summaries with anchor links, planned.

If you find an issue not listed here, please report it (see Feedback below).

Third-party content. Where Finatha embeds content or services from third parties (for example, payment checkout pages from our merchant of record), the third-party surface may not meet the same conformance level. We choose partners with an active accessibility roadmap and flag known gaps inline where we can.

User-contributed content. Notes, tags, or images you add to your records are rendered as you wrote them. We do not modify or summarise your text. Please consider readers when you write.

Beta features. Features marked beta may not meet AA at all times. Where this is the case, the beta surface includes an accessible alternative or escape route.

If you cannot use part of Finatha because of an accessibility barrier, please write to accessibility@finatha.app with:

• The page or screen.
• What you were trying to do.
• The assistive technology, browser, and operating system you were using.
• Any error message you saw.

We aim to acknowledge within 2 business days and to provide an update or workaround within 10 business days. For urgent compliance complaints, contact privacy@finatha.app.

This statement was prepared using a combination of:

• Self-evaluation by Finatha's design and engineering team against WCAG 2.2 AA.
• Automated checks in continuous integration (axe-core or equivalent).
• Manual keyboard and screen-reader testing on representative flows (sign-in, onboarding, transactions, planning).
• Independent audit: the current audit is documented at docs/audit/FINATHA_WEB_UX_GAP_ANALYSIS.md and informs the backlog above.

The statement is reviewed at least quarterly and after any material change to the product.

If you are not satisfied with our response, you may contact the appropriate regulator:

• United Kingdom: the Equality and Human Rights Commission (EHRC), via the Equality Advisory and Support Service.
• European Union: the relevant member state body designated under the European Accessibility Act.
• Qatar: the Compliance and Data Protection Department, Ministry of Communications and Information Technology.
• United Arab Emirates: the UAE Data Office.
• Saudi Arabia: the Saudi Data and Artificial Intelligence Authority (SDAIA).

Contacting a regulator does not affect your other legal rights.