Closed Bug 1879447 Opened 5 months ago Closed 4 months ago

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

Categories

(Toolkit :: UI Widgets, task)

task

Tracking

()

RESOLVED FIXED
125 Branch
Accessibility Severity s4
Tracking Status
firefox125 --- fixed

People

(Reporter: ayeddi, Assigned: ayeddi)

References

(Blocks 2 open bugs)

Details

(Keywords: access)

Attachments

(1 file)

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

Flags: needinfo?(ayeddi)
Blocks: 1883610
Flags: needinfo?(ayeddi)
Blocks: 1884278

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.

Blocks: 1884825
Blocks: 1854625
Pushed by ayeddi@mozilla.com:
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
Status: NEW → RESOLVED
Closed: 4 months ago
Resolution: --- → FIXED
Target Milestone: --- → 125 Branch
Blocks: 1885008
Blocks: 1885020
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: