Urgent.News

What's breaking now, across thousands of outlets.

Tech

I Ran Modern Web Guidance on a Vibe-Coded Landing Page. The Scanner Missed the Worst Parts.

On November 10, Chrome shipped Modern Web Guidance 1.0 , and the project is now stewarded by Chrome, Edge, Firefox, and MDN together. On X it got passed around as "the thing that fixes AI coding habits", usually right next to the other running complaint of the week: vibe-coded sites all look the same, and they all ship the same 2019-era front-end code underneath. The pitch is simple. Coding…

On November 10, Chrome released Modern Web Guidance 1.0, a project now overseen by Chrome, Edge, Firefox, and MDN. The initiative has been widely shared on X as a solution for addressing AI coding habits, often alongside complaints about vibe-coded websites that look identical and utilize similar 2019-era front-end code. The core idea behind Modern Web Guidance is straightforward: coding agents can handle almost any task using JavaScript, but a web platform expert can often identify native HTML or CSS features that offer a more efficient and accessible solution.

This guidance is made accessible to agents through search capabilities and a static scanner called legacy-scan. The project's release notes indicate significant improvements in pass rates when agents utilize the guidance, but these figures should be viewed as reasons to try the tool rather than guarantees. The reporter sought to determine the extent to which Modern Web Guidance can identify issues in a vibe-coded marketing site before launch.

To investigate, the reporter created a small fixture, acme-landing, in the style commonly produced by agents and app builders for a typical SaaS landing page. This landing page includes a modal, a sign-up form, a testimonial rendered with dangerouslySetInnerHTML, a fade-in wrapper, a dark-mode toggle, a navigation menu with scroll highlighting, hover-only tooltips, and third-party scripts and stylesheets from a CDN.

The reporter ran the scanner on this fixture using the command `npx modern-web-guidance@latest legacy-scan`. The scanner returned six findings across five guides:

1. The password input field on the sign-up form lacked the autocomplete attribute. Fix: `autocomplete= "new-password"`.

2. The complex shapes and soft-edge content fade effect used `-webkit-mask-image` with no standard property. Fix: replace with `mask-image` without the prefix.

3. The dark-mode toggle incorrectly used `localStorage` and a `.dark` class to toggle the theme. Fix: use the `color-scheme` meta tag and CSS `color-scheme` and `light-dark()` functions.

4. The navigation menu highlighted the current section using a scroll listener. Fix: implement scrollspy or a navbar solution.

5. The fade-in wrapper used `IntersectionObserver` to fade in elements as they scrolled into view. Fix: use scroll entry/exit effects as recommended in the guidance.

6. A type=text email field in the sign-up form did not provide the appropriate mobile keyboard or autofill. Fix: use type=email to trigger the correct input type.

However, the reporter noted that the scanner did not catch several critical issues that could negatively impact user experience. These issues include:

1. A div-based modal that traps keyboard and screen-reader users.

2. Unsanitized HTML, creating an XSS vulnerability if the testimonial is wired to a CMS.

3. The email field lacking proper mobile keyboard and autofill functionality.

The scanner is designed to catch deterministic issues in only about 20% of web development practices, covering aspects like modal dialogs, unsanitized HTML, scroll effects, navigation highlighting, and fade-in animations. For the remaining 80% of potential issues, the guidance recommends using search functions to retrieve specific recommendations tailored to the developer's needs.

For instance, when faced with a modal dialog requiring a form, developers can run `modern-web-guidance search modal dialog with form` to receive a curated set of recommendations.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

Shopify's image_tag already lazy-loads. Here's what it leaves to you.

I used to write my own lazy-loading logic in every Shopify theme. Then I read the image_tag docs properly and deleted most of it.

  • Shopify's imagetag implements lazy-loading but lacks full performance optimization
  • Imagetag adds width, height, srcset, lazy-loading for non-critical images, and uses WebP/AVIF

Keep CSS scroll snap targets visible below a fixed header

A scroll-snap layout can select the correct section and still feel broken: the section heading lands beneath a fixed header. The snap rule is not necessarily wrong.

  • Use scroll-padding-top to reserve space for fixed header.
  • Maintain scroll-snap-align: start and vertical snapping.
  • Verify heading's top edge is at or below header's bottom edge.

Part 29: Agent cards in practice

Part 29 · One Agent, Five Platforms An agent card is a CV for an agent. It tells other agents who it is, what it can do, where to reach it and how to prove who's calling.

  • Agent card contains agent's name, description, version and capabilities.
  • Invoice exception agent is read-only, uses Entra agent identity for authentication.
  • Supplier-communication agent drafts reply skill, but doesn't send emails.

More from Wednesday 18 November →