ACCESSIBILITY

Accessibility at Volunteero

We want our website, web app and mobile app to work for the widest possible audience, whatever technology people use and whatever their ability. This page sets out what we do, how we measure up against WCAG 2.1 and how to tell us about a problem.

Page updated October 2026

At a glance

Key facts about the accessibility of Volunteero.

Standard

WCAG 2.1

Target level

AA

Status

Partially conformant

Assessment

Self-evaluation

Covers

Website, web app and mobile app

Display options

Light and dark mode

Screen readers

Regularly tested with the default text-to-speech on mainstream devices

Technologies

React Native and Vue.js

Designed for every volunteer

Volunteero is designed for volunteers of all ages, including people who are older or less confident with technology.

Clear navigation and plain language.

Mobile-friendly access with no complex setup.

Volunteers can use it on a phone, tablet or computer, including through a web browser without installing an app.

Common tasks take as few steps as possible.

Volunteers only see what they need.

Staff can take actions on a volunteer’s behalf when they need help.

How we build accessibility in

Alongside the technical work, we take these organisational measures.

We include accessibility throughout our internal policies.

We build accessibility into our procurement practices.

We provide continual accessibility training for our staff.

We set clear accessibility goals and assign responsibility for them.

Perceivable

Content should be easy to see, hear and take in, including with assistive technologies.

We provide text alternatives for non-text content. Where colour conveys information, a text alternative is also given.

Buttons across the app carry accessibility labels.

Mission pages use headings and landmarks for better screen reader support.

We meet the WCAG contrast requirements.

Light and dark modes are available for people with sight impairments.

We regularly test the app with the default text-to-speech programs on mainstream devices, so that all elements can be read aloud.

Operable

People should be able to use every part of Volunteero, whatever way they interact with it.

We aim to make all functionality available from a keyboard.

Our navigation includes ARIA labels.

We aim to give people enough time to read and use content.

We do not use content known to cause seizures or physical reactions.

We aim to help people navigate and find content.

We aim to make it easier to use inputs other than a keyboard.

Understandable

Content and controls should be clear and behave in the way people expect.

We aim to make text readable and easy to understand.

We aim to make content appear and work in predictable ways.

We aim to help people avoid and correct mistakes.

Conformance status

The Web Content Accessibility Guidelines (WCAG) set out requirements for designers and developers to improve accessibility for people with disabilities. The Volunteero web app is partially conformant with WCAG 2.1 level AA. Partially conformant means that some parts of the content do not fully meet the standard.

Standard

Web Content Accessibility Guidelines (WCAG) 2.1

Conformance levels

A, AA and AAA

Our target

Level AA

Current status

Partially conformant

Technical specifications

The accessibility of Volunteero relies on the following technologies working with your web browser and any assistive technologies or plug-ins on your device. We rely on these technologies for conformance with the accessibility standards we use.

Mobile and web app

React Native and Vue.js

Works with

Your web browser and any assistive technologies or plug-ins you have installed

Assessment approach

We assessed the accessibility of Volunteero ourselves.

Current method

Self-evaluation by the Volunteero team

Next step

We plan to seek an independent external evaluation

Feedback

If something on our website, web app or mobile app is hard to use, please tell us. Your feedback helps us find and remove barriers.

Contact our support team through our support page.

Tell us which page, screen or feature you were using and what happened.

If you can, let us know the device, browser or assistive technology you use.

Report an accessibility issue

Found something that’s hard to use?

Found something that’s hard to use?

Tell us about any barrier you find on our website, web app or mobile app.