This repository is a fork from accessible-modal-dialog by Greg Kraus. We at Edenspiekermann are big fans of the original version, although we discovered we could improve it and make it even better. On top of that, the original script depends on jQuery, which happened to be a problem for us.

The original repository being apparently unmaintained, we decided to fork it and release our own version of the accessible modal dialog. All credits to the original author.

You can try the live demo.

• No more dependency to jQuery (vanilla JS only);
• Possibility to have several different modals on the page;
• DOM API for modal openers (data-modal-show="modal-id") and closers (data-modal-hide);
• JS API to manually show and hide modals (modal.show(), modal.hide());
• JS API to know whether a modal is hidden or shown (modal.shown);
• Addition of [tabindex]:not([value="-1"]) to focusable elements;
• No more display manipulation in JS, the hiding mechanism is entirely up to the CSS layer (using [aria-hidden] selectors);
• Cleaner code.

npm install accessible-modal-dialog --save

Or you could also copy/paste the script in your project directly, but you will be disconnected from this repository, making it hard for your to get updates.

You will find a concrete demo in the example folder of this repository, but basically here is the gist:

Here is the basic markup, which can be enhanced. Pay extra attention to the comments.

<!--
  Main container related notes:
  - It doesn’t have to be a `main` element, however this is recommended.
  - It doesn’t have to have the `aria-label="Content"` attribute, however this is recommended.
  - It can have a different id than `main`, however you will have to pass it as a second argument to the Modal instance. See further down.
-->
<main id="main" aria-label="Content">
  <!--
    Here lives the main content of the page.
  -->
</main>

<!--
  Modal container related notes:
  - It is not the actual modal, just the container with which the script interacts.
  - It has to have the `aria-hidden="true"` attribute.
  - It can have a different id than `my-accessible-modal`.
-->
<div id="my-accessible-modal" aria-hidden="true">

  <!--
    Overlay related notes:
    - It has to have the `tabindex="-1"` attribute.
    - It doesn’t have to have the `data-modal-hide` attribute, however this is recommended. It hides the modal when clicking outside of it.
  -->
  <div tabindex="-1" data-modal-hide></div>

  <!--
    Modal content relates notes:
    - It is the actual visual modal element.
    - It has to have the `role="dialog"` attribute.
    - It doesn’t have to have a direct child with the `role="document"`, however this is recommended.
  -->
  <div role="dialog">
    <div role="document">
      <!-- 
        Here lives the main content of the modal.
      -->

      <!--
        Closing button related notes:
        - It does have to have the `type="button"` attribute.
        - It does have to have the `data-modal-hide` attribute.
        - It does have to have an aria-label attribute if you use an icon as content.
      -->
      <button type="button" data-modal-hide aria-label="Close this modal">
        &times;
      </button>
    </div>
  </div>
</div>

You will have to implement some styles for the modal to “work” (visually speaking). The script itself does not take care of any styling whatsoever, not even the display property. It basically mostly toggles the aria-hidden attribute on the main element and the modal itself. You can use this to show and hide the modal:

.modal[aria-hidden="true"] {
  display: none;
}

// Get the modal element (with the accessor method you want)
var modalEl = document.getElementById('my-awesome-modal');

// Instanciate a new Modal module
var modal = new Modal(modalEl);

The script assumes the main document of the page has a main id. If it is not the case, you can pass the main node as second argument to the Modal constructor:

var modal = new Modal(modalEl, mainEl);

There are 2 ways of toggling the modal. Either through the DOM API, or directly with JavaScript. Both ways are inter-operable so feel free to use both if you need it.

The following button will open the modal with the my-awesome-modal id when interacted with.

<button type="button" data-modal-show="my-awesome-modal">Open the modal</button>

The following button will close the modal in which it lives when interacted with.

<button type="button" data-modal-hide aria-label="Close the modal">&times;</button>

The following button will close the modal with the my-awesome-modal id when interacted with. Given that the only focusable elements when the modal is open are the focusable children of the modal itself, it seems rather unlikely that you will ever need this but in case you do, well you can.g

<button type="button" data-modal-hide="my-awesome-modal" aria-label="Close the modal">&times;</button>

Regarding the JS API, it simply consists on show() and hide() methods on the modal instance.

// Show the modal
modal.show();

// Hide the modal
modal.hide();

The example page is deployed through GitHub Pages.

npm run example