You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When registering for an event in LibCal, users would like to be able to choose whether they are attending live or would only like to receive a copy of the Zoom recording after the event is complete (only one Follow Up email can be sent per event, so in fact, everyone who registers - even live attendees - will get the Follow Up email with Zoom recording link).
Acceptance criteria
Add new Event Location in LibCal called "Get Notification of Event Recording" (in-person location)
Set up hybrid event in order to track attendance based on whether people signed up for in-person ("get notification of recording") or online
In Admin -> System Settings -> Language Options, define in-person registration as "Get notification of recording"
Modify registration form questions to include: "Attend LIVE" and "Get Recording Notification"
I can successfully use this feature with Voice Over in Safari.
I have checked this feature using one of the following browser extensions and confirmed that it does not add any level A or level AA issues:
axe dev tools
Lighthouse
Wave
Concrete example
Our registration form would look something like this:
Implementation notes, if any
Changing the language settings will change them across the board for ALL calendars in our system.
There's not currently an automatic way to email attendees based on their registration type for hybrid events.
The text was updated successfully, but these errors were encountered:
User story
When registering for an event in LibCal, users would like to be able to choose whether they are attending live or would only like to receive a copy of the Zoom recording after the event is complete (only one Follow Up email can be sent per event, so in fact, everyone who registers - even live attendees - will get the Follow Up email with Zoom recording link).
Acceptance criteria
Concrete example
Our registration form would look something like this:
Implementation notes, if any
The text was updated successfully, but these errors were encountered: