Accessibility Statement

Pause Ltd is committed to making the Pause mobile application accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.

This accessibility statement applies to the Pause mobile application for iOS and Android.
Application name: Pause

 Organisation: Pause Ltd 

Platforms: iOS and Android App versions covered by this statement: iOS 2.7.1 / Android 3.3.8

 Statement prepared: April 2026

 Statement last reviewed: May 2026

The Pause app is designed to support parents and carers through digital parenting tools, guidance and personalised support. We want as many people as possible to be able to use the app.
For example, we want users to be able to:

use the app on supported iOS and Android devices
use operating-system accessibility settings such as larger text, screen zoom and speech input where supported
use the app with screen reader software such as VoiceOver on iOS and TalkBack on Android
understand the content, which we aim to write as clearly as possible
complete key journeys such as onboarding, entering a group/access code, setting up a child profile, using tools, using Ask Shelley, writing journal entries, viewing programme and schedule information, and accessing support and privacy information

Pause Ltd is currently carrying out an internal accessibility audit of the Pause app against WCAG 2.2 Level AA.

Compliance status

The Pause mobile application is currently being assessed against the Web Content Accessibility Guidelines version 2.2 AA standard through an internal self-assessment.
The Pause mobile application is partially compliant with the Web Content Accessibility Guidelines version 2.2 AA standard, due to the non-compliances listed below.
The statement will be updated when the current internal audit is complete and when significant accessibility fixes are released.

Non-accessible content

The content listed below is non-accessible for the following reasons:

Text size, resizing and layout

Some screens may not yet fully support larger operating-system text sizes without text truncating, overlapping or becoming harder to use.
This may affect WCAG 2.2 success criterion 1.4.4 Resize Text and 1.4.10 Reflow.
We are testing key screens using iOS Dynamic Type and Android font/display size settings. Issues found during testing will be prioritised for remediation. We aim to complete the current review and fix high-impact issues affecting core journeys by June 2026.

Colour Contrast

The app uses a fixed visual design and colour palette. Colour contrast is considered during design, but a full contrast check is currently being completed across screens, states and components.

This may affect WCAG 2.2 success criterion 1.4.3 Contrast Minimum and 1.4.11 Non-text Contrast.
We are checking text, icons, controls and important visual states using contrast tools and accessibility scanners. We aim to complete the current contrast review and address high-impact issues by June 2026.

Touch target size

Our internal audit checks found touch targets to meet the WCAG 2.2 minimum of 24 by 24 CSS pixels in the areas reviewed so far. We are also checking controls against platform best practice, including Apple’s 44 by 44 point guidance and Android’s 48 by 48 dp guidance where practical.

Some controls may need further improvement to meet platform best practice consistently.
This may affect WCAG 2.2 success criterion 2.5.8 Target Size (Minimum).
We aim to review and improve touch targets on key journeys by June 2026

Screen reader labels and roles

Some custom controls, images, cards or interactive elements may not yet have complete accessibility labels, roles or descriptions.
This may affect WCAG 2.2 success criterion 1.1.1 Non-text Content, 1.3.1 Info and Relationships, 2.4.6 Headings and Labels, and 4.1.2 Name, Role, Value.
We are reviewing interactive elements using VoiceOver and TalkBack, and adding or improving labels, traits, roles and descriptions where needed. We aim to complete high-impact fixes for key journeys by June 2026

Focus order and navigation

Some complex screens and custom components may need further testing to confirm that screen reader focus order is logical and predictable.
This may affect WCAG 2.2 success criterion 2.4.3 Focus Order.
We are testing the app using VoiceOver on iOS and TalkBack on Android, including swipe navigation through key journeys.

Focus not obscured
Some screens include fixed headers, bottom navigation or overlays. These need further testing to confirm that focused elements are not hidden behind other interface elements.
This may affect WCAG 2.2 success criterion 2.4.11 Focus Not Obscured (Minimum).
We are checking screens with sticky headers, footers, sheets and overlays as part of the internal audit.

Use of colour
Some status indicators or error states may need checking to ensure that information is not communicated by colour alone.
This may affect WCAG 2.2 success criterion 1.4.1 Use of Color.
We are reviewing errors, status messages and selected states to ensure that colour is supported by text, icons or other visible indicators.

