Accessibility statement
Last updated 5 November 2026
We want everyone who runs or joins an improv group to be able to use ImprovTeam. This statement says how accessible it is. It is voluntary: no law asks ImprovTeam to publish one, so it is written the way a public body would write it, to hold us to the same standard.
The standard we aim for
We aim for the Web Content Accessibility Guidelines (WCAG) 2.2, level AA. We have not had an independent audit, so we do not claim full conformance. We say what we check and what we know falls short.
How it is checked
- Automated checks. The axe-core engine scans the key pages in a real browser: the home page, features, sign-in, a city page, a team site, a show page, and signed in, the home feed, a group page, the RSVP grid, an event, Money, notification settings, the poster builder, the form builder and the admin home. It scans at phone and desktop widths, in the light and the dark theme, and a serious or critical finding fails the test. These checks cover the WCAG 2.0 and 2.1 A and AA rules and axe's own best practices, which is only part of WCAG 2.2.
- Colour contrast. Text and controls are built from a fixed set of colours that keep a contrast ratio of at least 4.5 to 1 against their background, in both themes.
- Keyboard and screen readers. The signed-in app has a skip link, every page has a visible focus ring, controls are real buttons and links with names, form fields have labels, and changes such as saved or failed are announced. We test these by hand while building. We do not run a regular test with a screen reader on each device, so some things will be missed.
- Motion. Fades and the crayon texture switch off when your device asks for reduced motion, and the Crayon texture setting can turn the texture off at any time.
- Venue access. Organisers can say whether a venue has step-free access, an accessible toilet, a hearing loop, seating and relaxed performances, and whether a date is captioned, has BSL or welcomes assistance dogs. It is shown as stated by the organiser.
What we know does not work well yet
- The automated scan does not open every state: error messages, toasts and pop-up sheets are not covered, and it collects only serious and critical findings, not moderate or minor ones. It runs when we run the full test suite, not on every change.
- Ordering things never needs a mouse. Where you can drag to reorder (a festival programme, a photo crop), there are buttons, a select or arrow keys that do the same.
- A poster you download is a picture. Its details are also on the show or event page as text, but the picture has no description of its own, and the preview in the poster builder has only a general description.
- A few tools need JavaScript, such as the site builder's page structure and teaching mode. Most forms still work without it, but not these.
- Photos, descriptions and notes are written by groups, not by us, and we cannot make sure every photo has a description. Where the app offers a place for one, we ask for it.
- The app is in English only for now.
- We have not tested every page with every screen reader and browser, and we have not tested the iPhone app and the Android app separately from the website.
Tell us about a problem
If something is hard to use, or you need information in another form, please tell us through the contact form (choose "Report a problem") or write to hello@improvteam.com. Say what you were trying to do, the page, and what got in the way. We will reply within 5 working days and tell you what we can do.
If you are not happy with our reply and you are in the UK, you can contact the Equality Advisory and Support Service. In Northern Ireland, contact the Equality Commission for Northern Ireland.
About this statement
This statement was written on 5 November 2026. We review it when something changes that matters to it, and at least once a year.