Skip to content
Merged
Show file tree
Hide file tree
Changes from 9 commits
Commits
Show all changes
22 commits
Select commit Hold shift + click to select a range
f31f5e4
[scheduler][docs] Create accessibility documentation section
mustafajw07 May 22, 2026
73a6d18
[docs] Update accessibility documentation for consistency in examples
mustafajw07 May 22, 2026
ac96e2b
fix(docs): correct formatting of header row in accessibility document…
mustafajw07 May 22, 2026
109dff6
fix(docs): update accessibility documentation for grid role and keybo…
mustafajw07 May 22, 2026
65598c6
[docs] update ariaLabelledBy for MoreEventsPopover to include schedul…
mustafajw07 May 23, 2026
bcc4a87
Merge branch 'master' into docs/21463-scheduler-accessibility-section
mustafajw07 May 27, 2026
740572e
fix(docs): enhance localization of ARIA labels in accessibility docum…
mustafajw07 May 27, 2026
d26500b
Merge branch 'master' into docs/21463-scheduler-accessibility-section
mustafajw07 May 29, 2026
f1a8e84
Merge branch 'master' into docs/21463-scheduler-accessibility-section
mustafajw07 May 30, 2026
9479000
Merge branch 'master' into docs/21463-scheduler-accessibility-section
mustafajw07 Jun 2, 2026
603b158
Merge branch 'master' into docs/21463-scheduler-accessibility-section
mustafajw07 Jun 3, 2026
1765e7c
Merge branch 'master' into docs/21463-scheduler-accessibility-section
mustafajw07 Jun 4, 2026
7e6e712
Merge branch 'master' into docs/21463-scheduler-accessibility-section
mustafajw07 Jun 5, 2026
545163b
[accessibility] Enhance ARIA labels and localization for improved scr…
mustafajw07 Jun 9, 2026
39786f6
[fix] updated localText files
mustafajw07 Jun 9, 2026
210b1ad
[accessibility] Improve ARIA labeling for event dialogs to enhance sc…
mustafajw07 Jun 10, 2026
cda73e4
Merge branch 'master' into docs/21463-scheduler-accessibility-section
mustafajw07 Jun 10, 2026
63ee6d3
Merge branch 'master' into docs/21463-scheduler-accessibility-section
rita-codes Jun 11, 2026
e7c7504
Merge branch 'master' into docs/21463-scheduler-accessibility-section
mustafajw07 Jun 12, 2026
d261844
Merge branch 'master' into docs/21463-scheduler-accessibility-section
mustafajw07 Jun 12, 2026
f99d03a
Merge branch 'master' into docs/21463-scheduler-accessibility-section
mustafajw07 Jun 15, 2026
60a972d
Merge branch 'master' into docs/21463-scheduler-accessibility-section
rita-codes Jun 15, 2026
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions docs/data/pages.ts
Original file line number Diff line number Diff line change
Expand Up @@ -36,6 +36,7 @@ const schedulerPages: MuiPage[] = [
children: [
{ pathname: '/x/react-scheduler/timezone', title: 'Timezones' },
{ pathname: '/x/react-scheduler/recurring-events', plan: 'premium' },
{ pathname: '/x/react-scheduler/accessibility', title: 'Accessibility' },
],
},
{
Expand Down
218 changes: 218 additions & 0 deletions docs/data/scheduler/accessibility/accessibility.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,218 @@
---
productId: x-scheduler
title: Accessibility
githubLabel: 'scope: scheduler'
waiAria: https://www.w3.org/WAI/ARIA/apg/patterns/grid/
packageName: '@mui/x-scheduler'
---

# Accessibility

<p class="description">Learn how the Scheduler implements accessibility features and guidelines, including ARIA semantics, keyboard navigation, and localization of accessible labels.</p>

## Guidelines

Common conformance guidelines for accessibility include:

- Globally accepted standard: [WCAG](https://www.w3.org/WAI/standards-guidelines/wcag/)
- US:
- [ADA](https://www.ada.gov/) - US Department of Justice
- [Section 508](https://www.section508.gov/) - US federal agencies
- Europe: [EAA](https://commission.europa.eu/strategy-and-policy/policies/justice-and-fundamental-rights/disability/european-accessibility-act-eaa_en) (European Accessibility Act)

[WCAG 2.2](https://www.w3.org/TR/WCAG22/) has three levels of conformance: A, AA, and AAA.
Level AA exceeds the basic criteria for accessibility and is a common target for most organizations, so this is what we aim to support.

The [WAI-ARIA Authoring Practices](https://www.w3.org/WAI/ARIA/apg/patterns/grid/) provide valuable information on how to optimize the accessibility of a scheduler component.

## ARIA structure and semantics

The Scheduler uses WAI-ARIA grid and tree roles to expose its structure to assistive technologies.

### Week and Day views

The day-time grid is exposed as a `role="grid"` with three logical rows:

| Row | `aria-rowindex` | Content |
| ------: | :-------------- | :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Header | `1` | Day column headers — `role="columnheader"` with an `aria-label` containing the full weekday name and date (for example, `"Monday 26"`) |
| All-day | `2` | All-day event cells — `role="gridcell"` with `aria-labelledby` pointing to the column header. The visible "All day" label is `aria-hidden="true"` and referenced via `aria-labelledby` on each cell |
| Timed | `3` | Per-column time cells |

The grid also exposes `aria-colcount` for the number of visible days and `aria-colindex` on every cell.

The time axis (hour labels and grid lines) is `aria-hidden="true"` as it is decorative.

### Month view

The month grid uses the same `role="grid"` pattern with `aria-rowcount`, `aria-colcount`, `aria-rowindex`, and `aria-colindex`.
Each weekday header cell carries a `role="columnheader"`.

When `showWeekNumber` is enabled, the week-number labels are `aria-hidden="true"` but each day cell in that row references the week-number element via `aria-labelledby`, so screen readers can announce it.

### Mini calendar (side panel)

The mini calendar is exposed as a `role="grid"` with an `aria-label` (localized — default: `"Calendar"`).

The grid body is wrapped in a `role="rowgroup"` element. Each day cell consists of a `role="gridcell"` container (with `aria-colindex`) wrapping a button element.

The button element carries:

- `aria-label` — the full formatted date string
- `aria-current="date"` — on today's date
- `aria-selected` — on the currently active (selected) date
- A roving `tabIndex` — `0` on the active cell, `-1` on all others

Weekday column headers carry a `role="columnheader"` with an `aria-label` containing the full weekday name (for example, `"Sunday"`).

### Events

Each event element has an `aria-labelledby` that composes the day column header ID and the event's own title element ID, so a screen reader announces the day context alongside the event title.

Multi-day events are rendered once as the main (visible) element and additionally as invisible placeholder elements in the spanned cells. The placeholder elements carry `aria-hidden="true"` so assistive technologies see only one announcement per event.

The resource color indicator inside an event uses `role="img"` with an `aria-label` describing the resource (for example, `"Resource: Sport"`). When no resource is assigned the label falls back to the localized `noResourceAriaLabel` value.

Recurring event icons are `aria-hidden="true"` as they are decorative.

### Agenda view

Each day group in the agenda carries `aria-labelledby` pointing to its day header cell. The day header cell itself has an `aria-label` composed of the weekday name and day-of-month (for example, `"Monday 26"`).

### Main calendar region

The main calendar view area is rendered as a `<section>` element with `aria-label="Calendar content"`, providing a named landmark region that assistive technology users can navigate to directly.

## Keyboard interactions

:::info
The key assignments in the table below apply to Windows and Linux users.

On macOS replace <kbd class="key">Ctrl</kbd> with <kbd class="key">⌘ Command</kbd>.

Some devices may lack certain keys, requiring the use of key combinations. In this case, replace:

- <kbd class="key">Home</kbd> with <kbd><kbd class="key">Fn</kbd>+<kbd class="key">Arrow Left</kbd></kbd>
- <kbd class="key">End</kbd> with <kbd><kbd class="key">Fn</kbd>+<kbd class="key">Arrow Right</kbd></kbd>
:::

### Calendar grid

The Week, Day, and Month views implement a `role="grid"` with full arrow key navigation between cells.

**Week and Day views** expose three logical rows: the header row (day names), the all-day row, and the timed-events row. Arrow keys move across all three rows.

**Month view** exposes the header row and one day-grid row per week. Arrow keys move between the header and each week row, and between individual weeks.

| Keys | Description |
| ---------------------------------: | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| <kbd class="key">Arrow Left</kbd> | Moves focus to the previous column in the same row |
| <kbd class="key">Arrow Right</kbd> | Moves focus to the next column in the same row |
| <kbd class="key">Arrow Up</kbd> | Moves focus to the same column in the row above. In Week/Day view: from all-day row to header, or from time-grid row to all-day. In Month view: from a week row to the one above, or from the first week row to the header |
| <kbd class="key">Arrow Down</kbd> | Moves focus to the same column in the row below |
| <kbd class="key">Enter</kbd> | On a day-grid or time-grid cell: starts event creation for that date or time slot. On a header cell: activates the day button (navigates to that day's view) |

#### Tab sequence

All grid cells have `tabIndex="0"`, so the <kbd class="key">Tab</kbd> key flows through the grid cell by cell in document order. When a focused cell contains events, <kbd class="key">Tab</kbd> enters the events inside it before moving to the next cell.

### Resources sidebar

The Resources sidebar uses the [MUI X Rich Tree View](/x/react-tree-view/) internally and inherits its full keyboard behavior. See the [Tree View accessibility page](/x/react-tree-view/accessibility/) for the complete keyboard interaction reference.

<kbd class="key">Space</kbd> additionally toggles the visibility (checked state) of the focused resource.

### Menus and popovers

| Keys | Description |
| ----------------------------: | :---------------------------------------------------------------------- |
| <kbd class="key">Escape</kbd> | Closes the View Switcher menu, Preferences menu, or More Events popover |
| <kbd class="key">Enter</kbd> | Activates (opens) a focused event in the More Events popover |
| <kbd class="key">Space</kbd> | Activates (opens) a focused event in the More Events popover |

## Live region announcements

The current month and year label in the header toolbar is wrapped in an `aria-live="polite"` region.
When a user navigates to the previous or next time span (for example, clicking **Previous week**), the updated toolbar label is automatically announced by screen readers without requiring focus to move.

## Event dialog

The Event Dialog is a non-modal dialog (`aria-modal="false"`) that floats next to the event that opened it.

### Read-only dialog

- Uses `aria-labelledby` pointing to a title with `id="${schedulerId}-draggable-dialog-title"`.
- The Close button carries a localized `aria-label` (default: `"Close"`).

### Editable dialog

- Uses `aria-labelledby` pointing to a title with `id="${schedulerId}-event-dialog-title"`.
- The event title input is labeled with a localized `aria-label` (default: `"Event title"`).
Comment on lines +143 to +149

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Small follow-up from the read-only dialog fix 👀

Now that the code normalizes the read-only dialog title to ${schedulerId}-event-dialog-title, both dialogs share the same id, so this line still pointing at the old draggable-dialog-title is now stale.

Rather than just swapping the id, I'd suggest dropping the literal id strings from both this and the editable section and saying something like "The dialog is labelled by its event title via aria-labelledby." That also closes @mj12albert's earlier point about exposing exact ids, and since both modes now share the same id, listing them separately is a bit redundant anyway.

What do you think?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good catch. Since both dialogs now use the same title id, documenting the specific id values doesn't add much value anymore, and the read-only dialog section is now stale.

I agree that describing the accessible behavior is clearer and more future-proof. Something along these lines?

  • The dialog is labelled by its event title via aria-labelledby.

Then keep the mode-specific details only for the controls that differ, e.g.:

Read-only dialog

  • The Close button carries a localized aria-label (default: "Close").

Editable dialog

  • The event title input is labeled with a localized aria-label (default: "Event title").

If that looks good to you, I'll update the docs accordingly.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, that sounds good to me!

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks! I've updated the docs accordingly.

- The color picker group has an `aria-label` (default: `"Event color"`), and each individual color option button is labeled (for example, `"Select green as event color"`).
- The Recurrence tab panel uses `role="tabpanel"` with `aria-labelledby` pointing to its tab.
- The recurring scope confirmation dialog radio group has an `aria-label` (default: `"Editing recurring events scope"`).

## More Events popover

When a month cell has more events than can be displayed, a **"X more"** button opens a popover listing all events for that day.

- The popover header element carries an `aria-label` with the full formatted date (for example, `"Monday, May 26"`).
- Each event inside the popover uses `aria-labelledby` that composes the popover header ID and the event title element ID, so screen readers announce the day context alongside the event title.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Noticed this doesn't match the implementation:

id={`${schedulerId}-PopoverHeader-${day.key}`}
aria-label={`${formatWeekDayMonthAndDayOfMonth(day.value, adapter)}`}
>
<MoreEventsPopoverTitle className={classes.moreEventsPopoverTitle}>
{formatWeekDayMonthAndDayOfMonth(day.value, adapter)}
</MoreEventsPopoverTitle>
</MoreEventsPopoverHeader>
<MoreEventsPopoverBody className={classes.moreEventsPopoverBody}>
{occurrences.map((occurrence) => (
<EventDialogTrigger occurrence={occurrence} key={occurrence.key}>
<EventItem
variant={isOccurrenceAllDayOrMultipleDay(occurrence, adapter) ? 'filled' : 'compact'}
occurrence={occurrence}
date={day}
ariaLabelledBy={`PopoverHeader-${day.key}`}

(Could be a bug, one of those don't have a schedulerId)

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good catch — there was an inconsistency between the generated header ID and the referenced aria-labelledby value. Updated the implementation so both now use the same ID format.

- Event items have `role="button"` with `tabIndex="0"`, and can be activated with <kbd class="key">Enter</kbd> or <kbd class="key">Space</kbd>.

## Preferences menu

The Preferences menu button exposes `aria-haspopup="true"`, `aria-expanded`, and `aria-controls`.
Inside the menu:

- Toggle items (for example, **Show weekends**, **Show week number**) use `role="menuitemcheckbox"` with `aria-checked`.
- Time format options use `role="menuitemradio"` with `aria-checked`.

## Localization of ARIA labels

All user-facing accessible labels are provided through the `localeText` prop and can be customized.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Some are not yet exposed, e.g.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You're right — updated the documentation wording.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

IMO the right thing to do is actually expose all user-facing text labels

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey @mj12albert , I noticed that ViewSwitcher.tsx has aria-label="Switch View" hardcoded (line 67). I wanted to flag two things:

  1. It's not localized. The button's visible text {localeText[view]} (for example, "Week", "Month") is already going through localeText, but the aria-label overrides that for screen readers with a hardcoded English string.

  2. Is it even needed? When a button has both visible text and an aria-label, the aria-label takes precedence and suppresses the visible text for screen readers. Since {localeText[view]} already communicates the current view ("Week", "Month", etc.) and the button also gets aria-expanded from the menu pattern, the hardcoded aria-label is actually making things worse — a French user would hear "Switch View" instead of "Mois".

Should we just remove it and let the button's localized visible text do the job? Or if we want to keep a label like "Switch View", it should go through localeText so it can be translated. Happy to do either — just wanted your input before changing it.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not specifically calling out "Switch View" here, but it's just one example of a non-exposed aria-label I noticed

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I believe all such cases have already been covered. Could you point out any specific aria-labels that you think are still missing so I can verify them?

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This for example:

aria-label={`Select ${colorOption} as event color`}

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This case is already covered. I added the corresponding label on line 182.

The following keys are specifically relevant to accessibility:

```ts
{
// Event dialog
closeButtonAriaLabel: 'Close',
eventTitleAriaLabel: 'Event title',
colorPickerLabel: 'Event color',
selectColorAriaLabel: (color) => `Select ${color} as event color`,
radioGroupAriaLabel: 'Editing recurring events scope',

// Events
noResourceAriaLabel: 'No specific resource',
resourceAriaLabel: (resourceName) => `Resource: ${resourceName}`,
hiddenEvents: (count) => `${count} more..`,

// Month view
weekNumberAriaLabel: (weekNumber) => `Week ${weekNumber}`,

// Mini calendar
miniCalendarLabel: 'Calendar',
miniCalendarGoToPreviousMonth: 'Show previous month in calendar',
miniCalendarGoToNextMonth: 'Show next month in calendar',

// Header toolbar
previousTimeSpan: (timeSpan) => `Previous ${timeSpan}`,
nextTimeSpan: (timeSpan) => `Next ${timeSpan}`,
openSidePanel: 'Open side panel',
closeSidePanel: 'Close side panel',
}
```

See the [Event Calendar localization page](/x/react-scheduler/event-calendar/localization/) and the [Event Timeline localization page](/x/react-scheduler/event-timeline/localization/) for the full list of available keys and instructions on how to apply them.

## Known limitations

### No arrow key navigation in the mini calendar

The mini calendar in the side panel exposes `role="grid"` and a roving `tabIndex` on the active date, but arrow key navigation between day cells is not implemented. Clicking a date or using the previous/next month buttons are the only supported interaction methods.

## API

- [EventCalendar](/x/api/scheduler/event-calendar/)
- [EventCalendarPremium](/x/api/scheduler/event-calendar-premium/)
- [EventTimelinePremium](/x/api/scheduler/event-timeline-premium/)
6 changes: 6 additions & 0 deletions docs/pages/x/react-scheduler/accessibility.js
Original file line number Diff line number Diff line change
@@ -0,0 +1,6 @@
import { MarkdownDocs } from '@mui/internal-core-docs/MarkdownDocs';
import * as pageProps from 'docs/data/scheduler/accessibility/accessibility.md?muiMarkdown';

export default function Page() {
return <MarkdownDocs {...pageProps} />;
}
Original file line number Diff line number Diff line change
Expand Up @@ -93,7 +93,7 @@ export default function MoreEventsPopoverContent(props: MoreEventsPopoverProps)
variant={isOccurrenceAllDayOrMultipleDay(occurrence, adapter) ? 'filled' : 'compact'}
occurrence={occurrence}
date={day}
ariaLabelledBy={`PopoverHeader-${day.key}`}
ariaLabelledBy={`${schedulerId}-PopoverHeader-${day.key}`}
/>
</EventDialogTrigger>
))}
Expand Down
Loading