Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Introduce a11y-focus mode for element inspector? #60941

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
1 of 2 tasks
moniuch opened this issue Apr 20, 2025 · 1 comment
Open
1 of 2 tasks

Introduce a11y-focus mode for element inspector? #60941

moniuch opened this issue Apr 20, 2025 · 1 comment

Comments

@moniuch
Copy link

moniuch commented Apr 20, 2025

Is this a bug report or a feature request?

  • Bug Report
  • Feature Request

Please provide the steps to reproduce the issue [Bug Report only]

Since what I'm asking for is not achievable in the native browser DevTools inspector, I thought maybe Angular DevTools could offer it.

I'd appreciate having an a11y focus mode in the element inspector.

Please provide the expected behavior vs the actual behavior you encountered [Bug Report only]

No response

Please provide a screenshot if possible [Bug Report only]

No response

Please provide the exception or error you saw [Bug Report only]


Is this a browser-specific issue? If so, please specify the device, browser, and version. [Bug Report only]


Description [Feature Request only]

No response

Proposed solution [Feature Request only]

This would be mode where the inspector would only show a specific subset of element attributes that allows debugging/troubleshooting HTML markup when ensuring proper a11y behaviors.

So the elements would show the attributes that contribute to correct a11y behavior: id, role, aria-*, tabindex (and maybe some others should they slip my memory)

This is not to be confused with the Accessibility Tree which serves a different purpose:

Image

Alternatives considered [Feature Request only]

The alternatives aren't really there:

  • native devtools' Element inspector shows a whole bunch of attributes, some of them being Angular proprietary ones, such as _ngcontent-ng-... _nghost-ng-..., input reflections, etc. which obscure the attributes that matter for a11y. When focusing on the correct a11y markup, it is difficult to get a good representation of the rendered page with the Angular "noise" filtered out.
  • the Accessibility tree serves a different purpose - it's not to show HTML
@JeanMeche
Copy link
Member

JeanMeche commented Apr 20, 2025

You're probably missing that the devtool only show the directive & component tree but not individual elements and their attributes.

This looks like a feature request for the devtools themselves.

@ngbot ngbot bot added this to the needsTriage milestone Apr 22, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants