Accessibility

This statement covers areyoufaster.com and the apps on it. Our target is WCAG 2.2 level AA. The Web Content Accessibility Guidelines were written for websites, but their success criteria are the clearest public yardstick for a mobile app too, so we use them for our apps alongside Apple's and Google's own accessibility guidance.

This website

areyoufaster.com is held to the same target. It has not been through an independent audit, and it has not been tested with people who use assistive technology every day. If any page gets in your way, tell us.

The home page and the AYF Mobile page are built as full-screen slides that move one screen at a time. On screens less than 600 pixels tall, with enlarged text or when your device asks for reduced motion, the slides switch off and the page scrolls normally.

personent

personent should work for anyone who wants to use it: readable at any text size, usable with a screen reader, never asking you to tell things apart by colour alone and never in a hurry. Accessibility is a requirement in the product specification rather than a later pass. That is a statement of how the app is built, not a claim of conformance.

What the app is built to do

• Text that scales. iOS Dynamic Type and Android font scaling are respected throughout. Screens are built to reflow at large text sizes rather than clip, truncate or hide information.
• Screen-reader support. Controls carry meaningful labels for VoiceOver and TalkBack, and focus order follows the order things appear on screen.
• Never colour alone. Status is never carried by colour by itself. An overdue follow-up is marked with words and an icon as well as a colour, so it reads the same in greyscale, in bright sun or aloud.
• Contrast built into the colours. Every colour comes from one shared token set, and each accent colour you can choose has been checked to reach at least 4.5:1 against both the light and the dark background before it was offered.
• Comfortable targets. Interactive elements are sized to at least 44 points square.
• Reduced motion. If your system asks for reduced motion, transitions are removed rather than merely shortened.
• A Bold theme. Higher contrast, larger typography and stronger separation between elements, for anyone who wants the interface to be as legible as it can be. Light, dark and follow-the-system themes are all available.
• Quieter notifications. Reminder notifications can be reduced to names only, or to "a connection needs attention" with no names at all, which matters if your device reads notifications aloud in company.
• Nothing to wait for. The app has no account, no sign-in and no network, so there are no loading spinners, timeouts, session expiries or connection errors to work around. Everything is already on the device.

What we have not verified

Everything above describes how personent is built, not a tested result.

• Only the iPhone app is out. The Android app is not released, so none of this can be checked on Android yet.
• There has been no independent audit. No formal WCAG 2.2 AA evaluation has been carried out and there is no accessibility conformance report. We cannot claim conformance, only tell you what we are aiming at.
• No testing with disabled users yet. Nobody who uses VoiceOver, TalkBack, Switch Control or Voice Control every day has tried personent. Testing by the person who built it is not the same thing, and we will not present it as though it were.
• Known hard areas. The parts most likely to fall short first are the timeline and group views at the very largest text sizes, the date and reminder pickers, and any screen where several pieces of status have to be announced at once. These are on the list. They are not solved.

This statement will be updated after any testing or audit, including if the findings are unflattering. If you rely on assistive technology and would be willing to try personent, we would like to hear from you: admin@areyoufaster.com.

If something does not work

Tell us. Email admin@areyoufaster.com. A report of a real barrier is more useful to us than any checklist.

It helps if you can include:

• what you were trying to do, and which page, app or screen you were on;
• your device and operating-system version;
• which assistive technology you use, and its settings if relevant;
• what happened, and what you expected instead.

A screenshot or recording helps but is never required, and please do not send anything from your own notes that you would rather keep private.

Where this sits legally

Are You Faster CIC is a community interest company, not a public sector body, so the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018 do not apply to it. We work to WCAG 2.2 AA regardless, because the alternative is deciding in advance which people do not matter.

Under the Equality Act 2010 we aim to make reasonable adjustments where someone tells us they need one. If something here is a barrier for you, say so and we will look at it properly.