Guide
Designing a calendar everyone can use
A month grid looks tidy and is hard to use on a phone, with a keyboard or with a screen reader. A few decisions make the same listings usable for far more people.

Start with a list
The most accessible calendar is a plain list of upcoming events in date order, with the date, time, title and place as text. It reads well in a screen reader, reflows on a narrow phone, and works when scripts fail.
A month grid is a second view for people who like to see the shape of a month. Offer it as an option, and make the list the default on small screens.
Use real structure
- Mark dates and times with the time element and a machine-readable value, for example time datetime="2026-01-13T19:00".
- Give each event a heading or a clear link text that makes sense out of context. Several links that all say More do not.
- If you show a month grid, build it as a table with weekday column headers, not as a pile of divs.
- Label the previous and next month buttons with the month they lead to.
Native HTML elements already carry keyboard behaviour and meaning. Heavy custom widgets need much more work to reach the same level, so reach for them only when there is a clear reason.
Do not rely on colour alone
WCAG success criterion 1.4.1 asks that colour is not the only way to carry information. If categories are colour-coded, add a text label or an icon with a text alternative. Text and its background should meet a contrast ratio of at least 4.5 to 1 for normal size text (criterion 1.4.3).
Status is the classic case. A cancelled event shown only in grey is invisible to many people. Write Cancelled in the title area as well.
Keyboard, focus and target size
- Everything that works with a mouse must work with the keyboard (criterion 2.1.1).
- The element that has focus must be visibly marked (criterion 2.4.7). Do not remove the outline without a replacement.
- Small targets are hard to hit. WCAG 2.2 adds a minimum target size of 24 by 24 CSS pixels for most controls (criterion 2.5.8), which matters for tiny day cells.
Test it yourself: put the mouse aside, press Tab, and try to find an event next Friday and subscribe to the feed.
Small screens and zoom
Content should reflow at a width of 320 CSS pixels without scrolling in two directions (criterion 1.4.10). A seven-column grid with long event titles in every cell cannot do this, which is why the list view matters. On a phone, show dots or counts in the grid and open the day's events in a list below it.
Filters and live updates
When a filter changes the list, tell assistive technology what happened, for example with a short status message that says 6 events found. WCAG 2.2 calls these status messages (criterion 4.1.3). Keep the filter controls as real form fields with visible labels.
Describe the venue too
Calendars often forget the practical facts: step-free entrance, accessible toilets, a hearing loop, a quiet room, whether captions or interpreters are provided. If you know them, add them as an optional field on every event. If you do not, say how to ask. See also running a community event calendar for the full list of fields.
Images of text
A flyer posted as an image is invisible to search and to screen readers. If an event exists only as a poster, add the date, time, place and a short description as text next to it.