1879447 - Investigate a11y-checks failing the test for tabs in tablist in Moz-page-nav component

Status: RESOLVED FIXED

(Toolkit :: UI Widgets, task)

Description

[Anna Yeddi [:ayeddi]]

Investigate why an accessible is created for a generic element between the tablist and tab, and ensure AccessibilityUtils are handling the tablist checks properly.

When this is resolved, fail-if notation can be removed from the firefoxview mochitest manifest

Comment 1

[Anna Yeddi [:ayeddi]]

Attachment: Bug 1879447 - Update AccessibilityUtils to support intervening generics between a tab and its tablist in isKeyboardFocusableTabInTablist check. r=Jamie!

There are cases in our code base, in the reusable component that is using Lit components, where a tablist includes a tab component wrapper (that has an accessible role ROLE_TEXT_CONTAINER) - the <moz-page-nav-button> - we want to include this case in the calculation of the tabs within a tablist calculation when checking the tablist's keyboard accessibility.

Comment 2

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/2ece02cea535
Update AccessibilityUtils to support intervening generics between a tab and its tablist in isKeyboardFocusableTabInTablist check. r=Jamie,fxview-reviewers

Comment 3

[pstanciu]

https://hg.mozilla.org/mozilla-central/rev/2ece02cea535