Enforce async a11y assertions and scope checks to <tab-container> in tests

[Copilot]

Accessibility assertions in test/test.js were using expect(...).to.be.accessible() without awaiting/returning the async result, so axe failures could be dropped. After fixing that, body-level checks were over-broad and failed region expectations unrelated to the component under test.

• Assertion lifecycle: make async checks observable

  • Convert relevant afterEach hooks to async and await the a11y assertion.
  • Wrap assertions in try/finally so DOM cleanup always runs.
  • Return the promise from it('has accessible markup', ...) so test runners correctly track failures.

• Assertion scope: test the component, not page layout

  • Change accessibility checks from document.body to the fixture’s tabContainer element.
  • Ensure each affected setup initializes tabContainer before assertions.

afterEach(async function () {
  try {
    await expect(tabContainer).to.be.accessible()
  } finally {
    document.body.innerHTML = ''
  }
})

it('has accessible markup', function () {
  return expect(tabContainer).to.be.accessible()
})

• Fixes Accessibility test results aren't checked #120

[Copilot]

Pull request overview

Ensures accessibility checks are awaited and scoped to the component fixture.

Changes:

• Await asynchronous accessibility assertions with guaranteed cleanup.
• Scope axe checks to <tab-container>.
• Initialize fixture references where required.

Show a summary per file

File	Description
test/test.js	Corrects accessibility assertion lifecycle and scope.

Review details

Tip

Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

• Files reviewed: 1/1 changed files
• Comments generated: 0
• Review effort level: Medium