Starter Web skill
Create an event registration form
Create an accessible registration form that collects only information needed to deliver the event.
Procedure
- Define eligibility, capacity, required decisions, data owners, retention, and participant journey.
- Collect only necessary identity, contact, ticket, payment, access, dietary, safeguarding, and consent information.
- Separate required delivery data from optional marketing, profile, and demographic questions.
- Use clear labels, instructions, formats, error messages, field grouping, and keyboard order.
- Explain purpose, sharing, recording, photography, communication, changes, withdrawal, and contact routes.
- Build confirmation, waitlist, edit, cancellation, refund, and assistance paths.
- Test keyboard, screen reader, zoom, mobile, validation, payment, timeout, and failure behavior.
- Verify secure delivery to authorized systems and delete test submissions.
Guardrails
- Do not make optional consent a condition of attendance.
- Never collect disability diagnosis, identity, or payment data without a necessary and protected purpose.
- Do not publish attendee information or share it with sponsors without a valid basis and clear notice.
--- name: create-an-event-registration-form category: web description: Create an accessible registration form that collects only information needed to deliver the event. Use when attendees must reserve, pay, request access, or receive event communications. --- # create-an-event-registration-form ## Procedure 1. Define eligibility, capacity, required decisions, data owners, retention, and participant journey. 2. Collect only necessary identity, contact, ticket, payment, access, dietary, safeguarding, and consent information. 3. Separate required delivery data from optional marketing, profile, and demographic questions. 4. Use clear labels, instructions, formats, error messages, field grouping, and keyboard order. 5. Explain purpose, sharing, recording, photography, communication, changes, withdrawal, and contact routes. 6. Build confirmation, waitlist, edit, cancellation, refund, and assistance paths. 7. Test keyboard, screen reader, zoom, mobile, validation, payment, timeout, and failure behavior. 8. Verify secure delivery to authorized systems and delete test submissions. ## Guardrails - Do not make optional consent a condition of attendance. - Never collect disability diagnosis, identity, or payment data without a necessary and protected purpose. - Do not publish attendee information or share it with sponsors without a valid basis and clear notice. ## Done - A working registration form collects justified fields with clear notices and choices - Accessibility, validation, confirmation, cancellation, and failure tests pass - Data routing, access, retention, consent, and owner evidence are recorded