Target standard and scope
We target WCAG 2.2 Level AA, the international reference most digital accessibility laws and policies build on, and review every new page against it before publishing.
This statement covers all pages on wesalna.com in both Arabic and English, including the Mushaf and its audio player, prayer times, Qibla, the calculators, radio, articles, stories and the policy pages.
Declared status: partially conformant. That means most success criteria are met, with the limited exceptions listed under "Known limitations" below. We use that wording deliberately, because a full conformance claim would require an independent third-party audit of every page.
Keyboard navigation
Everything reachable with a mouse or touch is reachable with a keyboard: Tab to move, Enter or Space to activate, Escape to dismiss dialogs and menus.
Focus order follows the logical reading order of the page, and we never use positive tabindex values that would scramble it.
The focus indicator is a clearly visible high-contrast ring on every interactive element; we do not remove the default indicator anywhere.
Dialogs and menus trap focus while open and return it to the trigger on close, so keyboard users never get stranded behind an overlay.
Screen readers and semantics
We use native semantic HTML: header, navigation, a single main landmark and footer, with exactly one page heading and a heading hierarchy that never skips levels.
Every button and link has an accessible name, and icon-only controls carry an explicit label that reads out clearly, such as "Play recitation" or "Close menu".
Illustrations in articles and stories carry alternative text describing what they convey; purely decorative artwork is hidden from screen readers so it does not add noise.
Updates that happen without a page reload, such as Mushaf search results, the Tasbih counter or validation messages, are announced through live regions so they are not silent.
Vision, contrast and typography
Text contrast targets a minimum of 4.5:1 for body text and 3:1 for large text and interface components, and colour is never the only carrier of meaning: error, success and warning states pair colour with an icon and explicit words.
Coloured Tajweed rendering in the Mushaf has a text alternative that names each rule in words rather than relying on hue, and colouring can be switched off entirely.
The Mushaf reader offers font size and line height controls, and pages can be zoomed to 200% without losing content or function because the layout reflows instead of forcing horizontal scrolling.
There is no blinking text and no content that changes rapidly on its own, which matters for readers with photosensitivity.
Motion and audio
We honour the system reduced-motion preference: with it enabled, entrance and transition animations are removed and the interface stays still and fully functional.
No audio starts on its own. Recitation, radio and narration begin only from an explicit action, every player has a clear stop control and volume, and two players can never run at once.
Pages with narrated audio always present the same text on screen, so no content is audio-only.
Forms, fields and calculators
Every input in the Zakat calculator, the inheritance calculator and the other tools is tied to a persistent label rather than placeholder text that vanishes as you type.
Error messages describe the problem in words, name the field they belong to and appear next to it instead of relying on a red border.
No input has a time limit, and no core function is gated behind a visual CAPTCHA.
Mobile, touch and language
Primary tap targets are at least 44x44 pixels with enough spacing to avoid mis-taps, and the interface works in both portrait and landscape.
Anything driven by a complex gesture, such as dragging or rotating the Qibla compass, has a single-tap or numeric-readout alternative.
The platform is fully bilingual: native RTL in Arabic, LTR in English, with the language attribute and text direction set on every page so screen readers pronounce each language correctly instead of mixing them.
How we test
We combine automated page-level auditing with manual review: full keyboard-only navigation, reading pages with a screen reader, contrast measurement, 200% zoom testing and a pass on a small phone screen.
We test with mainstream screen readers on up-to-date systems: VoiceOver on iOS and macOS, TalkBack on Android and NVDA on Windows, using current Chrome, Safari, Firefox and Edge.
Known limitations
Content we do not produce cannot be guaranteed: Quran radio streams come from third-party providers, and their quality or availability is outside our control.
A few long tables, such as monthly prayer timetables, still need horizontal scrolling on very narrow screens; we are converting them to cards at those sizes.
Qibla compass accuracy depends on the device sensor, which is why the bearing is always shown numerically as a compass-free alternative.
Some alternative text on older illustrations is shorter than we would like, and we are expanding it progressively.
Settings that help in your browser
Zoom with Ctrl and + (Command and + on a Mac), and enable reduced motion or increased contrast in your operating system's accessibility settings; the platform responds to those preferences automatically.
The Mushaf reader remembers your font size and line height on your device, so you do not have to set them again on each visit.
Tell us, and ask for an alternative
Hit a barrier? Email access@wesalna.com with the page URL, a description and the assistive technology you use. Accessibility reports are handled as a priority and we aim to reply within five working days.
If a barrier keeps you from information, tell us and we will provide it in an accessible alternative format. For anything unrelated to accessibility, see the contact page.