Our aim
UAT Studio (app.uat.studio) and this website aim to meet the Web Content Accessibility Guidelines (WCAG) 2.1, level AA, the standard that public organisations in the Netherlands and the EU use (EN 301 549).
Status: partly meets. Our own checks find no problems, but an independent audit has not been done yet. Until then we do not claim to meet the standard in full.
How we check it
- Every new version of UAT Studio is checked automatically before it goes live: every screen, in the three looks (mixed, light and dark), the dialogs, and the main screens on a phone. A problem stops the release.
- The same check runs on every page of this website, in every language.
- Keyboard use is tested too: a Skip to content link on every page, dialogs that take the focus, keep it inside and give it back when they close, and rows that open with Enter.
- Colours are checked for enough contrast, also the colour a partner chooses for its own brand: the app makes links darker or lighter until they are readable.
What you can expect
- Every action can be done with the keyboard. The focus is always visible.
- Every page has its own title, a clear structure with headings, and labels on every field.
- Statuses are shown in words as well as in colour (for example Pass, Fail, Blocked).
- The app works at 200% zoom and on a phone without scrolling sideways.
- Charts have a text alternative that says what they show.
- The film on the homepage has no sound and a pause button, and it stays still when your device asks for less motion.
What is not right yet
- The PDF of the go/no-go report and of a quote are not tagged for screen readers yet. The same information is on the screen, where it is accessible.
- The slides of the go/no-go report (PowerPoint) follow the layout of the screen but have not been checked with a screen reader.
- We have not yet tested with every screen reader. If something does not work for you, we want to know.
Tell us about a problem
Do you run into something you cannot use, or need information in another form? Mail [email protected] with the page and what happened. We answer within 5 working days and tell you when it is solved.
Last changed: 25 October 2026.
