Skip to content

"Blocked aria-hidden on an element" error upon closing calcite-alert #11494

@MikeTschudi

Description

@MikeTschudi

Check existing issues

Actual Behavior

Error message appears in debugger console when alert is closed:

Blocked aria-hidden on an element because its descendant retained focus. The focus must not be hidden from assistive technology users. Avoid using aria-hidden on a focused element or its ancestor. Consider using the inert attribute instead, which will also prevent focus. For more details, see the aria-hidden section of the WAI-ARIA specification at https://w3c.github.io/aria/#aria-hidden.
Element with focus: button
Ancestor with aria-hidden:
Image

Expected Behavior

No error message

Reproduction Sample

CodePen in doc page https://developers.arcgis.com/calcite-design-system/components/alert

Reproduction Steps

  1. Go to alert doc page https://developers.arcgis.com/calcite-design-system/components/alert
  2. Open "Edit sample on CodePen"
  3. Open the debugger
  4. Close the alert using the close button

What's weird is that if I change the Calcite version, the problem is usually not repeatable, including if I go back to version 2.13.2. (I was trying to answer the regression? question.)

Reproduction Version

2.13.2

Relevant Info

Windows 11 Enterprise; Chrome 132

Regression?

No response

Priority impact

impact - p3 - not time sensitive

Impact

It does not affect our team at this time.

Calcite package

  • @esri/calcite-components
  • @esri/calcite-components-react
  • @esri/calcite-design-tokens
  • @esri/calcite-ui-icons
  • @esri/eslint-plugin-calcite-components

Esri team

ArcGIS Solutions

Metadata

Metadata

Assignees

No one assigned

    Labels

    0 - newNew issues that need assignment.ArcGIS SolutionsIssues logged by ArcGIS Solutions team members.bugBug reports for broken functionality. Issues should include a reproduction of the bug.estimate - 1Very small fix or change (potentially a single line), doesn't require updates to tests.impact - p3 - not time sensitiveUser set priority impact status of p3 - not time sensitivep - lowIssue is non core or affecting less that 10% of people using the library

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions