Publish event details in HTML

Put the event facts in HTML

Write a page heading that names the event, followed by a short description and a clearly labeled list of details. Include the date, start and end time, time zone when the audience may be remote, venue or online location, audience, cost if applicable, registration deadline, and the purposeful registration action. Add access information that has been confirmed for this event. If an event changes, update the HTML details first and then update or replace the supporting flyer.

• When: Wednesday, October 14, 2026, 10:00 a.m. to 12:00 p.m. Pacific Time
• Where: Campus auditorium, with an online attendance option
• Registration: Registration closes October 10

Use the same date and time wording in the page title, registration instructions, and any supporting graphic. Spell out the month and include an end time when the event has one. If registration requires a separate process, state what the person will need before they follow the link. This reduces the need to interpret a poster or guess which “Register” action is current.

Use the event-copy example tool to check whether the notice still works when the supporting flyer is removed.

Use the flyer as supporting content

If a designed flyer is important to the campaign, publish it after the same information appears as text. Give the image a concise alternative that identifies it as a flyer and conveys its purpose, not every line of small type. If the flyer contains unique instructions, reproduce those instructions in HTML or provide an accessible document equivalent. Avoid text embedded in images for information that people need to copy, search, translate, or enlarge.

Check contrast and legibility at normal zoom before publishing. Do not use color, font size, or placement alone to communicate that an event is canceled or that registration is required. Use a real heading, paragraph, list, or status message as appropriate.

Coordinate updates and technical review

Give the reviewer the source facts, approved event owner, and expiry or update date. The editor owns accuracy of the facts and links. If the event owner provides a verified accommodation contact, publish the approved office or person, contact method, and response deadline in HTML near the event details. If no contact is confirmed, ask the event owner to supply one rather than guessing. A developer should confirm that the event information is real text in the page structure, links have clear names, the flyer has the intended alternative, and the page remains usable when text is enlarged or the image fails to load. For event registration, hand off the form interaction separately; a correct announcement does not guarantee an accessible registration flow.