ChromeDevTools
Expose accessibility findings from lighthouse
Is your feature request related to a problem? Please describe.
As Lighthouse provides some limited automatic accessibility testing I would like to see it in the MCP as well. It is always an option to use other, specialized MCPs for accessibility needs, but I think offering Lighthouse accessibility testing results directly in Chrome DevTools MCP could be beneficial to awareness and even helping with suggestions for basic fixes.
Describe the solution you'd like
As a minimum, tools would get a section called Accessibility that would have at least two tools:
- getting the accessibility score for a page (as per https://developer.chrome.com/docs/lighthouse/accessibility/scoring) - I am aware that scores are not representing the whole situation as per limitations of automatic tests, but it would be useful to get at least a hint that the score represents.
- getting accessibility audit details - a list of errors and impacted code / DOM elements - so that AI can try to come with fix suggestions.
Describe alternatives you've considered
Using snapshot tool does not offer insights into automatically detected issues, so the only alternative now is to use a specialized MCP for accessibility.
Additional context
I am using/testing multiple other accessibility oriented MCPs now, but if I consider people just starting with accessibility - it would be a great start and better to have something than nothing.
Background: We are evaluating right now how to best make LH audits and Issues available on the MCP server.
@BogdanCerovac how would you expect your AI agent would make use of this in detail? What prompts would you write that would spark the MCP client calling the relevant MCP tool on our end? What prevents you from adding LH directly to your tool chain und using directly?
@natorion - nice, thanks.
As a minimum, I would like to get the accessibility score, list all accessibility issues and, if possible, also get some fix recommendations (I am aware that this can be difficult for some cases, but at least give some basic suggestions could help some people to investigate more).
Basically similar to what is shown in the video made for performance issues on https://developer.chrome.com/blog/chrome-devtools-mcp
But with accessibility in mind, like for example support prompts like:
- What is the accessibility score on https://localhost
- Check for accessibility issues on https://localhost
- Try to fix accessibility issues on https://localhost
I've done some testing and made my own MCP server for accessibility and it worked quite well (limited by the capability of automatic testing ofc.), but I think we should get some basics out of Chrome DevTool MCP for more reach (especially useful for people that are early on their accessibility journey and not (yet) focused on accessibility.