AccordionSummary API

The API documentation of the AccordionSummary React component. Learn more about the props and the CSS customization points.

Import

import AccordionSummary from '@material-ui/core/AccordionSummary';
// or
import { AccordionSummary } from '@material-ui/core';

You can learn more about the difference by reading this guide.

The MuiAccordionSummary name can be used for providing default props or style overrides at the theme level.

Name	Type	Default	Description
children	node		The content of the accordion summary.
classes	object		Override or extend the styles applied to the component. See CSS API below for more details.
expandIcon	node		The icon to display as the expand indicator.
focusVisibleClassName	string		This prop can help identify which element has keyboard focus. The class name will be applied when the element gains the focus through keyboard interaction. It's a polyfill for the CSS :focus-visible selector. The rationale for using this feature is explained here. A polyfill can be used to apply a `focus-visible` class to other components if needed.
IconButtonProps	object	{}	Props applied to the `IconButton` element wrapping the expand icon.

The ref is forwarded to the root element.

Any other props supplied will be provided to the root element (ButtonBase).

Rule name	Global class	Description
root	.MuiAccordionSummary-root	Styles applied to the root element.
expanded	.Mui-expanded	Pseudo-class applied to the root element, children wrapper element and `IconButton` component if `expanded={true}`.
focusVisible	.Mui-focusVisible	Pseudo-class applied to the ButtonBase root element if the button is keyboard focused.
disabled	.Mui-disabled	Pseudo-class applied to the root element if `disabled={true}`.
content	.MuiAccordionSummary-content	Styles applied to the children wrapper element.
expandIcon	.MuiAccordionSummary-expandIcon	Styles applied to the `IconButton` component when `expandIcon` is supplied.

You can override the style of the component thanks to one of these customization points:

If that's not sufficient, you can check the implementation of the component for more detail.

The props of the ButtonBase component are also available. You can take advantage of this behavior to target nested components.