
Registration Pages
Part of Event landing pages and registration
Reducing friction in mobile event registration
Check an event booking from phone-sized page to confirmation, with clearer fields, less repeated entry and recoverable errors.
To improve mobile event registration, review the whole booking on a phone-sized screen, from event page to confirmation. Make key details readable, limit typing, give controls people can select accurately and explain how to recover from errors. Include any separate ticketing or payment step in the review.
Key WCAG 2.2 Success Criteria for Mobile Registration
- 1.4Reflow (Success Criterion .10) — Content must reflow without horizontal scrolling
- 1.3Labels (Success Criterion .1) — Form fields must have visible, persistent labels
- 1.3Input Purpose (Success Criterion .5) — Browsers should recognise field types like email or tel
- 1.3Redundant Entry (Success Criterion .5) — Avoid asking for same info twice unless justified
Keep the decision clear on a narrow screen
Near the start of the page, show what the event is for, when it happens, the named time zone and how to register. People should be able to find any fee, eligibility condition and participation format before submitting a booking. A large image or banner should not obscure those facts.
Check the page with enlarged text as well as at its default size. Ordinary content and form fields should reflow without unnecessary sideways scrolling. Watch for wide tables, fixed banners and embedded ticket widgets that cover an action or error. If a booking service opens on another page, make sure that page identifies the same event and the selected ticket.
Reduce typing while keeping fields clear
Use only the fields needed for this booking. Give each a visible label that remains identifiable after entry. Where appropriate, use email or telephone field types and recognised autocomplete purposes. Browser support and saved information vary, so attendees must be able to review and change a suggested value.
Avoid asking for the same information twice within one booking process unless re-entry has a valid reason. If several steps are needed, show where the person is and what remains. Preserve valid entries when they go back or correct an error, subject to appropriate security handling for payment details. Check that a session choice remains clear when someone moves to a payment provider and returns.
Make ticket, date and consent choices easy to distinguish and select. Associate labels with their controls so the label can help enlarge the selectable area. Give neighbouring controls enough size or space to reduce accidental selection.
Explain errors and confirm success
State unusual formats or restrictions before submission. If a submission fails, identify the affected field and explain the correction in text. “Invalid input” leaves the person guessing whether an answer is missing, a session is unavailable or an address has been mistyped. Keep other valid answers where appropriate and make the error easy to find.
After a successful booking, show a clear confirmation state with the event name and selected ticket or session. If a confirmation message will follow, say where it will be sent and provide a help route if it does not arrive. This helps people avoid a second submission when they are unsure what happened.
Check the complete booking route
Before promotion:
- Open the page on a narrow screen and with enlarged text. Find the outcome, date, time zone, fee and registration action.
- Complete each relevant ticket or attendance route using the on-screen keyboard. Check that fields, buttons and instructions remain available.
- Enter an incorrect value, correct it and confirm that other appropriate answers remain.
- Return from any external booking or payment step and check the event and selections.
- Complete a booking and inspect the success screen and confirmation message.
Use the real site and devices or browser settings relevant to its audience. Repeat the checks after changes to the form, ticketing route or payment step.



