FansaChat

Legal

Accessibility Statement — FansaChat

Last updated: 3 August 2026

1. Our commitment

Aminur Rahman Noor, the operator of FansaChat, is committed to making fansachat.com usable by as many people as possible, including people who use screen readers, keyboard-only navigation, magnification, or other assistive technology.

2. The standard we are working to

We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA — the standard referenced by EN 301 549 in the EU, by the Public Sector Bodies Accessibility Regulations in the UK, and by Section 508 in the US.

2a. What FansaChat is built with, and what it works with

Accessibility here relies on HTML, WAI-ARIA, CSS and JavaScript. The site needs JavaScript enabled; with it switched off, most of the application will not work.

We aim to support current versions of Chrome, Edge, Firefox and Safari, on desktop and mobile, used with the screen reader normally paired with each platform — NVDA or JAWS on Windows, VoiceOver on macOS and iOS, and TalkBack on Android. Older browsers may work but are not tested.

3. How conformant FansaChat is today

FansaChat is partially conformant with WCAG 2.2 Level AA. Parts of the site meet the standard; the areas below do not yet.

Known limitations:

  • Animated backgrounds are not reduced for users who ask for less motion. The site respects the prefers-reduced-motion setting in several places — smooth scrolling, and the /about and waitlist pages — but the animated aurora background on the landing page deliberately keeps moving regardless. That is a design decision, and we are naming it rather than hiding it. (WCAG 2.3.3 Animation from Interactions)
  • The workflow view. Workflows are shown as a branching diagram. A diagram is hard to convey non-visually, and the text alternative is not yet complete. (WCAG 1.1.1 Non-text Content)
  • Third-party sign-in. The Google sign-in screen is provided by Google and we do not control its accessibility.
  • Not yet independently audited. Everything here is self-assessed.

What the audit confirmed is working: the page has proper <main> and <nav> landmarks, a skip-to-content link for keyboard users, exactly one <h1> per page with headings in sequence, and the decorative WebGL backgrounds are hidden from screen readers rather than read out as noise.

What we deliberately did not do: FansaChat is not a drag-and-drop node canvas. You describe what you want in ordinary sentences and it is built for you. That design is, as it happens, considerably more accessible than the node-dragging interfaces it replaces — but we are not claiming credit for conformance we have not measured.

4. What we have done

  • Semantic HTML headings and landmarks
  • Text alternatives for meaningful images; decorative images hidden from assistive technology
  • Keyboard operation of the main navigation, forms and buttons
  • Visible focus indicators
  • Colour contrast checked against the AA thresholds
  • Forms with associated labels and clear error messages

5. Telling us about a problem

If something on FansaChat is not accessible to you, please email support@fansachat.com.

It helps if you can tell us: - the page address - what you were trying to do - what assistive technology you use, if any

We will acknowledge your email within 5 working days, tell you what we can do and by when, and offer a workaround while we fix it.

6. If we do not resolve it

If you are not satisfied with our response, you can escalate to the accessibility enforcement body in your country — for example the Equality Advisory and Support Service in the UK, or the national body designated under the Web Accessibility Directive in EU member states. Nothing here affects your legal rights.

7. Preparation of this statement

This statement was prepared on 2 August 2026 and last revised on 3 August 2026. It is based on a self-assessment of fansachat.com carried out by the operator. We review it when the site changes materially, and at least once a year.

8. Contact

support@fansachat.com