Dynamic content and status messages
Some loading states, progress messages, generated responses or other dynamic content may not yet be announced consistently to screen reader users.
This may affect WCAG 2.2 success criterion 4.1.3 Status Messages.
We are reviewing dynamic screens and will add accessibility announcements where needed.

Orientation
The app is primarily designed for portrait use. Some screens may not yet have been fully tested in landscape orientation.
This may affect WCAG 2.2 success criterion 1.3.4 Orientation. We are reviewing whether any orientation restrictions are essential and whether all features remain usable.

Complex gestures
Where the app uses swipe or gesture-based interaction, a non-gesture alternative is available.

Accessible authentication
The app uses authentication methods such as Google/Apple sign-in and/or passwordless email OTP. We are reviewing authentication flows to ensure they do not rely on unnecessary cognitive tests and support copy/paste, password managers or device-level assistance where applicable.
This may affect WCAG 2.2 success criterion 3.3.8 Accessible Authentication (Minimum).

Disproportionate burden

Pause Ltd is not currently claiming that any accessibility fixes would be a disproportionate burden.

If a future issue is considered for disproportionate burden, Pause Ltd will complete and document a disproportionate burden assessment before relying on that exemption.

Content that is not within the scope of the accessibility regulations

The Pause mobile application is distributed through Apple App Store and Google Play. Store listing pages and operating-system interface elements controlled by Apple, Google, iOS or Android are outside Pause Ltd’s direct control.
The public information website at mypause.org is separate from the Pause mobile application and may have its own website accessibility considerations.

Pause Ltd is currently carrying out an internal accessibility audit of the Pause app against WCAG 2.2 Level AA.
The audit includes the following areas:

colour contrast
text resizing and Dynamic Type
device orientation
touch target size
avoiding colour-only information
screen reader labels
focus order
use of native components, roles and traits
alternatives to complex gestures
focus not being obscured by sticky headers or footers
accessible authentication
VoiceOver testing on physical iOS devices
TalkBack testing on physical Android devices
Android Accessibility Scanner testing
manual review of key user journeys

The internal audit covers key journeys including:

onboarding
home/toolkit navigation
Ask Shelley
Key modules
journal/data entry
programme and schedule screens
support and privacy information
settings

Remediation roadmap

May 2026

Complete the current internal WCAG 2.2 AA self-assessment.
Record issues by severity and user impact.
Identify quick fixes for labels, headings, contrast, touch targets and text scaling.
Fix high-impact issues that affect core journeys.
Improve support for larger text sizes on key screens.

Late May-June 2026

Improve VoiceOver and TalkBack labels, roles, hints and focus order.
Review and improve colour contrast for text, icons and controls.

June 2026

Complete a follow-up internal regression test.
Update this accessibility statement with audit findings and remediation progress.
Consider commissioning an independent accessibility audit if required by a public-sector partner or contract.

Ongoing

Include accessibility checks in the release process for new features and substantial UI changes.
Review this accessibility statement at least once a year and after major changes to the app.

Preparation of this accessibility statement

This statement was prepared on 30 April 2026.

This statement was prepared using an internal self-assessment against WCAG 2.2 Level AA. The self-assessment includes visual and design checks, technical checks, and manual testing with assistive technologies on physical iOS and Android devices.
The internal audit is currently in progress. This statement will be updated when the audit is completed and when significant accessibility fixes are released.

This statement was last reviewed on 4 May 2026.

Feedback and contact information

If you find any accessibility problems not listed in this statement, or think we are not meeting accessibility requirements, contact Pause Ltd:
Email: pause@mypause.org 

Technical and accessibility contact: niel@mypause.org

If you need information from the app in a different format, such as large print, accessible PDF, easy read, audio recording or another format, contact us using the email addresses above.
We will consider your request and aim to respond within 5 working days.

Enforcement procedure

The Equality and Human Rights Commission (EHRC) is responsible for enforcing the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.
If you’re not happy with how we respond to your complaint, contact the Equality Advisory and Support Service (EASS).