[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ASKV5S2D6VVHCJ9WAF91XS":3,"skill-same:01M7ASKV5S2D6VVHCJ9WAF91XS":48},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7ASKV5S2D6VVHCJ9WAF91XS","ui-ux-reference",null,"Use when reviewing an interface for known anti-patterns, weighing contested questions (minimalism vs signifiers, expressive vs neutral design, consistency vs platform nativeness, APCA vs WCAG 2 contrast, chat vs GUI for AI features, hamburger menus, disabled submit buttons, A\u002FB testing vs qualitative research, design-system centralization, whether UX = UI still holds), checking whether a platform or regulatory claim is still current (snapshot verified August 2026), finding the books, primary sources, and ongoing sources, or needing the numbers, design review checklist, and 'this feels wrong but I can't say why' diagnosis. Companion to the other ui-ux-design-principles skills.","the-vibey-project\u002Fvibey","the-vibey-project","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F329298758?v=4","01M7AJHGZ9722CTJ4JNQZVRH0Q","the vibey project","01M7AJHGZVMG2K7TGXQ6XFHVG3",5,"MIT","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fui-ux-design-principles\u002Fskills\u002Fui-ux-reference\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: ui-ux-reference\ndescription: \"Use when reviewing an interface for known anti-patterns, weighing contested questions (minimalism vs signifiers, expressive vs neutral design, consistency vs platform nativeness, APCA vs WCAG 2 contrast, chat vs GUI for AI features, hamburger menus, disabled submit buttons, A\u002FB testing vs qualitative research, design-system centralization, whether UX = UI still holds), checking whether a platform or regulatory claim is still current (snapshot verified August 2026), finding the books, primary sources, and ongoing sources, or needing the numbers, design review checklist, and 'this feels wrong but I can't say why' diagnosis. Companion to the other ui-ux-design-principles skills.\"\n---\n\n# UI\u002FUX Design: Anti-Patterns, Contested Questions, Currency, and Canon\n\n> **Part 5 of 5** of the *UI\u002FUX Design Principles — Mobile, Tablet, Web, Desktop* reference (plugin `ui-ux-design-principles`), covering §15–§20. Sibling skills: `ui-ux-cognition-heuristics-and-navigation` (§0–§3), `ui-ux-interaction-layout-and-visual-design` (§4–§6), `ui-ux-design-systems-platforms-and-accessibility` (§7–§9), `ui-ux-writing-forms-research-and-ethics` (§10–§14). Section numbers are shared across the set; a reference written as §N → `skill` points into that sibling skill.\n>\n> **Currency:** Verified August 2026. See §17 below for the currency snapshot and what goes stale first.\n>\n> **Related:** Overlaps the `frontend-design:graphic-ux-ui-design` skill. That one is oriented to implementation-time component and token decisions; this one is oriented to design reasoning, cross-form-factor principles, research method, and the regulatory landscape. Use both.\n\n> **How to read this.** Reference, not tutorial. Sections are independent. Three markers:\n> - **[DURABLE]** — grounded in perception, cognition, motor control, or decades of\n>   replicated research. Does not expire. Trust it.\n> - **[PLATFORM]** — a convention of Apple, Google, Microsoft, GNOME\u002FKDE, or the web.\n>   Verify against the current HIG; these change.\n> - **[CONTESTED]** — competent practitioners disagree, or the evidence is thinner than the\n>   confidence with which it's usually asserted. Both cases given.\n>\n> **⚠️ GOTCHA** boxes mark the mistakes that survive design review and get caught in\n> production, in court, or in the analytics.\n>\n> **The framing that organizes everything below:** an interface is a *proposal about how\n> a person should think*. Good design makes the proposal match how they already think.\n> Every principle in this document is a specialization of that idea — to a thumb, a\n> screen size, a screen reader, a legal regime, or an attention budget.\n\n---\n\n## §15. Anti-Patterns\n\n| Anti-pattern | Why it fails | Do instead |\n|---|---|---|\n| Placeholder text as the label | Disappears on focus, fails contrast, breaks autofill and translation, invisible to some AT | Persistent label above the field |\n| Two primary buttons | Von Restorff: two emphases = none | One primary, rest secondary\u002Ftertiary |\n| Icon-only controls without labels | Icons aren't universal; tooltips don't exist on touch | Icon + label, or label at minimum |\n| Removing focus outlines | WCAG Level A failure; breaks keyboard use | `:focus-visible` with a designed indicator |\n| Disabling zoom (`user-scalable=no`) | Hostile to low-vision users; WCAG failure | Never do this |\n| Fixed pixel font sizes \u002F ignoring OS text scale | Breaks for everyone over ~45 | Relative units; test at 200% |\n| Color as the only signal | Fails ~8% of men and every grayscale\u002Flow-vision case | Color + icon + text |\n| Confirmation dialogs everywhere | Habituation makes them useless | Undo (§2.3 → `ui-ux-cognition-heuristics-and-navigation`) |\n| Hamburger for primary navigation | Measurably reduces discovery of hidden items | Tab bar for the top 3–5 |\n| Modal for anything non-blocking | Interrupts, traps, and stacks | Inline, sheet, or side panel |\n| Infinite scroll where users need to find and return | Destroys position memory; breaks the footer | Pagination or \"load more\" |\n| Carousels for important content | Very low engagement past slide 1; auto-advance is an a11y failure | Show the content |\n| Auto-playing audio\u002Fvideo | Universally hated; a11y violation | User-initiated |\n| Hijacking scroll, Back, or system gestures | Breaks the trust users place in platform behaviour | Don't |\n| Equal spacing above and below labels | Proximity ambiguity — the classic form bug | Tighter within groups than between |\n| Centered long body text | Ragged left edge slows reading | Left-align |\n| Full-width text on wide screens | Exceeds 75-character measure | max-width or multi-column |\n| Skeleton\u002Fspinner with no context | Doesn't reduce anxiety, just delays it | Say what's loading; show progress |\n| \"Something went wrong\" | Unactionable | What\u002Fwhy\u002Fwhat next (§10.2 → `ui-ux-writing-forms-research-and-ethics`) |\n| Testing only the happy path | Real pain lives in errors and second sessions | Test failure and recovery |\n| Designing only at 1440 px in Figma | Never sees the 375 px reality | Design mobile-first; open the small frame |\n| Hiding content on mobile with `display:none` | Mobile users are not second-class | Reorganize, don't delete |\n| Optimizing engagement metrics alone | Rewards confusion and manipulation | Pair with quality metrics (§12.4 → `ui-ux-writing-forms-research-and-ethics`) |\n| Adding a preference for every disagreement | Pushes design decisions onto users | Choose a good default |\n| Accessibility overlay widget | Doesn't work; no legal protection; opposed by AT users | Fix the underlying markup |\n| Shipping WCAG 2.0 in 2026 | Below every current legal baseline | Build to 2.2 AA (§9.2 → `ui-ux-design-systems-platforms-and-accessibility`) |\n| Quoting \"5 users is enough\" as universal | Misreads the finding (§12.2 → `ui-ux-writing-forms-research-and-ethics`) | 5 per segment per round, 3 rounds |\n| Quoting \"7±2\" as a menu-length rule | Miller said no such thing (§1.2 → `ui-ux-cognition-heuristics-and-navigation`) | Categorize; don't make people recall |\n\n---\n\n## §16. Contested Questions\n\n**16.1 Minimalism vs. signifiers.** Flat\u002Fminimal design demonstrably improved consistency\nand scalability and reduced visual noise; it also removed the cues that tell people what's\nclickable, with a documented cost concentrated in older and less experienced users. Neither\n\"add bevels back\" nor \"clean is always better\" is right. The resolution is *deliberate\nsignification*: keep the aesthetic, but ensure every interactive element is identifiable\nwithout hover, and test that assumption with real users rather than with your team.\n\n**16.2 Expressive vs. neutral design.** Material 3 Expressive's research argues emotional\nexpressiveness and usability are complementary — bolder shapes and bigger primary actions\nmade key elements ~4× faster to spot and closed the usability age gap. The counterweight:\nthese are vendor studies of vendor components, the mechanism is mostly \"prominence helps\"\n(which we already knew), and expressiveness is genuinely wrong for some contexts — Google's\nown team notes you may not want a playful UI for paying a parking ticket. Direction:\nwell-supported. Specific numbers: don't generalize.\n\n**16.3 Consistency vs. platform nativeness.** §8.5 → `ui-ux-design-systems-platforms-and-accessibility`.\n\n**16.4 APCA vs. WCAG 2 contrast.** §9.3 → `ui-ux-design-systems-platforms-and-accessibility`. This one has legal consequences, so precision\nmatters more than usual.\n\n**16.5 Chat vs. GUI for AI features.** §14.1 → `ui-ux-writing-forms-research-and-ethics`.\n\n**16.6 Hamburger menus.** §3.2 → `ui-ux-cognition-heuristics-and-navigation`.\n\n**16.7 Disabled submit buttons.** §4.6 → `ui-ux-interaction-layout-and-visual-design`.\n\n**16.8 A\u002FB testing vs. qualitative research.** A\u002FB tests answer \"which is better\" with\nstatistical rigour but cannot tell you *why*, cannot evaluate options you didn't build, and\nsystematically favour short-term engagement over long-term value (the classic failure: the\nvariant that wins on click-through erodes trust over months). Qualitative research explains\nmechanism and generates options but can't quantify effect. **They answer different questions\nand neither substitutes for the other.** Teams that use only A\u002FB testing optimize into local\nmaxima; teams that use only qualitative research ship confident guesses.\n\n**16.9 Design system centralization.** A single central team produces consistency and\nquality but becomes a bottleneck and drifts from product reality; a federated model produces\nadoption and relevance but drifts toward inconsistency. Most mature organizations end up\nwith a small core team owning foundations plus a contribution model with review — and the\ngovernance, not the model, is what determines whether it works.\n\n**16.10 Does \"UX = UI\" still hold?** NN\u002Fg's 2026 position is that UI is becoming less of a\ndifferentiator as design systems standardize components and AI mediation sits above the\ninterface. The counterargument is that this has been predicted before, that most software\nin the world is still mediocre at basic interface craft, and that declaring UI solved while\n83.9% of top sites fail color contrast is premature. Both can be true: the *ceiling* on\nUI differentiation may be falling while the *floor* remains unmet.\n\n---\n\n## §17. Currency Snapshot — verified August 2026\n\n| Thing | Status as of Aug 2026 | Decay risk |\n|---|---|---|\n| **WCAG 2.2** | Current W3C Recommendation (Oct 2023; updated Dec 2024). **Approved as ISO\u002FIEC 40500:2025**; the Dec-2024 text expected as ISO\u002FIEC 40500:2026 by late 2026 | Low |\n| **WCAG 3.0** | **Working Draft only.** March 2026 draft with ~174 requirements; Bronze\u002FSilver\u002FGold outcome-based conformance. Candidate Rec ~Q4 2027; final Rec realistically **2028–2030**. **Not legally required anywhere.** Will not deprecate WCAG 2 | Medium |\n| **EU Accessibility Act** | **Enforceable since 28 June 2025**. EN 301 549 currently → WCAG 2.1 AA; **v4.1.1 expected 2026 → WCAG 2.2**. Existing services to 28 June 2030; pre-June-2025 contracts to June 2027. Enforcement intensifying per-member-state (Dutch ACM active on e-commerce) | Medium |\n| **ADA Title II** | ⚠️ **Deadlines extended one year on 20 April 2026** (Interim Final Rule): 50,000+ population → **26 April 2027**; under 50,000 and special districts → **26 April 2028**. WCAG 2.1 AA. Obligation is in force now; only the date moved. DOJ signaled possible further rulemaking; comment period closed 22 June 2026 | **High** |\n| **Section 504 \u002F HHS** | Deadlines also extended (7 May 2026): ≥15 employees → 11 May 2027; \u003C15 → 10 May 2028 | High |\n| **APCA** | Candidate contrast method for WCAG 3; available in Chrome DevTools (experimental). **Referenced by no law.** Practitioner guidance is to satisfy WCAG 2 and optionally also APCA | Medium |\n| **Contrast failure rate** | WebAIM Million 2026: **83.9%** of top 1M home pages have WCAG 2 contrast failures (up from 79.1%), ~34 instances\u002Fpage | Annual |\n| **Core Web Vitals** | LCP ≤ **2.5 s**, INP ≤ **200 ms**, CLS ≤ **0.1**, at the 75th percentile of real Chrome users over 28 days. **INP replaced FID in March 2024.** ~43% of sites fail INP — the most commonly failed metric | Medium |\n| **Container queries** | **Baseline Widely Available since August 2025** (~93% support). Now the default tool for component-level responsiveness | Low |\n| **Design Tokens (DTCG)** | **First stable spec, v2025.10, published 28 Oct 2025.** A W3C **Community Group** spec, *not* a Recommendation. Style Dictionary v4 has first-class support (full 2025.10 in v5); Figma Variables export; Penpot, Tokens Studio, Terrazzo, Supernova, zeroheight adopting. Token adoption ~84% of teams (zeroheight survey, ~300 respondents) | Low |\n| **Material 3 Expressive** | Announced May 2025 as an enhancement to M3 (**not \"M4\"**). 46 studies \u002F 18,000+ participants; reported up to **4× faster** identification of key UI elements and closure of the usability age gap. Rolling across Google's app ecosystem | Medium |\n| **Apple Liquid Glass** | Introduced in macOS 26 \u002F iOS 26 (Sept 2025). Free on recompile for framework chrome; custom components need work; Icon Composer required for icons. Ongoing legibility criticism | Medium |\n| **Dark-pattern regulation** | DSA Art. 25 and DMA in force; EDPB Guidelines 03\u002F2022 (six categories); CRD financial-services dark-pattern ban **applicable 19 June 2026**; **Digital Fairness Act proposal expected late 2026** (not law). FTC actively enforcing, naming individual executives | **High** |\n| **Enforcement scale** | FTC 2024 study: 76% of 642 sites\u002Fapps used ≥1 possible deceptive pattern. EU 2022 study: 97%. Fines: Amazon $2.5B (FTC) and €746M (EU), Epic $245M, TikTok €345M, Google €150M, Microsoft €60M | Medium |\n| **Cart abandonment** | Baymard meta-analysis (50 studies, updated Sept 2025): **70.22%**; ~35.26% conversion uplift available from checkout design (upper bound, not a promise); ~23.5 form elements typical vs 12–14 achievable | Low |\n| **Design tooling** | Figma **Config 2026** (June 23–25): code layers, design agents, MCP server, generative plugins. State of the Designer 2026 (n=906): **72%** use gen-AI in workflow, **98%** increased usage YoY, **91%** report quality gains. Penpot shipped an MCP server; native DTCG tokens; open-source\u002Fself-hostable | **High** |\n| **NN\u002Fg position** | State of UX 2026: UI becoming less of a differentiator; AI mediation above the interface; \"outcome-oriented design\" framing. 36% of surveyed designers fear AI-normalized dark patterns | Medium |\n\n**Goes stale fastest:** legal deadlines (ADA Title II moved *this year*), design-tool\nfeature sets, AI-interface conventions, platform design-language versions.\n**Essentially never stale:** §1 → `ui-ux-cognition-heuristics-and-navigation` (perception\u002Fcognition), §2 → `ui-ux-cognition-heuristics-and-navigation` (heuristics), §3 → `ui-ux-cognition-heuristics-and-navigation` (IA), §4.1 → `ui-ux-interaction-layout-and-visual-design`–4.2\n(input physics), §5.1 → `ui-ux-interaction-layout-and-visual-design` (layout primitives), §6.1 → `ui-ux-interaction-layout-and-visual-design` (typography), §10 → `ui-ux-writing-forms-research-and-ethics` (writing), §15\n(anti-patterns).\n\n---\n\n## §18. The Canon\n\n### 18.1 Books\n\n| Author | Work | Why |\n|---|---|---|\n| **Don Norman** | *The Design of Everyday Things* (rev. ed.) | The foundational vocabulary: affordances, signifiers, mappings, gulfs. Read first. |\n| **Steve Krug** | *Don't Make Me Think, Revisited*; *Rocket Surgery Made Easy* | The best short book on web usability, and the best case for cheap, frequent testing |\n| **Jeff Johnson** | *Designing with the Mind in Mind* | The cognitive-psychology basis for UI rules — the \"why\" behind §1 → `ui-ux-cognition-heuristics-and-navigation` |\n| **Alan Cooper et al.** | *About Face: The Essentials of Interaction Design* | Interaction design canon; goal-directed design, personas, the \"elastic user\" |\n| **Ellen Lupton** | *Thinking with Type* | The standard typography reference |\n| **Robert Bringhurst** | *The Elements of Typographic Style* | The deeper one |\n| **Edward Tufte** | *The Visual Display of Quantitative Information*; *Envisioning Information* | Data display; data-ink ratio; chartjunk |\n| **Rosenfeld, Morville & Arango** | *Information Architecture* (\"the polar bear book\") | The IA reference (§3 → `ui-ux-cognition-heuristics-and-navigation`) |\n| **Bill Buxton** | *Sketching User Experiences* | Why sketching and breadth-first exploration beat premature fidelity |\n| **Jenifer Tidwell et al.** | *Designing Interfaces* | The pattern catalogue |\n| **Luke Wroblewski** | *Web Form Design*; *Mobile First* | Still the reference on forms (§11 → `ui-ux-writing-forms-research-and-ethics`) and the origin of mobile-first |\n| **Kim Goodwin** | *Designing for the Digital Age* | The most complete end-to-end process book |\n| **Erika Hall** | *Just Enough Research*; *Conversational Design* | Research pragmatism; and the best sober treatment of conversational UI |\n| **Torrey Podmajersky** | *Strategic Writing for UX* | UX writing (§10 → `ui-ux-writing-forms-research-and-ethics`) |\n| **Alla Kholmatova** | *Design Systems* | Design systems as culture, not component libraries |\n| **Sarah Wachter-Boettcher** | *Technically Wrong*; *Design for Real Life* (w\u002F Meyer) | Stress cases, edge cases, and design harm |\n| **Harry Brignull** | *Deceptive Patterns* | By the person who coined \"dark patterns\" (§13 → `ui-ux-writing-forms-research-and-ethics`) |\n| **Laura Kalbag** | *Accessibility for Everyone* | Accessible entry point to §9 → `ui-ux-design-systems-platforms-and-accessibility` |\n| **Heydon Pickering** | *Inclusive Components* | The best practical guide to accessible component patterns |\n| **Susan Weinschenk** | *100 Things Every Designer Needs to Know About People* | Research-backed, browsable |\n| **Tognazzini** | *Tog on Interface* \u002F First Principles of Interaction Design | Where a lot of Mac interaction philosophy originates |\n\n### 18.2 Primary sources\n\n- **W3C \u002F WAI** — WCAG 2.2, Understanding docs, Techniques, ARIA Authoring Practices Guide\n  (APG), WCAG-EM. **Use the Understanding documents**, not blog summaries — they contain\n  the intent and the exceptions.\n- **Apple Human Interface Guidelines** + WWDC design sessions.\n- **Material Design 3** (`m3.material.io`) + Google Design (`design.google`) — the M3\n  Expressive research writeups are unusually transparent for vendor material.\n- **Microsoft Fluent 2**; **GNOME HIG**; **KDE HIG**.\n- **Design Tokens Community Group** (`designtokens.org`, `w3.org\u002Fcommunity\u002Fdesign-tokens`).\n- **web.dev** — Core Web Vitals, performance, accessibility (Google, but the CWV\n  documentation is the authoritative source for the metrics).\n- **MDN** — the reference for what CSS\u002FHTML\u002FARIA actually does.\n- **EDPB Guidelines 03\u002F2022** on deceptive design; **FTC dark patterns staff report** (2022)\n  and the 2024 sweep; **EU Digital Fairness Act** initiative pages.\n\n### 18.3 Ongoing sources\n\n**Nielsen Norman Group** (`nngroup.com`) — still the highest-volume source of\nmethodologically-grounded UX research; **Baymard Institute** — the deepest e-commerce\nusability data set (paywalled, worth it if you sell things); **WebAIM** (the annual Million\nreport; a11y technique articles); **Adrian Roselli**, **Scott O'Hara**, **Heydon Pickering**,\n**Sara Soueidan**, **TetraLogical**, **Deque** — the accessibility practitioner bench;\n**Smashing Magazine**, **A List Apart**, **CSS-Tricks** (archive), **Josh Comeau** — craft;\n**Interaction Design Foundation**; **Laws of UX** (`lawsofux.com`) — a good index, but check\neach \"law\" against §1 → `ui-ux-cognition-heuristics-and-navigation` before citing it, because several are folk versions of real findings.\n\n---\n\n## §19. Quick Reference\n\n### 19.1 The numbers\n- Touch target: **44 pt** (Apple) \u002F **48 dp** (Material) \u002F **24 px** WCAG AA floor,\n  **44 px** WCAG AAA. Design to 44–48.\n- Body text: **≥16 px** web; measure **45–75 characters**; line-height **1.4–1.6**.\n- Contrast: **4.5:1** body, **3:1** large text and UI components.\n- Response: **\u003C100 ms** instant · **\u003C400 ms** stays in flow (Doherty) · **>1 s** show\n  progress · **>10 s** allow cancel.\n- Core Web Vitals: LCP **2.5 s** · INP **200 ms** · CLS **0.1**, at p75.\n- Motion: **150–300 ms**, ease-out in, ease-in out.\n- Working memory: ~**4** chunks (not 7).\n- Usability testing: **5 per segment per round**, **3 rounds**.\n- SUS: **68** average, **80+** good.\n- Text expansion for localization: budget **+30–40%**.\n- Checkout: **~70%** abandonment; target **12–14** form fields, not 23.\n\n### 19.2 Design review checklist\n- [ ] Is the primary action obvious, singular, and reachable (thumb zone on mobile)?\n- [ ] Does spacing group correctly — tighter within, looser between? (§1.3 → `ui-ux-cognition-heuristics-and-navigation`)\n- [ ] Is every interactive element identifiable *without* hover? (§2.2 → `ui-ux-cognition-heuristics-and-navigation`)\n- [ ] Are all states designed: hover, focus, active, disabled, loading, error, empty, selected?\n- [ ] Contrast ≥4.5:1 body \u002F ≥3:1 UI; meaning never carried by color alone?\n- [ ] Full keyboard operation with a visible focus indicator?\n- [ ] Works at 200% zoom and 320 px reflow? Respects OS text size?\n- [ ] Screen-reader tested — labels, headings, landmarks, focus management?\n- [ ] Errors say what happened, why, and what to do next?\n- [ ] Is there undo instead of a confirmation dialog? (§2.3 → `ui-ux-cognition-heuristics-and-navigation`)\n- [ ] Does Back \u002F Escape \u002F Enter do what the platform says they do?\n- [ ] Do the defaults serve the user rather than the business? (§13.4 → `ui-ux-writing-forms-research-and-ethics`)\n- [ ] Does the copy use the user's words and front-load meaning?\n- [ ] What happens at 0 items, 1 item, 10,000 items, and on a failed request?\n- [ ] Has anyone outside the team completed the task without help?\n\n### 19.3 \"This feels wrong but I can't say why\" — diagnostic\nHierarchy unclear (§6.1 → `ui-ux-interaction-layout-and-visual-design`) → grouping ambiguous (§1.3 → `ui-ux-cognition-heuristics-and-navigation`) → too many equal-weight options\n(§1.2 → `ui-ux-cognition-heuristics-and-navigation`) → signifiers missing (§2.2 → `ui-ux-cognition-heuristics-and-navigation`) → inconsistent with itself or the platform (§2.1 → `ui-ux-cognition-heuristics-and-navigation` #4,\n§8 → `ui-ux-design-systems-platforms-and-accessibility`) → language is the product's, not the user's (§10 → `ui-ux-writing-forms-research-and-ethics`) → state is hidden so the user must\nremember (§1.2 → `ui-ux-cognition-heuristics-and-navigation`) → the wrong gulf: they can't figure out how to act (execution) or can't\ntell whether it worked (evaluation) (§2.2 → `ui-ux-cognition-heuristics-and-navigation`).\n\n---\n\n## §20. Sources and Method\n\n**Method.** Narrative (not systematic) review. The durable material — §1 → `ui-ux-cognition-heuristics-and-navigation` (perception,\ncognition, motor control), §2 → `ui-ux-cognition-heuristics-and-navigation` (heuristics and Norman's model), §3 → `ui-ux-cognition-heuristics-and-navigation` (IA), §4.1 → `ui-ux-interaction-layout-and-visual-design`–4.2 (input),\n§5.1 → `ui-ux-interaction-layout-and-visual-design`, §6.1 → `ui-ux-interaction-layout-and-visual-design`–6.5, §10 → `ui-ux-writing-forms-research-and-ethics`, §11.1 → `ui-ux-writing-forms-research-and-ethics`, §12 → `ui-ux-writing-forms-research-and-ethics`, §15 — is synthesized from the primary research literature\nand canonical texts in §18. Every **time-sensitive** claim (standards versions, legal\ndeadlines, platform design-language status, tooling, survey figures) was verified against a\nprimary or near-primary source in **August 2026** and is flagged in §17 with a decay-risk\nrating. Where practitioners disagree, §16 presents both cases rather than adjudicating.\n\n**Search log** (August 2026): WCAG 3.0 status and timeline · European Accessibility Act and\nADA Title II deadlines · Material 3 Expressive research · Core Web Vitals thresholds ·\nW3C Design Tokens Community Group specification status · responsive design, container\nqueries, and foldables · APCA vs. WCAG 2 contrast · NN\u002Fg and AI-era UX patterns · WCAG 2.2\ntouch-target requirements vs. platform guidelines · dark-pattern regulation (FTC, EU DFA,\nEDPB, CPRA) · design tooling 2026 (Figma Config, Penpot) · Baymard checkout research.\n\n**Primary and near-primary sources consulted (selected):**\n- W3C \u002F WAI — WCAG 2 Overview; WCAG 3.0 Working Draft (March 2026); WAI Current Work;\n  ISO\u002FIEC 40500:2025 announcement\n- ADA.gov and the **Federal Register** — Extension of Compliance Dates for ADA Title II\n  web accessibility (Interim Final Rule, 20 April 2026)\n- European Commission \u002F EU consumer-policy materials — European Accessibility Act;\n  Digital Fairness Act initiative and 2030 Consumer Agenda; EDPB Guidelines 03\u002F2022\n- Design Tokens Community Group — `designtokens.org`; W3C DTCG announcement of the first\n  stable specification (28 October 2025); Style Dictionary DTCG documentation\n- Google — `developers.google.com\u002Fsearch` Core Web Vitals documentation; Google Design,\n  \"Expressive Design: Google's UX Research\" and the Material 3 Expressive Design Notes\n- Apple — Newsroom announcement of the new software design (Liquid Glass); WWDC25\u002F26\n  design sessions; \"Adopting Liquid Glass\" documentation\n- Nielsen Norman Group — articles index; State of UX 2026 coverage; \"AI: First New UI\n  Paradigm in 60 Years\"; outcome-oriented design\n- Baymard Institute — cart abandonment meta-analysis (`baymard.com\u002Flists\u002Fcart-abandonment-rate`)\n- Adrian Roselli — \"WCAG3 Contrast as of April 2026\"; APCA project documentation\n- WebAIM — Million report figures (via secondary reporting)\n- Figma — Config 2026 recap; State of the Designer 2026; AI documentation. Penpot — MCP and\n  tokens announcements\n\n**Confidence statement.** **High confidence** in §1–§6 → `ui-ux-cognition-heuristics-and-navigation`, `ui-ux-interaction-layout-and-visual-design`, §9.1 → `ui-ux-design-systems-platforms-and-accessibility`–9.2, §10 → `ui-ux-writing-forms-research-and-ethics`, §12 → `ui-ux-writing-forms-research-and-ethics`, §15, §18–§19 —\nthese rest on primary research, standards documents, and law. **High confidence** in §17's\nverified items as of the stated date. **Moderate confidence** in §7.4 → `ui-ux-design-systems-platforms-and-accessibility`, §11.2 → `ui-ux-writing-forms-research-and-ethics`, §13 → `ui-ux-writing-forms-research-and-ethics`'s\nenforcement figures, and §14.4 → `ui-ux-writing-forms-research-and-ethics` — these rest on vendor surveys, commercial research\norganizations, and practitioner reporting where methodology is often unpublished and\nincentives differ; they are stated as reported findings with their sources named, not as\nestablished fact. The Material 3 Expressive figures in §8.2 → `ui-ux-design-systems-platforms-and-accessibility` and the Baymard figures in\n§11.2 → `ui-ux-writing-forms-research-and-ethics` are specifically flagged in place as vendor\u002Fcommercial research whose *direction*\nis more reliable than its *magnitudes*.\n","# UI\u002FUX Design: Anti-Patterns, Contested Questions, Currency, and Canon\n\n> **Part 5 of 5** of the *UI\u002FUX Design Principles — Mobile, Tablet, Web, Desktop* reference (plugin `ui-ux-design-principles`), covering §15–§20. Sibling skills: `ui-ux-cognition-heuristics-and-navigation` (§0–§3), `ui-ux-interaction-layout-and-visual-design` (§4–§6), `ui-ux-design-systems-platforms-and-accessibility` (§7–§9), `ui-ux-writing-forms-research-and-ethics` (§10–§14). Section numbers are shared across the set; a reference written as §N → `skill` points into that sibling skill.\n>\n> **Currency:** Verified August 2026. See §17 below for the currency snapshot and what goes stale first.\n>\n> **Related:** Overlaps the `frontend-design:graphic-ux-ui-design` skill. That one is oriented to implementation-time component and token decisions; this one is oriented to design reasoning, cross-form-factor principles, research method, and the regulatory landscape. Use both.\n\n> **How to read this.** Reference, not tutorial. Sections are independent. Three markers:\n> - **[DURABLE]** — grounded in perception, cognition, motor control, or decades of\n>   replicated research. Does not expire. Trust it.\n> - **[PLATFORM]** — a convention of Apple, Google, Microsoft, GNOME\u002FKDE, or the web.\n>   Verify against the current HIG; these change.\n> - **[CONTESTED]** — competent practitioners disagree, or the evidence is thinner than the\n>   confidence with which it's usually asserted. Both cases given.\n>\n> **⚠️ GOTCHA** boxes mark the mistakes that survive design review and get caught in\n> production, in court, or in the analytics.\n>\n> **The framing that organizes everything below:** an interface is a *proposal about how\n> a person should think*. Good design makes the proposal match how they already think.\n> Every principle in this document is a specialization of that idea — to a thumb, a\n> screen size, a screen reader, a legal regime, or an attention budget.\n\n---\n\n## §15. Anti-Patterns\n\n| Anti-pattern | Why it fails | Do instead |\n|---|---|---|\n| Placeholder text as the label | Disappears on focus, fails contrast, breaks autofill and translation, invisible to some AT | Persistent label above the field |\n| Two primary buttons | Von Restorff: two emphases = none | One primary, rest secondary\u002Ftertiary |\n| Icon-only controls without labels | Icons aren't universal; tooltips don't exist on touch | Icon + label, or label at minimum |\n| Removing focus outlines | WCAG Level A failure; breaks keyboard use | `:focus-visible` with a designed indicator |\n| Disabling zoom (`user-scalable=no`) | Hostile to low-vision users; WCAG failure | Never do this |\n| Fixed pixel font sizes \u002F ignoring OS text scale | Breaks for everyone over ~45 | Relative units; test at 200% |\n| Color as the only signal | Fails ~8% of men and every grayscale\u002Flow-vision case | Color + icon + text |\n| Confirmation dialogs everywhere | Habituation makes them useless | Undo (§2.3 → `ui-ux-cognition-heuristics-and-navigation`) |\n| Hamburger for primary navigation | Measurably reduces discovery of hidden items | Tab bar for the top 3–5 |\n| Modal for anything non-blocking | Interrupts, traps, and stacks | Inline, sheet, or side panel |\n| Infinite scroll where users need to find and return | Destroys position memory; breaks the footer | Pagination or \"load more\" |\n| Carousels for important content | Very low engagement past slide 1; auto-advance is an a11y failure | Show the content |\n| Auto-playing audio\u002Fvideo | Universally hated; a11y violation | User-initiated |\n| Hijacking scroll, Back, or system gestures | Breaks the trust users place in platform behaviour | Don't |\n| Equal spacing above and below labels | Proximity ambiguity — the classic form bug | Tighter within groups than between |\n| Centered long body text | Ragged left edge slows reading | Left-align |\n| Full-width text on wide screens | Exceeds 75-character measure | max-width or multi-column |\n| Skeleton\u002Fspinner with no context | Doesn't reduce anxiety, just delays it | Say what's loading; show progress |\n| \"Something went wrong\" | Unactionable | What\u002Fwhy\u002Fwhat next (§10.2 → `ui-ux-writing-forms-research-and-ethics`) |\n| Testing only the happy path | Real pain lives in errors and second sessions | Test failure and recovery |\n| Designing only at 1440 px in Figma | Never sees the 375 px reality | Design mobile-first; open the small frame |\n| Hiding content on mobile with `display:none` | Mobile users are not second-class | Reorganize, don't delete |\n| Optimizing engagement metrics alone | Rewards confusion and manipulation | Pair with quality metrics (§12.4 → `ui-ux-writing-forms-research-and-ethics`) |\n| Adding a preference for every disagreement | Pushes design decisions onto users | Choose a good default |\n| Accessibility overlay widget | Doesn't work; no legal protection; opposed by AT users | Fix the underlying markup |\n| Shipping WCAG 2.0 in 2026 | Below every current legal baseline | Build to 2.2 AA (§9.2 → `ui-ux-design-systems-platforms-and-accessibility`) |\n| Quoting \"5 users is enough\" as universal | Misreads the finding (§12.2 → `ui-ux-writing-forms-research-and-ethics`) | 5 per segment per round, 3 rounds |\n| Quoting \"7±2\" as a menu-length rule | Miller said no such thing (§1.2 → `ui-ux-cognition-heuristics-and-navigation`) | Categorize; don't make people recall |\n\n---\n\n## §16. Contested Questions\n\n**16.1 Minimalism vs. signifiers.** Flat\u002Fminimal design demonstrably improved consistency\nand scalability and reduced visual noise; it also removed the cues that tell people what's\nclickable, with a documented cost concentrated in older and less experienced users. Neither\n\"add bevels back\" nor \"clean is always better\" is right. The resolution is *deliberate\nsignification*: keep the aesthetic, but ensure every interactive element is identifiable\nwithout hover, and test that assumption with real users rather than with your team.\n\n**16.2 Expressive vs. neutral design.** Material 3 Expressive's research argues emotional\nexpressiveness and usability are complementary — bolder shapes and bigger primary actions\nmade key elements ~4× faster to spot and closed the usability age gap. The counterweight:\nthese are vendor studies of vendor components, the mechanism is mostly \"prominence helps\"\n(which we already knew), and expressiveness is genuinely wrong for some contexts — Google's\nown team notes you may not want a playful UI for paying a parking ticket. Direction:\nwell-supported. Specific numbers: don't generalize.\n\n**16.3 Consistency vs. platform nativeness.** §8.5 → `ui-ux-design-systems-platforms-and-accessibility`.\n\n**16.4 APCA vs. WCAG 2 contrast.** §9.3 → `ui-ux-design-systems-platforms-and-accessibility`. This one has legal consequences, so precision\nmatters more than usual.\n\n**16.5 Chat vs. GUI for AI features.** §14.1 → `ui-ux-writing-forms-research-and-ethics`.\n\n**16.6 Hamburger menus.** §3.2 → `ui-ux-cognition-heuristics-and-navigation`.\n\n**16.7 Disabled submit buttons.** §4.6 → `ui-ux-interaction-layout-and-visual-design`.\n\n**16.8 A\u002FB testing vs. qualitative research.** A\u002FB tests answer \"which is better\" with\nstatistical rigour but cannot tell you *why*, cannot evaluate options you didn't build, and\nsystematically favour short-term engagement over long-term value (the classic failure: the\nvariant that wins on click-through erodes trust over months). Qualitative research explains\nmechanism and generates options but can't quantify effect. **They answer different questions\nand neither substitutes for the other.** Teams that use only A\u002FB testing optimize into local\nmaxima; teams that use only qualitative research ship confident guesses.\n\n**16.9 Design system centralization.** A single central team produces consistency and\nquality but becomes a bottleneck and drifts from product reality; a federated model produces\nadoption and relevance but drifts toward inconsistency. Most mature organizations end up\nwith a small core team owning foundations plus a contribution model with review — and the\ngovernance, not the model, is what determines whether it works.\n\n**16.10 Does \"UX = UI\" still hold?** NN\u002Fg's 2026 position is that UI is becoming less of a\ndifferentiator as design systems standardize components and AI mediation sits above the\ninterface. The counterargument is that this has been predicted before, that most software\nin the world is still mediocre at basic interface craft, and that declaring UI solved while\n83.9% of top sites fail color contrast is premature. Both can be true: the *ceiling* on\nUI differentiation may be falling while the *floor* remains unmet.\n\n---\n\n## §17. Currency Snapshot — verified August 2026\n\n| Thing | Status as of Aug 2026 | Decay risk |\n|---|---|---|\n| **WCAG 2.2** | Current W3C Recommendation (Oct 2023; updated Dec 2024). **Approved as ISO\u002FIEC 40500:2025**; the Dec-2024 text expected as ISO\u002FIEC 40500:2026 by late 2026 | Low |\n| **WCAG 3.0** | **Working Draft only.** March 2026 draft with ~174 requirements; Bronze\u002FSilver\u002FGold outcome-based conformance. Candidate Rec ~Q4 2027; final Rec realistically **2028–2030**. **Not legally required anywhere.** Will not deprecate WCAG 2 | Medium |\n| **EU Accessibility Act** | **Enforceable since 28 June 2025**. EN 301 549 currently → WCAG 2.1 AA; **v4.1.1 expected 2026 → WCAG 2.2**. Existing services to 28 June 2030; pre-June-2025 contracts to June 2027. Enforcement intensifying per-member-state (Dutch ACM active on e-commerce) | Medium |\n| **ADA Title II** | ⚠️ **Deadlines extended one year on 20 April 2026** (Interim Final Rule): 50,000+ population → **26 April 2027**; under 50,000 and special districts → **26 April 2028**. WCAG 2.1 AA. Obligation is in force now; only the date moved. DOJ signaled possible further rulemaking; comment period closed 22 June 2026 | **High** |\n| **Section 504 \u002F HHS** | Deadlines also extended (7 May 2026): ≥15 employees → 11 May 2027; \u003C15 → 10 May 2028 | High |\n| **APCA** | Candidate contrast method for WCAG 3; available in Chrome DevTools (experimental). **Referenced by no law.** Practitioner guidance is to satisfy WCAG 2 and optionally also APCA | Medium |\n| **Contrast failure rate** | WebAIM Million 2026: **83.9%** of top 1M home pages have WCAG 2 contrast failures (up from 79.1%), ~34 instances\u002Fpage | Annual |\n| **Core Web Vitals** | LCP ≤ **2.5 s**, INP ≤ **200 ms**, CLS ≤ **0.1**, at the 75th percentile of real Chrome users over 28 days. **INP replaced FID in March 2024.** ~43% of sites fail INP — the most commonly failed metric | Medium |\n| **Container queries** | **Baseline Widely Available since August 2025** (~93% support). Now the default tool for component-level responsiveness | Low |\n| **Design Tokens (DTCG)** | **First stable spec, v2025.10, published 28 Oct 2025.** A W3C **Community Group** spec, *not* a Recommendation. Style Dictionary v4 has first-class support (full 2025.10 in v5); Figma Variables export; Penpot, Tokens Studio, Terrazzo, Supernova, zeroheight adopting. Token adoption ~84% of teams (zeroheight survey, ~300 respondents) | Low |\n| **Material 3 Expressive** | Announced May 2025 as an enhancement to M3 (**not \"M4\"**). 46 studies \u002F 18,000+ participants; reported up to **4× faster** identification of key UI elements and closure of the usability age gap. Rolling across Google's app ecosystem | Medium |\n| **Apple Liquid Glass** | Introduced in macOS 26 \u002F iOS 26 (Sept 2025). Free on recompile for framework chrome; custom components need work; Icon Composer required for icons. Ongoing legibility criticism | Medium |\n| **Dark-pattern regulation** | DSA Art. 25 and DMA in force; EDPB Guidelines 03\u002F2022 (six categories); CRD financial-services dark-pattern ban **applicable 19 June 2026**; **Digital Fairness Act proposal expected late 2026** (not law). FTC actively enforcing, naming individual executives | **High** |\n| **Enforcement scale** | FTC 2024 study: 76% of 642 sites\u002Fapps used ≥1 possible deceptive pattern. EU 2022 study: 97%. Fines: Amazon $2.5B (FTC) and €746M (EU), Epic $245M, TikTok €345M, Google €150M, Microsoft €60M | Medium |\n| **Cart abandonment** | Baymard meta-analysis (50 studies, updated Sept 2025): **70.22%**; ~35.26% conversion uplift available from checkout design (upper bound, not a promise); ~23.5 form elements typical vs 12–14 achievable | Low |\n| **Design tooling** | Figma **Config 2026** (June 23–25): code layers, design agents, MCP server, generative plugins. State of the Designer 2026 (n=906): **72%** use gen-AI in workflow, **98%** increased usage YoY, **91%** report quality gains. Penpot shipped an MCP server; native DTCG tokens; open-source\u002Fself-hostable | **High** |\n| **NN\u002Fg position** | State of UX 2026: UI becoming less of a differentiator; AI mediation above the interface; \"outcome-oriented design\" framing. 36% of surveyed designers fear AI-normalized dark patterns | Medium |\n\n**Goes stale fastest:** legal deadlines (ADA Title II moved *this year*), design-tool\nfeature sets, AI-interface conventions, platform design-language versions.\n**Essentially never stale:** §1 → `ui-ux-cognition-heuristics-and-navigation` (perception\u002Fcognition), §2 → `ui-ux-cognition-heuristics-and-navigation` (heuristics), §3 → `ui-ux-cognition-heuristics-and-navigation` (IA), §4.1 → `ui-ux-interaction-layout-and-visual-design`–4.2\n(input physics), §5.1 → `ui-ux-interaction-layout-and-visual-design` (layout primitives), §6.1 → `ui-ux-interaction-layout-and-visual-design` (typography), §10 → `ui-ux-writing-forms-research-and-ethics` (writing), §15\n(anti-patterns).\n\n---\n\n## §18. The Canon\n\n### 18.1 Books\n\n| Author | Work | Why |\n|---|---|---|\n| **Don Norman** | *The Design of Everyday Things* (rev. ed.) | The foundational vocabulary: affordances, signifiers, mappings, gulfs. Read first. |\n| **Steve Krug** | *Don't Make Me Think, Revisited*; *Rocket Surgery Made Easy* | The best short book on web usability, and the best case for cheap, frequent testing |\n| **Jeff Johnson** | *Designing with the Mind in Mind* | The cognitive-psychology basis for UI rules — the \"why\" behind §1 → `ui-ux-cognition-heuristics-and-navigation` |\n| **Alan Cooper et al.** | *About Face: The Essentials of Interaction Design* | Interaction design canon; goal-directed design, personas, the \"elastic user\" |\n| **Ellen Lupton** | *Thinking with Type* | The standard typography reference |\n| **Robert Bringhurst** | *The Elements of Typographic Style* | The deeper one |\n| **Edward Tufte** | *The Visual Display of Quantitative Information*; *Envisioning Information* | Data display; data-ink ratio; chartjunk |\n| **Rosenfeld, Morville & Arango** | *Information Architecture* (\"the polar bear book\") | The IA reference (§3 → `ui-ux-cognition-heuristics-and-navigation`) |\n| **Bill Buxton** | *Sketching User Experiences* | Why sketching and breadth-first exploration beat premature fidelity |\n| **Jenifer Tidwell et al.** | *Designing Interfaces* | The pattern catalogue |\n| **Luke Wroblewski** | *Web Form Design*; *Mobile First* | Still the reference on forms (§11 → `ui-ux-writing-forms-research-and-ethics`) and the origin of mobile-first |\n| **Kim Goodwin** | *Designing for the Digital Age* | The most complete end-to-end process book |\n| **Erika Hall** | *Just Enough Research*; *Conversational Design* | Research pragmatism; and the best sober treatment of conversational UI |\n| **Torrey Podmajersky** | *Strategic Writing for UX* | UX writing (§10 → `ui-ux-writing-forms-research-and-ethics`) |\n| **Alla Kholmatova** | *Design Systems* | Design systems as culture, not component libraries |\n| **Sarah Wachter-Boettcher** | *Technically Wrong*; *Design for Real Life* (w\u002F Meyer) | Stress cases, edge cases, and design harm |\n| **Harry Brignull** | *Deceptive Patterns* | By the person who coined \"dark patterns\" (§13 → `ui-ux-writing-forms-research-and-ethics`) |\n| **Laura Kalbag** | *Accessibility for Everyone* | Accessible entry point to §9 → `ui-ux-design-systems-platforms-and-accessibility` |\n| **Heydon Pickering** | *Inclusive Components* | The best practical guide to accessible component patterns |\n| **Susan Weinschenk** | *100 Things Every Designer Needs to Know About People* | Research-backed, browsable |\n| **Tognazzini** | *Tog on Interface* \u002F First Principles of Interaction Design | Where a lot of Mac interaction philosophy originates |\n\n### 18.2 Primary sources\n\n- **W3C \u002F WAI** — WCAG 2.2, Understanding docs, Techniques, ARIA Authoring Practices Guide\n  (APG), WCAG-EM. **Use the Understanding documents**, not blog summaries — they contain\n  the intent and the exceptions.\n- **Apple Human Interface Guidelines** + WWDC design sessions.\n- **Material Design 3** (`m3.material.io`) + Google Design (`design.google`) — the M3\n  Expressive research writeups are unusually transparent for vendor material.\n- **Microsoft Fluent 2**; **GNOME HIG**; **KDE HIG**.\n- **Design Tokens Community Group** (`designtokens.org`, `w3.org\u002Fcommunity\u002Fdesign-tokens`).\n- **web.dev** — Core Web Vitals, performance, accessibility (Google, but the CWV\n  documentation is the authoritative source for the metrics).\n- **MDN** — the reference for what CSS\u002FHTML\u002FARIA actually does.\n- **EDPB Guidelines 03\u002F2022** on deceptive design; **FTC dark patterns staff report** (2022)\n  and the 2024 sweep; **EU Digital Fairness Act** initiative pages.\n\n### 18.3 Ongoing sources\n\n**Nielsen Norman Group** (`nngroup.com`) — still the highest-volume source of\nmethodologically-grounded UX research; **Baymard Institute** — the deepest e-commerce\nusability data set (paywalled, worth it if you sell things); **WebAIM** (the annual Million\nreport; a11y technique articles); **Adrian Roselli**, **Scott O'Hara**, **Heydon Pickering**,\n**Sara Soueidan**, **TetraLogical**, **Deque** — the accessibility practitioner bench;\n**Smashing Magazine**, **A List Apart**, **CSS-Tricks** (archive), **Josh Comeau** — craft;\n**Interaction Design Foundation**; **Laws of UX** (`lawsofux.com`) — a good index, but check\neach \"law\" against §1 → `ui-ux-cognition-heuristics-and-navigation` before citing it, because several are folk versions of real findings.\n\n---\n\n## §19. Quick Reference\n\n### 19.1 The numbers\n- Touch target: **44 pt** (Apple) \u002F **48 dp** (Material) \u002F **24 px** WCAG AA floor,\n  **44 px** WCAG AAA. Design to 44–48.\n- Body text: **≥16 px** web; measure **45–75 characters**; line-height **1.4–1.6**.\n- Contrast: **4.5:1** body, **3:1** large text and UI components.\n- Response: **\u003C100 ms** instant · **\u003C400 ms** stays in flow (Doherty) · **>1 s** show\n  progress · **>10 s** allow cancel.\n- Core Web Vitals: LCP **2.5 s** · INP **200 ms** · CLS **0.1**, at p75.\n- Motion: **150–300 ms**, ease-out in, ease-in out.\n- Working memory: ~**4** chunks (not 7).\n- Usability testing: **5 per segment per round**, **3 rounds**.\n- SUS: **68** average, **80+** good.\n- Text expansion for localization: budget **+30–40%**.\n- Checkout: **~70%** abandonment; target **12–14** form fields, not 23.\n\n### 19.2 Design review checklist\n- [ ] Is the primary action obvious, singular, and reachable (thumb zone on mobile)?\n- [ ] Does spacing group correctly — tighter within, looser between? (§1.3 → `ui-ux-cognition-heuristics-and-navigation`)\n- [ ] Is every interactive element identifiable *without* hover? (§2.2 → `ui-ux-cognition-heuristics-and-navigation`)\n- [ ] Are all states designed: hover, focus, active, disabled, loading, error, empty, selected?\n- [ ] Contrast ≥4.5:1 body \u002F ≥3:1 UI; meaning never carried by color alone?\n- [ ] Full keyboard operation with a visible focus indicator?\n- [ ] Works at 200% zoom and 320 px reflow? Respects OS text size?\n- [ ] Screen-reader tested — labels, headings, landmarks, focus management?\n- [ ] Errors say what happened, why, and what to do next?\n- [ ] Is there undo instead of a confirmation dialog? (§2.3 → `ui-ux-cognition-heuristics-and-navigation`)\n- [ ] Does Back \u002F Escape \u002F Enter do what the platform says they do?\n- [ ] Do the defaults serve the user rather than the business? (§13.4 → `ui-ux-writing-forms-research-and-ethics`)\n- [ ] Does the copy use the user's words and front-load meaning?\n- [ ] What happens at 0 items, 1 item, 10,000 items, and on a failed request?\n- [ ] Has anyone outside the team completed the task without help?\n\n### 19.3 \"This feels wrong but I can't say why\" — diagnostic\nHierarchy unclear (§6.1 → `ui-ux-interaction-layout-and-visual-design`) → grouping ambiguous (§1.3 → `ui-ux-cognition-heuristics-and-navigation`) → too many equal-weight options\n(§1.2 → `ui-ux-cognition-heuristics-and-navigation`) → signifiers missing (§2.2 → `ui-ux-cognition-heuristics-and-navigation`) → inconsistent with itself or the platform (§2.1 → `ui-ux-cognition-heuristics-and-navigation` #4,\n§8 → `ui-ux-design-systems-platforms-and-accessibility`) → language is the product's, not the user's (§10 → `ui-ux-writing-forms-research-and-ethics`) → state is hidden so the user must\nremember (§1.2 → `ui-ux-cognition-heuristics-and-navigation`) → the wrong gulf: they can't figure out how to act (execution) or can't\ntell whether it worked (evaluation) (§2.2 → `ui-ux-cognition-heuristics-and-navigation`).\n\n---\n\n## §20. Sources and Method\n\n**Method.** Narrative (not systematic) review. The durable material — §1 → `ui-ux-cognition-heuristics-and-navigation` (perception,\ncognition, motor control), §2 → `ui-ux-cognition-heuristics-and-navigation` (heuristics and Norman's model), §3 → `ui-ux-cognition-heuristics-and-navigation` (IA), §4.1 → `ui-ux-interaction-layout-and-visual-design`–4.2 (input),\n§5.1 → `ui-ux-interaction-layout-and-visual-design`, §6.1 → `ui-ux-interaction-layout-and-visual-design`–6.5, §10 → `ui-ux-writing-forms-research-and-ethics`, §11.1 → `ui-ux-writing-forms-research-and-ethics`, §12 → `ui-ux-writing-forms-research-and-ethics`, §15 — is synthesized from the primary research literature\nand canonical texts in §18. Every **time-sensitive** claim (standards versions, legal\ndeadlines, platform design-language status, tooling, survey figures) was verified against a\nprimary or near-primary source in **August 2026** and is flagged in §17 with a decay-risk\nrating. Where practitioners disagree, §16 presents both cases rather than adjudicating.\n\n**Search log** (August 2026): WCAG 3.0 status and timeline · European Accessibility Act and\nADA Title II deadlines · Material 3 Expressive research · Core Web Vitals thresholds ·\nW3C Design Tokens Community Group specification status · responsive design, container\nqueries, and foldables · APCA vs. WCAG 2 contrast · NN\u002Fg and AI-era UX patterns · WCAG 2.2\ntouch-target requirements vs. platform guidelines · dark-pattern regulation (FTC, EU DFA,\nEDPB, CPRA) · design tooling 2026 (Figma Config, Penpot) · Baymard checkout research.\n\n**Primary and near-primary sources consulted (selected):**\n- W3C \u002F WAI — WCAG 2 Overview; WCAG 3.0 Working Draft (March 2026); WAI Current Work;\n  ISO\u002FIEC 40500:2025 announcement\n- ADA.gov and the **Federal Register** — Extension of Compliance Dates for ADA Title II\n  web accessibility (Interim Final Rule, 20 April 2026)\n- European Commission \u002F EU consumer-policy materials — European Accessibility Act;\n  Digital Fairness Act initiative and 2030 Consumer Agenda; EDPB Guidelines 03\u002F2022\n- Design Tokens Community Group — `designtokens.org`; W3C DTCG announcement of the first\n  stable specification (28 October 2025); Style Dictionary DTCG documentation\n- Google — `developers.google.com\u002Fsearch` Core Web Vitals documentation; Google Design,\n  \"Expressive Design: Google's UX Research\" and the Material 3 Expressive Design Notes\n- Apple — Newsroom announcement of the new software design (Liquid Glass); WWDC25\u002F26\n  design sessions; \"Adopting Liquid Glass\" documentation\n- Nielsen Norman Group — articles index; State of UX 2026 coverage; \"AI: First New UI\n  Paradigm in 60 Years\"; outcome-oriented design\n- Baymard Institute — cart abandonment meta-analysis (`baymard.com\u002Flists\u002Fcart-abandonment-rate`)\n- Adrian Roselli — \"WCAG3 Contrast as of April 2026\"; APCA project documentation\n- WebAIM — Million report figures (via secondary reporting)\n- Figma — Config 2026 recap; State of the Designer 2026; AI documentation. Penpot — MCP and\n  tokens announcements\n\n**Confidence statement.** **High confidence** in §1–§6 → `ui-ux-cognition-heuristics-and-navigation`, `ui-ux-interaction-layout-and-visual-design`, §9.1 → `ui-ux-design-systems-platforms-and-accessibility`–9.2, §10 → `ui-ux-writing-forms-research-and-ethics`, §12 → `ui-ux-writing-forms-research-and-ethics`, §15, §18–§19 —\nthese rest on primary research, standards documents, and law. **High confidence** in §17's\nverified items as of the stated date. **Moderate confidence** in §7.4 → `ui-ux-design-systems-platforms-and-accessibility`, §11.2 → `ui-ux-writing-forms-research-and-ethics`, §13 → `ui-ux-writing-forms-research-and-ethics`'s\nenforcement figures, and §14.4 → `ui-ux-writing-forms-research-and-ethics` — these rest on vendor surveys, commercial research\norganizations, and practitioner reporting where methodology is often unpublished and\nincentives differ; they are stated as reported findings with their sources named, not as\nestablished fact. The Material 3 Expressive figures in §8.2 → `ui-ux-design-systems-platforms-and-accessibility` and the Baymard figures in\n§11.2 → `ui-ux-writing-forms-research-and-ethics` are specifically flagged in place as vendor\u002Fcommercial research whose *direction*\nis more reliable than its *magnitudes*.\n",{"name":5,"description":7},"develop","ae32736a1aabddabca5d2c96d665aa0ebc7d8700","src\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fui-ux-design-principles\u002Fskills\u002Fui-ux-reference",3,"https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey","https:\u002F\u002Fthe-vibey-project.github.io\u002Fvibey\u002F","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project","https:\u002F\u002Fvibewithadam.matthewsteinberger.com","freedom for software engineers","2026-11-15 05:47:42",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add the-vibey-project\u002Fvibey --skill ui-ux-reference",{"tool":40,"command":41},"bunx","bunx skills add the-vibey-project\u002Fvibey --skill ui-ux-reference",{"tool":43,"command":44},"pnpm","pnpm dlx skills add the-vibey-project\u002Fvibey --skill ui-ux-reference","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fui-ux-design-principles\u002Fskills\u002Fui-ux-reference\u002FSKILL.md",true,[],[49,56,63,70,77,84],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":19},"01M7AT1FQJAE1FQYAMDTF490Y4","white-paper-writing","Use when writing white papers, technical reports, policy documents, thought leadership pieces, or any long-form authoritative document. Triggers on requests to write, structure, outline, or review white papers, technical reports, position papers, policy briefs, or evidence-driven arguments. Also use for B2B content marketing strategy, technical documentation requiring authority, academic-style reports, or any document that must educate while persuading. Use when someone asks \"how should I structure this\" for a long-form document.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fwhite-paper-writing\u002FSKILL.md",[],[],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M7AT16BJRJJKK2MASXRZS76G","prose-technical-mechanics","Use when editing or writing prose at a technical\u002Fmechanical level: choosing between Anglo-Saxon and Latinate diction, placing information in topic vs stress positions, writing periodic vs cumulative sentences, handling sentence rhythm, punctuation as logic, transitions, paragraph structure, or phonesthetics. Use when someone wants to understand WHY prose works or doesn't, not just surface-level style advice. Triggers on word choice, sentence structure, emphasis, rhythm, diction, or any deep writing mechanics question.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fprose-technical-mechanics\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7AT0W9HT0ZZ9Y287NW99MR3","prose-mechanics","Use when writing, editing, or analyzing prose style; when trying to avoid generic AI-sounding writing; when applying specific prose styles such as journalistic, academic, narrative, KJV biblical, Hemingway plain, Latinate\u002FJamesian, Orwellian, Augustan, Victorian, Early Modern (Bacon, Browne, Milton), or free indirect discourse; or when coaching someone on writing voice and mechanics. Triggers on any request to improve, analyze, or write in a specific prose style, to fix \"AI-sounding\" writing, to make prose more vivid or concrete, to vary sentence rhythm, or to understand how a particular writer achieves their effects.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fprose-mechanics\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7AT0KR635JX66X2X6F3E2CP","narrative-structure","Use when structuring stories, pitches, presentations, white papers, or any persuasive narrative; analyzing the hero's journey in fiction or non-fiction; applying StoryBrand for business communication; designing narrative arcs for thought leadership; or understanding Vogler, Snyder, Propp, or Campbell frameworks. Triggers on any narrative structure, storytelling, pitch structure, StoryBrand, hero's journey, three-act structure, Freytag, Save the Cat, narrative arc, or \"how should I structure this story\u002Fpitch\u002Fpresentation\" request.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fnarrative-structure\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7AT0AKGW09NKKZDYBT8VRDE","legal-brief-writing","Use when writing legal briefs, motions, or any court filing; when analyzing judicial cognition and persuasion; when applying elite brief-writing techniques from Roberts, Clement, Kagan, Garner; or when structuring legal arguments for maximum persuasion. Also use for autistic\u002Fneurodivergent advocates who need to understand how their natural communication style maps to elite legal advocacy. Triggers on any legal writing, brief drafting, motion preparation, or legal argument structuring request.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Flegal-brief-writing\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7AT00VWPS4Q8B5VEMXX9NQT","journal-publishability-criteria","Use whenever a research paper, article or preprint is being written, revised, reviewed or published, and specifically before every publication of docs\u002Fpaper.md. Covers what legitimate journals actually gate on, in order of gating — the editor's desk screen (scope, novelty, package problems), what reviewers judge (methodological soundness, claims the evidence can carry, statistical and qualitative reporting), EQUATOR reporting guidelines, the ICMJE authorship criteria, COPE's view of text recycling, the near-universal generative-AI policy (no AI author, disclosure, author responsibility), TOP 2025 transparency standards, how to verify a journal is legitimate, submitting without an institution, and a pre-submission checklist. Triggers on requests to evaluate, review, prepare or submit a paper, to judge publishability, to write a declarations or data-availability section, to disclose AI use, or to check a journal.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fjournal-publishability-criteria\u002FSKILL.md",[],[]]