Content Quality: News article (869 words, 140-character title) whose focus is WebKit's developer guidance for Safari on Apple HomeView; the press and Apple sections are subordinate and stay tied to the same recipe, Safari and display topics, so it does not drift into a product review. The lead gives WebKit's bottom line and attribution first, then a section per topic in the post (recipes, captions and input, user agent, screen shape).
Source Verification: Read all 7 snapshots in sources/2026-11/webkit-says-safari-on-apple-homeview-most-likely-needs-no-site-changes-but-points-to-recipe-json-ld-an-ios-user-agent-and-a-short-viewport/ (source-0..6.html.gz, all HTTP 200, no archive fallback, suspicious_patterns null for all seven; no prompt-injection text found). Re-fetched the WebKit post live with a browser User-Agent: the raw HTML hash (141b2a124b82c0ec...) equals the snapshot's. source-0 webkit.org/blog/18608: the page is on WebKit's own blog, byline 'by Jen Simmons', dated 'Nov 13, 2026'. Every quoted WebKit string was checked verbatim on that page: 'also lives on Apple HomeView, joining Safari on macOS, iOS, iPadOS, and visionOS'; 'Most likely, you don’t need to do anything. This is Safari, powered by WebKit.'; 'recognizes when users are on a webpage with a recipe, and offers a streamlined view of step-by-step instructions'; 'creates this view from recipe data in the schema.org recipe type in JSON-LD'; 'a key part of how people use the device'; 'real buttons, links, and form fields, and a clear label on every control'; 'Safari on HomeView also reports an iOS user agent'; 'can result in unintended consequences as technology evolves'; 'might not make sense on HomeView, and you can rely on Safari to figure that out'; 'the square, 7-inch display'; 'and never square'; 'the viewport is always taller than 600px, while on HomeView it’s shorter'; 'might leave almost no room for the main content'; 'might leave users with no way to dismiss them'; the CSS fix max-height: 90svh; overflow-y: auto; and the 448×364 Responsive Design Mode viewport. Headline test: 'Most Likely Needs No Site Changes' keeps WebKit's hedge ('Most likely, you don’t need to do anything', and again 'Most likely, your website already works great'); the post then says 'there might be a few things you can do', so 'but Points to ...' is accurate. The three items in the headline (recipe JSON-LD, iOS user agent, short viewport) are three of the post's items, not its complete list: the post also covers WebVTT captions in track elements, voice input with semantic HTML, a square screen and Smart App Banners. The headline does not claim completeness ('Points to'), the Overview says 'among them', and the body covers every item, so the headline does not mislead; no correction filed. 'Short viewport' matches the post ('on HomeView it’s shorter' than 600px; the 600px figure is the sites' assumed threshold, and the post's test viewport is 448×364, 364 being below 600). source-1 MacRumors (Joe Rossignol, Fri Nov 13 2026 8:21 am PST): 'launched today' and 'lets you browse the web and includes a new Cooking experience that auto-detects supported recipes, reformatting them with step-by-step instructions and inline timers' verbatim; the piece relays Apple's HomeView 27.2 release notes from an Apple support document, as the article says, so it is Apple's wording, not independent testing. source-2 MacRumors tidbits (Juli Clover, Nov 13 2026): 'Safari can be turned on or off, or adult websites can be blocked' under Guest Controls, 'The HomeView owner has multiple options for what guests can access'; this is MacRumors' own roundup. source-3 9to5Mac (Chance Miller, Nov 12 2026 6:00 am PT): 'ten days living with HomeView in my kitchen'; quotes 'gives you the option to convert it into a dedicated cooking interface', 'with recipes of varying lengths from multiple different websites without any major problems' and 'it does struggle if a website splits the recipe into multiple pages' verbatim; the hold-the-iPhone handoff is described; the review gives 1088 × 1088 at 220 ppi; no mention of schema.org, JSON-LD or WebKit. source-4 apple.com/apple-homeview: 'When you find a recipe in Safari, just tap the Start Cooking button to view a streamlined format that’s easy to follow.' verbatim; footnote says 'HomeView software version 27.2'. source-5 apple.com specs: '1088-by-1088-pixel resolution at 220 ppi' verbatim for the 7-inch display. source-6 MDN: 'Feature detection is where you check to see if a specific feature is available to the client instead of figuring out which browser is rendering your page' (the article's quote is a verbatim part of this sentence); MDN is cited only as background for feature detection, as the article uses it. Independence: WebKit (Apple-affiliated project) and the two apple.com pages are first-party; MacRumors release-notes piece relays Apple; independent reporting is 9to5Mac and MacRumors' own tidbits (two outlets). Neither outlet cites WebKit's post (grep for 'webkit' across source-1..5: 0 hits), which the article states only as 'in the pages cited'. Anthropic disclosure: not required - the story is WebKit/Apple's HomeView; no source mentions Anthropic, Claude or Bun (grep 0 hits in all seven snapshots).
Factual Accuracy: Claim-accuracy tests run. Quantifier/absence sentences, each checked against every snapshot by grep: 'None of the cited sources gives the Safari or WebKit version running on HomeView' holds (no Safari/WebKit version for HomeView in source-0..5; MDN's Safari versions are generic UA examples); 'refer to HomeView software version 27.2' holds for apple.com/apple-homeview and the MacRumors release-notes piece; 'None ... says what Safari's cooking experience does with a recipe page that lacks the schema.org markup' holds (WebKit says to add the markup, 9to5Mac says HomeView 'intelligently detects the actual recipe information' without saying how, MacRumors/Apple say 'supported recipes' undefined); 'WebKit's post gives no example user-agent string' holds; 'does not mention schema.org or JSON-LD' (9to5Mac) holds; 'WebKit's post does not mention multi-page recipes' holds; 'Neither MacRumors nor 9to5Mac ... refers to WebKit's post' holds. Numbers: 1088 by 1088 at 220 ppi is Apple's figure (labelled as from Apple's specifications page) and 9to5Mac repeats '1088 × 1088 ... 220 pixels per inch'; 448×364 is WebKit's test viewport; the article states these are different measures and that no cited source relates them, and it does not infer a relationship. Dates: WebKit post Nov 13; MacRumors Nov 13; 9to5Mac Nov 12, all as stated. The sample-markup field list matches the post's JSON-LD. Apple/MacRumors wording is correctly labelled as Apple's, relayed. Internal link /article/2026-10/24-webkit-says-safari-271-on-iphone-duo-previews-device-posture-and-viewport-segments-apis-behind-feature-flags exists; the article is a Briefing on WebKit's Safari 27.1 post of October 23, 2026 about iPhone Duo, as described, and has no corrections record. No errors found.
Overall Assessment: Accurate, well-sourced developer-guidance News article; headline, summary and lead are each backed by the WebKit post, every quoted string checked is verbatim, absence claims are scoped to the cited sources and survive grep, and no correction is needed. Featured candidacy: 1 - solid, accurate coverage of new-platform guidance for a defined audience of web developers