Skip to main content
Every renderer ships accessible defaults: every event, day cell, and day-column header carries a full label and role out of the box, and moving or resizing an event has an alternative to dragging. On React Native it is a set of screen-reader actions; on the web it is a dialog of buttons that works with a keyboard, a single click, or a tap.

Labels

Day cells announce the full date, today, selection state, and how many events they hold (“Friday, 17 July 2026, today, 3 events”). Events announce their title and time range; all-day events say so instead of a time. Override the event announcement with eventAccessibilityLabel:

Translating the labels

The date part of each label follows locale. The words around it come from labels, so pass translations to localize them. Keys you omit stay in English (defaultCalendarLabels). Define the object outside the component, or memoize it, so the views don’t re-render on every pass:
The ", " separator and the word order are fixed. To word a whole event label differently, use eventAccessibilityLabel.

Screen-reader actions (React Native)

Dragging is a gesture, so draggable events expose the same operations as accessibility actions: VoiceOver and TalkBack users pick “Move 15 minutes later/earlier” or “Extend/Shorten by 15 minutes” from the actions rotor, and the change commits through the same onDragEvent path as a gesture. The step follows dragStepMinutes. Time-grid events and ResourceTimeline bars both expose them whenever onDragEvent is set. Translate their names with labels.

Move and resize actions (web)

In React DOM and Solid, Edit events opens a list of the visible events you can move or resize in TimeGrid and either ResourceTimeline orientation. The chooser shows each event’s date and time, plus its resource on the board. Long lists scroll while each choice keeps its full title and dates visible. Titles without spaces wrap within the choice or dialog. Its buttons have separate targets, even when events overlap or the calendar is narrow. Choosing an event never activates it or starts a drag. Opening the chooser focuses its first event. Use the arrow keys, Home, End, or Tab to navigate its choices; Escape closes it and focuses Edit events. Choose an event to open a modal dialog named after the event (“Move or resize Planning”). The dialog is centered in the viewport, shows the event’s time, and lists native buttons:
  • Move 15 minutes later / earlier and Extend / Shorten by 15 minutes, stepping by dragStepMinutes.
  • Move to next / previous week (or day, or N days) in TimeGrid.
  • Move to the neighbouring lanes in ResourceTimeline, named after the resources.
Each button commits through the same path as a drop. onDragEvent receives the proposed start and end (and the target resource on the board), the same bounds a drag produces. eventOverlap={false}, draggable: false, startEditable, and durationEditable apply as they do to a drag. A shorten that would leave the event below one step is marked unavailable with aria-disabled. Returning false from onDragEvent leaves the event where it was. A rejected change shows labels.eventChangeRejected in a polite status region, including overlap rejections. Repeated rejections update the region again; an accepted edit clears it. The calendar stays controlled. After an accepted change, the dialog follows the unique new event you render in its place (same title, new times, and new lane on the board), so you can press Move later several times in a row. Other event objects must keep their references for this default matching to work. For full data refreshes, pass getEventId to web Calendar, TimeGrid, or ResourceTimeline. Return a stable string or number that uniquely identifies each event in events. For recurring data, identify each occurrence, not its series. Numeric 0 and string "0" are distinct IDs. The dialog follows that ID when objects, titles, times, or lanes change, and actions use the latest event. Without getEventId, a full refresh closes the dialog. The dialog closes if the event disappears, its identity is ambiguous, its lane goes away, or editing is turned off. With getEventId, removing the getter or providing missing, invalid, or duplicate IDs also closes it. IDs must be strings or numbers. The live description includes both dates for multi-day events and, on the board, the resource. When the dialog opens, focus moves to its first action. The arrow keys, Home, and End move between the actions alongside Tab. PageUp and PageDown do not page the calendar behind the dialog. Escape, the Close button, or a click on the backdrop closes it and returns focus to Edit events. If that control is gone, focus returns to the calendar. Style the parts with eventActionsTrigger (the chooser button), eventActionsList (the event list), eventActions (the dialog), and eventAction (each button) slots, and translate the words with labels:

Keyboard (web)

  • Paging — on react-native-web the left/right arrow keys page the month and time-grid views (the schedule scrolls instead); the dom renderer pages with PageUp/PageDown when onChangeDate is wired.
  • keyboardDayNavigation (dom MonthView / MonthList) — arrow keys move between day cells, Enter/Space selects.
  • keyboardEventNavigation (dom TimeGrid) — Up/Down move through a day’s events by time, Left/Right jump to the nearest event in the adjacent day, Home/End reach the first/last, Enter/Space activate. Navigation is additive: every event stays in the Tab order.
  • Date pickers: opening a DatePicker or DateRangePicker moves focus to the selected day (or today, or the first available day in that month). If that month has no available days, focus moves to the popover panel. Arrow keys move between days; Escape closes the popover and returns focus to the field. Picking a date or completing a range also returns focus to the field.

Reduced motion

On React Native the time grid honours the OS reduce-motion setting: its one animated snap (recentring after a cell press) becomes an instant jump. The month pager’s page transitions never animate programmatic jumps in the first place. Reanimated drives the remaining transitions on the UI thread, so nothing relies on JS-thread timing.

Automated checks

The shared browser tests run axe against the month list, time grid, resource timelines, date pickers, and the actions dialog in Chromium, Firefox, and WebKit, together with keyboard and focus assertions. These checks catch common semantic and focus problems. They do not replace testing with the screen readers your users rely on.

Custom renderers

A custom renderEvent receives accessibilityActions / onAccessibilityAction in its args on native; spread them onto your pressable root so screen-reader move/resize keeps working (the built-in renderers do this for you). On the web, the event chooser also works with custom renderEvent content, so your renderer does not need to add controls.