Skip to content
Start free
the fine print, in plain English · 4 of 5

Accessibility Statement

Every parent should be able to register their senior, sign up for a shift or make a donation — whatever device they use and however they use it.

Effective
October 1, 2026
Last updated
October 15, 2026
Questions
[email protected]

What we commit to

  • WCAG 2.2 Level AA as our standard
  • Automated accessibility tests on every release
  • Real help from a person within 2 business days
  • Another way to register if something doesn't work for you
section 1

Our commitment

We aim for OurStudentParty — our website, every event site, registration, donation and volunteer sign‑up forms, and the Organizer tools — to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA.

section 2

What we do

  • Test our pages automatically against the WCAG 2.2 A and AA rules that can be checked by software, using axe‑core. Our website, account sign‑up and sign‑in are tested on every release, and a release that fails is stopped. Event sites are tested in both designs, with both dark and light school colors.
  • Keep text readable whatever school colors an Organizer picks: when a color is too light to read, event sites automatically use a darker shade of it for text and for anything with text on top.
  • Label every form field and give images text alternatives
  • Design for keyboard use, visible focus, zoom and phone screens
  • Fix accessibility problems people report to us

Automated tests find many problems but not all of them. We have not yet had an independent audit or done formal testing with screen readers; see Known limitations.

section 3

Event site content

Each event site is written by its Organizer. We help keep their content accessible, for example by adjusting school colors that would be hard to read, but Organizers are responsible for the words, photos and documents they add.

section 4

Payment forms

Card entry fields are provided by our payment processor, Stripe, inside secure frames. Stripe publishes accessibility commitments of its own. If a payment field doesn't work for you, contact us and we will help you complete your registration another way.

section 5

Known limitations

  • Screen readers. We have not yet tested event sites and registration with screen readers such as VoiceOver and NVDA. Our automated tests pass, but they can't find every problem a screen reader user might meet. This testing is planned.
  • Payment fields. Card fields come from our payment processors (see Section 4), and we can't change how they work.
  • Documents and images Organizers add. Uploaded documents and photos may not have full text alternatives.

If you run into any of these, contact us and we will help you register, volunteer or donate another way.

section 6

Need help or found a problem?

Email [email protected] and tell us the page and what happened. A person will reply within 2 business days. If you need to register, volunteer or donate right away, we will help you do it by email or phone, or put you in touch with the event's Organizer.

section 7

How we check

This statement was last reviewed on October 1, 2026 through a self‑assessment, supported by the automated testing described in Section 2. We review it at least once a year and whenever we make major changes.