details element, the native html trigger

10 minutes read

What the <details> element is? Well, generally speaking, this element is made to easily create collapsible content without using Javascript. Let's see the basic HTML structure:

<summary>Click to expand</summary>
Sample content

If you inspect the code, you can notice that there is an open attribute that is being added when the content is expanded. Well, this is the key point of this story, with this attribute we can build a lot of UI widgets without using javascript (this doesn't mean you don't need js at all)

The open attribute is added and removed by the browser, based on the state

Let's see now how to use the details element to build other widgets. First of all we need to transform the summary element and make it looks like a button by adding some CSS:

.Button {
appearance: none;
display: inline-flex;
background-color: hsl(220deg 100% 50%);
padding: 1ch 1.4ch;
border-radius: 4px;
cursor: pointer;
color: #fff;

summary.Button::-webkit-details-marker {
display: none;

Then we can apply it to the summary element along with accessibility related attributes.

<summary class="Button" role="button">
Click to open ▾

This is what you get with the above CSS and HTML:

::-webkit-details-marker is used to remove the default arrow

We have now a <summary> element dressed as a button. We'll use this class in the following examples.

To build a dropdown menu using the details element, we need first to set its positioning to be relative because the popup menu will have a position: absolute. We also need to add the aria-haspopup="menu" to the summary element and role="menu" to the custom menu to make them a bit accessible.

<summary class="Button" role="button" aria-haspopup="true">
Click to open ▾
<ul class="Menu" role="menu">
<li>Item 1</li>
<li>This is a super long item 2</li>
<li>Item 3</li>

We can add now the style for the custom menu element, we will use a simple css class to target

.Menu {
all: unset;
position: absolute;
inset-block-start: calc(100% + 8px);
inset-inline-start: 0;
background-color: #fbfbfb;
padding: 0.5em 1em;
min-width: 50px;
list-style: none;
box-shadow: inset 0 0 0 2px hsl(220deg 100% 50%);

.Menu > li {
padding: 0.5em 0;
white-space: nowrap;

There are some key properties here. With the all property we're removing all the default style from the ul. The inset-block-start and inset-inline-start are the logical properties equivalent of top and left (they change based on the text direction), you can learn more on CSS logical properties on MDN. The white-space on the li elements is required to force the menu width to overflow its parent width, which in this case is the width of the fake button.

Here's the final result, without the JS part that update the aria-related attributes based on the state.

Modal dialogs are complex components that require attention and effort to be fully accessible. For example, you should trap the focus inside the modal when it's open, you should hide underlying content from AT when it's open, it should be closed by pressing esc and return the focus to the element which opens it. The WAI ARIA site made a full example, check it to learn more about fully accessible modal.

In this example we'll see only how to use the details element to show/hide the modal and what we can do with the open attribute. The core principles are the same of the dropdown menu, create a details and your modal inside it, but this time we don't want the modal to be positioned relative to the details, so we can remove the .Dropdown class. Here the starting markup:

<summary class="Button" role="button">
Open Modal
<div class="Modal" role="dialog" aria-modal="true">

Now we can add some style to the .Modal element to make it look like a classic modal. Code marked as "functional style" is required to positioning the modal, while the "visual style" is just appearance.

.Modal {
/* Functional style */
position: fixed;
inset: 20vh 2vh auto 2vh;
margin: 0 auto;
z-index: 2;

/* Visual style */
background-color: #fff;
border: 2px solid hsl(220deg 100% 50%);
padding: 24px;
max-width: 448px;

Now we have our modal, but as you can see something is missing, the interactive overlay which should close the modal when clicked.

So let's add the backdrop layer, which as mentioned above should react to the user click. To do it we'll use the <summary> element since it already has that behavior, more precisely we are going to add a ::before pseudo-element to it, but only when the details have the open attribute.

In real situations you have to target only the summary element inside the details that contains a modal, but for this simple example, the following selector is enough.

details[open] summary::before {
content: "";
background: hsl(0 0% 0% / 30%);
position: fixed;
inset: 0;
z-index: 1;

Remember, this is just half of the work you need to do to make a fully accessible modal. You will need javascript to handle the focus trap, the keyboard interactions, and other things, but using the details element we can avoid a bit of js and let the browser doing the rest.

Adding fun

If we want to add a bit of movement we can use the open attribute to trigger animations when the content is showed up. Starting from the dropdown example, let's add a keyframe animation and apply it once the dropdown is visible.

details[open] > .Menu {
animation: fadeIn 200ms cubic-bezier(0, 0.55, 0.45, 1);

@keyframes fadeIn {
0% {
opacity: 0;
transform: translateY(-10px);

100% {
opacity: unset;
transform: none;

More examples

here some example of popover and vied/edit mode built using the details element:


The <details> element can be considered as a native HTML trigger to show hide things without using javascript. You can use it everywhere you have a two-state widget like visible/hidden and open/closed. The important thing is to remember that the accessibility of interactive elements should be implemented by yourself when using this approach.