Accessible sign-up sheets for everyone
Anyone should be able to grab a volunteer shift or RSVP, whether they use a screen reader, a keyboard, voice control, or zoom. SignupKit is built to WCAG 2.2 Level AA, and our VPAT is available for school, nonprofit, and government reviews.
Last reviewed October 11, 2026
Our commitment
Sign-up sheets are how a lot of people join in: a classroom volunteer shift, a church meal train, a food bank Saturday, a team snack schedule. If the sheet does not work with someone’s assistive technology, they are left out. We design, build, and test SignupKit so the volunteer, the guest, and the organizer can all use it.
We review new features for keyboard access, screen reader labels, and color contrast. When we find a gap we fix it, and we keep the VPAT up to date as we go.
For volunteers and participants
Everything on the public signup page, the page people open from your link.
No account to sign up
Volunteers and guests open the link, pick a slot, and enter their details. No password, no login screen, no app to install.
Works with a keyboard alone
Every step of the public signup page, from picking a slot to submitting, can be done with Tab, Enter, and Space.
Sign Up buttons say which slot
A sheet with twenty “Sign Up” buttons is hard to use by ear. Each button tells a screen reader its slot and time, like “Sign Up, Setup crew, Saturday 9:00 AM”.
Labeled, grouped form fields
Every field has a label. Address parts, checkboxes, and multiple-choice questions are grouped under their question so a screen reader reads them together.
Browser autofill
Name, email, phone, and address fields tell the browser what they are. Autofill and password managers can fill them in one step, which saves a lot of typing.
Sign a waiver without drawing
If a sheet needs a signature, volunteers can draw it or sign with their typed name and a checkbox. No mouse or touchscreen needed.
Errors are announced
Problems like a wrong password on a protected sheet are announced as soon as they appear and tied to the field they belong to.
Motion you can turn off
Animated themes (falling leaves, fireworks, snow) stop when your device is set to reduce motion.
Readable emails and calendar invites
Confirmation and reminder emails declare their language for screen readers, and include a calendar invite so the date lands in your own calendar app.
For organizers
The sheet builder and dashboard are built for organizers who use assistive technology too, and they keep your sheet readable no matter how you style it.
Readable buttons in any color
Pick any accent color for your sheet. If white text would be hard to read on it, SignupKit switches the button text to dark or white, whichever meets the 4.5:1 WCAG AA contrast ratio better.
Accessible built-in themes
Theme defaults are tuned for contrast. We darkened the default purple and indigo accents so button text clears WCAG AA.
A keyboard-friendly builder
Question toggles, required switches, slot settings, and option lists in the sheet builder all work from the keyboard and have clear names.
Named icon buttons
Icon-only buttons across the dashboard, like Edit, Delete, More actions, and Previous month, are labeled for screen readers.
Labeled settings
Notification settings, search boxes, and every on/off switch say what they control, so you are never guessing which toggle is which.
Signatures with text alternatives
Signed waivers show up on your roster with alt text naming the signer. Typed-name signatures say so in plain text.
Make your own sheet more accessible
You write the content, so a few habits go a long way:
- Write slot titles that make sense on their own, like “Setup crew, 8–10 AM”, not just “Shift 1”
- Use the description field for directions and parking, not an image of a flyer
- If you attach a document, prefer a PDF with real text over a scanned photo
- Keep questions short and mark only what you really need as required
- Offer another way to sign up, like an email address, for anyone who asks
Standards and VPAT
A VPAT (Voluntary Product Accessibility Template) is the document procurement teams ask for to see how a product meets accessibility standards. Once filled in, it is also called an Accessibility Conformance Report (ACR).
WCAG 2.2 Level AA
The Web Content Accessibility Guidelines from the W3C. This is the standard we build and test against.
Section 508
The US federal accessibility standard. Section 508 points to WCAG, so our WCAG work covers it.
ADA Title II and III
There is no official ADA certification for websites. WCAG 2.1 AA is the benchmark US schools and public bodies are expected to meet.
EN 301 549
The European accessibility standard. Its web requirements are also based on WCAG.
Need our VPAT for a school district, PTA, nonprofit, or agency review? Email hello@signupkit.co and we will send the current version.
Known limitations
We would rather tell you up front. These are the areas we know need care.
Content organizers write
Organizers write their own slot titles, descriptions, and questions, and can upload images and documents. We cannot check that an uploaded image has a description or that a PDF is tagged.
Drawn signatures
The drawing pad itself needs a pointer. The typed-name option is the accessible alternative and is always available alongside it.
Third-party pages
Paid slots go to Stripe Checkout, which Stripe builds and maintains. Stripe publishes its own accessibility information.
Report a problem
If something on SignupKit does not work with your assistive technology, tell us. Send the page link, what you were trying to do, and your browser and assistive technology if you can. We treat anything that blocks someone from signing up as urgent.
Questions
- Do you have a VPAT?
- Yes. Email hello@signupkit.co and we will send our current VPAT, also called an Accessibility Conformance Report (ACR). We typically reply within one business day. Schools, districts, and nonprofits often need it for a procurement or vendor review.
- Is SignupKit ADA compliant or Section 508 compliant?
- There is no official ADA certification for websites. Most US schools, agencies, and nonprofits use WCAG 2.1 or 2.2 Level AA as the yardstick, and Section 508 points to WCAG as well. We build SignupKit to WCAG 2.2 Level AA and document where we fall short in the VPAT.
- Can someone sign up using only a keyboard or a screen reader?
- Yes. Every step of the public signup page works with a keyboard. Each Sign Up button names its slot and time, so a screen reader user can tell twenty "Sign Up" buttons apart. Form fields have labels, and errors are announced when they appear.
- What if a volunteer cannot draw a signature on a waiver?
- They can sign with their typed name instead. They type their legal name and tick a box agreeing that it is their signature. No mouse, touchscreen, or drawing needed.
- Do participants need an account to sign up?
- No. Participants open the link, pick a slot, and enter their details. No account, password, or app to install, so there is no login screen to get through.
- What happens if an organizer picks a hard-to-read color?
- Button text adjusts automatically. When the label color would fall below the WCAG AA contrast ratio of 4.5:1 on the organizer’s accent color, SignupKit switches it to dark or white text, whichever reads better.
- How do I report an accessibility problem?
- Email hello@signupkit.co with the page link and what went wrong. Mention the browser and any assistive technology you use if you can. We typically reply within one business day and treat blockers on the public signup page as urgent.