Accessibility Statement

Last updated · Version 0.1

This document is not final.

Paddles Up is in beta. This text has not been through legal review. Some details in it are our best understanding rather than something anyone has signed off.

We publish it anyway because you should be able to read what you are agreeing to. We will tell you before a final version takes effect.

Our commitment

We want everyone who plays to be able to use Paddles Up, including people using a screen reader, keyboard navigation, magnification, voice control, or captions.

Where we are

We are building toward WCAG 2.2 Level AA. We have not completed a formal accessibility audit, so we do not claim conformance to it today. We would rather say that plainly than assert a level nobody has measured.

What we do have: accessible components as the default across the app rather than retrofitted screen by screen, keyboard paths through the flows that matter most — signing in, entering an event, signing a document — and no accessibility overlay widget, which we do not use and do not intend to.

Tell us what is broken

If you hit a barrier, write to accessibility@paddlesup.io. Tell us what you were trying to do, what got in the way, and what you were using. We will reply, tell you what we are doing about it and when, and find you another way through in the meantime.

If you need something in another format — a waiver as plain text, results read out, a form completed with you over the phone — ask and we will provide it.

This channel is not decoration. It is the most useful thing on this page, and the thing we will act on fastest.

Standards we are working to

WCAG 2.2 Level AA, which is also the basis of EN 301 549, the standard behind the European Accessibility Act.