How to fix aria dialog name on Adobe Commerce (Magento)

Add a descriptive accessible name to every dialog and alertdialog element using aria-label or aria-labelledby so screen-reader users know what the dialog is about.

Steps for Adobe Commerce (Magento)

  1. Dialogs in Adobe Commerce (Magento 2) are typically rendered via the modal UI component (Magento_Ui/js/modal/modal) or custom .phtml templates.
  2. For the built-in modal component, override the template in your custom theme at app/design/frontend/<Vendor>/<Theme>/Magento_Ui/templates/modal/modal-popup.html (or modal-slide.html) and add aria-labelledby or aria-label to the outer <div role="dialog"> element.
  3. For custom .phtml popups, edit the template file directly and add the appropriate aria attribute to the dialog container.
  4. If the dialog title is rendered inside the modal, give that element a unique id and reference it with aria-labelledby on the dialog wrapper.
  5. Run bin/magento setup:static-content:deploy after changes, clear cache (bin/magento cache:flush), then verify with axe DevTools.
Official Adobe Commerce (Magento) documentation ↗
<div role="dialog" aria-modal="true" aria-labelledby="cart-dialog-title">
  <h2 id="cart-dialog-title">Your Shopping Cart</h2>
  <!-- dialog content -->
</div>

<!-- OR, when no visible heading exists -->
<div role="dialog" aria-modal="true" aria-label="Newsletter signup">
  <!-- dialog content -->
</div>

What is aria dialog name?

Any time your store shows a popup, modal, or overlay — such as a cookie notice, quick-view product panel, cart drawer, age-verification gate, or newsletter signup — that element needs an accessible name. An "accessible name" is a short label that screen readers announce when the dialog opens, telling the user what the popup is for. It is provided either by pointing to a visible heading inside the dialog (aria-labelledby) or by writing a brief label directly on the element (aria-label). Without one, screen-reader users land in the dialog with no context about its purpose.

Screen readers used by blind and low-vision shoppers announce the accessible name of a dialog the moment it opens. Without a name, a user hears only "dialog" — with no indication of whether it is a cart, a promo, a warning, or something else — making the popup effectively unusable. This violates WCAG 2.1 Success Criterion 4.1.2 (Name, Role, Value), which is a legal requirement under the ADA, the European Accessibility Act, and similar laws in many countries. Beyond legal risk, an inaccessible checkout or cart modal directly reduces conversions among the estimated 7–8 % of online shoppers who rely on assistive technology. Fixing this also benefits keyboard-only users and voice-control software that rely on the same label.

See the complete Aria dialog name guide for every platform and the full background.

Not sure if your Adobe Commerce (Magento) store has this?

Run a free SEOLZ audit — we’ll find aria dialog name and every other issue across your whole site.

Scan my site free

Fix aria dialog name on another platform