Closed Bug 1844092 Opened 5 months ago Closed 1 month ago

Stacktrace frame location can't be focused with keyboard only


(DevTools :: Console, defect, P2)



(Accessibility Severity:s2, firefox121 fixed)

121 Branch
Accessibility Severity s2
Tracking Status
firefox121 --- fixed


(Reporter: nchevobbe, Assigned: nchevobbe)


(Blocks 1 open bug)


(Keywords: access)


(1 file)

When an error is thrown, the links to methods called are included in the trace but they are not focusable with keyboard (only “Learn more” link is focusable that sends a user to MDN), while mouse users could hover and activate these links. No role is provided for a screen reader as well, so its user would not know if they can, in fact, activate these links that are announced as static text.

Accessibility Severity: --- → s2
Severity: S2 → S3
Priority: -- → P2

The severity field for this bug is set to S3. However, the accessibility severity is higher, .
:nchevobbe, could you consider increasing the severity?

For more information, please visit BugBot documentation.

Flags: needinfo?(nchevobbe)
Flags: needinfo?(nchevobbe)

The frame elements already had the correct roles assigned,
but this was made completely useless because we had a
display: contents on them, which strips any accessibility role.
This was done for layout purpose that we now can do with
subgrids, so we update the component's CSS.
A webconsole test is added to ensure those stactkrace frames
can be navigated with the keyboard.

Depends on D190578

Assignee: nobody → nchevobbe
Pushed by
[devtools] Make Stacktrace frame location keyboard accessible. r=devtools-reviewers,bomsy.

Backed out for causing dt failures on browser_webconsole_context_menu_copy_message_with_framework_stacktrace.js

Backout link

Push with failures

Failure log

Flags: needinfo?(nchevobbe)
Pushed by
[devtools] Make Stacktrace frame location keyboard accessible. r=devtools-reviewers,bomsy.
Closed: 1 month ago
Resolution: --- → FIXED
Target Milestone: --- → 121 Branch
Flags: needinfo?(nchevobbe)
You need to log in before you can comment on or make changes to this bug.