Chapter 1
WCAG 2.2 AA Target
Moseyaround Limited aims to make the Mosey public website and mobile application accessible to as many people as possible. WCAG 2.2 Level AA is our accessibility target. We are not claiming full WCAG 2.2 AA conformance until the relevant website and production app have been tested sufficiently to support that claim.
1. Scope
This statement applies to the public Mosey website and the Mosey mobile application published by Moseyaround Limited.
The website and app are different technical products and may have different accessibility limitations. Third-party content or interfaces embedded in or opened from Mosey may also have accessibility characteristics controlled by the relevant provider.
Back to top ↑2. Accessibility standard and current status
Our target is Web Content Accessibility Guidelines (WCAG) 2.2 Level AA, using appropriate mobile accessibility guidance when applying WCAG principles to the native mobile app.
Mosey does not currently claim that either the website or production mobile app is fully WCAG 2.2 AA conformant. A full accessibility audit has not yet been completed across every relevant production screen, interaction and assistive-technology combination.
We will update this statement after meaningful testing and will only describe a product as fully conformant when the evidence supports that statement.
Back to top ↑3. What we are working towards
Accessibility work includes considering:
- sufficient colour contrast for text, controls and meaningful graphical content
- text resizing, reflow and readable layouts
- logical keyboard/focus order and visible focus indicators on the website
- meaningful headings, labels and accessible names
- screen-reader labels, roles, states and announcements in the app
- adequate touch/click target sizes and spacing
- alternatives to gestures or motion-only interaction where needed
- reduced-motion preferences where animation could create a barrier
- clear error messages and instructions
- meaningful alternative text for informative images
- avoiding unnecessary flashing or rapidly changing content
- compatibility with common assistive technologies and platform accessibility settings
4. Known and potential limitations
Until the formal audit is completed, the following areas should be treated as known or potential limitations rather than assumed to be fully accessible:
- some animated mascot, walking, game or reward interfaces may require further reduced-motion, screen-reader or non-visual alternatives
- some game interactions may require further testing for keyboard, switch-control, VoiceOver/TalkBack and non-gesture alternatives
- colour contrast and text-over-image combinations may require adjustment on individual screens or promotional graphics
- some custom controls may require improved accessible names, roles, states, focus order or announcements
- touch-target size and spacing require systematic testing across the production app
- third-party offerwall, advertising or reward interfaces may have accessibility limitations outside Mosey’s direct control
- PDF versions of legal documents may not be as accessible as the corresponding HTML legal pages; the HTML pages should be treated as the preferred accessible version
This list will be replaced or refined with specific verified findings as testing is completed.
Back to top ↑5. Website and mobile-app testing
We intend to use a combination of automated checks and manual testing. Automated testing alone is not sufficient to establish WCAG conformance.
Relevant manual testing should include keyboard-only navigation for the website and platform assistive technologies such as VoiceOver and TalkBack for the app, together with checks for zoom/text scaling, orientation, focus order, touch targets, labels, contrast and motion.
Material new screens and components should be checked for accessibility as part of development rather than waiting solely for an annual review.
Back to top ↑6. Accessibility and reward earning
Mosey does not treat legitimate accessibility or assistive technology as cheating merely because it changes how a member interacts with the app. The Fair Play & Anti-Cheat Policy contains the applicable accessibility-technology protection.
Where an accessibility barrier prevents use of a feature, contact us so that we can consider an accessible alternative or reasonable adjustment where appropriate.
Back to top ↑7. Requesting an accessible format or reasonable adjustment
If you need information in a different accessible format, need help using a Mosey feature, or wish to request a reasonable adjustment, contact [email protected] or [email protected].
Please tell us what you are trying to access, the barrier you encountered, the device or assistive technology involved if relevant, and the format or adjustment that would help. You do not need to disclose more information about a disability than is reasonably necessary to explain the requested adjustment.
We will consider requests individually and aim to provide a practical accessible alternative where reasonably possible.
Back to top ↑8. Reporting an accessibility problem
If you find an accessibility problem that is not listed here, email [email protected]. Accessibility reports are welcomed and will not affect your account, rewards or ability to make a complaint.
For general support, contact [email protected]. For legal enquiries, contact [email protected].
Back to top ↑9. Third-party services
Mosey may use third-party services such as authentication providers, rewarded-advertising/offerwall providers and reward fulfilment services. We aim to consider accessibility when selecting and reviewing providers, but we cannot represent that every third-party interface is WCAG 2.2 AA conformant.
Where a third-party barrier materially prevents access to a Mosey feature, members can report it so we can consider available alternatives, provider escalation or other reasonable steps.
Back to top ↑10. Review and improvement
This statement will be reviewed after material accessibility testing, after significant changes affecting accessibility, and at least annually.
Last reviewed: 25 August 2026. Next scheduled review: no later than 25 August 2027.
Once the first structured audit has been completed, this statement should record the testing date, scope/method and verified non-conformities rather than relying on the provisional limitation list above.
Back to top ↑11. Legal position
Accessibility obligations can arise under applicable equality, disability and consumer laws even where a particular public-sector accessibility regulation does not apply to a private company. Nothing in this statement limits any non-waivable right or obligation under applicable law.
This statement describes our current accessibility approach and target; it is not a guarantee that every device, assistive technology, third-party service or feature will operate without an accessibility issue.
Back to top ↑18. Accessibility Standard and Target
Mosey uses WCAG 2.2 Level AA as its target for the public website and for web-style content within the service where the criteria are applicable. Native mobile controls are also designed with platform accessibility guidance in mind.
This is a target and not a claim that every page or app screen currently conforms in full. Known issues will be recorded, prioritised and reviewed as testing progresses.
Back to top ↑19. Known Limitations and Review
Known or potential areas requiring continued testing include animation and motion preferences, colour contrast in some branded artwork, alternative text for promotional imagery, keyboard/focus behaviour in interactive components, screen-reader labelling in game interfaces, and accessibility of third-party offerwall or reward-provider content.
Last accessibility review: 21 August 2026. Next scheduled review: no later than 21 August 2027 and sooner after material redesigns or significant accessibility reports.
Back to top ↑20. Reasonable Adjustments
If a disabled user experiences a barrier, they may contact [email protected] to request a reasonable adjustment or an accessible alternative. Requests will be considered individually in accordance with applicable equality law and practical circumstances.
Back to top ↑Document record
Version history
| Chapter title | Effective date | Status |
|---|---|---|
| WCAG 2.2 AA Target | 25 August 2026 | Approved master wording |
Contact [email protected] or [email protected].
