← Back to Ansitly
Accessibility Statement
Last updated: September 30, 2026
Ansitly exists specifically to make the khutbah accessible — live
captions for Deaf and hard-of-hearing attendees, and real-time
translation for congregants who don't speak the khutbah's language.
Accessibility isn't a feature we bolted on afterward; it's the reason
this tool exists. This page describes, honestly, what we've done, how
well it works, and where it still falls short.
Conformance target
We aim for WCAG 2.1 Level AA wherever it meaningfully
applies to a live, real-time captioning tool — some WCAG guidance is
written for static content and doesn't map cleanly onto a screen that is,
by design, constantly updating. This statement is a good-faith account of
where we stand, not a claim of full or certified conformance.
What's in place today
- Adjustable caption size — the A+ / A− controls resize
captions from 24px up to 96px, independent of the browser's own zoom.
- Screen-reader announcements for live captions — each caption
is announced through a dedicated live region as it appears, separately
from the visual display, so a screen-reader user gets the same running
commentary a sighted viewer reads on screen.
- Correct language tagging — each caption line, and any
Qur'anic Arabic quoted within it, is marked with its actual language
(Urdu, English, or Arabic) so assistive technology uses the right
pronunciation rather than reading Urdu or Arabic script as if it were
English.
- Keyboard operability — every control is a standard
button, input, or select element, reachable and operable by keyboard
alone; the control bar can also be shown or hidden with a single key
(C) for a distraction-free, large-text caption view.
- High-contrast design — the primary caption text runs
at a contrast ratio of roughly 13:1 against its
background (WCAG AAA), and every other text/background pairing on the
screen has been checked and meets at least AA for its actual size.
Known limitations
We'd rather list these plainly than let you discover them the hard way:
- Captions are generated by real-time speech recognition and AI
translation. Both can make mistakes — background noise, an
unfamiliar accent, cross-talk, or a spoken word the model mishears can
all produce an inaccurate caption. Treat the captions as an aid to
following along, not as a verbatim legal transcript.
- Urdu speech recognition on iPhone runs on different
underlying technology than on Android or desktop, because
Apple's own on-device speech engine currently has no Urdu support at
all, on any iPhone — a gap in Apple's platform, not a choice we made.
We built a separate path to work around it; if it ever behaves
differently from Arabic or English recognition on the same device,
that's why.
- Accessibility review has focused on the main caption screen —
the masjid sign-up, dashboard, and admin pages have not yet had the
same level of screen-reader and keyboard testing.
- This statement describes our current, ongoing effort. It is not a
certification of full conformance to any specific standard.
Browser and device support
Live captioning needs a browser with built-in speech recognition:
Google Chrome or Microsoft Edge (desktop or Android), or Safari on
iPhone/iPad. Firefox has no live speech recognition support and cannot
run this tool. The page will tell you plainly if your current browser
can't run it, rather than failing silently.
Reporting an accessibility problem
If any part of this tool is hard to use with a screen reader, keyboard
alone, at a different text size, or with any other assistive technology,
please tell us — we want to fix it.
Technical details we've verified
| Text | Contrast ratio | WCAG level |
| Caption text (cream on dark teal) | 13.2:1 | AAA |
| Status text | 8.9:1 | AAA |
| Qur'an verse quotes (gold) | 6.3:1 | AA |
| Hadith quotes (green) | 5.6:1 | AA |
| Error messages | 4.9:1 | AA |
This statement is reviewed whenever the app's accessibility features
change in a meaningful way.
Accessibility Statement ·
Terms of Service ·
Privacy Policy