{
  "id": 20537251,
  "title": "I Ran Modern Web Guidance on a Vibe-Coded Landing Page. The Scanner Missed the Worst Parts.",
  "url": "https://urgent.news/2026/11/18/i-ran-modern-web-guidance-on-a-vibe-coded-landing-page-the-scanner",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-11-18T03:10:34.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/polydraft/i-ran-modern-web-guidance-on-a-vibe-coded-landing-page-the-scanner-missed-the-worst-parts-5f7c"
  },
  "original_language": "en",
  "account": "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:\n\n1. The password input field on the sign-up form lacked the autocomplete attribute. Fix: `autocomplete= \"new-password\"`.\n2. 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.\n3. 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.\n4. The navigation menu highlighted the current section using a scroll listener. Fix: implement scrollspy or a navbar solution.\n5. 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.\n6. 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.\n\nHowever, the reporter noted that the scanner did not catch several critical issues that could negatively impact user experience. These issues include:\n\n1. A div-based modal that traps keyboard and screen-reader users.\n2. Unsanitized HTML, creating an XSS vulnerability if the testimonial is wired to a CMS.\n3. The email field lacking proper mobile keyboard and autofill functionality.\n\nThe 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.",
  "summary": "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…",
  "key_points": [
    "Modern Web Guidance 1.0 released by Chrome, Edge, Firefox, and MDN.",
    "Scanner identifies 6 issues in vibe-coded landing page, but misses 4 critical UX problems.",
    "Guidance covers deterministic issues, not all potential web development problems."
  ],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}