Schedule —
Two tracks, one hall, no slides with more than six words.
The schedule is a genuinely two-dimensional dataset, so it is a
<table>. Every data cell names its governing headers with the
headers attribute, so a screen reader announces time, track, and
session even when rowspan makes the geometry irregular.
| Time | Structure track | Meaning track |
|---|---|---|
| Opening keynote — The Document Outline Strikes Back | ||
| Landmarks in the wild: auditing 10,000 homepages | Why your dates all belong in
<time> |
|
| Lunch — dietary details in the logistics section | ||
|
double slot |
Workshop: tables that screen readers can actually read (this table is the courseware) | Ruby annotations beyond Japanese |
| Bidirectional text without tears | ||
Closing
panel — Was the |
||
| Total | 7 sessions across | |
Logistics
- Venue
- Document Hall, Rotterdam
- Doors open
- Lunch
- Vegetarian by default; every dish labeled with its allergens.