Stacktrace frame location can't be focused with keyboard only
Categories
(DevTools :: Console, defect, P2)
Tracking
(Accessibility Severity:s2, firefox121 fixed)
Tracking | Status | |
---|---|---|
firefox121 | --- | fixed |
People
(Reporter: nchevobbe, Assigned: nchevobbe)
References
(Blocks 1 open bug)
Details
(Keywords: access)
Attachments
(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.
Assignee | ||
Updated•1 year ago
|
Assignee | ||
Updated•1 year ago
|
Assignee | ||
Updated•1 year ago
|
Comment 1•1 year ago
|
||
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.
Updated•1 year ago
|
Assignee | ||
Comment 2•1 year ago
|
||
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
Updated•1 year ago
|
Comment 4•1 year ago
|
||
Backed out for causing dt failures on browser_webconsole_context_menu_copy_message_with_framework_stacktrace.js
Comment 6•1 year ago
|
||
bugherder |
Assignee | ||
Updated•1 year ago
|
Description
•