Sector content and pathways

Events: registration, changes and closure

An event site must remain consistent before, during and after its holding. Program information, advertised capacity and registration messages must be linked to the same validated version.

These files describe preparation methods. They do not present customer achievements and do not replace the validation of information by the organization concerned.

All sectoral files

Identify dates and program

View Year, Location and Times, with the time zone when the public participates remotely. Distinguish confirmed speaker and provisional program. Each session must be able to be recognized without depending on a poster. A downloadable version should remain aligned on the page that shows the latest changes.

Set registration status

Explain whether the action reserves a place, submits a request, or adds to a waiting list. Describe the next step and confirmation channel. Only display a number of remaining places if its source and update are reliable. Demo registrations remain in the test environment.

Prepare for changes

Define who validates a location, schedule or session change. Update the page and channels used to inform registrants. The site should help recognize the current version without deleting the information needed to understand an old confirmation.

Test the full course

Check registration, duplicate, waiting list, correction and cancellation with test data. Check the confirmations in all the languages offered. On mobile, the main action must remain understandable even with long titles and names; On the keyboard, errors must be accessible.

close without losing context

Close the registration at the right time and present the event as completed. Publish a report only after validation of the facts. Keep authorized media with their credits and remove private participation information. For a new edition, create a dated page rather than mixing multiple programs.

Information to gather before writing

  • Year, useful schedules and time zone
  • Confirmed or provisional program
  • Registration status and confirmation
  • Responsible for changes
  • Closing and Rules of the Archives

For each item, keep the source, the person validating it and the language versions concerned. Missing information must become a question to solve, never a value invented to fill the page.

Frequently asked questions

Reuse the same page every year?

A permanent entry point can point to dated editions. Old programs must remain separate and clearly identified.

Display a waiting list?

Yes if its management and confirmation are defined. It should not suggest that a place is reserved.

What to test after a change of location?

Check the page, access link, confirmations and related documents, and then check their consistency in each language.

resources to deepen

Additional reference: W3C Wai: Structure an accessible page. The sectoral recommendations of this sheet are an editorial method; This reference does not certify the information specific to an establishment.

Browse other files