
Registration Pages
Event landing pages and registration
Plan an event page that explains who should attend and carries accurate details through registration and confirmation.
An event landing page should help someone decide whether to attend, then let them register for the event described. State the attendee outcome, audience, date, named time zone, format, location or joining arrangement, and any fee or conditions. Carry those details through the form and confirmation.
Give the page one clear job
Open with the task or question the event will address and an outcome the programme can deliver. Say who the event is for and whether participants need prior knowledge. An agenda that describes what will happen is more useful than a list of speakers without session topics. Identify speakers accurately, but do not rely on their credentials to explain a vague programme.
If the agenda does not support the stated outcome, revise the promise or the programme before promoting the page.
Keep the page focused on one action, with the date, time and registration button visible without hunting. Remove navigation menus, unrelated links and competing offers that pull attention away from registering.
Put decision facts near registration
Before asking someone to commit, make it easy to find:
- the date, start and finish times, and named time zone;
- whether the event is online, in person or hybrid, and what each participation route offers;
- the venue location or joining arrangement;
- any fee, eligibility rule, capacity limit or registration deadline;
- what is included, where that affects the decision; and
- a contact route for questions and access requirements.
For an in-person event, describe confirmed venue access and travel information. For an online or hybrid event, say whether remote participants can contribute or only watch. Mark material details that remain unconfirmed, and consider whether registration should open before they are settled.
Use a descriptive action such as “Register for the workshop”. Repeat it on a longer page where useful. Provide a separate contact route for someone who needs help deciding or registering.
Plan access before registration opens
Ask about accessibility needs at registration, including Auslan interpreters and wheelchair access. Choose a venue with step-free entry, accessible bathrooms and nearby public transport, and check that breakout spaces and catering areas are accessible too. Share venue access information with attendees ahead of time.
Begin the event with a short orientation from the host covering the room layout, breakout rooms, toilets, meal areas, fire exits and emergency procedures. Use plain English in written materials and ensure they meet WCAG 2.1 AA standards.
For online and hybrid events, choose video conferencing or webinar tools that meet WCAG 2.1 AA, and avoid platforms that require attendees to download software or plug-ins. Check for live captions or screen reader support, test the platform with users beforehand, and offer a dial-in alternative for anyone who cannot access it.
Pre-Registration Accessibility Checklist
- Confirm venue has step-free entry and accessible bathroomsRequired for compliance with NSW Government accessibility standards
- Provide Auslan interpreter availability on requestRecommended for inclusive event design
- Ensure video conferencing tool meets WCAG 2.1 AA standardsMandatory for digital accessibility under W3C guidelines
- Offer dial-in alternative for online participantsSupports users with limited internet access or device compatibility
- Share venue access information with attendees in advancePart of reasonable steps under APP 5 (Privacy Act)
Connect the form to event delivery
For each question, identify its purpose and who will use the answer. A contact route may be needed to confirm a booking; a session choice may be needed to allocate limited places.
Offer a way to request access support without requiring someone to disclose a diagnosis in a general form, and provide a private contact option. Do not make a field compulsory simply because its answer might be useful for later promotion.
For APP entities, APP 3 requires personal information to be collected by lawful and fair means and from the individual concerned, unless this is unreasonable or impracticable (additional exceptions apply). For non-sensitive information, agencies may collect it only where reasonably necessary for, or directly related to, their functions or activities; organisations may collect it only where reasonably necessary for their functions or activities.
APP 3 has additional requirements for collecting sensitive information. Take a data minimisation approach and collect only what is reasonably necessary for the entity’s functions and activities.
APP 5 requires APP entities to take reasonable steps to notify people of, or ensure they are aware of, matters including the collector’s identity and contact details, the fact and circumstances of collection, whether collection is required or authorised by law, and its purposes.
Those matters also include the consequences of not providing information, usual disclosures, the privacy policy, and likely overseas disclosures and, if practicable, countries where recipients are located.
Take these steps before or at collection, or as soon as practicable afterwards if that is not practicable.
Give fields visible labels, identify required answers and explain unusual formats. If registration has several steps, show progress and avoid needless repeated entry within the same process. Explain errors while retaining valid answers where appropriate. Show a clear result after a successful submission.
If possible, forms should not have a time limit, so people can complete them at their own pace. If a limit needs to be in place, for example for security reasons, users should be able to turn it off or extend it. This does not apply when the limit is due to a live event or when the time to complete the form is essential for a valid submission.
Key Registration Requirements Under Australian Privacy Law
- Collection must be lawful and fair (APP 3)Personal information collected only from the individual unless impracticable
- Notification required (APP 5)Attendees must be informed of collection purpose, contact details, and consequences of non-provision
- Data minimisation principleOnly collect what is reasonably necessary for event delivery
- No compulsory fields for promotion purposesAvoid collecting data solely for marketing without explicit consent
Follow the route on a phone
On a narrow screen, the outcome, date and registration action should remain easy to find. Text and form fields should reflow without unnecessary sideways scrolling. Labels must remain identifiable after a field has been filled, and controls should be easy to select accurately. Appropriate field types and autocomplete purposes may help with entry where supported, but people must still be able to review and edit their answers.
Check the full route, including any separate ticketing or payment page. A readable landing page does little good if the booking step loses a selection or hides an error. Provide a contact route for people who cannot complete it.
Reflow means content can be presented without loss of information or functionality, and without scrolling in two dimensions, at a width equivalent to 320 CSS pixels — roughly a 1280-pixel viewport at 400% zoom. Maps, diagrams, video and data tables may scroll in two dimensions.
Registration Process Flow for Inclusive Event Pages
- View clear outcome and date/timeVisible without scrolling; includes named time zone (AEST/AWST)
- Confirm format (online/in-person/hybrid)Details on participation options and access features provided
- Complete form with accessible fieldsLabels remain visible after input; no unnecessary re-entry
- Request access support privatelyNo diagnosis disclosure required; separate contact route available
- Receive confirmation with consistent detailsMatches landing page and success screen; includes event ID and next steps
Check consistency before promotion
Compare the invitation, page, form, success screen and confirmation message with the approved event details. Check the audience, programme, date, time zone, format, location or joining method, fee and conditions. Complete each relevant booking route, recover from an invalid entry and inspect what the registrant receives.
When event details change, update the page and booking route together. Tell affected registrants what changed so their confirmation remains understandable.
In this guide
- Explaining the value of attending an eventWrite an event promise that names a useful attendee outcome, shows how the agenda delivers it and helps readers judge fit.
- Asking only necessary questions on a registration formDecide which event registration fields are required, optional or better asked later, with a clear purpose for each answer.
- Reducing friction in mobile event registrationCheck an event booking from phone-sized page to confirmation, with clearer fields, less repeated entry and recoverable errors.



