Accessibility Statement

Last updated: 30 July 2026

1. Our Commitment

FoundPhones is committed to making its website, dashboard, QR-code recovery pages, and related digital services accessible and usable for as many people as possible.

We want FoundPhones to work well for people using different devices, browsers, screen sizes, assistive technologies, and access needs.

This includes people who may use:

Screen readers
Keyboard-only navigation
Screen magnification
Voice recognition software
High contrast settings
Reduced motion settings
Mobile accessibility features
Alternative input devices

FoundPhones is a service designed to help people recover lost phones. That means accessibility is especially important because users, finders, and trusted contacts may need to use the service quickly, calmly, and safely.

2. Accessibility Standard We Aim For

We aim to make FoundPhones meet the Web Content Accessibility Guidelines, also known as WCAG, version 2.2 at Level AA where reasonably possible.

WCAG is an internationally recognised standard for making websites and digital services more accessible.

The main accessibility principles we work towards are that FoundPhones should be:

Perceivable: information should be available in ways people can see, hear, or otherwise understand.
Operable: the website should be usable with a keyboard, mouse, touch screen, and assistive technologies.
Understandable: content, forms, navigation, and error messages should be clear.
Robust: the website should work reliably across modern browsers, devices, and assistive technologies.

3. How Accessible FoundPhones Is

We are working to make FoundPhones accessible across the main parts of the service, including:

The public website
Account registration and login
User dashboard pages
QR-code recovery pages
Help and FAQ pages
In-account support (dashboard support tickets for signed-in customers)
Email support and accessibility contact channels
Subscription and checkout pages
Cookie and privacy controls
Mobile-friendly layouts

We aim to support:

Clear headings and page structure
Readable text and good colour contrast
Keyboard navigation
Visible focus states
Descriptive links and buttons
Labels for form fields
Useful error messages
Responsive layouts for mobile and desktop
Text alternatives for important images
Simple, plain English content where possible

4. QR Codes and Recovery Pages

FoundPhones uses QR codes to help return lost phones.

We aim to make QR recovery pages simple, fast, and accessible. This means recovery pages should:

Load clearly on mobile devices
Use readable text
Avoid unnecessary visual clutter
Show important contact or recovery information clearly
Use accessible form labels where a finder can submit information
Avoid relying only on colour to explain meaning
Work with screen readers where reasonably possible

Because QR codes are visual by nature, users should also make sure their recovery information is available in a clear and readable way once the QR code has been scanned.

5. Known Accessibility Limitations

We are still reviewing and improving FoundPhones.

Some areas may not yet be fully accessible. These may include:

Some images or icons that may need better alternative text
Some colour combinations that may need contrast review
Third-party checkout or payment pages outside our full control
Mobile app or lock-screen behaviour that depends on device settings and operating system support
Features that are added or changed before they have been fully accessibility tested

We will continue working to identify and fix accessibility issues.

6. Third-Party Services

FoundPhones may use third-party services for things such as payments, hosting, analytics, security, email delivery, app stores, or embedded tools.

We do not fully control the accessibility of third-party services, but we aim to choose reliable providers and improve the overall user experience wherever reasonably possible.

If you experience an accessibility issue with a third-party part of the service, contact us and we will try to help or provide an alternative route where possible.

7. What We Are Doing to Improve Accessibility

We are working to improve accessibility by:

Reviewing pages against WCAG 2.2 AA guidance
Testing key pages with keyboard navigation
Checking colour contrast
Improving form labels and error messages
Using clear headings and page structure
Making recovery pages simple and mobile friendly
Improving alt text for important images
Avoiding unnecessary animation or motion
Keeping content as clear as possible
Reviewing accessibility when adding new features

As FoundPhones grows, accessibility will remain part of the design, development, and testing process.

8. Alternative Formats and Support

If you need information from FoundPhones in a different format, or if you have difficulty using part of the website, contact us.

We will do our best to provide a reasonable alternative.

This may include:

Explaining information by email
Helping you update account or recovery details
Providing information in simpler wording
Helping with recovery page setup
Reviewing an accessibility problem you report

There is no separate public “contact us” web form. You can:

Email the accessibility contact below
Read [Help & FAQ](/faq)
Use Dashboard → Support when you are signed in (support tickets)
Use the website AI chat “talk to the team” option where it is available

noreply@foundphones.com

Please include:

The page or feature you were using
What went wrong
What device and browser you were using, if known
Any assistive technology you were using, if relevant
What would help you access the information or service

9. Reporting Accessibility Problems

If you find an accessibility problem on FoundPhones, we would like to know.

Please contact us at:

noreply@foundphones.com

We aim to review accessibility reports within a reasonable time and fix issues where reasonably possible.

Some fixes may take longer depending on the nature of the problem, the part of the service affected, and whether a third-party provider is involved.

10. Reasonable Adjustments

We understand that different people have different access needs.

Where reasonable and practical, we will make adjustments to help disabled users, finders, trusted contacts, and customers use FoundPhones.

This may include providing support by email, helping with account setup, helping with recovery page information, or reviewing barriers that prevent someone from using the service.

11. Technical Information

FoundPhones aims to work with:

Current versions of major browsers
Desktop, tablet, and mobile devices
Keyboard navigation
Screen readers and assistive technology where reasonably possible
Built-in accessibility features on modern operating systems

FoundPhones may not work perfectly on very old browsers, unsupported devices, outdated operating systems, or heavily customised browser setups.

12. Compliance Status

FoundPhones is currently working towards WCAG 2.2 Level AA accessibility.

We do not yet claim full WCAG 2.2 AA compliance across every page and feature because the website, dashboard, app-related features, and QR recovery tools are still being reviewed and improved.

This statement will be updated as accessibility testing and improvements continue.

13. Preparation of This Statement

This Accessibility Statement was prepared on 5 July 2026 and updated on 30 July 2026.

It is based on a review of the FoundPhones service, including the public website, recovery pages, account features, help/support channels, and app-related functionality.

We intend to review this statement regularly and update it when significant changes are made to the website, dashboard, recovery pages, or app features.

14. Contact

For accessibility support or to report an accessibility issue, contact:

noreply@foundphones.com

For general support, contact:

noreply@foundphones.com

For privacy-related requests, read our [Privacy Policy](/privacy) or contact:

noreply@foundphones.com