Accessibility Statement

Published: 2026-08-11 · Version 1.0 · Applies to: the Questify mobile app (Android and iOS) and this website

Questify is built and run by one person. We want it to be usable by as many people as possible, and we would rather tell you honestly what does not work yet than claim a level of accessibility we have not reached.

This statement describes the current, real state of the app, based on an audit completed on 11 August 2026. It is not a marketing claim.

1. Conformance status

The Web Content Accessibility Guidelines (WCAG) define requirements for making digital content more accessible. WCAG 2.1 Level AA is the standard most commonly referenced in law, and it is the standard we are working toward.

The single largest barrier is the Map tab. If you use a screen reader, the map is effectively unusable today. See §4 for the routes that do work.

2. What works today

The following were verified during the audit:

• Main body text and buttons meet AA contrast comfortably — primary text measures between 15.6:1 and 20.2:1 against its background, well above the 4.5:1 requirement.
• Most buttons announce themselves as buttons to TalkBack and VoiceOver, with their label read out.
• The Board tab is a genuine non-map alternative for browsing and accepting quests, and for browsing landmarks. It is a standard scrolling list.
• Escrow and quest status are announced as text, not conveyed by colour alone.
• Reduce Motion is partially honoured — when your device has it enabled, Questify mutes haptic feedback.
• No flashing or strobing content anywhere in the app. There is no known seizure risk.
• No time limits. No action in Questify expires while you are completing it, and there is nothing you must do within a countdown.
• No CAPTCHA. You are never asked to identify images or transcribe distorted text to use the app.
• Standard system text fields throughout, so system keyboards, dictation, switch access and external keyboards behave normally.
• This website uses semantic headings, a skip link, visible focus outlines, and respects your browser text size.

3. Known limitations

We are listing these plainly because you deserve to know before you rely on the app.

For people who use a screen reader (TalkBack, VoiceOver)

• The Map tab is not usable. Map pins are not exposed to the screen reader at all — they are not announced, not labelled, and not reachable by swiping. The map is the app's default tab on launch.
• Taverns can only be joined or created from the map. There is currently no alternative route, which means this feature is not available to you. We consider this the most serious gap and it is first on our fix list.
• Dropping a marker can only be done from the map (by long-pressing a location). Same limitation as above.
• Images have no alternative text. Landmark artwork, achievement badges, profile photos and quest photos are announced as unlabelled images or skipped entirely.
• Some controls are unlabelled and will be announced only as "button". These include the chat send and attachment buttons, the show/hide password toggle, and several close buttons on dialogs.

For people with low vision

• Text size is capped at 130%. If your device is set to a larger system text size, Questify will not grow text beyond 130% of its default. This cap exists to prevent layout breakage and is a limitation we intend to raise.
• Secondary and faded text does not meet AA contrast. Muted labels, timestamps, helper text and input placeholders currently measure between roughly 1.9:1 and 3.4:1, below the 4.5:1 requirement. Primary text is unaffected.
• The app is dark-themed by default and does not offer a high-contrast mode.

For people sensitive to motion

• Reduce Motion is not fully honoured. With Reduce Motion enabled, the pulsing location marker, the animated starfield background, and automatic photo-carousel advancement still animate.
• The photo carousel advances on its own and has no pause control. You can still swipe it manually.

For people with motor or dexterity disabilities

• The app is locked to portrait orientation. If you use a mounted device or an attached keyboard in landscape, you cannot rotate Questify to match.
• Dropping a marker requires a long press on the map, with no alternative single-tap route.

Cognitive and general

• Some errors are shown only as a brief message at the bottom of the screen, which may disappear before it is read.
• The app is available in English, Montenegrin, Italian and Russian. It has not been reviewed for plain-language readability.

4. Alternative ways to use Questify

If the map is not usable for you, these routes are:

If a barrier stops you from doing something in Questify, write to us and we will do it with you or for you, at no cost and without you having to explain your disability. This is a standing offer, not a favour.

5. Tell us about a barrier

If you hit something in Questify you cannot use, we want to hear about it — it is the fastest way for us to fix the right things.

Email: hello@usequestify.com
Subject line: “Accessibility — [what you were trying to do]”

Please tell us, as much as you are able and comfortable sharing:

• What you were trying to do, and where in the app
• Your device and operating system version
• Which assistive technology you use, if any

We aim to acknowledge every accessibility report within 5 working days and to tell you either how to work around the problem or when we expect to fix it. If a report reveals a barrier that blocks you from a core feature, we will offer to complete that action on your behalf in the meantime.

You are never required to disclose a diagnosis or provide proof of disability to get help from us.

6. How we assessed this

This statement is based on a self-assessment carried out on 11 August 2026 against WCAG 2.1 Level AA, covering:

• A review of every screen in the app's source code for accessibility labelling, semantic roles and focus handling
• Calculated contrast ratios for the app's text and interface colour pairings
• A review of text-scaling, reduce-motion and orientation behaviour
• A review of the sign-up, quest, chat and profile flows for time limits, CAPTCHAs and error handling

It has not been audited by an independent third party, and it has not yet been tested by users who rely on assistive technology day to day. Both are things we intend to do. Until then, treat this statement as our best honest reading of our own work — and please correct us where we have got it wrong.

7. What we are fixing, in order

These are our priorities, highest impact first. They are intentions rather than contractual commitments, and we will update this page as each lands.

1. Label the unlabelled controls in chat, sign-up and posting, so screen-reader users are not blocked in core flows.
2. Give Taverns and marker-posting a non-map route, so no feature is map-only.
3. Raise the 130% text-size cap and fix the layout problems that follow.
4. Fix secondary-text and placeholder contrast to meet the 4.5:1 requirement.
5. Add labels to map pins so the map becomes navigable rather than silent.
6. Complete Reduce Motion support and add a pause control to the photo carousel.
7. Add alternative text to images, starting with the ones that carry meaning.

8. Scope and limits of this statement

This statement covers the Questify mobile app for Android and iOS, and the pages on usequestify.com.

It does not cover third-party content or services reached from within Questify — including map tiles and map data supplied by third parties, the app stores themselves, and content written by other users. We do not control their accessibility.

Questify is operated from Podgorica, Montenegro by a sole operator. Nothing on this page is legal advice, and this statement does not itself create or waive any legal right.

9. Contact and escalation

Email: hello@usequestify.com
Operator: Vladimir Rakočević (sole operator of Questify)
Location: Podgorica, Montenegro

If you are not satisfied with how we respond to an accessibility report, tell us so directly in a reply — we will escalate it internally and give you a written answer. If you wish to take the matter further, you may raise it with the consumer-protection or equality body responsible in your country of residence.

See also our Terms of Service and Privacy Policy.