<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"><channel><title>The Website Specification — Changelog</title><description>New topics, status changes, and removals in The Website Specification, newest first.</description><link>https://specification.website</link><language>en-GB</language><atom:link href="https://specification.website/changelog/rss.xml" rel="self" type="application/rss+xml"/><lastBuildDate>Thu, 18 Jun 2026 00:00:00 GMT</lastBuildDate><sy:updatePeriod>weekly</sy:updatePeriod><sy:updateFrequency>1</sy:updateFrequency><item><title>Redundant entry (WCAG 2.2 SC 3.3.7)</title><link>https://specification.website/changelog/#2026-06-18-redundant-entry</link><guid isPermaLink="true">https://specification.website/changelog/#2026-06-18-redundant-entry</guid><description>Added a page on redundant entry, WCAG 2.2 Success Criterion 3.3.7 (Level A): information a user already entered earlier in the same process must be auto-populated or selectable, not typed again. It covers the essential, security, and expired exceptions and the carry-forward and autocomplete patterns that satisfy it.</description><pubDate>Thu, 18 Jun 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;Added a page on &lt;a href=&quot;https://specification.website/spec/accessibility/redundant-entry/&quot;&gt;redundant entry&lt;/a&gt;, WCAG 2.2 Success Criterion 3.3.7 (Level A): information a user already entered earlier in the same process must be auto-populated or selectable, not typed again. It covers the essential, security, and expired exceptions and the carry-forward and &lt;code&gt;autocomplete&lt;/code&gt; patterns that satisfy it.&lt;/p&gt;</content:encoded><category>added</category></item><item><title>New page on the Server-Timing header</title><link>https://specification.website/changelog/#2026-06-18-server-timing</link><guid isPermaLink="true">https://specification.website/changelog/#2026-06-18-server-timing</guid><description>Added a page on the Server-Timing header, which surfaces backend metrics — database time, cache hits, edge processing — in browser DevTools and to real-user monitoring via the PerformanceServerTiming API. The site now ships it as a worked example: every response carries an edge timing metric measured in the Cloudflare Pages middleware.</description><pubDate>Thu, 18 Jun 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;Added a page on &lt;a href=&quot;https://specification.website/spec/performance/server-timing/&quot;&gt;the &lt;code&gt;Server-Timing&lt;/code&gt; header&lt;/a&gt;, which surfaces backend metrics — database time, cache hits, edge processing — in browser DevTools and to real-user monitoring via the &lt;code&gt;PerformanceServerTiming&lt;/code&gt; API. The site now ships it as a worked example: every response carries an &lt;code&gt;edge&lt;/code&gt; timing metric measured in the Cloudflare Pages middleware.&lt;/p&gt;</content:encoded><category>added</category></item><item><title>New page on the translate attribute</title><link>https://specification.website/changelog/#2026-06-18-translate-attribute</link><guid isPermaLink="true">https://specification.website/changelog/#2026-06-18-translate-attribute</guid><description>Added a page on the translate attribute, which marks content that automatic translation systems must leave alone — brand names, code, and identifiers. It complements the lang attribute: lang declares what language content is in, while translate=&quot;no&quot; keeps Google Translate and the browser’s built-in translation from mangling terms that have no localised form.</description><pubDate>Thu, 18 Jun 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;Added a page on &lt;a href=&quot;https://specification.website/spec/i18n/translate-attribute/&quot;&gt;the &lt;code&gt;translate&lt;/code&gt; attribute&lt;/a&gt;, which marks content that automatic translation systems must leave alone — brand names, code, and identifiers. It complements &lt;a href=&quot;https://specification.website/spec/i18n/lang-attribute/&quot;&gt;the &lt;code&gt;lang&lt;/code&gt; attribute&lt;/a&gt;: &lt;code&gt;lang&lt;/code&gt; declares what language content is in, while &lt;code&gt;translate=&quot;no&quot;&lt;/code&gt; keeps Google Translate and the browser’s built-in translation from mangling terms that have no localised form.&lt;/p&gt;</content:encoded><category>added</category></item><item><title>Added a page on accessible authentication</title><link>https://specification.website/changelog/#2026-06-17-accessible-authentication</link><guid isPermaLink="true">https://specification.website/changelog/#2026-06-17-accessible-authentication</guid><description>New Accessibility topic on accessible authentication — WCAG 2.2 added success criteria 3.3.8 and 3.3.9, which forbid making people pass a cognitive function test (recalling a password, transcribing a code, solving a puzzle) to log in unless an accessible alternative exists. The page covers supporting password managers, allowing paste, autocomplete=&quot;one-time-code&quot;, and passkeys; status: recommended.</description><pubDate>Wed, 17 Jun 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;New &lt;strong&gt;Accessibility&lt;/strong&gt; topic on &lt;a href=&quot;https://specification.website/spec/accessibility/accessible-authentication/&quot;&gt;accessible authentication&lt;/a&gt; — WCAG 2.2 added success criteria 3.3.8 and 3.3.9, which forbid making people pass a cognitive function test (recalling a password, transcribing a code, solving a puzzle) to log in unless an accessible alternative exists. The page covers supporting password managers, allowing paste, &lt;code&gt;autocomplete=&quot;one-time-code&quot;&lt;/code&gt;, and passkeys; status: recommended.&lt;/p&gt;</content:encoded><category>added</category></item><item><title>MDN&apos;s MCP server cited on the MCP page</title><link>https://specification.website/changelog/#2026-06-17-mdn-mcp-reference</link><guid isPermaLink="true">https://specification.website/changelog/#2026-06-17-mdn-mcp-reference</guid><description>The MCP and tool discovery page now points to MDN’s 2026 MCP server as a real-world example of a reference site exposing its documentation and Baseline browser-compatibility data over the protocol — reinforcing that a structured, queryable corpus is the case where shipping an MCP server earns its keep.</description><pubDate>Wed, 17 Jun 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;The &lt;a href=&quot;https://specification.website/spec/agent-readiness/mcp-and-tool-discovery/&quot;&gt;MCP and tool discovery&lt;/a&gt; page now points to MDN’s 2026 MCP server as a real-world example of a reference site exposing its documentation and Baseline browser-compatibility data over the protocol — reinforcing that a structured, queryable corpus is the case where shipping an MCP server earns its keep.&lt;/p&gt;</content:encoded><category>changed</category></item><item><title>Added a page on the Reporting API (Reporting-Endpoints)</title><link>https://specification.website/changelog/#2026-06-16-reporting-api</link><guid isPermaLink="true">https://specification.website/changelog/#2026-06-16-reporting-api</guid><description>New Security topic on the Reporting API — the Reporting-Endpoints response header that names collectors for the browser’s structured reports: CSP and COOP violations, permissions-policy breaches, deprecations, interventions, and crashes. It supersedes the legacy Report-To header and report-uri directive. The site now ships the header and a collector, closing a ship-it-before-you-spec-it gap; status: recommended.</description><pubDate>Tue, 16 Jun 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;New &lt;strong&gt;Security&lt;/strong&gt; topic on the &lt;a href=&quot;https://specification.website/spec/security/reporting-endpoints/&quot;&gt;Reporting API&lt;/a&gt; — the &lt;code&gt;Reporting-Endpoints&lt;/code&gt; response header that names collectors for the browser’s structured reports: CSP and COOP violations, permissions-policy breaches, deprecations, interventions, and crashes. It supersedes the legacy &lt;code&gt;Report-To&lt;/code&gt; header and &lt;code&gt;report-uri&lt;/code&gt; directive. The site now ships the header and a collector, closing a ship-it-before-you-spec-it gap; status: recommended.&lt;/p&gt;</content:encoded><category>added</category></item><item><title>Added a page on cross-origin isolation (COOP / COEP / CORP)</title><link>https://specification.website/changelog/#2026-06-11-cross-origin-isolation</link><guid isPermaLink="true">https://specification.website/changelog/#2026-06-11-cross-origin-isolation</guid><description>New Security topic on cross-origin isolation — the Cross-Origin-Opener-Policy, Cross-Origin-Embedder-Policy, and Cross-Origin-Resource-Policy response headers that sever risky cross-window links (tabnabbing, XS-Leaks) and keep your resources out of an attacker’s process (Spectre). The site already ships COOP and CORP on every response, so this closes a ship-it-before-you-spec-it gap; status: recommended.</description><pubDate>Thu, 11 Jun 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;New &lt;strong&gt;Security&lt;/strong&gt; topic on &lt;a href=&quot;https://specification.website/spec/security/cross-origin-isolation/&quot;&gt;cross-origin isolation&lt;/a&gt; — the &lt;code&gt;Cross-Origin-Opener-Policy&lt;/code&gt;, &lt;code&gt;Cross-Origin-Embedder-Policy&lt;/code&gt;, and &lt;code&gt;Cross-Origin-Resource-Policy&lt;/code&gt; response headers that sever risky cross-window links (tabnabbing, XS-Leaks) and keep your resources out of an attacker’s process (Spectre). The site already ships COOP and CORP on every response, so this closes a ship-it-before-you-spec-it gap; status: recommended.&lt;/p&gt;</content:encoded><category>added</category></item><item><title>Added a page on Compression Dictionary Transport</title><link>https://specification.website/changelog/#2026-06-10-compression-dictionary-transport</link><guid isPermaLink="true">https://specification.website/changelog/#2026-06-10-compression-dictionary-transport</guid><description>New Performance topic on Compression Dictionary Transport (RFC 9842) — reusing a previously served response, or a dedicated dictionary, as a Brotli/Zstandard dictionary so updated assets compress to a fraction of their size. Pure progressive enhancement over ordinary compression; status: optional.</description><pubDate>Wed, 10 Jun 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;New &lt;strong&gt;Performance&lt;/strong&gt; topic on &lt;a href=&quot;https://specification.website/spec/performance/compression-dictionary-transport/&quot;&gt;Compression Dictionary Transport&lt;/a&gt; (RFC 9842) — reusing a previously served response, or a dedicated dictionary, as a Brotli/Zstandard dictionary so updated assets compress to a fraction of their size. Pure progressive enhancement over ordinary compression; status: optional.&lt;/p&gt;</content:encoded><category>added</category></item><item><title>FAQ rich results retired by Google</title><link>https://specification.website/changelog/#2026-06-10-faq-rich-results-retired</link><guid isPermaLink="true">https://specification.website/changelog/#2026-06-10-faq-rich-results-retired</guid><description>Updated Structured data to reflect that Google retired the FAQ rich result in 2026. FAQPage is still valid schema.org vocabulary, but it no longer produces a search feature and no answer engine has confirmed it favours the markup over rendered HTML — so add it only for genuine, visible Q-and-A content, never for SERP or “GEO” gain.</description><pubDate>Wed, 10 Jun 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;Updated &lt;a href=&quot;https://specification.website/spec/seo/structured-data/&quot;&gt;Structured data&lt;/a&gt; to reflect that Google retired the FAQ rich result in 2026. &lt;code&gt;FAQPage&lt;/code&gt; is still valid schema.org vocabulary, but it no longer produces a search feature and no answer engine has confirmed it favours the markup over rendered HTML — so add it only for genuine, visible Q-and-A content, never for SERP or “GEO” gain.&lt;/p&gt;</content:encoded><category>changed</category></item><item><title>Added a page on conditional requests</title><link>https://specification.website/changelog/#2026-06-09-conditional-requests</link><guid isPermaLink="true">https://specification.website/changelog/#2026-06-09-conditional-requests</guid><description>New Performance topic on conditional requests — how ETag, Last-Modified and 304 Not Modified responses let browsers and agents revalidate cached responses cheaply instead of re-downloading unchanged bodies. Status: recommended.</description><pubDate>Tue, 09 Jun 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;New &lt;strong&gt;Performance&lt;/strong&gt; topic on &lt;a href=&quot;https://specification.website/spec/performance/conditional-requests/&quot;&gt;conditional requests&lt;/a&gt; — how &lt;code&gt;ETag&lt;/code&gt;, &lt;code&gt;Last-Modified&lt;/code&gt; and &lt;code&gt;304 Not Modified&lt;/code&gt; responses let browsers and agents revalidate cached responses cheaply instead of re-downloading unchanged bodies. Status: recommended.&lt;/p&gt;</content:encoded><category>added</category></item><item><title>Six new topics across six categories</title><link>https://specification.website/changelog/#2026-06-08-new-topics</link><guid isPermaLink="true">https://specification.website/changelog/#2026-06-08-new-topics</guid><description>A batch of new pages landed: Mobile-friendly form inputs, dynamic viewport units, graceful degradation when JavaScript fails, mixed content and upgrade-insecure-requests, server-side rendering, and /.well-known/webauthn for Related Origin Requests.</description><pubDate>Mon, 08 Jun 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;A batch of new pages landed: &lt;a href=&quot;https://specification.website/spec/accessibility/mobile-form-inputs/&quot;&gt;Mobile-friendly form inputs&lt;/a&gt;, &lt;a href=&quot;https://specification.website/spec/performance/dynamic-viewport-units/&quot;&gt;dynamic viewport units&lt;/a&gt;, &lt;a href=&quot;https://specification.website/spec/resilience/graceful-degradation/&quot;&gt;graceful degradation when JavaScript fails&lt;/a&gt;, &lt;a href=&quot;https://specification.website/spec/security/mixed-content/&quot;&gt;mixed content and &lt;code&gt;upgrade-insecure-requests&lt;/code&gt;&lt;/a&gt;, &lt;a href=&quot;https://specification.website/spec/seo/server-side-rendering/&quot;&gt;server-side rendering&lt;/a&gt;, and &lt;a href=&quot;https://specification.website/spec/well-known/webauthn/&quot;&gt;&lt;code&gt;/.well-known/webauthn&lt;/code&gt;&lt;/a&gt; for Related Origin Requests.&lt;/p&gt;</content:encoded><category>added</category></item><item><title>The Website Specification, v0.1</title><link>https://specification.website/changelog/#2026-05-29-launch</link><guid isPermaLink="true">https://specification.website/changelog/#2026-05-29-launch</guid><description>First public version: a platform-agnostic specification of what a good website does, spanning Foundations, SEO, Accessibility, Security, Well-Known URIs, Agent Readiness, Performance, Privacy, Resilience and Internationalisation. Every topic is tagged required, recommended, optional or avoid, and cited from primary sources. Available as HTML, Markdown, a checklist, llms.txt, RSS, and an MCP server.</description><pubDate>Fri, 29 May 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;First public version: a platform-agnostic specification of what a good website does, spanning Foundations, SEO, Accessibility, Security, Well-Known URIs, Agent Readiness, Performance, Privacy, Resilience and Internationalisation. Every topic is tagged required, recommended, optional or avoid, and cited from primary sources. Available as HTML, Markdown, a &lt;a href=&quot;https://specification.website/checklist/&quot;&gt;checklist&lt;/a&gt;, &lt;code&gt;llms.txt&lt;/code&gt;, RSS, and an &lt;a href=&quot;https://specification.website/mcp/&quot;&gt;MCP server&lt;/a&gt;.&lt;/p&gt;</content:encoded><category>added</category></item></channel></rss>