Safari 27.0 ships with a Model Cooperation Protocol (MCP) server that lets coding agents like Claude control your browser to test code, plus major improvements to form controls and 3D model support. The real story is 844 quality fixes addressing compatibility, standards alignment, and feature interactions that were previously broken.

• Safari MCP lets AI coding agents see how your code renders in real-time, check accessibility issues, and test across browsers without you manually sharing screenshots or jumping between windows
• The customizable `<select>` element now supports full CSS styling and custom HTML content inside options, with improved default styles that don't require extra work to make usable
• The release includes 844 bug fixes (up from 525 announced at WWDC), with deep work on SVG (66 fixes), HTML tables, CSS Zoom rebuild, and fixes for feature interactions like `-webkit-line-clamp` combined with `text-wrap: balance`

A study compared usability feedback from participants with self-identified cognitive disabilities against general population testers across three AI-generated websites. Cognitive participants uncovered 1.8× more issues and made 1.8× more suggestions, with distinct patterns in content, icons, and visual elements and varied usability scores.

• Testers who self-identify as having cognitive disabilities surfaced 1.8x more usability issues (197 vs 113) and suggestions (93 vs 54) than general-population testers across three test sites.
• On Strong Snacks, cognitive participants found more issues on average (9.8 vs 6.4) and scored the site 13.7 points lower on the 0–100 Accessible Usability Scale.
• More complex sites like Turning Pages amplified the gap, producing even higher problem counts and lower satisfaction from cognitive testers.
• Screening specifically for cognitive disabilities in UX research reveals significantly more design flaws than standard testing pools catch.

This edition breaks down Audi’s Nuvolari supercar and Apple’s WWDC reveals, including Liquid Glass refinements and new AI photo-editing tools. It also covers shifting UX trends, WCAG compliance levels, the rise of digital design skills, plus fresh resources from Hooksy, Boneyard, Glaze, and more.

• Audi's Nuvolari supercar: 4L twin-turbo V8 + 3 electric motors, ~1,000 hp, only 499 units, $650,000+ each
• Apple's iOS 27 Photos app adds AI tools (Cleanup, Extend, Reframe) via Apple Intelligence, launching later this year
• Siri's AI-powered app overhaul, delayed for years, now slated for September
• AI reshapes design workflows but doesn't replace core UX/product/dev roles—collaboration skills remain the key differentiator for employers

This edition covers Amazon’s new AI-powered merch creator, Meta’s Edits app getting an AI assistant and desktop build, and iOS 27’s redesigned AirPods settings interface. It also dives into UX research with cognitive inclusion, tips for AI-ready design systems, timeless design principles from Dieter Rams, human-centered connection over perfection, a semiconductor-industry rebrand, and how designers earn strategic influence.

• Amazon now generates custom merch (hoodies, tumblers, etc.) from AI text prompts via Alexa, printing and shipping it directly—undercutting Redbubble and Bonfire.
• Fable's research found users with cognitive disabilities caught 1.8x more usability issues and gave 2x more suggestions on AI-generated sites than general testers, surfacing problems like mental load that others missed.
• iOS 27 redesigns AirPods settings with icon-driven menus instead of long lists, cutting taps needed for navigation.
• Meta's Edits app is adding an AI assistant that uses Instagram performance data to suggest clips, audio, and posting times, plus a desktop version and A/B testing for reels.

Safari 27’s customizable select lets you fully style <select> controls without JavaScript, but you must include text or accessible labels for each option. Skipping text breaks keyboard navigation, screen readers, and fallbacks in unsupported browsers—icons or swatches must supplement, not replace, option text.

• Safari 27's customizable select allows full CSS styling of dropdowns while keeping native keyboard/accessibility behavior, but only if every option retains real text or an aria-label.
• Icon-only options (e.g., a hummingbird icon with no label) leave screen readers silent and sighted users guessing, since nothing conveys which option is selected or what it means.
• If CSS fails or a browser lacks support, the control falls back to a default select—so text-less options degrade into a list of blank entries.
• Best practice: wrap custom styles in @supports(appearance: base-select), design with plain text as the foundation, and add icons/swatches as supplements—visually hidden if needed—never as replacements for text.

A contractor rebuilt a utility company’s user sign-up flow with an HTML-first, Astro-based form that works without JavaScript, stores each step server-side, and meets WCAG AA. By using simple form submissions, progressive enhancement, and a tiny web component for validation, form completions doubled overnight and users never lost their data.

• An HTML-first, server-rendered Astro rebuild (each wizard step a real page, plain form POSTs) doubled form completions overnight after a React version with spinners and localStorage-based image storage failed and was rolled back in three days.
• The "missing" users were real all along—JS-based analytics tools had been silently dropping people whose browsers/connections choked on the old JS bundles.
• A 1KB web component (validation-enhancer) added accessible, non-intrusive validation on top of native HTML form validation without sacrificing progressive enhancement or WCAG AA compliance.
• Storing each step's data server-side meant users never lost progress, even resuming an application a month later.

Google has published the draft specification for DESIGN.md, letting Stitch export and import design rules across projects. This shared format lets AI agents identify color roles and check choices against WCAG accessibility standards.

• Google open-sourced the draft DESIGN.md spec, so any tool/platform can read design rules directly instead of AI guessing intent from context.
• The format encodes semantic meaning behind values (e.g. #0057FF = "primary button," not just "blue"), letting agents apply brand rules automatically across projects.
• It runs built-in WCAG contrast/accessibility checks, catching violations before they ship.
• David East's demo shows generating DESIGN.md files from scratch, editing them, and re-importing into Stitch to cut down on manual style-guide rework.

A Lobste.rs thread where developers share untested ideas—from building GUI toolkits with an accessibility-first architecture to enable better testing and scripting, to using 32-bit pointers on 64-bit systems for memory savings, and applying property-based approaches to infrastructure. Contributors discuss tools like AccessKit, the x32 ABI, and the benefits of driving design by fundamental properties rather than legacy constraints.

• Building GUI toolkits with accessibility as the core data model (not bolted on) enables pixel-free testing, automation via high-level actions, and multiple "themes" (graphical, voice, terminal, remote) on one semantic backbone—AccessKit already does much of this for Rust/Egui.
• Reviving x32 ABI (32-bit pointers on 64-bit hardware) cut Mastodon's RAM use from 650MB to 350MB by shrinking pointers and improving cache density, though Debian disables it by default and most distros don't ship it.
• V8 and other JIT engines already use pointer compression for sandboxing, suggesting broader adoption of narrow pointers could yield wider resource savings.