twimco.Let’s talk ↗︎
Menu
Field notes / Buying software

Browser makers released free web guidance for AI coding agents. Ask whoever builds your site whether it's switched on

If the person who builds your website uses an AI coding tool, the code it writes comes from what the tool already knows. Chrome, Edge, Firefox and MDN just shipped a free add-on that fills in what it gets wrong. Asking about it takes one email.

Editorial engraving of a shopkeeper testing a purchase on his phone at a stationery-shop counter while a developer watches with a laptop.

On November 10, 2026 Chrome, with Edge, Firefox and MDN, released version 1.0 of Modern Web Guidance, a free open-source add-on that gives AI coding agents current web-platform advice on accessibility, performance, security and checkout forms, plus a scan for outdated code. It doesn't replace testing. Ask your developer three things: do they use it, what does the scan find in your site, and how do they check forms and checkout on a phone.

What shipped

Picture your site's developer or agency working with an AI coding tool, as a lot of them now do. The code it writes comes from whatever the tool learned, and that doesn't always match what browsers can do today.

On November 10, Chrome announced the stable release of Modern Web Guidance 1.0. It's a set of skills that put web-platform advice, best practices and browser-compatibility data directly into coding agents, and Chrome says Firefox and Edge are now joining it as a cross-browser effort, with MDN as a partner. You install it in a project with one command, and the GitHub repository carries an Apache-2.0 license.

Chrome gives its reasons plainly. Its evaluations show that even good coding models fall short in a few areas. It names accessibility, such as keyboard focus, reduced-motion support and accessible form validation, along with user experience, performance, such as preventing layout shift, and security, such as safe HTML handling, strict content security policies and passkeys. It also says models are good at making things work with JavaScript, when a plain HTML or CSS feature could do the job with less code and better accessibility.

Version 1.0 adds a modernization workflow. It scans the HTML, CSS, JavaScript and package.json of an existing project, looking for outdated workarounds, unneeded dependencies and polyfills that aren't needed anymore, and guides the agent through changing them. Chrome says that in this first release the scan uses static analysis for a limited set of patterns, and that it plans to cover more over time. Chrome also says every guide has had expert review, with accessibility specialists checking the user-facing ones, and that there's a public dashboard showing how agents do with and without it.

Why a site owner should care

You probably don't read package.json files. You do care whether your checkout works on a phone, whether a screen reader user can fill in your contact form and whether your pages jump around while loading. Those are exactly the things Chrome says models get wrong by default.

Chrome also mentions two details that matter to a shop. Autofill can improve checkout flows, especially on mobile, which it says often fail when custom JavaScript form controls are used. And passkeys, through the WebAuthn standard, offer faster and more secure sign-in.

None of this means your developer is doing anything wrong. It means there's now a free, open-source way to reduce one kind of mistake, and that the people who build your site may or may not have heard of it.

How the work moves

An afternoon, three asks

  1. Ask whether it's switched on

    Which AI coding tools are used on your site, and is Modern Web Guidance installed in them.

  2. Ask for the scan

    A list of outdated patterns found in your current code. A list, not a rewrite.

  3. Ask for the phone test

    How forms, checkout autofill and sign-in were checked on real phones.

  4. Read the answers

    Plain sentences, with a date and a name, are what you want.

  5. Decide what to fix first

    Pick the changes that touch customers: forms, checkout, accessibility.

Illustrative plan for a site owner working with a developer or agency.
The cheapest way to find out how your developer uses AI is to ask what it gets wrong.

Three asks

Here's what we'd put in the next email to whoever builds your site, a developer or an agency. The point isn't to catch anyone out. It's to find out how they work.

1. Do you use AI coding tools on our site, and is Modern Web Guidance part of that setup? A good answer names the tools and says yes, or says why not. A bad answer is "we don't use AI" when they do, or a puzzled silence. The cheapest way to find out how your developer uses AI is to ask what it gets wrong.

2. Can you run the modernization scan on our current code and send us the list? Ask for the list, not the changes. A site that earns money shouldn't have code rewritten because a scan flagged a pattern. The list is useful on its own: it tells you how much outdated code the site carries and gives you something concrete to prioritize. Chrome is explicit that the scan checks a limited set of patterns for now, so a short list isn't a clean bill of health.

3. How did you check forms, checkout and sign-in on real phones? This one has nothing to do with the new tool, and it's the most important. A guide can steer an agent, but only someone buying a pair of socks on a mid-range phone will tell you whether checkout works. The answer should include which phones and which browsers, and who did it.

What good answers look like

Plain sentences, a name and a date. "We use X and Y, we install Modern Web Guidance in each project, here's the scan result from Tuesday, and here's the list of phone tests with the results." That's what you want to read. You don't need to understand every item. You need to see that someone looked.

If the answers are vague, don't panic. Many teams haven't heard of it yet; it was only released a few days ago. The useful reaction is that they go and look, and come back with a plan. If they don't, that tells you how they treat a free improvement.

Decision guide

What the guidance and scan can and can't do

ConsiderationWhat it's built to help withWhat still needs a person
Code habitsSteers agents toward newer, lighter browser features where they fitDeciding whether your audience's browsers need the old way
AccessibilityGuides on focus, reduced motion and form validationTesting with real assistive technology on your own pages
Existing codeA scan for a limited set of outdated patternsJudging what's safe to change in a site that earns money
Checkout and sign-inPointers on autofill and passkeysBuying something on a phone, start to finish
Drawn from Chrome's November 10, 2026 announcement and docs; illustrative reading, not a test of the product.

What it won't do

Keep it in proportion. Chrome's own post says the tool covers a defined set of problems, and it recommends pairing it with Chrome DevTools for agents, so the agent runs the code it wrote and sees whether it works. The guidance steers what gets written. It isn't a substitute for testing.

It also won't make a poorly planned site good. It won't fix a slow server, a confusing checkout or a product page that doesn't answer the questions a buyer has. And the scan, in this first release, looks for a limited set of patterns by static analysis. A clean result means those patterns weren't found, not that the site is modern.

There's a human side as well. Chrome says many developers found the guides useful as a way to learn, not only as input to an agent. That's worth encouraging in whoever works on your site: a team that reads the guidance is better placed to judge what the agent hands back than a team that only installs it.

For the accessibility side, see what the accessibility deadline means for your vendors. For a broader way to size up whoever builds your software, our handover scorecard lists what to ask for at the end of a project.

If you'd like help working out what your site's code needs, or a second opinion on what an agency sends back, that's part of our web application work. Talk to us.

Related work: Paddle8

twimco.

We build alongside the people doing the work.
Bring us the problem you’re thinking about.

Related work

Paddle8 ↗︎