September was the month the tools stopped asking whether agents should touch our design systems and started handing them write access. Figma, Supernova, Framer and Anthropic all shipped ways for agents to read, edit or reuse system-level decisions. Meanwhile the accessibility baseline in Europe quietly moved up. Here’s what I think is worth your time if you work on design systems, enterprise products or accessibility.
Must-read
The Custodial Era of UX: Cleaning Up After AI (NN/G) (Aug 28) The best description I’ve read of what a lot of us are living through: “production has become cheaper than UX evaluation,” so designers get pulled in to clean up after the fact. The useful part is the fix. Triage before you polish, speed up evaluation, and put UX guidance (design system, accessibility requirements, deceptive patterns to avoid) into the generation step so the same mess doesn’t keep coming back.
When Should You Disclose AI Use? The PACED Framework (NN/G) (Sep 25) The EU AI Act’s transparency obligations started in August 2026, so this is now a product question as much as an ethics one. PACED (policy, audience, context, expectations, degree of AI use) is a solid checklist for deciding where AI disclosures go in your UI. The research summary is worth reading too: getting exposed by a third party hurts trust more than disclosing up front.
How to Make Your Design System AI-Ready (DesignWhine) (Sep 4) A long, practical guide that gets the order right: audit first, then semantics, explicit states, tokens, Code Connect, and only then MCP and agent rules. The line I’ll be quoting in reviews: “MCP is an access layer… it cannot decide which version of your system deserves to be trusted.” The 10-point readiness score at the end is a ready-made workshop exercise.
Tools
Figma: generative plugins & shaders get code, publishing and MCP (Sep 1) + Motion animation styles & Lottie export (Sep 30)
Agent-made shaders and plugins can now be published privately to your org, their code can be viewed and downloaded, and they’re reachable through the Figma MCP server (shaders carry through into generated React). Motion now has reusable, variable-backed animation styles you can publish to libraries, and agents can apply them via MCP or Skills. For design-system teams that means motion is finally a system decision, not a per-file habit. Keep an eye on prefers-reduced-motion as you scale it.
Supernova Editor MCP (Aug 26, public beta) It gives write access to docs, tokens and components from Cursor, Claude, VS Code, Codex or ChatGPT. Supernova’s own framing nails it: “Without write, agents are well-informed spectators.” I’d start with the boring stuff, like finding pages that are missing states or usage guidance and catching Figma variants that have drifted from coded props, and keep humans approving anything that renames or deprecates.
Framer Skills (Sep 22) Skills are reusable instructions that point Framer’s agent at your components and explain how they fit together. It’s the same idea as DESIGN.md and Figma Skills: a sticker sheet shows the parts, and a skill explains the rules for combining them. If you maintain a system, writing these “how to compose” rules is now real work, not optional documentation.
accessFlow Code Agent (accessiBe) (Sep 17, beta) It reviews GitHub pull requests against WCAG 2.2 AA, flags the exact line and suggests an inline fix, and you can make it a required check before merge. Moving checks into the PR rather than patching at runtime is the right direction. Just remember that automated checks only cover part of WCAG.
News
Claude Design, Slides and Docs now work in any Claude conversation, including Claude Code (Sep 16)
You can ask for a mockup straight from a repo session, and /design-sync pulls in an existing design system (details). The design surface now sits where engineers already work. That’s great for speed, and it’s exactly why your design system has to be the context these tools read from, not an afterthought.
Elyx, a new design tool from Sketch’s co-founders (announced mid-September, private beta)
It’s built around a human-readable .elyx format that lives in Git next to the code, with a native editor plus a CLI and agent skills. It’s too early to judge the editor, but “design files as versionable text that agents can diff” is the most interesting bet in tooling this year. It’s also the one that challenges Figma most directly.
EN 301 549 v4.1.1 published (AccessibleEU) (Sep 7) The European standard now uses WCAG 2.2 as its benchmark, drops 4.1.1 Parsing, and adds an annex mapping requirements to the EAA. It isn’t the legal presumption standard until it’s cited in the Official Journal (v3.2.1 / WCAG 2.1 still applies), but if you ship B2B software into the EU, update your audit checklists and procurement templates now.
WCAG 3 Working Draft, September 2026 (W3C) (Sep 10) A new draft with open review questions on the conformance model. It’s not something to comply with yet, and WCAG 2.x is still the baseline. Still, if you own an accessibility program, now is the time to read it and send feedback while the structure is still being shaped.
Worth watching
A11yLTLNav: Automatic Detection of Accessibility Navigation Failures (arXiv) (Sep 16) Most checkers look at a static snapshot. This one explores pages by keyboard and checks focus, state and feedback over time. The authors report 274 confirmed failures across 31 generated websites at 88.7% precision. It’s research, not a product, but it’s the kind of check AI-generated UI badly needs, because the hard accessibility bugs happen during interaction.
That’s September. Build the context before you add agents, and keep a human in charge of what “good” means.