fix: support inert attribute and <search> element in role queries

[mixelburg]

Summary

This PR addresses two related issues in role-based queries:

1. inert attribute not hiding elements from a11y tree (#1364)

Elements with the inert attribute (and their descendants) should be excluded from the accessibility tree. Per the HTML spec, inert makes the element and all its contents hidden from assistive technologies.

Fix: Added a check in isSubtreeInaccessible that returns true when:

• The element itself has the inert attribute, OR
• The element has an ancestor with the inert attribute (via element.closest('[inert]'))

2. <search> element not found by getByRole('search') (#1359)

The <search> HTML element has an implicit ARIA role of search per the HTML-ARIA spec, but aria-query@5.3.0 does not include this mapping in its elementRoles map.

Fix: Added a fallback in getImplicitAriaRoles that returns [search] for <search> elements. This workaround can be removed once aria-query publishes a version that includes this mapping (the mapping exists in aria-query's main branch but is not yet released).

Test plan

• Added test case for <div inert /> to the existing shouldExcludeFromA11yTree test matrix
• Added test case for elements nested inside an inert subtree
• Added test case for <search> element implicit role
• All 669 existing tests pass
• Full test suite passes: 29 passed, 29 total

Related issues

• Fixes Elements with an inert="" attribute aren't being hidden from the accessibility tree #1364
• Fixes getByRole('search') does not find <search /> #1359

[codesandbox-ci]

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

Latest deployment of this branch, based on commit 7451bae:

Sandbox	Source
react-testing-library-examples	Configuration

[philwolstenholme]

Nice! I think I'll have a use case for this soon so might try it out via patching the main package

[philwolstenholme]

Although have you seen the history on #1366? @eps1lon had some concerns about how dialog elements handle inert, so it's not as simple as just 'anything inside an inert parent is also inert', unfortunately.

That said, for my use case this will probably be fine, so I'll probably still apply the patch.