What changed
On November 10, 2026, Google's Chrome team released Modern Web Guidance 1.0, a free open-source collection of web-platform guides and agent integrations with Firefox and Edge contributors. The release adds a code-modernization workflow, expert-reviewed accessibility and browser compatibility guidance, and public evaluations of agent output. Developers can install it through npx modern-web-guidance@latest install. The scanner is deliberately a limited static pattern checker, not a comprehensive audit or automatic fixer.
Why it matters
Coding agents can produce functional interfaces while missing current native HTML/CSS, accessibility and browser compatibility details. A maintained, cross-browser knowledge source gives small teams a practical way to steer agents without writing every instruction from scratch. The meaningful trade-off is that guidance improves the odds of better code, not correctness guarantees: project-specific browser support, assistive technology behaviour, and the extra agent tokens and time still need verification.
The browser teams are maintaining guidance together
Chrome's November 10 announcement says Firefox and Edge contributors have joined the project. Guides cover accessibility, modern CSS and HTML, security, performance, browser compatibility and native APIs. The project draws on Baseline support data, and an agent can retrieve relevant guides rather than rely only on its model's training-time knowledge.
The new modernization workflow is narrower than a full audit
Version 1.0 adds a workflow that statically inspects existing HTML, CSS, JavaScript and package.json for certain legacy patterns. Google says the first scanner covers a limited subset of patterns and is designed to grow. It reports opportunities rather than silently rewriting a codebase; a clean scan cannot prove a website has no accessibility, security or compatibility issues.
Independent tests find useful guidance and blind spots
A November 12 independent WordPress-site test found six scanner findings associated with one CSS rule but missed a consequential FAQ fragment-navigation issue; consulting the guide helped the tester implement a fix, which then required browser checks. A separate November 15 hands-on test found only one of four deliberately planted old patterns, with tooltip, modal and scroll-reveal examples missed. These small tests establish limitations, not an overall accuracy rate.
Public benchmark gains carry evaluation and cost caveats
The project's public dashboard reports substantial pass-rate gains on tasks designed around its guides. In one November 9 Codex CLI run, the dashboard reports 50% to 86% on its chosen checks, with tokens increasing from about 13k to 28.3k and time from 85 to 102 seconds. These are project-controlled tasks and checks, not an independent production-wide quality or WCAG assessment. Chrome also cites adopter results from note inc., MetaMask and other teams; these are self-reported case studies rather than controlled independent replication.
Adoption should include actual browser testing
Install or update the skill pack, specify the browsers and support baseline the project needs, ask the agent to explain which guidance it applied, then test keyboard interactions, focus, reduced-motion behaviour, browser support, security-sensitive DOM handling and real device layouts. Chrome itself recommends pairing guidance with browser debugging and performance traces; guidance alone cannot inspect runtime behaviour.