Open Bug 2008208 Opened 8 months ago Updated 7 months ago

Focus not returned after activating button (All "..." menu buttons, except buttons that open dialogs or trigger navigation)

Categories

(Firefox :: New Tab Page, defect)

Firefox 148
defect

Tracking

()

Accessibility Severity s3

People

(Reporter: john.northup, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: access)

Attachments

(1 file)

Steps to Reproduce

Activate any button within a disclosure (except buttons that open dialogs or trigger navigation).

Expected Behavior

Focus remains on the button so that users can continue navigating the items within the disclosure.
If that button has been removed as a result of user-initiated action (e.g., removing a card or a link), then focus advances to the next focusable item.

Actual Behavior

Disclosure closes, focus is not returned.

User Impact

Users cannot see or hear their place on the page.

WCAG 2.2 References

Recommendations

Keep focus on the button so that users can continue navigating the items within the disclosure.
If that button has been removed as a result of user-initiated action (e.g., removing a card or a link), then set focus on the next focusable item.

Testing Environment

Any

Assistive Technology Used

Any or None

Code Pointers


Further Reference

I've reproduced this issue in Nightly 149.0a1 on macOS 15. Marking as New.

Status: UNCONFIRMED → NEW
Ever confirmed: true
Accessibility Severity: --- → s3
Summary: Focus not returned after activating button (All buttons within disclosures, except buttons that open dialogs or trigger navigation) → Focus not returned after activating button (All "..." menu buttons, except buttons that open dialogs or trigger navigation)

Pressing tab once would move the focus back to the URL input, but it is still confusing to hear New tab document, because the user would not know if they've lost the location of their page review. This is especially made more cumbersome, given the ... menu buttons are not always visible, until hovered, thus there is no way to quickly navigate back to that same menu button.

Assigning the Severity value to align with the Accessibility severity, per discussions with :thecount and :marco

Severity: -- → S3
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: