Accessibility Tree vs DOM: Visually hiding an element (e.g., CSS opacity: 0) behaves differently for screen readers than display: none or aria-hidden="true". The takesnapshot tool returns the accessibility tree of the page, which represents what assistive technologies "see", making it the most reliable source of truth for semantic structure.
Reading web.dev documentation: If you need to research specific accessibility guidelines (like https://web.dev/articles/accessible-tap-targets), you can append .md.txt to the URL (e.g., https://web.dev/articles/accessible-tap-targets.md.txt) to fetch the clean, raw markdown version. This is much easier to read!
Chrome automatically checks for common accessibility problems. Use listconsolemessages to check for these native audits first:
Utilise Chrome DevTools MCP pour le débogage et l'audit d'accessibilité (a11y) basés sur les directives web.dev. À utiliser pour tester le HTML sémantique, les étiquettes ARIA, les états de focus, la navigation au clavier, les cibles tactiles et le contraste des couleurs. Source : chromedevtools/chrome-devtools-mcp.