#  Use a table to highlight time, location, and registration 

 



 ##  

  expand\_more  

 
  

 

When you're listing multiple sessions, workshops, or keynotes, a well-structured table helps attendees quickly see what’s happening, when, and where. Tables are especially effective for comparing sessions that overlap or follow a clear progression. While the Simple Table component is deprecated, you can still create effective tables using CKEditor, just follow a few key layout and accessibility best practices.



 

##  Sample Event Table 

Sort**Time****Session Title****Location****Register**10:00–11:00 AM

Teaching with AI: Challenges & Opportunities

Room 201

[Register Now](#)

11:15–12:15 PM

Tools for Research Collaboration

Room 212

[Join Session](#)

1:30–2:30 PM

Designing for Equity in Tech

Sanders Theatre

[Add to Calendar](#)







 

##  Using tables for events in your pages 

### Best for

Presenting short, structured event data (e.g., agendas, room assignments) side-by-side in a single view.

### Component used

Inline Table

### What It does

Allows editors to create custom tables directly in the content area using the WYSIWYG editor. These tables are rendered inline and can be styled using text fomatting and basic structure tools (bold, alignment, etc.).



 

##  Setup tips 

- Keep content in each row concise to avoid overflowing cells
- If you include links, use **action-oriented text** like “Register Now” or “Add to Calendar”
- **Keep tables small and focused.** Use 2–4 columns max to maintain readability.
- **Always include header rows** (`<th>`) to label each column, this helps both sighted users and screen readers.
- Use **clear, concise column headings** like *Time*, *Session*, *Location*, *Register*
- For tables with more than one row of headings, consider using captions to add context
- On mobile, test for horizontal scroll. Use shorter labels or abbreviations if needed (e.g., “Rm 101” instead of “Room 101”)



 

##  Pros &amp; cons 

### Added benefit

- Makes event comparison fast and frictionless
- Reduces scrolling and cognitive load
- Keeps information together on a single page section

### Potential drawbacks

- Doesn’t support dynamic filtering or interaction, use Event List for that
- Accessibility requires manual care, avoid using tables for layout or including non-table content inside table cells
- Not ideal for content that requires long descriptions or formatting



 

 



 

 See also:- [ Content Clarity ](/how-guides-topics/content-clarity)
- [ Event Communication ](/how-guides-topics/event-communication)
- [ How-To Guides ](/page-categories/how-guides)