Accessibility statement

Our commitment

Arqaan is made by Hajify Ltd. We want this website and the app to work for as many people as possible, including disabled people and people who use a screen reader, screen magnification, voice control or switch access.

We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA. We don't meet all of it yet. This page says what works, what doesn't, and how to get help in the meantime.

How accessible Arqaan is

This website

• You can reach every link and control with a keyboard, and an outline shows where you are.
• Pages fit narrow screens and zoomed-in text without scrolling sideways.
• Pages have headings in order, and images have text descriptions.
• The moving garden at the top of the home page has a pause button. It also holds still while you use the keyboard in that part of the page, and if your device is set to reduce motion.

The app

• Text grows with your phone's text size setting, up to 130%, and follows Bold Text. The Qur'an reader has its own text sizes as well.
• A dark theme with stronger contrast is in Settings, under Preferences, Theme.
• Most buttons and switches have names and states that screen readers can read out.
• Most buttons and controls are at least 44 points across.
• Many animations stop or calm down when your phone's reduce-motion setting is on.
• Most Arabic is shown with a transliteration and an English translation.
• Lessons and quizzes have no time limit.
• You can sign in with Google, or with Apple on iPhone, and a password manager can fill in your email address and password.

Known limitations

These are the parts we know don't fully meet WCAG 2.2 level AA. If you find others, please tell us.

On this website

• The launch countdowns on the home page change every second. You can't pause them, and they keep changing if your device is set to reduce motion.
• Some small grey, green and amber text is lighter than the contrast standard asks for.
• On screen, the email box in the waitlist form is labelled only by faint placeholder text, which disappears as you type. Its border is faint too.
• The waitlist form may show a check that you're not a bot.
• Turning the garden at the top of the home page needs a drag, or the arrow keys once the garden has keyboard focus. Zooming it needs a mouse wheel, and while the pointer is over the garden the wheel zooms it instead of scrolling the page.
• To a screen reader, the garden is not marked as a control, although its label explains how to turn it.
• In the example league on the home page, names are cut off on very narrow screens, and screen readers hear each row as numbers without their column names.
• Some screen readers may not read the labels on the countdowns and on the tree growth example on the home page.

In the app

• We have not yet tested Arqaan from start to finish with VoiceOver on iPhone or TalkBack on Android.
• Text in Arqaan grows with your phone's text size only up to 130%. The Qur'an reader has its own text size setting as well.
• Arqaan works in portrait only. The 3D practice scenes work in landscape only.
• Some buttons are not named for screen readers. These include the back buttons on Settings, Subscription, Profile and a friend's garden, and the tiles you tap to plant your first seed.
• Headings on most screens are not marked as headings, so screen readers can't jump from one to the next.
• Most text boxes, such as the email and password boxes for signing in, are labelled only by a hint inside the box, which disappears as you type.
• On the Home screen, whether each prayer is logged, missed, current or still to come is shown by colour, and screen readers do not read it out.
• On the Learn path, whether a lesson is done, next or locked is shown by an icon, and screen readers do not read it out.
• In quizzes, screen readers do not say which answer you picked or announce the result. The result appears as text under the question.
• Some small text in the light theme has less contrast than recommended. The dark theme has stronger contrast; you can turn it on in Settings, under Preferences, Theme.
• Short messages at the bottom of the screen disappear after about 2 seconds. The Undo button after logging a prayer stays for about 4.5 seconds. You cannot make them stay longer.
• Arabic text is not marked as Arabic, so a screen reader may read it with the wrong voice. Most Arabic is shown with a transliteration and an English translation.
• Screen readers do not announce when Hadi is typing or when a new reply arrives.
• Most buttons and switches cannot be reached with an external keyboard.
• You can turn and zoom the garden only with drag and pinch gestures. Planting a tree works with a single tap.
• The Haptics switch in Settings does not yet turn off vibration. The dhikr counter has its own Haptic switch.
• Some animations keep moving when your phone's reduce-motion setting is on.
• When you sign in, sign up or reset your password with an email address, Arqaan may show a check that you're not a bot.
• The six 3D practice scenes (Tawaf, Sa'i, Mina, Muzdalifah, Jamarat and the Sacrifice) cannot be used with a screen reader.
  • They need two thumbs to move and look around.
  • Some instructions refer to colours, such as "the green start line".
  • Their text does not follow your phone's text size.
  • Some dua cards in them do not yet show the English translation.
  • They are optional: you can finish every lesson and test without them.

If you can't use something

Email contact@hajify.com and tell us what you were trying to do, and we'll help you do it another way. Some things already have another way:

• Joining the waitlist. If you can't complete the check on the form, email us and we'll add you to the list.
• Signing in to the app. If you can't complete the check when you use an email address, sign in with Google, or with Apple on iPhone, instead.
• Low contrast in the app. Turn on the dark theme in Settings, under Preferences, Theme.
• The moving garden. Press the pause button under it on the home page, or set your device to reduce motion.
• The 3D practice scenes. They are optional: you can finish every lesson and test without them.
• Deleting your account without the app. Ask by email, as Delete your account explains.
• Another format. If you need something on this website in a different format, such as plain text or large print, email us.

Feedback and contact

Tell us about any barrier you meet on this website or in the app, or ask us for help with one. A person reads that mailbox, and we reply within 14 working days.

Technical information

Hajify Ltd wants this website and the Arqaan app to be accessible, and measures them against the Web Content Accessibility Guidelines (WCAG) version 2.2, level AA. For the app, we apply WCAG the way W3C's guidance for software and mobile apps (WCAG2ICT) describes.

Conformance status

This website and the app are partially conformant with WCAG 2.2 level AA. Partially conformant means that some parts don't fully meet the standard. They are listed under Known limitations above.

What they are built with

This website relies on HTML, CSS, JavaScript and WAI-ARIA. The garden at the top of the home page also needs WebGL; without it, a drawn garden shows instead. The app is built with Flutter, and its 3D practice scenes with Unity.

How we tested

We checked this website and the app ourselves on 16 October 2026. This was a self-assessment, made up of:

• automated checks of every page of this website with axe-core 4.10.2;
• keyboard and zoom checks of every page in a Chromium browser, including narrow screens and wider text spacing;
• a review of the app's code and design documents.

We have not yet tested with screen readers, such as VoiceOver, TalkBack, NVDA or JAWS, or with voice control, and no one outside Hajify Ltd has audited Arqaan.

What we're doing next

• Test the app from start to finish with VoiceOver on iPhone and TalkBack on Android, and fix what we find.
• Work through the limitations on this page, starting with those that stop someone finishing a task.
• Update this statement each time we fix one of them.

About this statement

We prepared this statement on 16 October 2026. It covers this website and version 1.0.0 of the app. We will review it by October 2027.