Intent to prototype: adding accessibility issues and provide squiggly lines support

[Yanling Wang]

Hello devtools-dev,

 

I've created an explainer on adding squiggly lines support for accessibility issues. Please take a look and leave any comments you have.

https://docs.google.com/document/d/1O2itGor2_kduEbKgKkzgcT6jRpWvuC-ouPYJVRuo_gw/edit?usp=sharing

 

Thank you!

[Changhao Han]

Could you please give comment access to this group? At least for now I don't have comment access to this doc.

Regarding adding squiggly line warnings in the DOM tree for any accessibility issues, I believe we have discussed this multiple times, and we have been quite skeptical about allowing an unmanned list of squiggly lines showing up in the DOM tree. So far we only have Autofill issues and customizable <select> issues showing up in the DOM tree, and they show up there not because which category they belong to, but because of the severity of the issues. I think our go-to guideline is, only when an issue is severe enough to warrant a console spam warning, it can be considered adding to the DOM tree as a warning. Even then I would suggest we be selective, because the DOM tree is already filled with information and different kinds of UX. More squiggly lines would risk creating visual noises for developers.

On the other hand, I would suggest considering the accessibility tree as an alternative place to put squiggly line warnings for accessibility issues. They fit with the context of an accessibility tree, where people go to debug accessibility issues.

I'll leave these as comments once my comment access is granted :)

Cheers

Changhao

--
You received this message because you are subscribed to the Google Groups "devtools-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to devtools-dev...@chromium.org.
To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/devtools-dev/fad0c894-c749-4312-b43b-5d04864509e9n%40chromium.org.

[Rob Paveza]

Hi Changhao,

I'll leave it to Yanling to add comment access to the doc (I can't do it myself).

That having been said, there are folks on the Google side who have been asking for this. One important part of this doc is that it won't happen unless and until a user runs a Lighthouse report, and even then the accessibility warnings can hidden from the DOM tree; so, it isn't a matter of just having as you say "unmanned lists of squiggly lines showing up in the DOM tree." This would be something that would be based on user interaction.

I'll make sure that we make a good connection with the other team that has been asking for this.

Thanks,

Rob

---

From: 'Changhao Han' via devtools-dev <devtoo...@chromium.org>
Sent: Wednesday, April 2, 2025 2:45 PM
To: Yanling Wang <yanli...@microsoft.com>
Cc: devtools-dev <devtoo...@chromium.org>
Subject: [EXTERNAL] Re: [devtools-dev] Intent to prototype: adding accessibility issues and provide squiggly lines support

 

To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/devtools-dev/CA%2Bzt-SONMcdQvRXerh4fpUYb%2BrWLUcSoGeDSqg%3DNMOZoeghGGg%40mail.gmail.com.

[Yanling Wang]

Hello devtools-dev,

We've updated the explainer based on our discussion with the Google team. Thanks Changhao for reviewing it and providing valuable insights.

This is to surface accessibility issues in the Issues panel and the accessibility tree. Please take a look and leave any comments you have:
https://docs.google.com/document/d/1O2itGor2_kduEbKgKkzgcT6jRpWvuC-ouPYJVRuo_gw/edit?usp=sharing

Thanks,
Yanling