A mobile-friendly event agenda helps attendees find the current session, the next useful option and the correct location on a small screen. Keep time, title and room easy to scan. Longer descriptions should be available without making every entry difficult to navigate.
Review the actual published page on a phone. A timetable that looks clear on a desktop can become cramped, require wide scrolling or separate the time from the session it describes.
Put essential information first
For each entry, show the start and end time, session title, room or online location, and speaker if relevant. Add a format or audience label when it helps people choose. Keep operational notes and long biographies out of the main list.
An attendee should not need to open several panels to find the room. Place preparation requirements where people can see them before the event, and indicate if a session requires a separate booking.
Choose a readable layout
| Layout | Useful when | Check |
|---|---|---|
| Chronological list | The programme has one main sequence | Times remain beside the correct entries |
| Day-by-day view | The event spans several dates | Selected date and time zone stay clear |
| Track filter with list | Attendees choose between parallel streams | Shared sessions remain visible |
| Scrollable table | Comparison across tracks matters | Time labels and headers remain understandable |
A narrow list is often a useful starting point for a sequential event. A grid may still help readers compare parallel sessions, but check how they move across it. Do not hide the relevant room or track merely to fit more columns on screen.
Use labels as well as colours
Colour can distinguish workshops, talks and breaks, but it should not be the only explanation. Keep a text label or another clear cue with the entry. Confirm that text remains readable against its background.
Use headings for dates or major sections so the page has a clear structure. For a timetable published as a table, use real header cells and meaningful column names. The W3C tables tutorial explains how table headers provide context for assistive technologies.
Check interactions and text size
Try the page with larger text and a narrow browser window. Expand descriptions, change the day and use any filters. Check that controls remain usable and that the displayed information still belongs to the correct session.
Also test keyboard navigation on a computer and visible focus on interactive controls. A phone review alone does not establish accessibility. The W3C Easy Checks guide offers an initial review, while noting that these checks are not a complete evaluation.
Make changes easy to understand
If a room or time changes, update the authoritative agenda and state the revision clearly. Ensure the update is reflected in any printed or emailed version. An attractive mobile layout cannot compensate for conflicting information.
Keep an easily readable alternative available when connectivity may be unreliable. A text schedule or a prepared printout can support attendees who cannot load the live page. Avoid offering only an image of a timetable, which is harder to search and adapt.
A practical phone check
- Find the next session without zooming out.
- Identify its room and finish time.
- Switch to another day without losing orientation.
- Open and close a description with enlarged text.
- Find a break and the event’s formal closing.
- Check a long title and an unusually long speaker name.
Use the results to change the layout or wording. Repeat the check when the full programme is loaded, since empty placeholders rarely reveal the problems created by real session information.
Put the plan into practice
Draft clear session records before choosing the publishing layout. Then test the final page with the actual titles, rooms and times on a phone. Open Agenda Creator to draft the sequence and test the timing.