Using the app

Accessibility statement

How the app works with screen readers, keyboards and larger text, and how to tell us when something does not.

Prepared 23 September 2026 · Last reviewed 23 September 2026 · en-GB

What this statement covers

This statement applies to the Forest School App, run by The Code Guy Ltd:

  • the public website at forestschool.app;
  • the signed-in web app, where a forest school keeps its children, sessions and records;
  • the Forest School App for Android and iPhone and iPad, which is the same app built to work in the woods without a signal.

We want as many people as possible to be able to use it. That means you should be able to change colours and contrast, zoom in to 400% without text spilling off the screen, work through the app with a keyboard alone, use speech recognition, and listen to it with a screen reader. AbilityNet has advice on making your own device easier to use.

How accessible this app is

The Forest School App is partially compliant with the Web Content Accessibility Guidelines version 2.2 level AA standard, because of the items listed below.

Non-accessible content

We audited the app on 23 September 2026. These are the things that stop it meeting the standard, and the date each one will be put right by.

  • Some text and lines do not stand out enough from what is behind them. This is mostly on the public website: hairline rules and boundaries on the cream background, and the blue used for information text. This fails WCAG 2.2 success criteria 1.4.3 (contrast minimum) and 1.4.11 (non-text contrast). Fixed by 31 October 2026.
  • On a phone, keyboard focus can end up behind the bottom bar. On long forms the action bar is fixed to the bottom of the screen, and the field you have tabbed to can scroll underneath it, so you cannot see what you are typing into. This fails WCAG 2.2 success criterion 2.4.11 (focus not obscured). It is fixed on the website. The fix reaches the mobile app at the next release, expected by 30 November 2026.
  • In the mobile app, screen readers are not always told what has happened. Some changes, such as a record saving, are not announced, and some dialogs let the keyboard wander onto the screen behind them instead of holding focus and handing it back on close. This fails WCAG 2.2 success criteria 4.1.3 (status messages), 2.4.3 (focus order) and 2.1.2 (no keyboard trap). It is fixed on the website. The fix reaches the mobile app at the next release, expected by 30 November 2026.

We are not claiming a disproportionate burden for any of them.

Tell us about a problem

If you find a problem that is not on this page, or you need something from the app in a different format, email hello@forestschool.app and say which screen you were on and what happened. We aim to reply within 5 working days.

If you need a session record, a risk assessment or a child's record in large print, plain text or another format, ask and we will send it. Tell us the format that works for you.

The rules that apply

We are a private company, so the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018 do not apply to us. Schools and nurseries are themselves only partly covered by those regulations: their obligation runs to the content people need in order to use their services, not to everything they publish.

The Equality Act 2010 does apply to us. As a service provider we have to make reasonable adjustments for disabled people, and that duty is anticipatory: we are meant to think about what someone will need before they ask.

Technical information

We measure the website and the signed-in app against WCAG 2.2 level AA, the standard the public sector uses. We measure the mobile apps against the same standard together with the mobile requirements in EN 301 549, which cover things like touch target size and screen orientation.

How we tested

We tested the app ourselves on 23 September 2026, across a sample covering the public pages, the signed-in screens a leader uses most (register, session, observations, risk assessments and settings) and the same screens in the field app. Testing was a mix of automated checks and going through each screen by keyboard and with a screen reader. Automated accessibility and colour-contrast checks run against the site on every deployment. The app has not been audited by an external organisation.

About this statement

This statement was prepared on 23 September 2026 and last reviewed on 23 September 2026. We review it every six months, and whenever the app changes in a way that affects it.