<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Yin-Ling Mack on Medium]]></title>
        <description><![CDATA[Stories by Yin-Ling Mack on Medium]]></description>
        <link>https://medium.com/@mackyinling1215?source=rss-a0521af3ea94------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*fEjMrNrljF6T-oYDkyVALg@2x.jpeg</url>
            <title>Stories by Yin-Ling Mack on Medium</title>
            <link>https://medium.com/@mackyinling1215?source=rss-a0521af3ea94------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 20:36:38 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@mackyinling1215/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[What I Learned About Token Management While Letting AI Build My Design System]]></title>
            <link>https://www.designsystemscollective.com/component-tokens-management-0c09fe402534?source=rss-a0521af3ea94------2</link>
            <guid isPermaLink="false">https://medium.com/p/0c09fe402534</guid>
            <category><![CDATA[design-to-code]]></category>
            <category><![CDATA[engineering-design]]></category>
            <category><![CDATA[component-tokens]]></category>
            <category><![CDATA[ux-ui-product-designer]]></category>
            <category><![CDATA[design-systems]]></category>
            <dc:creator><![CDATA[Yin-Ling Mack]]></dc:creator>
            <pubDate>Tue, 13 May 2025 15:52:50 GMT</pubDate>
            <atom:updated>2025-05-14T09:04:47.765Z</atom:updated>
            <content:encoded><![CDATA[<h4>Component Token Management: Centralised or split by UI component?</h4><figure><img alt="Cover image showing the subtitle “Component Token Management: Centralised or split by UI component?” On the bottom, an icon of a single folder labelled component-tokens is contrasted with two separate folders labelled button-tokens and card-tokens, with “vs.”" src="https://cdn-images-1.medium.com/max/1024/1*5ZnAbxBFF0yK40VtAgEScg.png" /></figure><p>Language / 語言 : English | <a href="https://medium.com/design-systems-collective-tw/component-tokens-management-8b3e125218d1"><strong>中文</strong></a></p><p>I’ve recently been experimenting with AI tools to improve the efficiency of my design workflow, and also thinking about how to make design handoffs to engineers smoother.</p><p>For one of my latest projects, which started from scratch, I imported a few completed UI components and screens from Figma into an AI tool. I asked it to generate the initial pages and, at the same time, help me build a Design System for the product.</p><p>However, as I collaborated with the AI, I found myself constantly reviewing what it produced. I kept wondering:</p><ul><li><strong>Can these files really be handed off to engineers as-is?</strong></li><li><strong>Does the structure make sense for long-term development and maintenance?</strong></li></ul><blockquote><em>In this article, I want to share a challenge I encountered while asking AI to help organize my Design System:</em></blockquote><blockquote><em>Should component tokens be managed in a single, centralised file — or split by UI component?</em></blockquote><p>This seemingly small decision around file structure had significant implications for collaboration, scalability, and maintainability. Based on discussions with engineers, I’ll walk through both approaches and explain which direction we ultimately chose — and why.</p><h3>This article is suitable for a UX/UI designer who’s curious about…</h3><ul><li>How engineers think about Design System file structures</li><li>Using AI to speed up your design-to-code workflow</li></ul><h3>Project Background</h3><h4>Project Goal</h4><p>This project started entirely from scratch, with a small team and limited resources. Our goal was to accelerate development as much as possible while still maintaining a consistent product style and long-term scalability. To support this, we decided to build a Design System from the beginning to make future maintenance and reuse easier.</p><h4>Tech Stack and AI Tool Selection</h4><figure><img alt="A visual illustration showing the workflow from v0.dev to code output. On the left is the v0.dev UI asking “What can I help you ship?”, with an orange arrow pointing to the right. On the right are code snippets including Tailwind CSS utility classes and React component code, along with Tailwind and React logos, representing the process of generating production-ready code from AI design input." src="https://cdn-images-1.medium.com/max/1024/1*M3sEzM3BZiD_x0kLJQ7OLQ.png" /></figure><p>We chose <a href="https://tailwindcss.com/"><strong>Tailwind CSS</strong></a> as our design and development framework to ensure visual consistency and flexible development. Tailwind is widely adopted by developers and offers enough flexibility to compose UI components with utility-first classes quickly.</p><p>To streamline the design-to-code process, we also experimented with AI collaboration. Specifically, we used <a href="https://v0.dev/"><strong>v0.dev</strong></a>, an AI tool that can generate clean, semantic Tailwind + React code based on design input. This allowed us to prototype and deliver components ready for handoff rapidly.</p><h4>Design Tokens Strategy</h4><figure><img alt="A collage of Tailwind CSS utility class documentation screenshots, showing categories like font-size, font-weight, margin, padding, border-width, width, border-radius, border-color, color, and background-color, including their class names and rendered styles. Demonstrates Tailwind’s utility-first approach as a design token source." src="https://cdn-images-1.medium.com/max/1024/1*U5wqPQEJtzWJTt7zU2DGgw.png" /></figure><p>For this project, I didn’t create an additional set of semantic tokens. Instead, I relied directly on Tailwind CSS’s rich set of utility classes to quickly compose the UI components used throughout the system. Tailwind’s class names are already semantically meaningful and flexible enough, saving me the time to define an extra semantic layer and allowing me to move straight into component development.</p><p>However, when I started using AI to help organise the component files, a new question came up:</p><blockquote><strong>How should these Tailwind-based styles effectively function as Component Tokens be managed?</strong></blockquote><p>That led me to a key decision point:</p><blockquote><em>Should all Component Tokens be stored in a single, centralised file like </em><em>component-tokens.js?</em></blockquote><blockquote><em>Or should each UI component have its own token file (e.g., </em><em>button-tokens.js) stored alongside the component code?</em></blockquote><p>This isn’t just a question of file organisation — it has real implications for how engineering teams maintain and scale the system over time. To explore the best approach, I spoke with several engineers and compared the pros and cons of both methods, which I’ll break down next.</p><h3>Centralised vs. Modular File Structures</h3><p>At first, I asked AI to generate a single Component Tokens file that centralised all UI styles in one place. This approach worked well during the early stage of the system, when there were only a few components. But as the number of components grew, the file became more complicated to manage, and it became increasingly difficult to locate and update specific styles.</p><p>That led me to reconsider whether <strong>a per-component file structure</strong> might be more maintainable, where each component would have its dedicated token file. To better understand the practical trade-offs, I asked a few engineers how they would approach it.</p><p>Based on those conversations, I’ve summarised the pros and cons of both approaches below:</p><figure><img alt="A side-by-side comparison of two file structure diagrams. The left is labelled “Centralised Management,” where all UI component styles are stored in a single component-tokens.tsx file. The right is labelled “Per-Component Management,” showing each component (e.g., buttons, cards) with its own *-tokens. The tsx file is placed alongside its implementation files in the same folder." src="https://cdn-images-1.medium.com/max/1024/1*Eh972yV4FOfp_vEfKGtcaw.png" /></figure><h4>1. Centralised Management</h4><blockquote><em>All component tokens are written in a single file, e.g., </em><em>component-tokens.js</em></blockquote><p><strong>Pros</strong></p><ul><li>Ideal for early-stage design systems with fewer components</li><li>Centralised style definitions make it easy to search and apply global updates</li><li>Engineers only need to access one file to see all UI styles</li></ul><p><strong>Cons</strong></p><ul><li>As the number of components increases, the file becomes large and hard to navigate</li><li>Updating one component’s style may inadvertently affect others</li><li>Requires strict naming discipline to avoid conflicts between tokens</li></ul><h4>2. Per-Component Management</h4><blockquote><em>Each component has its own token file (e.g., button-tokens.js) stored alongside its implementation files</em></blockquote><p><strong>Pros</strong></p><ul><li>Clear structure that scales well as the number of components grows</li><li>Updates are isolated to specific components, reducing risk</li><li>Enables version control and refinement at the component level</li><li>Aligns better with atomic design and modular development practices</li></ul><p><strong>Cons</strong></p><ul><li>New designers or engineers need to understand the file structure first</li><li>Engineers may need to reference multiple files to collect the styles used on a page</li></ul><h3>Final Implementation</h3><h4>Choosing Per-Component Management</h4><p>After discussing with the engineering team, we ultimately decided to go with a <strong>per-component management</strong> approach for organising our Component Tokens. This method allows each UI component to have a clear, modular structure that’s easier to maintain, update, and scale over time.</p><p>Here’s an overview of our current file structure:</p><pre>|-- ui // UI components<br>  |-- components<br>    |-- buttons<br>    |-- button-tokens.tsx // Shared styles for button components<br>    |-- button.tsx // Default button content<br>    |-- icon-button.tsx // Icon button content<br>    |-- index.ts // Export barrel<br>  |-- cards<br>    |-- card-tokens.tsx // Shared styles for card components<br>    |-- base-card.tsx // Base card content<br>    |-- feature-card.tsx // Feature card content<br>    |-- index.ts // Export barrel<br>  |-- ... // Other components<br>|-- lib<br> |-- base-tokens.tsx // Global styles shared across the system<br> |-- index.ts // Export barrel</pre><p>This structure ensures that each component’s style definitions live alongside its functional logic, simplifying ongoing maintenance. If we need to define cross-component styles in the future, such as consistent typography (h1, h2, body1, etc.)—we can extract them into a global base-tokens.tsx file to promote consistency and reusability across the system.</p><p>Through this experience of building a Design System with the help of AI tools, I also gained valuable insights from an engineering perspective, especially around managing component-level styles effectively. I hope this article is helpful for other designers who, like me, often find themselves working at the intersection of design and development.</p><p>If you found this article helpful, please show your support with a clap and share it with friends who might be interested.</p><p>If you’d like to learn more about Design Systems, feel free to contact me!</p><p><a href="https://www.linkedin.com/in/yin-ling-mack/">LinkedIn</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0c09fe402534" width="1" height="1" alt=""><hr><p><a href="https://www.designsystemscollective.com/component-tokens-management-0c09fe402534">What I Learned About Token Management While Letting AI Build My Design System</a> was originally published in <a href="https://www.designsystemscollective.com/">Design Systems Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[我讓 AI 幫我建立 Design System，從中學到的 Token 管理思維]]></title>
            <link>https://medium.com/design-systems-collective-tw/component-tokens-management-8b3e125218d1?source=rss-a0521af3ea94------2</link>
            <guid isPermaLink="false">https://medium.com/p/8b3e125218d1</guid>
            <category><![CDATA[design-to-code]]></category>
            <category><![CDATA[ux-ui-product-designer]]></category>
            <category><![CDATA[component-tokens]]></category>
            <category><![CDATA[design-systems]]></category>
            <category><![CDATA[design-engineer]]></category>
            <dc:creator><![CDATA[Yin-Ling Mack]]></dc:creator>
            <pubDate>Tue, 13 May 2025 15:52:35 GMT</pubDate>
            <atom:updated>2025-05-14T08:50:12.431Z</atom:updated>
            <content:encoded><![CDATA[<h4>Component Tokens 的管理方式：集中還是分開管理？</h4><figure><img alt="封面圖展示文章副標題『Component Tokens 的管理方式：集中還是分分開管理？』，下方圖示為一個單一資料夾 component-tokens 對比兩個分開資料夾 button-tokens 與 card-tokens，中間以 ‘vs.’ 作為視覺比較。" src="https://cdn-images-1.medium.com/max/1024/1*l3VC0iIf9fyMxD5CosSm4g.png" /></figure><p>語言 / Language : 中文 | <a href="https://medium.com/@mackyinling1215/component-tokens-management-0c09fe402534"><strong>English</strong></a></p><p>最近開始嘗試使用 AI 工具來提升設計工作的效率，也思考著如何讓設計轉交給工程團隊時能更順暢。剛好最近手上有一個從 0 開始的專案，我就把已完成的幾個 UI 元件風格與設計介面從 Figma 匯入到 AI 工具中，並請它幫我生成初版頁面並同時建立此系統的 Design System。</p><p>在這過程中，我發現自己常常需要反覆檢查AI 產出的檔案，我也常常思考這些檔案真的可以直接交給工程師嗎？它所建立的結構，是否符合真正的團隊開發流程與維護習慣？</p><blockquote><em>這篇文章想分享的是，在我請 AI 協助整理 Design System 中的 Component Tokens 時，意外遇到了一個通常是工程師們才會面對的問題：</em><strong><em>這些 tokens 應該集中放在一個檔案中統一管理，還是應該依據 UI 元件拆分成多個檔案？</em></strong></blockquote><p>這個看似簡單的檔案結構選擇，其實會影響到之後工程團隊的系統維護與擴充。在這篇文章我會分享關於我與工程師們討論後這兩種做法的分析，也會說明最後團隊選擇的方法與背後的考量。</p><h4>適合閱讀此文章的對象：</h4><p><strong>UX UI 產品設計師想要…</strong></p><ul><li>了解工程師如何整理 Design System 檔案</li><li>利用 AI 工具協助建立 Design System</li></ul><h3>專案背景</h3><h4>專案目標</h4><p>這是一個從 0 開始開發的專案，團隊資源有限，因此希望能盡可能加快開發速度，同時保有產品的風格一致性與長期可維護性。所以，我們決定從一開始就建立 Design System，方便之後的擴充與重複使用。</p><h4>技術框架與 AI 工具選擇</h4><figure><img alt="圖像展示 v0.dev 的介面截圖與其輸出結果的流程圖。左側為 v0.dev 的輸入介面畫面，中間用橘色箭頭連接，右側則顯示由 v0.dev 產出的 Tailwind CSS 樣式程式碼與 React 元件程式碼，並搭配 Tailwind 與 React 的標誌，代表從設計輸入到程式輸出的過程。" src="https://cdn-images-1.medium.com/max/1024/1*M3sEzM3BZiD_x0kLJQ7OLQ.png" /></figure><p>為了確保產品具有一致的視覺風格與靈活的開發彈性，我們選擇使用 <a href="https://tailwindcss.com/"><strong>Tailwind CSS</strong></a> 作為設計與開發上的工具。Tailwind 是許多工程師熟悉的工具，同時也具備良好的設計自由度，可以快速搭建 UI 元件。</p><p>在設計轉成程式碼的過程中，我嘗試導入 AI 協作，所以選擇了 <a href="https://v0.dev/"><strong>v0.dev</strong></a> 作為生成工具。這個工具可以根據設計稿產出語意清晰且乾淨的 Tailwind + React 程式碼，幫助我們快速建立可交付的元件與頁面。</p><h4>Design Tokens 規劃</h4><figure><img alt="多張 Tailwind CSS 公用樣式截圖排版而成，包含 font-size、font-weight、margin、padding、border-width、width、border-radius、border-color、color、background-color 等類別與對應的 class name 和 CSS 效果，用來說明 Tailwind 的實用性與可作為設計 tokens 的基礎。" src="https://cdn-images-1.medium.com/max/1024/1*U5wqPQEJtzWJTt7zU2DGgw.png" /></figure><p>在這個專案中，我並沒有另外建立 Semantic Tokens，而是直接使用 Tailwind CSS 提供的豐富 class，並快速組成系統內的 UI 元件。Tailwind 本身的語意命名已經具備足夠的清晰度與彈性，因此可以省下建立 Semantic Tokens 的時間成本，並快速進入 UI 元件開發階段。</p><p>但當我開始利用 AI 整理這些 UI 元件檔案時，也開始思考：</p><blockquote><strong>這些以 Tailwind class 為基礎組合出來的 UI 元件樣式（可視為Component Tokens），應該如何管理？</strong></blockquote><p>所以，我面臨的問題是：</p><blockquote><em>應該集中將所有Component Tokens 寫在一個統一的 </em><em>component-tokens.js 檔案中？</em></blockquote><blockquote><em>還是應該依照每個 UI 元件拆分成獨立檔案（例如 </em><em>button-tokens.js），並與該元件的相關程式碼放在一起？</em></blockquote><p>這不只是檔案架構的選擇，更直接影響到工程團隊在維護與擴充上的效率。因此我與工程師們深入討論後，整理了這兩種方式的優缺點比較，供大家參考。</p><h3>Component Tokens 檔案管理方式比較</h3><p>一開始我請 AI 產出一個統一的 Component Tokens 檔案，將所有元件的樣式集中管理。這種做法在元件數量少的階段確實方便有效，但隨著元件不斷增加，我漸漸發現這個檔案變得愈來愈龐大，也愈來愈難快速找到需要調整的特定元件樣式。</p><p>因此我開始思考是否應該改為「依元件分檔管理」，讓每個元件都有自己專屬的 tokens 檔案。為了了解更實際的開發需求，我也詢問了工程師們的做法。</p><p>為了讓大家能根據各自團隊的需求，選擇最適合的方式，我整理了「集中管理」與「分元件管理」兩種做法的優缺點比較如下：</p><figure><img alt="兩個並排的程式檔案結構圖，左側標示為「集中管理」，顯示所有 UI 元件樣式統一放在 component-tokens.tsx 中；右側標示為「分元件管理」，顯示每個元件（如按鈕、卡片）有各自的 *-tokens.tsx 樣式檔案，並與元件程式碼放置在同一資料夾中。" src="https://cdn-images-1.medium.com/max/1024/1*PTW_miYTVgCmjy1fJ43tRw.png" /></figure><h4>1. 集中管理</h4><blockquote><em>將所有元件的 tokens 統一寫在一個檔案中，例如 </em><em>component-tokens.js</em></blockquote><p><strong>優點</strong></p><ul><li>適合設計系統初期，元件數較少時使用</li><li>所有元件樣式集中管理，方便統一查找與修改</li><li>只需從單一檔案讀取，即可取得所有元件的樣式資訊</li></ul><p><strong>缺點</strong></p><ul><li>元件數量增加時，檔案會變得很龐大，查找與維護困難</li><li>修改某元件樣式時，需小心避免影響到其他元件</li><li>Token 命名需嚴格控管，避免與其他元件重複</li></ul><h4>2. 分元件管理</h4><blockquote><em>每個元件有自己獨立的 token 檔案，例如 </em><em>button-tokens.js，並與該元件放在相同資料夾中</em></blockquote><p><strong>優點</strong></p><ul><li>結構清晰，元件數量增加時仍易於維護與查找</li><li>修改元件樣式時，影響範圍清楚，降低風險</li><li>可針對單一元件進行版本控制與調整</li><li>更符合原子化設計與模組化開發，可以重複使用以建立好的元件</li></ul><p><strong>缺點</strong></p><ul><li>新進設計師或工程師需熟悉檔案架構</li><li>在開發頁面時，可能需從多個檔案中擷取不同元件的樣式資訊</li></ul><h3>實踐結果</h3><h4>使用分元件管理</h4><p>經過與工程師們的討論，我們最終選擇採用<strong>分元件管理</strong>的方式來組織 Component Tokens。這樣的做法讓每個 UI 元件都具備清楚的樣式邏輯與結構，方便版本控管與日後擴充。</p><p>以下是目前的檔案結構示意：</p><pre>|-- ui // UI元件<br>  |-- components<br>    |-- buttons<br>    |-- button-tokens.tsx // 按鈕元件共用樣式<br>    |-- button.tsx // 一般按鈕內容<br>    |-- icon-button.tsx // 圖示按鈕內容<br>    |-- index.ts // 統一匯出 (export barrel)<br>  |-- cards<br>    |-- card-tokens.tsx // 卡片元件共用樣式<br>    |-- base-card.tsx // 基本卡片內容<br>    |-- feature-card.tsx // 功能卡片內容<br>    |-- index.ts // 統一匯出 (export barrel)<br>  |-- ... // 其他元件<br>|-- lib<br> |-- base-tokens.tsx // 整個系統共用樣式<br> |-- index.ts // 統一匯出 (export barrel)</pre><p>這種檔案組織方式讓每個元件的樣式定義與功能邏輯共存於同一資料夾中，方便日後的維護與管理。若未來有跨元件共用的樣式需求，也可以另外抽出一個 base-tokens.tsx 作為 global tokens 使用，例如定義常用的文字樣式（如 h1、h2、body1 等），進一步提升系統一致性與可重用性。</p><p>透過這次用 AI 工具建立 Design System 的經驗，也從工程師的角度學習到了許多關於元件樣式管理的實務觀點，希望這篇文章能對同樣在設計又碰到一點開發的設計師有所幫助。</p><p>如果這篇文章對你有幫助，歡迎給予拍手鼓勵，也請分享給可能會感興趣的朋友。</p><p>想了解更多關於 Design System 的內容，歡迎與我聯繫！</p><p><a href="https://www.linkedin.com/in/yin-ling-mack/">LinkedIn</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8b3e125218d1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-systems-collective-tw/component-tokens-management-8b3e125218d1">我讓 AI 幫我建立 Design System，從中學到的 Token 管理思維</a> was originally published in <a href="https://medium.com/design-systems-collective-tw">Design Systems TW</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Accessibility design 101: A quick introduction to A11y and WCAG]]></title>
            <link>https://medium.com/design-bootcamp/accessibility-wcag-design-101-a25898952655?source=rss-a0521af3ea94------2</link>
            <guid isPermaLink="false">https://medium.com/p/a25898952655</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[web-accessibility]]></category>
            <category><![CDATA[wcag]]></category>
            <category><![CDATA[a11y]]></category>
            <dc:creator><![CDATA[Yin-Ling Mack]]></dc:creator>
            <pubDate>Mon, 05 May 2025 11:18:01 GMT</pubDate>
            <atom:updated>2025-05-05T15:51:40.080Z</atom:updated>
            <content:encoded><![CDATA[<h4>A brief guide to the EU’s 2025 focus on accessibility and the core principles of WCAG POUR</h4><figure><img alt="Cover image for an article titled “Introduction to Accessibility Design: A Quick Guide to A11y and WCAG”" src="https://cdn-images-1.medium.com/max/1024/1*fMwTVvfQTTqyG0PLgL9R2g.png" /></figure><p>Language / 語言 : <em>English</em> | <a href="https://medium.com/@mackyinling1215/accessibility-wcag-design-guide-60cb2fe90ccb"><strong>中文</strong></a></p><p>Lately, I’ve noticed many designers and digital marketers working on EU-related products actively aligning with the new WCAG accessibility regulations.</p><p>This made me realize that accessibility design is no longer just a UX/UI concern — it’s becoming a core competency every digital product team should understand.</p><h3>Why has accessibility design become an increasing focus for businesses in the EU?</h3><p>In 2024, the European Union announced that starting in June 2025, many digital products and services will be required to comply with <strong>WCAG 2.1 Level AA</strong> accessibility standards.</p><p>As a result, organizations across industries have started preparing to ensure their digital experiences meet these upcoming requirements.</p><blockquote><em>This article offers a practical overview of </em><strong><em>what accessibility design (A11y) means</em></strong><em>, and how the </em><strong><em>WCAG framework</em></strong><em> can be applied in real-world product development.</em></blockquote><h3><strong>Who is this article for?</strong></h3><h4><strong>For UX UI designers who want to:</strong></h4><ul><li>Understand the core principles of accessibility</li><li>Start designing digital products that align with WCAG standards</li></ul><h4><strong>For digital marketers who want to:</strong></h4><ul><li>Ensure their company websites meet regulatory requirements and are WCAG-compliant</li></ul><h3>What is accessibility design?</h3><figure><img alt="Conceptual illustration of accessibility design features, including visual icons, font sizing, button interactions, contrast adjustment, and an accessibility symbol." src="https://cdn-images-1.medium.com/max/1024/1*TNibF5a5tbYqGAyvlisTFg.png" /></figure><p>At its core, <strong>accessibility design aims to ensure that everyone can effectively use a product or service.</strong> This means taking into account users with different needs and usage contexts during the design process.</p><p>For example:</p><ul><li>For <strong>older adults</strong>, interfaces should allow text enlargement without causing layout issues.</li><li>For <strong>users with color vision deficiencies (color blindness)</strong>, content and background must have sufficient contrast to support readability and prevent confusion.</li></ul><h3>Key user groups and design considerations</h3><h4>1. Users with visual impairments</h4><ul><li><strong>Users with color vision deficiencies</strong>: Rely on color contrast to distinguish information</li><li><strong>Blind users</strong>: Use screen readers to access content on websites or in videos</li></ul><h4>2. Users with hearing impairments</h4><p>Provide complete textual alternatives and use visual cues (such as alerts or icons) to compensate for the lack of auditory information.</p><h4>3. Older adults</h4><p>Designs should account for age-related changes in vision and motor skills. Interfaces should allow users to adjust text size as needed and include large buttons and intuitive layouts to lower the barrier to interaction.</p><h4>4. Users with cognitive or learning disabilities</h4><p>This group includes individuals who face challenges with understanding, memory, attention, or processing information — for example, those with learning disabilities, attention disorders, intellectual disabilities, or memory impairments.</p><p>Interfaces should avoid overly complex language or layouts, and maintain consistent logic to support ease of use.</p><h4>5. Users with temporary impairments</h4><p>Designs should also support users in specific temporary contexts, such as operating a device with one hand or using it in noisy or quiet environments.</p><h3>What is WCAG (Web content accessibility guidelines)?</h3><p><strong>WCAG</strong>, or the <strong>Web Content Accessibility Guidelines</strong>, is an international standard developed by the <strong>W3C</strong> specifically for making web content accessible. <strong>Its core goal is to ensure that all people — including those with disabilities — can access and use web content equally and effectively.</strong></p><blockquote><strong><em>“The power of the Web is in its universal. Access by everyone regardless of disability is an essential aspect.” </em></strong><em><br>— Tim Berners-Lee, W3C Director and inventor of the World Wide Web</em></blockquote><p>The latest version of WCAG is <strong>2.2</strong>, but <strong>WCAG 2.0</strong>, <strong>2.1</strong>, and <strong>2.2</strong> are all valid. Beginning in <strong>June 2025</strong>, the <strong>European Union</strong> will mandate compliance with <strong>WCAG 2.1 Level AA</strong> as the minimum requirement for digital accessibility.</p><h4>WCAG defines three levels of accessibility compliance:</h4><ul><li><strong>Level A</strong>: Basic requirements that address the most critical accessibility barriers</li><li><strong>Level AA</strong>: Intermediate requirements and the <strong>minimum standard</strong> adopted by most organizations and regulations</li><li><strong>Level AAA</strong>: The highest level of accessibility, covering more detailed needs — <strong>often not required by law</strong></li></ul><figure><img alt="Illustration of the four WCAG accessibility principles: Perceivable, Operable, Understandable, and Robust, each represented with an icon." src="https://cdn-images-1.medium.com/max/1024/1*6LD0BnwhOsfoSKBgF1UaTA.png" /></figure><h4>The four core principles of WCAG (POUR):</h4><ol><li><strong>Perceivable : </strong>Information must be presented in ways users can perceive</li><li><strong>Operable : </strong>User interface components must be usable via various input methods</li><li><strong>Understandable</strong> : Information and operation must be clear and predictable</li><li><strong>Robust</strong> : Content must be compatible with a wide range of devices and assistive technologies</li></ol><h3>Page-level accessibility guidelines</h3><h4>1. Page title</h4><figure><img alt="Browser tab showing the page title “YinLing Mack | UX UI Product Designer,” highlighting the importance of setting a clear and descriptive page title." src="https://cdn-images-1.medium.com/max/1024/1*I5iIWSsCFXMhs-qVYgB2cA.png" /></figure><p>To enhance a webpage’s <strong>Perceivability</strong>, each page should have a clear, descriptive title. This title appears in the browser tab and is typically the first element read aloud by screen readers when the page loads.</p><p><strong>Purpose</strong>:</p><ul><li>Helps <strong>visually impaired users</strong> quickly identify which page they are on using a screen reader</li><li>Allows <strong>general users</strong> to easily distinguish between open pages in their browser</li></ul><p><strong>Recommended practice</strong>:</p><ul><li>Use concise, meaningful language to describe the main content of the page — for example:</li><li><strong>“YinLing Mack | UX UI Product Designer”</strong>, rather than generic titles like <strong>“Home”</strong> or <strong>“Products”</strong>.</li></ul><h4>2. Skip link</h4><figure><img alt="“Skip to main content” link appears after pressing the Tab key, allowing keyboard users to bypass navigation and access the main content directly." src="https://cdn-images-1.medium.com/max/1024/1*yQfgZkR9HabNrymOoSLx_Q.png" /></figure><p>To enhance a webpage’s <strong>Operability</strong>, it’s recommended to include a hidden navigation shortcut that allows users to bypass repetitive content (such as navigation menus) and jump directly to the main content area.</p><p>This feature is primarily designed for users who navigate using a <strong>keyboard</strong> or <strong>screen reader</strong>. It is typically hidden by default and only becomes visible when the user presses the <strong>Tab</strong> key.</p><p><strong>Purpose</strong>:</p><p>Helps users avoid repeatedly pressing the <strong>Tab</strong> key by allowing them to jump directly to the main content, improving navigation efficiency.</p><p><strong>Recommended link text</strong>:</p><p>Use clear, descriptive text such as <strong>“Skip to main content”</strong>.</p><h4>3. Language</h4><figure><img alt="Language switcher displayed at the top right of a webpage, offering English, Chinese, and Japanese options — illustrating accessible language selection." src="https://cdn-images-1.medium.com/max/1024/1*HsnETZE_KQ4SetHOHjuQ_A.png" /></figure><p>To improve a website’s <strong>Understandability</strong>, each page should declare a <strong>default language</strong> and, if the site is multilingual, provide a clear and accessible way to switch between languages.</p><p>This helps screen readers pronounce content correctly and enhances the overall user experience for people navigating across languages.</p><p><strong>Purpose</strong>:</p><ul><li>Allows <strong>screen readers</strong> to interpret and pronounce content based on the correct language setting (e.g., preventing German text from being read with an English voice)</li><li>Provides a clear language switch for multilingual sites, so users can choose the interface that best suits them</li></ul><p><strong>Recommended practice</strong>:</p><p>When offering language options, <strong>use language names (e.g., “English”, “Deutsch”) instead of flag icons</strong></p><ul><li>Flags can be misleading (e.g., English ≠ United Kingdom)</li><li>Text labels are clearer and more accessible for assistive technologies</li></ul><h4>4. Zoom levels</h4><figure><img alt="Side-by-side comparison of a webpage at original size and at 200% zoom, illustrating responsive layout and readable text for visual accessibility." src="https://cdn-images-1.medium.com/max/1024/1*oKu9L601iy4w4ipwqGBl1g.png" /></figure><p>To support both <strong>Perceivability</strong> and <strong>Operability</strong>, designs should allow users to adjust text size and content scaling according to their needs — while ensuring that the interface remains clear, usable, and free from layout issues even when zoomed in.</p><p>This is especially important for <strong>users with low vision or for older adults</strong>, helping them read and interact with content more comfortably.</p><p><strong>Purpose</strong>:</p><ul><li>Allows users with visual impairments or aging-related needs to enlarge content without compromising the usability of the page</li><li>Ensures that content reflows properly when zoomed, avoiding the need for horizontal scrolling</li></ul><p><strong>Accessibility requirement</strong>:</p><p>According to <strong>WCAG 2.1 Level AA</strong>, websites must support zooming up to <strong>200%</strong> without requiring assistive technologies — while maintaining access to all content and functionality, without causing overlap, hidden elements, or horizontal scrolling.</p><h4>5. Color contrast</h4><figure><img alt="Comparison of two sets of buttons showing text and background contrast. One meets WCAG AA standards (5.37:1), the other fails (1.73:1)." src="https://cdn-images-1.medium.com/max/1024/1*66_R2D9Ze0lakX0AijwZrQ.png" /></figure><p>To enhance a website’s <strong>Perceivability</strong>, content and background colors must have sufficient contrast to ensure readability and usability for <strong>all users — especially those with color vision deficiencies or age-related vision loss.</strong></p><p>When text and background colors (or buttons and their surroundings) lack adequate contrast, users may have difficulty identifying information or miss important visual cues, which can impact overall usability.</p><p><strong>Purpose</strong>:</p><ul><li>Helps users with color vision impairments or reduced vision distinguish text and interface elements clearly</li><li>Improves readability in various environments, such as bright outdoor settings</li></ul><p><strong>Contrast requirements (WCAG 2.1 Level AA)</strong>:</p><ol><li><strong>Regular text</strong>: Minimum contrast ratio of <strong>4.5:1</strong></li><li><strong>Large text</strong> (18pt or 14pt bold and above): Minimum contrast ratio of <strong>3:1</strong></li><li><strong>Non-text elements</strong> (e.g., icons, button borders): Recommended minimum contrast ratio of <strong>3:1</strong></li></ol><p><strong>Check your contrast</strong>:</p><p>Use free online tools such as the <a href="https://webaim.org/resources/contrastchecker/"><strong>WebAIM Contrast Checker</strong></a> to quickly evaluate the contrast ratio between two colors.</p><p>These tools will also indicate whether your contrast meets <strong>WCAG Level AA</strong> or <strong>AAA</strong> standards.</p><h4>6. Visible keyboard focus</h4><figure><img alt="After pressing the Tab key, keyboard focus is shown on the “About me” button in the navigation bar — illustrating visible focus for keyboard users." src="https://cdn-images-1.medium.com/max/1024/1*SjQftCXJ-3Jkm4jRLk1e4g.png" /><figcaption>After pressing the Tab key, keyboard focus is shown on the “About me” button in the navigation bar.</figcaption></figure><p>To support both <strong>Perceivability</strong> and <strong>Operability</strong>, all interactive elements — such as buttons, links, and form fields — should clearly indicate when they are focused through keyboard navigation.</p><p>This is a fundamental accessibility feature for users who cannot use a mouse and rely on the keyboard to navigate websites.</p><p><strong>Purpose</strong>:</p><ul><li>Allows <strong>keyboard users</strong> to easily identify which element is currently focused, so they can navigate and interact with confidence</li><li>Helps <strong>all users</strong> understand whether an element is interactive (e.g., a button or a link)</li></ul><p><strong>Implementation tip</strong>:</p><p>When users navigate using the <strong>Tab</strong> key, the focused element should be visually highlighted—such as with a visible outline or border.</p><h4>7. Headings</h4><figure><img alt="Webpage showing HTML tags like h1, h2, and button, illustrating how semantic structure supports screen reader navigation." src="https://cdn-images-1.medium.com/max/1024/1*yhhDddoZCW0P00Mz6b-6IQ.png" /></figure><p>To support both <strong>Perceivability</strong> and <strong>Understandability</strong>, page content should follow a <strong>meaningful hierarchical structure</strong>, using semantic HTML elements (such as h1, h2, p, etc.) to reflect the correct levels and order of information.</p><p>This not only helps screen readers interpret and announce content properly, but also improves the overall clarity and scanability of the page for all users.</p><p><strong>Purpose</strong>:</p><ul><li>Enables <strong>visually impaired users</strong> to understand the structure and main topics of the page using a screen reader</li><li>Enhances readability, allowing all users to quickly scan and comprehend content</li></ul><p><strong>Implementation tips</strong>:</p><ul><li>Each page should have <strong>one — and only one — </strong><strong>h1</strong> as the main title</li><li>Use h2, h3, etc. to reflect content hierarchy, and <strong>avoid skipping levels</strong> (e.g., don’t jump from h1 to h4)</li><li>Use appropriate semantic tags for non-heading content (e.g., use p for paragraphs, rather than using div to mimic headings)</li></ul><h4>8. Status messages</h4><p>To support <strong>Perceivability</strong>, <strong>Understandability</strong>, and <strong>Robustness</strong>, interfaces must be designed so that assistive technologies — such as screen readers — can accurately announce all <strong>status messages and real-time content changes</strong>.</p><p>These include error alerts, form submission confirmations, system notifications, loading indicators, and more.</p><p>If these messages are not properly implemented, users with visual impairments may be unaware of important changes on the page — leading to confusion, incorrect actions, or task failure.</p><p><strong>Purpose</strong>:</p><ul><li>Helps <strong>screen reader users</strong> understand dynamic updates and status changes in real time</li><li>Ensures all system feedback (e.g., success, error, warnings) is recognizable and can be reliably announced by assistive tools</li></ul><h3>Image guidelines</h3><h4>1. Alternative text (alt text)</h4><p>To support <strong>Perceivability</strong>, all non-text content — such as images, icons, and decorative elements — should include <strong>alternative text (alt text)</strong>. This ensures that when images fail to load or are accessed via screen readers, users can still understand the intended meaning or content.</p><p><strong>Purpose</strong>:</p><ul><li>Helps <strong>visually impaired users</strong> understand the purpose and content of images through screen readers</li><li>Provides a textual fallback when images cannot be displayed (e.g., due to network issues)</li></ul><p><strong>Writing tips</strong>:</p><p>Use concise and clear descriptions that convey the <strong>information or meaning</strong> of the image.</p><p>For example:</p><blockquote>⭕️ <em>“A woman sunbathing on a balcony”</em></blockquote><blockquote>❌ <em>“This is an image”</em></blockquote><h4>2. Avoid text in images</h4><p>To support <strong>Perceivability</strong>, avoid embedding important text directly within images. Unless absolutely necessary — such as for logos or chart labels — informational text should be presented using actual HTML text rather than image-based text.</p><p>Text embedded in images can cause readability issues when zoomed, translated, or accessed via screen readers. It also creates barriers for users with visual impairments.</p><p><strong>Purpose</strong>:</p><ul><li>Ensures that <strong>visually impaired users</strong> can access all important information through screen readers</li><li>Prevents layout and readability problems in various viewing contexts (e.g., zoomed-in views, slow networks)</li></ul><h3>Video guidelines</h3><h4>1. Audio control</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4Q7c9cY7722OXStaeKJe8g.png" /></figure><p>To support <strong>Operability</strong>, any audio content that plays automatically must include <strong>accessible and user-friendly controls</strong>. Users should be able to pause, stop, or adjust the volume at any time to prevent disruption — especially for screen reader users, who may experience interference from unexpected sound.</p><p><strong>Purpose</strong>:</p><ul><li>Prevents autoplay audio from interfering with screen readers or other assistive technologies</li><li>Allows users to manage audio based on their environment (e.g., libraries, offices, commuting)</li></ul><p><strong>Design suggestions</strong>:</p><ul><li>Avoid autoplaying audio whenever possible</li><li>Provide clear and visible control options, such as: <strong>Play / Pause, Volume adjustment and Mute</strong></li></ul><h4>2. Captions / Subtitles</h4><figure><img alt="Captions displayed at the bottom of a video player, illustrating how on-screen text helps deaf users or those in silent environments understand the content." src="https://cdn-images-1.medium.com/max/1024/1*0PvRjHyMPY-0FPDkB-KlaQ.png" /></figure><p>To support <strong>Perceivability</strong> and <strong>Understandability</strong>, all video and audio content should include captions. For live content — such as real-time broadcasts or virtual meetings — <strong>live captions</strong> should be provided whenever possible to ensure that deaf and hard-of-hearing users can access the information in real time.</p><p>Captions also benefit general users who are in sound-off environments (e.g., during commutes or in public spaces), helping them understand the video without audio.</p><p><strong>Purpose</strong>:</p><ul><li>Enables <strong>deaf and hard-of-hearing users</strong> to follow spoken content and dialogue in videos</li><li>Helps <strong>general users</strong> comprehend video content in situations where audio playback isn’t practical</li></ul><h4>3. Transcriptions</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_eeyvnm0xLweaw1q_zf6_g.png" /></figure><p>To support <strong>Perceivability</strong> and <strong>Understandability</strong>, all pre-recorded video or audio content should be accompanied by a <strong>transcript</strong>.</p><p><strong>Purpose</strong>:</p><p>Enables <strong>deaf users</strong> or anyone who prefers to read content to fully understand audio or video material through plain text.</p><h3>4. Audio description</h3><p>To support <strong>Perceivability</strong> and <strong>Understandability</strong>, pre-recorded video content should include <strong>audio descriptions</strong>. This is an accessibility feature designed for users who are blind or have low vision. It inserts spoken narration between the original audio to describe key visual elements — such as actions, scenes, facial expressions, and other non-verbal content.</p><p><strong>Purpose</strong>:</p><p>Helps <strong>visually impaired users</strong> understand <strong>non-verbal information</strong> in a video — such as gestures, environmental changes, on-screen text, or charts — so they can fully comprehend the content without relying on visuals.</p><h3>Differences between captions, transcriptions, and audio descriptions</h3><p><strong>Target audience</strong>:</p><ul><li><strong>Captions</strong>: For deaf or hard-of-hearing users, or viewers in silent environments</li><li><strong>Transcriptions</strong>: For deaf users or those who prefer to read video/audio content</li><li><strong>Audio Descriptions</strong>: For blind or visually impaired users</li></ul><p><strong>Presentation style</strong>:</p><ul><li><strong>Captions</strong>: <br>Text appears <strong>synchronized with the video</strong>, directly within the video frame</li></ul><pre>// Captions are displayed in real-time as the video plays.<br><br>[Soft music playing]  <br>Host: Welcome, Ling.  <br>Ling: Thank you, I’m glad to be here.  </pre><ul><li><strong>Transcriptions:</strong> <br>A full-text record of the video or audio content, usually displayed separately and not time-synced</li></ul><pre>//  Transcripts are plain text and not synchronized with the video.<br><br>Host: Welcome, Ling.  <br>Ling: Thank you, I’m glad to be here.  <br>(Background music playing)  </pre><ul><li><strong>Audio Descriptions:</strong> <br>Spoken narration that describes visual information not covered in dialogue, inserted between original audio</li></ul><pre>// Audio description adds spoken narration to explain what’s happening on screen.<br><br>[Narrator] Ling pulls out a chair and sits down.  </pre><h3>Form field guidelines</h3><h4>1. Form field labels</h4><figure><img alt="Form field example showing default and error states for a password input. Error message reads “Password is too short. Please enter at least 8 characters.”" src="https://cdn-images-1.medium.com/max/1024/1*N6sm9BwXSr5CnZczZLaJOw.png" /></figure><p>In alignment with the principles of <strong>Operability</strong> and <strong>Understandability</strong>, all form fields should include <strong>clear and consistent labels</strong>. Additionally, when users make input errors, the system should provide <strong>specific, understandable error messages</strong> along with guidance on how to fix them.</p><p>Labels are not only important visual indicators — they are also essential for screen readers to correctly identify the function of each field. If the label element in the code does not match the visible content, assistive technologies may not be able to communicate the field’s purpose effectively.</p><p><strong>Purpose</strong>:</p><ul><li>Helps <strong>screen reader users</strong> understand the role of each input field</li><li>Clearly informs users of any input errors and how to resolve them</li></ul><p><strong>Design recommendation</strong>:</p><p>Error messages should specify both the field name and the issue, e.g., “Password is too short. Please enter at least 8 characters.”</p><h4>2. Required fields</h4><p>To support <strong>Understandability</strong>, all required fields in a form should be clearly indicated. If a required field is left blank or filled out incorrectly, the system should provide <strong>specific, actionable error messages</strong> along with guidance for correction.</p><p>For screen reader users, unclear requirements or vague error messages can significantly impact their ability to complete tasks successfully.</p><p><strong>Purpose</strong>:</p><ul><li>Helps both general users and screen reader users easily identify which fields are required</li><li>Clearly communicates what’s missing or incorrect and how to resolve it</li></ul><p><strong>Design recommendations</strong>:</p><ul><li>Visually and programmatically distinguish required fields from optional ones</li><li>Provide clear error messages that reference the field name and the issue, e.g., “Date of birth is required.”</li></ul><p>The content above introduces the <strong>fundamental concepts of Accessibility Design (A11y) and WCAG (Web Content Accessibility Guidelines).</strong></p><p>If you’d like to explore further, you can visit the <a href="https://www.w3.org/WAI/fundamentals/">official W3C accessibility website</a> for more resources and guidance.</p><h3>References</h3><ul><li>AccessibleEU :</li></ul><p><a href="https://accessible-eu-centre.ec.europa.eu/content-corner/news/eaa-comes-effect-june-2025-are-you-ready-2025-01-31_en">The EAA comes into effect in June 2025. Are you ready?</a></p><ul><li>W3C :</li></ul><p><a href="https://www.w3.org/WAI/fundamentals/">Accessibility Fundamentals Overview</a></p><ul><li>Evaluating Web Accessibility Overview from W3C :</li></ul><p><a href="https://www.w3.org/WAI/test-evaluate/">Evaluating Web Accessibility Overview</a></p><ul><li>Web Accessibility Perspective :</li></ul><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F3f31oufqFSM%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D3f31oufqFSM&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F3f31oufqFSM%2Fhqdefault.jpg&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/c01f45c09de3e73b168e2e9640f6d224/href">https://medium.com/media/c01f45c09de3e73b168e2e9640f6d224/href</a></iframe><ul><li>WebAIM Contrast Checker :</li></ul><p><a href="https://webaim.org/resources/contrastchecker/">Contrast Checker</a></p><p>If you found this article helpful, please show your support with a clap and share it with friends who might be interested.</p><p>If you’d like to learn more about UX UI Design, feel free to contact me!</p><p><a href="https://www.linkedin.com/in/yin-ling-mack/">LinkedIn</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a25898952655" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/accessibility-wcag-design-101-a25898952655">Accessibility design 101: A quick introduction to A11y and WCAG</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[無障礙設計入門：快速認識 A11y 與 WCAG]]></title>
            <link>https://medium.com/@mackyinling1215/accessibility-wcag-design-guide-60cb2fe90ccb?source=rss-a0521af3ea94------2</link>
            <guid isPermaLink="false">https://medium.com/p/60cb2fe90ccb</guid>
            <category><![CDATA[accessbility]]></category>
            <category><![CDATA[a11y]]></category>
            <category><![CDATA[wcag]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[web-accessibility]]></category>
            <dc:creator><![CDATA[Yin-Ling Mack]]></dc:creator>
            <pubDate>Fri, 02 May 2025 12:26:19 GMT</pubDate>
            <atom:updated>2025-05-05T13:56:34.334Z</atom:updated>
            <content:encoded><![CDATA[<h4>快速了解今年 (2025年) 歐盟對於無障礙設計 WCAG POUR 的核心理念</h4><figure><img alt="無障礙設計入門封面圖，標題為「無障礙設計 (Accessibility Design) 入門：快速認識 A11y 與 WCAG」" src="https://cdn-images-1.medium.com/max/1024/1*hJIQ2tlarFj4NndPeyK-aA.png" /></figure><p>語言 / Language : <em>中文</em><strong> </strong>| <a href="https://medium.com/@mackyinling1215/accessibility-wcag-design-101-a25898952655"><strong>English</strong></a></p><p>最近我和一位從事行銷的朋友聊天，她提到自己最近正因為無障礙設計相關的 WCAG 法規忙得焦頭爛額。這讓我意識到，無障礙設計（Accessibility Design）不再只是 UX/UI 設計師關心的議題，而是逐漸成為所有數位產品團隊都需要了解的基本能力。</p><h4>為什麼無障礙設計會成為歐盟境內企業近期關注的重點？</h4><p>歐盟在去年正式公告：<br><strong>從今年 (2025年) 6月起，許多產品與服務都需符合無障礙設計 WCAG (Web Content Accessibility Guidelines) 2.1 Level AA 的要求。</strong></p><p>因此，從去年開始，許多公司便已開始積極準備，以確保數位產品能符合即將上路的歐盟新規範。</p><blockquote>因此，這篇文章將帶你認識： 無障礙設計（Accessibility Design / A11y）與 WCAG 標準的基本概念與實務應用。</blockquote><h4><strong>適合閱讀此系列文章的對象：</strong></h4><p><strong>UX UI 產品設計師想要…</strong></p><ul><li>初步了解無障礙設計的原則與核心概念</li><li>開始設計符合 WCAG 標準的數位產品</li></ul><p><strong>行銷人員想要…</strong></p><ul><li>優化公司網站配合法規，確保內容符合 WCAG 要求</li></ul><h3>什麼是無障礙設計 (Accessibility Design)？</h3><figure><img alt="無障礙設計概念示意圖，包含視覺圖示、字體大小、按鈕操作、對比調整與可及性圖標。" src="https://cdn-images-1.medium.com/max/1024/1*DDCLjN0qBki09cS7VLn4ig.png" /></figure><p>無障礙設計的核心理念，是讓所有人都能順利使用產品與服務。也就是說在設計時，需考量不同使用情境與需求的使用者，例如：為了<strong>高齡的使用者</strong>，需讓用戶能將文字內容放大，而頁面也不會錯位或破版；或者為了<strong>色覺缺陷者 (色盲) </strong>能清楚閱讀內容，內容與背景需要足夠的顏色對比，讓用戶不會有閱讀上的問題。</p><h4>主要對象與設計需求</h4><p><strong>1. 視覺障礙者：</strong></p><ul><li>色覺缺陷者：需透過顏色對比來辨識資訊</li><li>失明使用者：需使用螢幕閱讀器來協助他們讀取網站或影片內容</li></ul><p><strong>2. 聽覺障礙者：</strong></p><p>應提供完整的文字內容，並以視覺化方式呈現提示與警示，去彌補無法接收聲音資訊的限制。</p><p><strong>3. 高齡者：</strong></p><p>因考量視力與動作能力的退化，設計上需能讓用戶可以應自己需求調整介面內容大小，並提供大尺寸按鈕、直覺的介面設計以降低操作門檻。</p><p><strong>4. 認知與學習障礙者：</strong></p><p>認知與學習障礙者是一群在理解、記憶、注意力或處理資訊方面有挑戰的使用者，例如：學習障礙、注意力缺陷、智能障礙、記憶障礙等等。介面應避免使用過於複雜的語句與設計，系統邏輯需保持一致，協助使用者更快速理解與操作。</p><p><strong>5. 臨時障礙者：</strong></p><p>在特定情境下，例如：只能單手操作、在吵雜或安靜的環境，也能順利使用產品。</p><h3>什麼是無障礙設計指南 WCAG (Web Content Accessibility Guidelines) ?</h3><p>WCAG（Web Content Accessibility Guidelines）是由 W3C 制定的國際標準，專為「<strong>網頁內容</strong>」的無障礙設計而設計。核心目標是確保所有人，包括身心障礙者，都能平等且順利地使用網站內容。</p><blockquote><strong>“The power of the Web is in its universal. Access by everyone regardless of disability is an essential aspect.”</strong><br><em> </em>— Tim Berners-Lee, W3C Director and inventor of the World Wide Web</blockquote><p>目前 WCAG 已發展至 2.2 版本 (最新版)，其中 WCAG 2.0、2.1、2.2 均為有效版本。<strong>歐盟於 2025 年6月起規定統一採用 WCAG 2.1 並要求必須符合 Level AA 的等級</strong>，作為數位產品無障礙的最低標準。</p><h4>WCAG 將無障礙符合程度分為三個等級：</h4><ul><li><strong>Level A</strong>：最基本的無障礙要求，僅涵蓋關鍵問題</li><li><strong>Level AA</strong>：中階標準，多數組織與法規的<strong>最低要求</strong></li><li><strong>Level AAA</strong>：最高標準，涵蓋細節較多，<strong>通常不作為強制依據</strong></li></ul><figure><img alt="圖示說明 WCAG 的四大無障礙設計原則：可感知（Perceivable）、可操作（Operable）、可理解（Understandable）、健壯性（Robust），搭配對應圖示。" src="https://cdn-images-1.medium.com/max/1024/1*hocNamxfzYwLEywUVNWuTA.png" /><figcaption>WCAG 四大核心原則 (POUR)</figcaption></figure><h4>WCAG 四大核心原則 (POUR)：</h4><ol><li><strong>可感知 (Perceivable)</strong>：用戶能正確接收資訊</li><li><strong>可操作 (Operable)</strong>：用戶能正常使用</li><li><strong>可理解 (Understandable)</strong>：資訊內容清晰且容易理解</li><li><strong>健壯性 (Robust)</strong>：與各種裝置與輔助技術相容</li></ol><h3>整體頁面規範</h3><h4>1. 網頁標題 (Page Title)</h4><figure><img alt="瀏覽器分頁顯示「YinLing Mack｜UX UI 產品設計師」作為網頁標題，強調設定具有描述性的 Page Title。" src="https://cdn-images-1.medium.com/max/1024/1*_0LVnWJ-shgM_49b7uaRtg.png" /></figure><p>為了提升網頁的<strong>可感知性 (Perceivable)</strong>，每個頁面都應設定一個<strong>具描述性的標題</strong>。這個標題會顯示在瀏覽器的分頁上，也是螢幕閱讀器進入頁面時最先讀出的內容。</p><p><strong>目的：</strong></p><ul><li>協助<strong>視障使用者</strong>透過螢幕閱讀器快速辨識目前所在的頁面</li><li>讓<strong>一般使用者</strong>在多個分頁中快速分辨每個頁面的用途或內容</li></ul><p><strong>標題內容建議：</strong></p><p>以<strong>簡潔明確</strong>的語句描述此頁的核心內容，例如：「YinLing Mack | UX UI 產品設計師」，而不是「首頁、產品」。</p><h4>2. 跳到主內容連結 (Skip Link)</h4><figure><img alt="按下 Tab 鍵後顯示「Skip to main content」連結，示意鍵盤使用者可跳過導覽列快速進入主內容。" src="https://cdn-images-1.medium.com/max/1024/1*aDhqwFewvIJwOH_A9x2vrA.png" /></figure><p>為了提升網頁的<strong>可操作性（Operable）</strong>，我們可以在頁面中提供一個<strong>隱藏的導覽捷徑</strong>，讓使用者能快速跳過重複區塊 (如導覽列)， 直接進入主要內容。</p><p>由於此功能主要<strong>針對使用鍵盤操作或螢幕閱讀器的使用者</strong>設計，因此通常會預設隱藏，但當使用者按下 Tab 鍵後才會顯示在頁面上。</p><p><strong>目的：</strong></p><p>協助使用者不必反覆按 Tab 鍵，而是可以快速跳轉至主內容區塊，加快操作流程。</p><p><strong>連結文字內容建議：</strong></p><p>清楚描述此連結跳轉區塊，例如：「跳至主內容」。</p><h4>3. 語言 (Language)</h4><figure><img alt="網頁右上方顯示語言切換功能，提供 English、中文與日語選項，示意無障礙設計中的語言切換原則。" src="https://cdn-images-1.medium.com/max/1024/1*gpC_H8WTIKmk4vK95P7NMw.png" /></figure><p>為了提升網站的<strong>可理解性（Understandable）</strong>，每個頁面都應有「<strong>預設語言</strong>」，並在有多語版本時提供清楚的語言切換設定。</p><p>這不僅能讓螢幕閱讀器正確朗讀內容，也能讓一般使用者在跨語系操作時有更好的體驗。</p><p><strong>目的：</strong></p><ul><li>協助螢幕閱讀器依照語言正確發音與解讀內容，避免中文用英文語音朗讀的情況</li><li>為多語系網站提供清楚的語言切換選項，讓使用者自由選擇適合的語言介面</li></ul><p><strong>語言設定內容建議：</strong></p><p>提供語言切換功能時，<strong>應使用語言名稱 (如「中文」「English」) 表示</strong>，而非僅用國旗圖示</p><ul><li>國旗可能與語言產生混淆 (例如英語≠英國)</li><li>語言名稱直覺也可被輔助工具朗讀</li></ul><h4>4. 縮放等級 (Zoom Levels)</h4><figure><img alt="左側為原始大小畫面，右側為放大至 200% 的介面，示意文字與版面可縮放且不破版的無障礙設計。" src="https://cdn-images-1.medium.com/max/1024/1*EFX7twdBEac-aD_VZs0FmA.png" /></figure><p>為了達到網頁的<strong>可感知性 (Perceivable)</strong> 與 <strong>可操作性 (Operable)</strong>，設計上應允許使用者根據各自需求可以自由調整文字大小與內容比例，並確保介面在放大後依然清楚、可用也不會破版。</p><p>這項設計主要是針對低視力者與高齡的使用者，幫助他們能更輕鬆地閱讀與操作網頁內容。</p><p><strong>目的：</strong></p><ul><li>讓<strong>視力較弱或年長的使用者</strong>可放大頁面內容而不影響操作體驗</li><li>保持內容在放大後仍能自動重排，避免需要橫向（水平）滑動</li></ul><p><strong>縮放規範：</strong></p><p>根據 <strong>WCAG 2.1 Level AA </strong>規定：網頁應允許使用者將比例放大到 <strong>200%</strong>，且在不使用輔助技術的情況下，仍不會導致內容遮蔽、重疊、需要水平捲動，或功能無法使用。</p><h4>5. 顏色對比 (Color Contrast)</h4><figure><img alt="比較兩組按鈕的文字與背景顏色對比，一組符合 WCAG AA 標準（對比比 5.37:1），另一組不符合（對比比 1.73:1）。" src="https://cdn-images-1.medium.com/max/1024/1*6YApGvGuIFchlEJspKzP8g.png" /></figure><p>為了提升網站的<strong>可感知性（Perceivable）</strong>，介面中的內容與背景必須具備足夠的顏色對比度，確保所有使用者，特別是色盲與高齡者都能清楚閱讀與操作。</p><p>當文字與背景、按鈕與底色顏色對比不足時，使用者可能會無法辨識資訊、錯過操作提示，而影響整體的可用性。</p><p><strong>目的：</strong></p><ul><li>幫助<strong>色覺障礙者與視力退化者</strong>等清晰辨識文字與介面元件</li><li>提升網頁在不同環境下（如陽光下）的易讀性</li></ul><p><strong>對比規範：</strong></p><ul><li>根據 <strong>WCAG 2.1 Level AA</strong> 標準：</li></ul><ol><li><strong>一般文字</strong>：與背景的對比比率須達到 <strong>4.5:1</strong></li><li><strong>大型文字</strong>（18pt 以上，或粗體 14pt 以上）：對比比率需達到 <strong>3:1</strong></li><li><strong>非文字元素</strong>（如圖示、按鈕邊框）：建議對比至少為 <strong>3:1</strong></li></ol><p><strong>檢查建議：</strong></p><p>可以使用免費的線上工具檢查顏色對比，例如：<a href="https://webaim.org/resources/contrastchecker/"><strong>WebAIM Contrast Checker</strong></a>。</p><p>這類工具能即時檢測兩種顏色之間的對比比率，並標示是否符合 WCAG AA 或 AAA 標準。</p><h4>6. 可見的鍵盤焦點 (Visible Keyboard Focus)</h4><figure><img alt="當按下 Tab 鍵後，焦點落在導覽列中的「關於我」按鈕，示意鍵盤可操作性與焦點樣式。" src="https://cdn-images-1.medium.com/max/1024/1*AJQjL7pprfLzJcQYrjHyVQ.png" /></figure><p>為了實現網頁的<strong>可感知性 (Perceivable)</strong> 與<strong>可操作性 (Operable)</strong>，介面中的互動元件 (如按鈕、連結、表單欄位等) 應在使用者透過鍵盤操作時，明確呈現目前的焦點位置。</p><p>這項設計對於無法使用滑鼠或改用鍵盤瀏覽網站的使用者而言，是基本且必要的輔助方式。</p><p><strong>目的：</strong></p><ul><li>鍵盤使用者能清楚辨識目前焦點所在的元件，順利進行操作</li><li>幫助所有使用者理解該元件是否為可互動項目 (例如按鈕、連結)</li></ul><p><strong>實作建議：</strong></p><p>當使用者按下 <strong>Tab</strong> 鍵進行瀏覽時，應以明顯的樣式 (如邊框) 標示焦點元件。</p><h4>7. 內容標題 (Headings)</h4><figure><img alt="頁面中標示 HTML 標籤如 h1、h2、button，示意內容階層應有語意結構以支援輔助技術。" src="https://cdn-images-1.medium.com/max/1024/1*hAADHGzxC2Xv2ouTMdMRQQ.png" /></figure><p>為了實現網頁的<strong>可感知性 (Perceivable)</strong> 與<strong>可理解性（Understandable）</strong>，頁面內的內容應以<strong>有意義的階層結構呈現</strong>，並正確使用 HTML 語意化標籤（如 h1、h2、p 等）來表達層級與順序。</p><p>這不僅有助於螢幕閱讀器正確朗讀內容，也能讓所有使用者更容易理解頁面的資訊架構與內容邏輯。</p><p><strong>目的：</strong></p><ul><li>協助<strong>視障使用者</strong>透過螢幕閱讀器快速掌握頁面內容的結構與主題重點</li><li>提升整體可讀性，讓使用者能更有效率地掃描與理解內容</li></ul><p><strong>實作建議：</strong></p><ul><li>每個頁面應有一個且只有一個 h1 作為主要標題</li><li>依照內容層級使用 h2、h3 等標籤，<strong>避免跳階層使用</strong>（例如從 h1 跳到 h4）</li><li>非標題內容應使用適合的語意標籤（如段落使用 p，非用 div 充當標題）</li></ul><h4>8. 訊息狀態 (Status Messages)</h4><p>為了實現網頁的<strong>可感知性 (Perceivable)</strong>、<strong>可理解性 (Understandable)</strong>與<strong>健全性性 (Robust）</strong>，整個介面必須讓輔助技術 (如螢幕閱讀器) 能正確朗讀所有狀態訊息與即時變化的內容。例如：錯誤提示、表單提交成功訊息、系統通知、loading 狀態等。</p><p>若設計上未妥善處理這些訊息，視障使用者將無法得知頁面發生了什麼狀況，進而導致操作錯誤或無法完成任務。</p><p><strong>目的：</strong></p><ul><li>協助<strong>視障使用者</strong>透過螢幕閱讀器即時掌握頁面內容的狀態變化</li><li>確保所有系統反饋 (成功、錯誤、提示) 都可被正確辨識與朗讀</li></ul><h3>圖片規範</h3><h4>1. 圖片替代文字 (Image Alternative Text)</h4><p>為了實現網頁的<strong>可感知性 (Perceivable）</strong>，所有非文字內容 (如圖片、圖示、裝飾性元素) 都應提供<strong>替代文字 (alt text)</strong>。當圖片無法載入時或使用者透過螢幕閱讀器瀏覽時，仍能理解圖片所想表達的資訊。</p><p><strong>目的：</strong></p><ul><li>幫助<strong>視障使用者</strong>透過螢幕閱讀器理解圖片內容與語意</li><li>當圖片因網路問題等無法顯示時，提供內容備援文字</li></ul><p><strong>文字撰寫建議：</strong></p><p>以<strong>簡潔明確</strong>的方式去描述此圖片的「資訊」或「意義」。例如「一位女士在陽台曬太陽」，而不是描述「這是一張圖片」。</p><h4>2. 避免文字圖像 (Avoid Text in Images)</h4><p>為了實現網頁的<strong>可感知性 (Perceivable）</strong>，應盡量避免直接<strong>將文字嵌入圖片中</strong>。除非是必要用途 (如品牌 Logo、圖表標籤等)，否則應使用真實的 HTML 文字來呈現資訊。</p><p>因為文字圖像在放大、轉譯、讀取時可能會遇到可讀性的問題，也無法被螢幕閱讀器正確辨識，對視障使用者非常不友善。</p><p><strong>目的：</strong></p><ul><li>為考慮要<strong>視障用戶</strong>確保所有重要資訊都能被螢幕閱讀器讀取</li><li>避免在不同情況可能導致的圖片讀取或破版問題</li></ul><h3>影片規範</h3><h4>1. 音訊控制 (Audio Control)</h4><figure><img alt="影片播放器左下角顯示暫停與靜音按鈕，示意使用者可控制自動播放音訊。" src="https://cdn-images-1.medium.com/max/1024/1*GDi9NSoFNcTFTI1rlxCSDA.png" /></figure><p>為了實現網頁的<strong>可操作性 (Operable）</strong>，所有自動播放的音訊內容都必須提供使用者可控的操作介面。使用者應能夠<strong>隨時暫停、停止或調整音量</strong>，以避免造成干擾，特別是對螢幕閱讀器使用者來說，突如其來的音訊可能會中斷整體操作流程。</p><p><strong>目的：</strong></p><ul><li>避免自動播放的音訊干擾螢幕閱讀器或其他輔助技術的運作</li><li>讓使用者根據情境 (如圖書館、辦公室、通勤中) 調整音量或啟用靜音模式</li></ul><p><strong>設計建議：</strong></p><ul><li>避免自動播放音訊</li><li>提供明確、可見的控制選項，例如：「播放／暫停」「音量調整」「靜音」按鈕</li></ul><h4>2. 字幕 (Captions / Subtitles)</h4><figure><img alt="影片畫面下方顯示即時字幕區塊，示意提供視覺化文字協助聽障或靜音環境使用者理解內容。" src="https://cdn-images-1.medium.com/max/1024/1*osAwSt32myxwjYVZ7BN9OQ.png" /></figure><p>為了實現網頁的<strong>可感知性（Perceivable)</strong> 與<strong>可理解性 (Understandable）</strong>，所有影音內容應提供字幕，特別是即時直播或線上會議等視訊內容，應盡可能提供即時字幕 (Live Captions)，確保聽障使用者也能同步獲取資訊。</p><p>字幕不僅對聽障使用者有幫助，也能協助一般使用者在無法開聲音的環境中 (如通勤、公共場合) 理解影片內容。</p><p><strong>目的：</strong></p><ul><li>協助<strong>聽障使用者</strong>理解影片中的語音與對話內容</li><li>讓一般使用者在各種情境下仍能理解影片資訊</li></ul><h4>3. 逐字稿 (Transcriptions)</h4><figure><img alt="影片下方顯示逐字稿內容區塊，提供完整文字記錄以輔助聽障或需要閱讀的使用者。" src="https://cdn-images-1.medium.com/max/1024/1*xVXA_3kSutxF-Rjkx4SPvw.png" /></figure><p>為了實現網頁的<strong>可感知性 (Perceivable)</strong> 與<strong>可理解性 (Understandable）</strong>，所有預錄的視訊或音訊內容應提供逐字稿（Transcript）。</p><p><strong>目的：</strong></p><p>幫助<strong>聽障或需讀取影片內容使用者</strong>透過純文字方式完整理解影音內容。</p><h4>4. 音訊描述 (Audio Description)</h4><p>為了實現網頁的<strong>可感知性 (Perceivable)</strong> 與<strong>可理解性 (Understandable）</strong>，對於預錄的視訊內容，應提供音訊描述。這是一種針對視障使用者的輔助機制，會在原影片語音間插入解說語音，用來描述畫面中非語音的關鍵資訊，如動作、場景、表情等。</p><p><strong>目的：</strong></p><p>幫助<strong>視障使用者</strong>了解影片中的<strong>非語音內容</strong>（例如肢體動作、環境變化、字幕、圖表），使他們在沒有畫面可視的情況下仍能理解完整影片內容。</p><h4>字幕 (Captions / Subtitles) 、逐字稿 (Transcriptions) 與音訊描述 (Audio Description) 的差異</h4><p><strong>對象：</strong></p><ul><li><strong>字幕</strong>：聽障者、需靜音情境的觀眾</li><li><strong>逐字稿</strong>：聽障或需讀取影片內容使用者</li><li><strong>音訊描述</strong>：視障者</li></ul><p><strong>呈現方式：</strong></p><ul><li>字幕：與影片同步文字呈現在影片裡</li></ul><pre>// 字幕會隨著影片播放出現<br><br>[輕柔音樂]<br>主持人：今天我們請到了 Ling。<br>Ling：謝謝，我很高興來這裡。</pre><ul><li>逐字稿：影片或音檔的完整文字記錄，但不是出現會呈現在影片裡</li></ul><pre>//  逐字稿只有純文字出現，並不與影片同步<br><br>主持人：今天我們請到了 Ling。<br>Ling：謝謝，我很高興來這裡。<br>（背景有音樂）</pre><ul><li>音訊描述：以語音形式描述畫面中未說出來的視覺資訊</li></ul><pre>// 音訊描述 插入旁白說明畫面<br><br>[旁白] Ling 拉開椅子並坐到椅子上。</pre><h3>欄位設定規範</h3><h4>1. 輸入框 (Form Field Labels)</h4><figure><img alt="表單顯示密碼欄位的預設與錯誤狀態，錯誤提示為「密碼長度不足，請輸入至少 8 個字元」。" src="https://cdn-images-1.medium.com/max/1024/1*43AcM5JKoSDg7qj7tn7_QA.png" /></figure><p>根據無障礙設計中的<strong>可操作性 (Operable)</strong> 與<strong>可理解性 (Understandable)</strong> 原則，所有表單欄位都應提供一致且清晰的標籤（Label），並在使用者填寫錯誤時提供具體、易懂的錯誤提示與修正建議。</p><p>標籤不僅是視覺提示，也是螢幕閱讀器辨識欄位功能的重要依據。若程式碼中的 label 元素與實際畫面顯示內容不一致，將導致輔助工具無法正確說明欄位用途。</p><p><strong>目的：</strong></p><ul><li>協助<strong>使用閱讀器的使用者</strong>了解每個輸入欄位的功能與目的。當填寫錯誤時，也能清楚告知哪個欄位有錯，以及如何修正</li></ul><p><strong>設計建議：</strong></p><ul><li>錯誤提示應明確指出欄位名稱與錯誤內容，例如：「密碼長度不足，請輸入至少 8 個字元」</li></ul><h4>2. 必填欄位 (Required Fields)</h4><p>為了實現網頁的<strong>可理解性 (Understandable)</strong>，表單中所有必填欄位都應明確標示，並在未填寫或填寫錯誤時，提供具體、可操作的錯誤訊息與修正建議。</p><p>對於使用閱讀器的用戶而言，若欄位是否必填不明確，或錯誤訊息不具體，將直接影響任務完成與使用體驗。</p><p><strong>目的：</strong></p><ul><li>協助一般與使用閱讀器的使用者清楚辨識哪些欄位是必要填寫的。當漏填或輸入錯誤時，清楚指出問題與修正方法</li></ul><p><strong>設計建議：</strong></p><ul><li>讓使用者能明確區分必填與非必填欄位，避免混淆</li><li>錯誤提示應明確指出欄位名稱與錯誤內容，例如：「此生日欄位為必填」</li></ul><p>以上內容是無障礙設計 ( Accessibility Design / A11y ) 與 WCAG (Web Content Accessibility Guidelines) 的基礎概念。</p><p>假如想要了解更多可以直接去 <a href="https://www.w3.org/WAI/fundamentals/">W3C</a> 的官網看看！</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/0*o5fu1uCoQySTNFrL.gif" /></figure><h3>參考資料</h3><ul><li>AccessibleEU :</li></ul><p><a href="https://accessible-eu-centre.ec.europa.eu/content-corner/news/eaa-comes-effect-june-2025-are-you-ready-2025-01-31_en">The EAA comes into effect in June 2025. Are you ready?</a></p><ul><li>W3C :</li></ul><p><a href="https://www.w3.org/WAI/fundamentals/">Accessibility Fundamentals Overview</a></p><ul><li>Evaluating Web Accessibility Overview from W3C :</li></ul><p><a href="https://www.w3.org/WAI/test-evaluate/">Evaluating Web Accessibility Overview</a></p><ul><li>Web Accessibility Perspective :</li></ul><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F3f31oufqFSM%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D3f31oufqFSM&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F3f31oufqFSM%2Fhqdefault.jpg&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/c01f45c09de3e73b168e2e9640f6d224/href">https://medium.com/media/c01f45c09de3e73b168e2e9640f6d224/href</a></iframe><ul><li>WebAIM Contrast Checker :</li></ul><p><a href="https://webaim.org/resources/contrastchecker/">Contrast Checker</a></p><p>如果這篇文章對你有幫助，歡迎給予拍手鼓勵，也請分享給可能會感興趣的朋友。</p><p>想了解更多關於 UX UI 設計相關的內容，歡迎與我聯繫！</p><p><a href="https://www.linkedin.com/in/yin-ling-mack/">LinkedIn</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=60cb2fe90ccb" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[製作工程導向的 UI 元件]]></title>
            <link>https://medium.com/design-systems-collective-tw/building-figma-ui-components-e5d28df2e4b7?source=rss-a0521af3ea94------2</link>
            <guid isPermaLink="false">https://medium.com/p/e5d28df2e4b7</guid>
            <category><![CDATA[figma]]></category>
            <category><![CDATA[design-systems]]></category>
            <category><![CDATA[ui-component]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[beginners-guide]]></category>
            <dc:creator><![CDATA[Yin-Ling Mack]]></dc:creator>
            <pubDate>Thu, 24 Apr 2025 13:17:36 GMT</pubDate>
            <atom:updated>2025-05-05T13:54:25.505Z</atom:updated>
            <content:encoded><![CDATA[<h4>在 Figma 建立符合工程導向的 UI 元件 (2/2)</h4><figure><img alt="Figma 建立 UI Components 系列：#2. 製作工程導向的 UI 元件。圖片右側為 Figma 與開發圖示。" src="https://cdn-images-1.medium.com/max/1024/1*UpoO2GaLcHE8GW7Iu0heHg.png" /></figure><p><em>Figma 建立 UI Components 系列：<br></em><a href="https://medium.com/@mackyinling1215/ui-components-user-facing-state-4fc0402d9f35"><strong>#1. 了解常見 UI 元件狀態</strong></a> <strong>|</strong> <em>#2. 設計工程導向的 UI 元件</em></p><blockquote>這系列文章將介紹如何在 Figma 中建立專業的 UI 元件，從了解常見 UI 元件的各個狀態介紹，到打造符合工程實務的元件設計。</blockquote><p>在了解了 UI 元件的基本狀態後，我們將深入探討如何在 Figma 中實際建立常用的 UI 元件。</p><p>這篇文章將介紹如何在 Figma 裡建立三個基礎且常使用的元件：<strong>按鈕 (Button)、複選框(Checkboxes)以及輸入框 (Text Input)</strong>。透過這三個範例，了解如何將我們在上篇介紹的所有元件狀態屬性設轉化為實際可用的元件。</p><h3><strong>1. 按鈕 ( Button )</strong></h3><h4>屬性架構</h4><figure><img alt="Figma 中按鈕元件的 Component Properties 設定示意圖，說明三大分類：樣式（外觀、風格、尺寸）、狀態（是否停用、互動狀態），以及內容（文字、圖示位置）。右側顯示對應按鈕範例與設定選項。" src="https://cdn-images-1.medium.com/max/1024/1*vWY3KEXYCH8RFOqtDQXmkw.png" /><figcaption>按鈕屬性設定</figcaption></figure><p>在 Figma 中建立按鈕元件時，屬性可分為三大類：</p><ol><li>樣式：按鈕外觀、顏色風格與尺寸大小</li><li>狀態：是否可點擊與可點擊時的互動方式</li><li>內容：按鈕的文案與是否需搭配圖示(icon)</li></ol><h4>a. 按鈕樣式設定</h4><figure><img alt="按鈕樣式設定示意圖，左側顯示外觀與風格的變體選項（如 filled、outlined、text、link），中間展示主題顏色搭配風格的按鈕範例，右側顯示不同尺寸（2xl 至 xs）下的主色按鈕外觀。" src="https://cdn-images-1.medium.com/max/1024/1*w9Wb7zQll5oPhcQoeNAJsw.png" /><figcaption>按鈕樣式屬性</figcaption></figure><p>按鈕樣式是由三種面向去搭配組成：外觀、顏色風格和尺寸。透過這些屬性的組合，我們可以創建不同視覺層級的按鈕。</p><p><strong>外觀 (Appearance)</strong></p><p>產品介面中常見的四種按鈕外觀：</p><ul><li><strong>填滿按鈕 (Filled)</strong>：作為頁面主要操作的按鈕，使用實心背景色來強調其重要性，提升使用者的注意力</li><li><strong>邊框按鈕 (Outlined)</strong>：常用於次要或輔助性操作，視覺層級較填滿按鈕柔和</li><li><strong>文字按鈕 (Text)</strong>：最基礎的按鈕形式，用於一般性操作</li><li><strong>連結按鈕 (Link)</strong>：雖然視覺呈現與文字按鈕相似，但在 HTML 結構上使用不同的標籤</li></ul><p><strong>重要區別：</strong></p><ol><li>視覺層級排序：填滿按鈕 &gt; 邊框按鈕 &gt; 文字按鈕 = 連結按鈕</li><li>HTML 標籤使用：</li></ol><ul><li>填滿、邊框、文字按鈕：使用 &lt;button&gt; 標籤</li><li>連結按鈕：使用 &lt;a&gt; 標籤</li></ul><pre>&lt;!-- 一般按鈕 --&gt;<br>&lt;button type=&quot;button&quot; onclick=&quot;alert(&#39;Hello world!&#39;)&quot;&gt;按鈕&lt;/button&gt;<br><br>&lt;!-- 連結按鈕 --&gt;<br>&lt;a href=&quot;https://medium.com/@mackyinling1215&quot;&gt;拜訪 Ling 的 Medium&lt;/a&gt;</pre><p><strong>顏色風格 (Style)</strong></p><p>按鈕的顏色風格會依照產品而有不同的顏色配置。例如，當一個產品有主要(primary color)與次要(secondary color)品牌色時，按鈕就會有四種顏色配置(主要色、次要色、中性色與危險操作色)。</p><p>但基本上，按鈕具備三種顏色配置：</p><ul><li>主要品牌色</li><li>中性色系（灰色系）</li><li>危險操作色（紅色系）</li></ul><p><strong>尺寸 (Size)</strong></p><p>根據產品需求，按鈕通常提供 3–5 種尺寸變化，例如：</p><ul><li>小 (sm)：36px</li><li>中 (md / default)：40px</li><li>大 (lg)：44px</li></ul><h4>b. 按鈕狀態設定</h4><figure><img alt="按鈕狀態示意圖，左側為 Figma 中的 isDisabled（是否停用）與 state（互動狀態）屬性設定；右側展示按鈕在啟用狀態下的四種互動狀態：預設、滑鼠懸停、焦點、按壓；停用狀態下按鈕無互動外觀。" src="https://cdn-images-1.medium.com/max/1024/1*TaTiVxGJ6_1IYeIt2qU8Uw.png" /><figcaption>按鈕狀態</figcaption></figure><p><strong>基礎狀態</strong></p><p>按鈕具有兩種基礎狀態：</p><ol><li>可點擊 (Enabled)</li><li>停用 (Disabled)</li></ol><p><strong>1. 可點擊狀態 (Enabled)</strong></p><p>可點擊狀態下包含四種互動變化：</p><ul><li><strong>預設 (Rest)</strong>：按鈕的初始狀態(default)，未與使用者產生任何互動時的樣式</li><li><strong>滑鼠懸停 (Hover)</strong>：當滑鼠移至按鈕上方時的視覺回饋，提示使用者此元件可互動</li><li><strong>焦點 (Focus)</strong>：透過鍵盤 Tab 鍵或點擊獲得焦點時的狀態，這對無障礙設計（Accessibility）至關重要</li><li><strong>按壓 (Active)</strong>：按鈕被按下但未放開時的狀態，提供即時的回饋</li></ul><p><strong>2. 停用狀態 (Disabled)</strong></p><p>此狀態下按鈕不回應任何使用者互動。</p><p><strong>進階狀態</strong></p><p>根據產品需求，可加入以下狀態：</p><ul><li><strong>載入 (Loading)</strong>：用於需要等待資料處理時的情境，如儲存或下載操作</li><li><strong>已訪問 (Visited)</strong>：專用於連結按鈕，協助使用者識別此為已造訪過的連結</li></ul><h4>c. 按鈕內容設定</h4><figure><img alt="按鈕內容設定示意圖，左側顯示文字內容（Label）與圖示相關屬性（iconLeading、iconTailing、swap iconLeading、swap iconTailing）設定方式；右側展示三種按鈕：純文字、圖示置前（＋新增）、圖示置後（下一步）。" src="https://cdn-images-1.medium.com/max/1024/1*hEWewSsNTTnfTzvljRYHJQ.png" /><figcaption>按鈕內容</figcaption></figure><p><strong>按鈕文案</strong></p><p>使用 text property 設定，方便之後可以在設定中直接調整文案內容。</p><p><strong>按鈕內圖示 (icon) 配置</strong></p><ul><li>位置選項：可在文字前 (iconLeading) 或文字後 (iconTailing)</li><li>圖示樣式切換：當圖示建立為元件時，可使用 swap 功能切換不同圖示樣式</li></ul><h3>2. 複選框 ( Checkbox )</h3><h4>屬性架構</h4><figure><img alt="Figma 中複選框元件的 Component Properties 設定示意圖，分為樣式（尺寸、是否勾選）、狀態（是否停用、是否為全選、不同行為狀態），與內容（文字說明）。右側展示對應選項按鈕與狀態切換。" src="https://cdn-images-1.medium.com/max/1024/1*kXQWmgRC1pda2ax835bO3w.png" /><figcaption>複選框屬性設定</figcaption></figure><p>在 Figma 中建立複選框元件時，屬性可分為三大類：</p><ol><li>樣式：尺寸大小</li><li>狀態：是否已勾選、是否為全選、是否可點擊與可點擊時的互動方式</li><li>內容：複選框選項內的文案</li></ol><h4>a. 複選框樣式設定</h4><p><strong>尺寸 (Size)</strong></p><p>根據產品需求，複選框通常可以有 1–2 種尺寸變化，例如：</p><ul><li>小：20px</li><li>中：24px</li></ul><h4>b. 複選框狀態設定</h4><figure><img alt="複選框（Checkbox）狀態對照圖，左側顯示 isChecked、isDisabled、state 三項元件屬性設定；右側分別展示四種互動狀態（預設、滑鼠懸浮、焦點、按壓）下，勾選與未勾選、可互動與停用的複選框樣式。" src="https://cdn-images-1.medium.com/max/1024/1*cuEst6G4azt1BX9p1pSU6g.png" /><figcaption>複選框狀態</figcaption></figure><p><strong>基礎狀態</strong></p><p>複選框具有未勾選(Uncheck)與已勾選(Check)兩種情況，而這兩種情況也會有以下兩種基礎狀態：</p><ol><li>可點擊 (Enabled)</li><li>停用 (Disabled)</li></ol><p><strong>1. 可點擊狀態 (Enabled)</strong></p><p>可點擊狀態下包含四種互動變化與按鈕的互動方式相似：</p><ul><li><strong>預設 (Rest)</strong>：複選框選項的初始狀態(default)，未與使用者產生任何互動時的樣式</li><li><strong>滑鼠懸停 (Hover)</strong>：當滑鼠移至複選框與文案上方時的視覺回饋，用以提示使用者此選項是可勾選的</li><li><strong>焦點 (Focus)</strong>：透過鍵盤 Tab 鍵或點擊獲得焦點時的狀態</li><li><strong>按壓 (Active)</strong>：複選框選項被按下但未放開時的狀態，提供即時的回饋</li></ul><p><strong>2. 停用狀態 (Disabled)</strong></p><p>此狀態下此複選框選項不回應任何使用者互動。</p><h4>c. 複選框內容設定</h4><figure><img alt="複選框內容設定示意圖，左側顯示文字內容（label）、是否顯示錯誤訊息（isInvalid）、錯誤訊息文字（invalidText）等屬性；右側展示兩種狀況：一般狀態與錯誤提示狀態，顯示錯誤文字為紅色。" src="https://cdn-images-1.medium.com/max/1024/1*IhBrOLZ9mzXcvDns8sLSKw.png" /><figcaption>複選框內容</figcaption></figure><p><strong>選項文案與錯誤提示文案</strong></p><p>使用 text property 設定，方便之後可以在設定中直接調整文案內容。</p><p><strong>錯誤訊息提示的顯示</strong></p><p>當此複選框需要有錯誤訊息提醒時，可以使用 boolean property 設定去決定是否顯示錯誤提示。</p><h3>3. 文字輸入框 ( Text Input )</h3><h4>屬性架構</h4><figure><img alt="Figma 中輸入框元件的屬性設定示意圖，包含狀態（驗證結果、是否停用、是否為 Placeholder、互動狀態）與內容（欄位標籤、是否必填、圖示位置、欄位描述）兩大分類，右側顯示對應設定範例。" src="https://cdn-images-1.medium.com/max/1024/1*PFVTwkWTZFby_H_r2iNX0A.png" /><figcaption>輸入框屬性</figcaption></figure><p>在 Figma 中建立文字輸入框元件時，屬性可分為兩大類：</p><ol><li>狀態：驗證是否成功、是否已有輸入文字（預設文字）、是否可點擊與可點擊時的互動方式</li><li>內容：輸入框標題、是否為必填欄位、輸入框內是否需圖示 (icon) 、是否需要欄位描述</li></ol><h4>a. 輸入框狀態設定</h4><figure><img alt="輸入框狀態對照圖，左側為 Figma 的元件屬性設定（isValid、isDisabled、isPlaceholder、state），右側依照不同屬性組合展示輸入框在預設、滑鼠懸停與焦點狀態下的樣式變化，包括未輸入、已輸入、驗證失敗與停用狀態。" src="https://cdn-images-1.medium.com/max/1024/1*1Zku3FN7VutkDDIBGYnkJg.png" /><figcaption>輸入筐狀態</figcaption></figure><p><strong>基礎狀態</strong></p><p>輸入框具有<strong>未輸入文字(Placeholder)</strong>與<strong>已輸入文字</strong>兩種情況，而這兩種情況也會有以下兩種基礎狀態：</p><ol><li>可點擊 (Enabled)</li><li>停用 (Disabled)</li></ol><p><strong>1. 可點擊狀態 (Enabled)</strong></p><p>可點擊狀態下包含主要三種互動變化：</p><ul><li><strong>預設 (Rest)</strong>：輸入框的初始狀態 (default)，未與使用者產生任何互動時的樣式</li><li><strong>滑鼠懸停 (Hover)</strong>：當滑鼠移至輸入框上方時的視覺回饋，用以提示使用者此輸入框可互動</li><li><strong>焦點 (Focus)</strong>：透過鍵盤 Tab 鍵或點擊獲得焦點時的狀態</li></ul><p><strong>2. 停用狀態 (Disabled)</strong></p><p>此狀態下此複選框不回應任何使用者互動。</p><h4>b. 輸入框內容設定</h4><figure><img alt="輸入框內容設定示意圖，左側為各屬性設定（是否顯示標籤、是否必填、是否顯示描述、圖示位置與替換），右側依據不同組合展示輸入框的樣式與內容，包括圖示置前、置後、顯示欄位描述與標註為必填項目。" src="https://cdn-images-1.medium.com/max/1024/1*hYIOkQy3h3soPCkcsXRoZQ.png" /><figcaption>輸入框內容</figcaption></figure><p><strong>欄位標題、必填欄位提示(*)與訊息提示的顯示</strong></p><p>可以使用 boolean property 設定，方便之後在不同情境時，可以快速切換並建立不同需求所需要的輸入框元件。</p><p><strong>欄位標題文案、欄位訊息與錯誤訊息文案</strong></p><p>可以使用 text property 設定，方便之後可以在設定中直接調整文案內容。</p><p><strong>輸入框內的圖示 (icon) 配置</strong></p><p>可以在輸入框欄位內建立圖示(icon)配置，這樣可以快速切換並建立不同需求所需要的輸入框元件。：</p><ul><li>位置選項：可在文字前 (iconLeading) 或文字後 (iconTailing)</li><li>圖示樣式切換：當圖示建立為元件時，可使用 swap 功能切換不同圖示樣式</li></ul><p>以上是三個基礎且常見的三個UI 元件。大家趕快開啟 Figma 嘗試照著做做看吧！</p><figure><img alt="Figma gif" src="https://cdn-images-1.medium.com/max/480/0*CmKL2Xt52mx6a0nq.gif" /></figure><h4>參考資料</h4><p>按鈕元件狀態：</p><p><a href="https://atlassian.design/components/button/examples">https://atlassian.design/components/button/examples</a></p><p>HTML link tag：</p><p><a href="https://www.w3schools.com/tags/tag_a.asp">W3Schools.com</a></p><p>HTML button tag：</p><p><a href="https://www.w3schools.com/tags/tag_button.asp">W3Schools.com</a></p><p><a href="https://medium.com/@mackyinling1215/ui-components-user-facing-state-4fc0402d9f35"><strong>#1. 了解常見 UI 元件狀態</strong></a> <strong>|</strong> <em>#2. 設計工程導向的 UI 元件</em></p><p>如果這篇文章對你有幫助，歡迎給予拍手鼓勵，也請分享給可能會感興趣的朋友。</p><p>想了解更多關於 Design System 的內容，歡迎與我聯繫！</p><p><a href="https://www.linkedin.com/in/yin-ling-mack/">LinkedIn</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e5d28df2e4b7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-systems-collective-tw/building-figma-ui-components-e5d28df2e4b7">製作工程導向的 UI 元件</a> was originally published in <a href="https://medium.com/design-systems-collective-tw">Design Systems TW</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[From Design to Code (II)]]></title>
            <link>https://www.designsystemscollective.com/from-design-to-code-ii-7a47036fb600?source=rss-a0521af3ea94------2</link>
            <guid isPermaLink="false">https://medium.com/p/7a47036fb600</guid>
            <category><![CDATA[design-systems]]></category>
            <category><![CDATA[code]]></category>
            <category><![CDATA[figma-plugin]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[figma]]></category>
            <dc:creator><![CDATA[Yin-Ling Mack]]></dc:creator>
            <pubDate>Tue, 11 Feb 2025 12:41:12 GMT</pubDate>
            <atom:updated>2025-05-05T13:23:14.360Z</atom:updated>
            <content:encoded><![CDATA[<h4>Quickly Building a Design System from Scratch (4/4)</h4><figure><img alt="Comprehensive overview of design and engineering integration, showing a design tokens JSON file, CSS variable naming, Tokens Studio for Figma interface, and linked typography styles in Figma." src="https://cdn-images-1.medium.com/max/1024/1*1yDChAcQr-eQtowXBuwVuA.png" /></figure><p>Language / 語言 : <em>English | </em><a href="https://medium.com/design-systems-collective-tw/design-system-from-design-to-code-a4848343db12"><strong>中文</strong></a></p><p><em>Quick Guide to Building a Design System Series:</em><br><a href="https://medium.com/@mackyinling1215/design-system-concepts-and-establishing-basic-design-tokens-en-b1a974da0c16"><strong>#1. Design System Concepts and Establishing Basic Design Tokens</strong></a> | <a href="https://medium.com/@mackyinling1215/expanding-design-tokens-and-ui-components-en-2d74d9adf75e"><strong>#2.</strong> <strong>Expanding Design Tokens and UI Components</strong></a> | <a href="https://medium.com/@mackyinling1215/from-design-to-code-i-en-92fbef6de06d"><strong>#3. From Design to Code (I)</strong></a> | <em>#4. From Design to Code (II)</em></p><blockquote>This series of articles will introduce how to quickly build a Design System from scratch, covering everything from establishing Design Tokens and UI Components to creating CSS Variants Code that engineers can use directly.</blockquote><p>In the previous article, we introduced how to build UI components and explored the foundational concepts of Design Tokens. This article will delve deeper into a crucial process: converting Design Tokens defined in Figma into implementable code for engineers.</p><p>Since the design-to-code conversion process involves multiple steps and complexities, I will divide this topic into two parts to ensure thorough coverage. It will help the reader better understand the complete workflow and establish seamless integration between design and development within the design system.</p><p><a href="https://medium.com/@mackyinling1215/from-design-to-code-i-en-92fbef6de06d"><strong>Design to Code (I)</strong></a> has introduced <a href="https://tokens.studio/"><strong>Tokens Studio for Figma</strong></a> and how to organize Design Tokens in Figma files. This organization makes it easier for engineers to directly use the code files generated after synchronizing Figma with Tokens Studio.</p><p>Next,<strong> this article</strong> will cover how to <strong>connect Tokens Studio with GitHub</strong> and <strong>push Design Tokens from Figma to GitHub</strong>. This workflow ensures consistency in design specifications and significantly improves collaboration efficiency between designers and engineers.</p><h3>Preparation for Synchronizing Figma and Tokens Studio</h3><p>Before we begin synchronizing Figma with the Tokens Studio for Figma plugin, we need to complete the following preparations:</p><ol><li>Create a GitHub account</li><li>Create a Repository and Personal Access Token for Design Tokens on GitHub</li><li>Connect Tokens Studio with that Repository</li></ol><p>After completing these settings, we can directly push Design Tokens to the GitHub Repository through Tokens Studio. Then, depending on team requirements, engineers can set up automatic JSON file conversion and version control requirements on GitHub.</p><h3>GitHub Setup Steps</h3><h4>1. Create a GitHub Account</h4><p>If you don’t have a GitHub account, you can create a new one at <a href="https://github.com/signup">https://github.com/signup</a>.</p><h4>2. Create a New Repository</h4><p>After creating your GitHub account, create a dedicated Repository for Design Tokens (page link: <a href="https://github.com/new">https://github.com/new</a>).</p><figure><img alt="Illustration of GitHub’s “Create a new repository” interface, with annotations for steps like repository URL, visibility, README setup, .gitignore template, license selection, and the create button." src="https://cdn-images-1.medium.com/max/1024/1*POvEnTFXDw4uzoQGhv1lSw.png" /><figcaption>Repository Creation Settings Guide</figcaption></figure><ol><li><strong>Repository URL Settings:<br></strong>The URL structure is [https://github.com/{owner}/{repository-name}]. For example: if your GitHub account is yinlingmack and the repository name is my-design-system, the complete URL will be [https://github.com/yinlingmack/my-design-system].</li><li><strong>Repository Settings:<br></strong>Public : Anyone can view it.<br>Private : Authorization required to view.</li><li><strong>Create README File:<br></strong>Must check Add a README file</li><li><strong>Add .gitignore:<br></strong>Can select None</li><li><strong>Choose License:<br></strong>Can select None</li><li><strong>Create Repository button</strong></li></ol><h4>3. Create a Personal Access Toke</h4><p><strong>A Personal Access Token</strong> acts as a security key, establishing a secure channel between GitHub and Tokens Studio, allowing bidirectional data transfer.</p><p><strong>How to Create a Personal Access Token</strong></p><p>First, log into your GitHub account and go to the <a href="https://github.com/settings/profile">account settings</a> page. In the left settings panel, find Developer settings. After clicking it, select Tokens (classic) under Personal Access Token in the left settings panel.</p><p>Once you’re on the Tokens (classic) page, click the Generate new token dropdown button in the top right and select New personal access token (classic).</p><p><strong>New Personal Access Token (classic) Settings Page</strong></p><figure><img alt="New Personal Access Token (classic) Settings Page" src="https://cdn-images-1.medium.com/max/1000/0*T5gKEZO4p6yTnpha.png" /><figcaption>Image Source：<a href="https://docs.tokens.studio/token-storage-and-sync/sync-provider-github">https://docs.tokens.studio/token-storage-and-sync/sync-provider-github</a></figcaption></figure><ol><li>Note: You can add a note about the purpose of this Personal Access Token</li><li>Expiration: The expiration date for this Personal Access Token. If you select 30 days, you&#39;ll need to create a new Personal Access Token and reconnect it with Tokens Studio after 30 days</li><li>Select scopes: You must choose Repo; other options can be selected based on team requirements</li><li>Click the Generate token button</li></ol><p>After creating the Personal Access Token, remember to save this Token, as it will only be shown once. If you lose it, you’ll need to create a new one.</p><h3>Tokens Studio Setup Steps</h3><p>Before we begin, we need to complete:</p><ol><li>Create a Design Tokens repository on GitHub</li><li>Create a Personal Access Token on GitHub</li></ol><p>Once everything is ready, you can open Tokens Studio for Figma in Figma to configure the connection settings.</p><h4>Initial Setup</h4><p>Open the Tokens Studio plugin in Figma and go to the Settings page. In the <strong>Sync Providers</strong> area, click Add new sync provider and select GitHub.</p><figure><img alt="Tokens Studio for Figma settings screen showing the “Add new sync provider” button under the Sync providers section, where users can add GitHub as a sync source." src="https://cdn-images-1.medium.com/max/1024/1*Eim1Yzf-p0FATTLqcUtWvQ.png" /><figcaption>Tokens Studio for Figma Settings Page</figcaption></figure><h4>Connection Settings Guide for Tokens Studio and GitHub</h4><figure><img alt="GitHub sync configuration screen in Tokens Studio for Figma, showing required fields: Name, Personal Access Token, Repository (owner/repo), Branch, and Token storage location. Annotations on the right explain each field." src="https://cdn-images-1.medium.com/max/1024/1*LCoyR3VzZjK3T90hTOO3cA.png" /><figcaption>GitHub Page Synchronization Settings</figcaption></figure><figure><img alt="Tokens Studio sync setup screen. The left panel shows form fields for entering “Name” and “Repository URL.” The right panel displays the Sync providers section, with GitHub repository successfully connected and an “Apply” button visible." src="https://cdn-images-1.medium.com/max/1024/1*XieNF-jNTxy9C_EMOUwkgg.png" /></figure><ol><li><strong>Name:</strong> <br>An identifier name that will be displayed in the Sync providers list</li><li><strong>Personal Access Token:</strong> <br>Paste the Personal Access Token previously created on GitHub</li><li><strong>Repository URL:</strong> <br>Format is [{owner}/{repository-name}]. For example: [yinlingmack/my-design-system]</li><li><strong>Repository Branch:</strong> <br>Should be chosen after discussion with the engineering team. You can select either an independent branch or an engineering branch. If choosing an independent branch, enter [main]</li><li><strong>Repository File Location:</strong> <br>The storage path for JSON files in GitHub should be determined after confirming automation process requirements with the engineering team</li></ol><p>After completing these settings, you can begin synchronizing Design Tokens from Figma.</p><h3>Figma and Tokens Studio Synchronization Settings</h3><h4>Importing Design Tokens to Tokens Studio</h4><p>Return to the Tokens page, and click the Styles &amp; Variables dropdown menu in the bottom left. Select Import variables to import all Design Tokens, and choose Import styles to import Text and Shadow styles.</p><figure><img alt="Tokens Studio for Figma plugin interface, with the dropdown menu at the bottom left opened and the “Import variables” option selected, preparing to import Figma Local Variables into design tokens." src="https://cdn-images-1.medium.com/max/1024/1*bLF_eHt3rJEbRRKdaeOw5g.png" /><figcaption>Import Variables from Figma</figcaption></figure><figure><img alt="Tokens Studio for Figma plugin interface, showing a dialog after selecting “Import styles”, with “Text” and “Shadows” options checked, preparing to import these styles into design tokens." src="https://cdn-images-1.medium.com/max/1024/1*vKuNi6KO9CzJnbT6k-9yVA.png" /><figcaption>Import Styles from Figma</figcaption></figure><h4>Tokens Studio Maintenance:</h4><ul><li>You can organize the Design Tokens structure in Tokens Studio for easier management.</li><li>When expanding the Design System later, you’ll need to synchronously update the Design Tokens in Tokens Studio and push them to the GitHub Repository.</li></ul><h3>Pushing Design Tokens to GitHub</h3><figure><img alt="The left image shows the Tokens Studio for Figma plugin with foundation and semantic token sets selected for color, spacing, and typography, ready to push changes to GitHub. The right image is a “Push to GitHub” popup with the commit message “modify semantic tokens color” and the target branch set to “main”." src="https://cdn-images-1.medium.com/max/1024/1*igCewPEOE69uO9j9A7aa5Q.png" /><figcaption>Tokens Studio</figcaption></figure><p>When Tokens Studio is connected to GitHub and there are new or modified Tokens, a blue dot will appear on the Push to GitHub button in the bottom left (as shown in the left image). After clicking the <strong>Push to GitHub</strong> button, a prompt for a Commit message will appear (as shown in the right image). The content entered here will be displayed in GitHub’s Commits history later, making it easy to identify the updates made in this commit.</p><figure><img alt="The left side shows the “Push to GitHub” panel in Tokens Studio for Figma, with the commit message “modify semantic tokens color” targeting the main branch; the right side displays the GitHub commits page, confirming the new commit appears at the top of the commit history." src="https://cdn-images-1.medium.com/max/1024/1*j06yiCnu4XrPJ1jkh4eqzA.png" /><figcaption>Commit message</figcaption></figure><h3>GitHub Extensions</h3><figure><img alt="GitHub interface showing the contents of the design-token folder within the my-design-system repository, listing files such as package.json, variables-map.scss, variables.css, and variables.scss." src="https://cdn-images-1.medium.com/max/1024/1*5W5x0yNc0utEBmPqwQcMSQ.png" /><figcaption>JSON to CSS Variants</figcaption></figure><h4>JSON to CSS Variants</h4><p>Based on company product requirements, we can ask our talented engineers to help us set up an automatic file conversion mechanism on GitHub to convert Design Tokens into required formats.</p><h4>Version Control</h4><p>To make Design Tokens easier to manage, we can again ask our engineers to help us establish an automatic version numbering mechanism on GitHub. This way, whenever we modify Design Tokens and push them to GitHub, it will automatically generate a version number [major.minor.patch].</p><p>The engineer I worked with wrote this for me:</p><ul><li>If the Commit Message includes [major], the version number on GitHub will increment by a major version. For example: remove redundant color prefix [major] will change the version from [1.0.0] to [2.0.0].</li><li>If the Commit Message includes [minor], the version number on GitHub will increment by a minor version. For example: add semantic token [minor] will change the version from [1.0.0] to [1.1.0].</li><li>If the Commit Message only includes a change description, for example: “change button radius tokens”, the version will only change from [1.0.0] to [1.0.1].</li></ul><p>The following two web pages might be helpful for engineers:</p><p><strong>Tokens Studio GitHub (Custom JSON Transformation)</strong></p><p><a href="https://github.com/tokens-studio/sd-transforms?tab=readme-ov-file&amp;source=post_page-----a4848343db12--------------------------------#readme">GitHub - tokens-studio/sd-transforms: Custom transforms for Style-Dictionary, to work with Design Tokens that are exported from Tokens Studio</a></p><p><strong>Detailed Configuration for Tokens Studio JSON Transformation</strong></p><p><a href="https://styledictionary.com/reference/hooks/formats/predefined/?source=post_page-----a4848343db12--------------------------------#cssvariables">Built-in formats</a></p><p><strong>Detailed Usage Instructions for Tokens Studio Official Website</strong></p><p><a href="https://docs.tokens.studio/?source=post_page-----a4848343db12--------------------------------">Tokens Studio for Figma - Tokens Studio for Figma Docs</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/0*P1aOcArqzOmCtejx.gif" /></figure><h4>Resources</h4><p><a href="https://uxdesign.cc/the-ultimate-design-token-setup-cdf50dc841c8">The ultimate Design Token setup</a></p><p><a href="https://medium.com/@mackyinling1215/design-system-concepts-and-establishing-basic-design-tokens-en-b1a974da0c16"><strong>#1. Design System Concepts and Establishing Basic Design Tokens</strong></a> | <a href="https://medium.com/@mackyinling1215/expanding-design-tokens-and-ui-components-en-2d74d9adf75e"><strong>#2.</strong> <strong>Expanding Design Tokens and UI Components</strong></a> | <a href="https://medium.com/@mackyinling1215/from-design-to-code-i-en-92fbef6de06d"><strong>#3. From Design to Code (I)</strong></a> | <em>#4. From Design to Code (II)</em></p><p>If you found this article helpful, please show your support with a clap and share it with friends who might be interested.</p><p>If you’d like to learn more about Design Systems, feel free to contact me!</p><p><a href="https://www.linkedin.com/in/yin-ling-mack/">LinkedIn</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7a47036fb600" width="1" height="1" alt=""><hr><p><a href="https://www.designsystemscollective.com/from-design-to-code-ii-7a47036fb600">From Design to Code (II)</a> was originally published in <a href="https://www.designsystemscollective.com/">Design Systems Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[將自己的經驗分享給 Design Systems TW]]></title>
            <link>https://medium.com/design-systems-collective-tw/design-systems-tw-become-a-writer-e46e8169abf9?source=rss-a0521af3ea94------2</link>
            <guid isPermaLink="false">https://medium.com/p/e46e8169abf9</guid>
            <category><![CDATA[設計師]]></category>
            <category><![CDATA[write-for-us]]></category>
            <category><![CDATA[工程師]]></category>
            <category><![CDATA[台灣]]></category>
            <category><![CDATA[design-systems]]></category>
            <dc:creator><![CDATA[Yin-Ling Mack]]></dc:creator>
            <pubDate>Sun, 12 Jan 2025 08:03:21 GMT</pubDate>
            <atom:updated>2025-01-12T14:40:16.426Z</atom:updated>
            <content:encoded><![CDATA[<h4>一起分享自己的 Design System 經驗與想法給大家吧！</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IFKxxuIJvKyjD40rtTljhg.png" /></figure><p>當你已經向我們申請成為 <strong>Design Systems TW</strong> 的 <strong>Writer</strong> ，並<strong>收到 Email</strong> 告知加入成功，請跟著下面幾個步驟開始分享你的 Design System 文章吧！</p><p>想開始分享經驗但還沒申請加入 Design Systems TW 的人，可以填寫以下表單申請加入我們的 Writer 。</p><p><a href="https://lively-scorpio-dd2.notion.site/178b4dc362f2804fb257ecec9890d388?pvs=105">申請成為 Design Systems TW 的一員 | Notion</a></p><h3>如何將自己的文章發布在 Design Systems TW？</h3><h4>1. 完成申請成為 Writer</h4><ul><li><a href="https://lively-scorpio-dd2.notion.site/178b4dc362f2804fb257ecec9890d388?pvs=105">申請成為 Writer</a>。</li><li>收到 Email 告知已加入成功。</li></ul><h4>2. 開始分享你的經驗</h4><ul><li>請使用 Medium 分享關於 Design System 的經驗與想法 。</li><li>可以使用文字搭配圖片、Code範例去向讀者解釋。</li></ul><h4>3. 發布文章到 Design Systems TW</h4><ul><li>打開你的文章。</li><li>點擊右上角的 『 … 』按鈕，並選擇 『 <strong>Add to publication</strong> 』 &gt;&gt; 『 <strong>Design Systems TW</strong> 』。</li></ul><h4>4. 等待發布</h4><ul><li>寄送發布申請後，我們會確認此文章是否與 Design Systems 相關。</li><li>確認完成後，你就會看到你的文章發布在 Design Systems TW 囉！</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/529/0*vt0FJ-bj-8Da2cwW.gif" /></figure><p>有任何問題，歡迎聯繫：design.systems.tw@gmail.com</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e46e8169abf9" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-systems-collective-tw/design-systems-tw-become-a-writer-e46e8169abf9">將自己的經驗分享給 Design Systems TW</a> was originally published in <a href="https://medium.com/design-systems-collective-tw">Design Systems TW</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[From Design to Code (I)]]></title>
            <link>https://www.designsystemscollective.com/from-design-to-code-i-en-92fbef6de06d?source=rss-a0521af3ea94------2</link>
            <guid isPermaLink="false">https://medium.com/p/92fbef6de06d</guid>
            <category><![CDATA[design-systems]]></category>
            <category><![CDATA[figma]]></category>
            <category><![CDATA[web]]></category>
            <category><![CDATA[code]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Yin-Ling Mack]]></dc:creator>
            <pubDate>Fri, 10 Jan 2025 12:06:16 GMT</pubDate>
            <atom:updated>2025-05-05T13:22:47.872Z</atom:updated>
            <content:encoded><![CDATA[<h4>Quickly Building a Design System from Scratch (3/4)</h4><figure><img alt="Overview of a design system including color scales, typography settings, Tokens Studio interface in Figma, and CSS variable-based code snippets — demonstrating the workflow between design and development." src="https://cdn-images-1.medium.com/max/1024/1*m9ZovTG3ZCpmsqqMyQ4oUw.png" /></figure><p>Language / 語言 : <em>English | </em><a href="https://medium.com/@mackyinling1215/design-system-from-design-to-code-f06f6b976953"><strong>中文</strong></a></p><p><em>Quick Guide to Building a Design System Series:</em><br><a href="https://medium.com/@mackyinling1215/design-system-concepts-and-establishing-basic-design-tokens-en-b1a974da0c16"><strong>#1. Design System Concepts and Establishing Basic Design Tokens</strong></a> | <a href="https://medium.com/@mackyinling1215/expanding-design-tokens-and-ui-components-en-2d74d9adf75e"><strong>#2.</strong> <strong>Expanding Design Tokens and UI Components</strong></a> | <em>#3. From Design to Code (I)</em> | <a href="https://medium.com/@mackyinling1215/from-design-to-code-ii-7a47036fb600"><strong>#4. From Design to Code (II)</strong></a></p><blockquote>This series of articles will introduce how to quickly build a Design System from scratch, covering everything from establishing Design Tokens and UI Components to creating CSS Variants Code that engineers can use directly.</blockquote><p>In the previous article, we introduced how to build UI components and explored the foundational concepts of Design Tokens. This article will delve deeper into a crucial process: converting Design Tokens defined in Figma into implementable code for engineers.</p><p>Since the design-to-code conversion process involves multiple steps and complexities, I will divide this topic into two parts to ensure thorough coverage. It will help the reader better understand the complete workflow and establish seamless integration between design and development within the design system.</p><p><strong>This article</strong> will focus on <a href="https://tokens.studio/"><strong>Tokens Studio for Figma</strong></a>, a powerful tool that bridges the gap between design and code, significantly streamlining the design system implementation process. We’ll explore how to systematically organize Design Tokens in Figma files to create a clear, structured design specification. This foundational work is crucial as it ensures that when we synchronize design specifications through Tokens Studio, the generated code maintains structural integrity and is immediately usable by engineering teams.</p><p><strong>The following article</strong>, <a href="https://medium.com/@mackyinling1215/from-design-to-code-ii-7a47036fb600"><strong>Design 到 Code (II)</strong></a><strong>,</strong> will cover the integration of Tokens Studio with GitHub and detail the process of pushing Figma’s Design Tokens to the repository. This workflow ensures consistency in design specifications and substantially enhances collaboration efficiency between designers and engineers.</p><h3><a href="https://tokens.studio/">Tokens studio</a></h3><p>This powerful tool serves as a crucial <strong>bridge between design and code</strong>. Using <strong>Tokens Studio for Figma</strong>, we can convert all Design Tokens created in Figma into a JSON file and push it to GitHub.</p><h4>Key benefits of using Tokens Studio for Figma:</h4><ul><li><strong>JSON Transformation:</strong> <br>Engineers can convert this JSON file into preferred formats, such as CSS Variants for web development.</li><li><strong>Version Control:</strong> <br>Implement Design Tokens version control on GitHub. This will enable engineers to roll back changes and review version history when necessary.</li><li><strong>Cross-platform Consistency</strong>: <br>Both web and app developers source Design Values from the same JSON file, ensuring consistent product styling across different platforms.</li></ul><h3>Preparation for Syncing Figma and Tokens Studio</h3><h4>Figma Files</h4><p>Before importing Figma’s Design Tokens into Token Studio, we need to organize our <strong>Local Variables</strong> and <strong>Local Styles</strong> in Figma.</p><p><strong>Local Variables</strong></p><ul><li><strong>Foundation Tokens: <br></strong>Define all fundamental design values in the product, serving as core elements of the design system.</li><li><strong>Semantic Tokens: <br></strong>Based on Foundation Tokens, assign specific usage scenarios and semantics.</li><li><strong>Component Tokens: <br></strong>Establish dedicated design parameters for complex UI components, ensuring component consistency and reusability.</li></ul><p><strong>Local Styles</strong></p><ul><li>Create text styles, effect styles, and other styles needed for the product, and link these styles with Foundation Tokens to establish Semantic Tokens for text and shadows.</li></ul><figure><img alt="Preparation diagram for syncing Figma with Tokens Studio, showing the need to organize local variables (such as color tokens) and text styles before integration." src="https://cdn-images-1.medium.com/max/1024/1*-T7gsJk0EUc5K0glVo5OPQ.png" /><figcaption>Organize Design Tokens in Figma</figcaption></figure><h4>Local Variables</h4><figure><img alt="Diagram explaining the structure of Figma local variables, highlighting four parts: variable collections, variable groups, variables, and modes for variables. Uses the “text primary” variable as an example with light and dark mode values." src="https://cdn-images-1.medium.com/max/1024/1*dV43p4Ug5ygHmeDvYPbohg.jpeg" /><figcaption>Figma’s Local Variables Interface</figcaption></figure><p><strong>Local Variables Interface and Usage Guide</strong></p><p>In Figma’s Local Variables interface, you can access Variable Collections through the dropdown menu in the top-left corner. Clicking the “…” option button beside the dropdown menu allows you to:</p><ul><li>Rename Collection</li><li>Delete existing Collection</li><li>Create new Collection</li></ul><p>For more details about Variable usage, you can refer to <a href="https://help.figma.com/hc/en-us"><strong>Figma Learn</strong></a> on <a href="https://help.figma.com/hc/en-us/articles/15145852043927-Create-and-manage-variables"><strong>Create and manage variable</strong></a>.</p><p>Important: These Variable Collections will map directly to the <strong>Set</strong> field in the Tokens Studio interface upon synchronization.</p><figure><img alt="Diagram showing how Figma variable collections are synced with the Sets panel in Tokens Studio. The left side displays local variables in Figma, while the right shows the corresponding Tokens Studio interface." src="https://cdn-images-1.medium.com/max/1024/1*EczQ8c6FYVHSJg0zigZtZw.png" /><figcaption>Relationship between Figma Variable Collections and Tokens Studio Set</figcaption></figure><p><strong>Variable Structure Guidelines</strong>: <br>When structuring Variable groups and Variables in Figma, we need to consider the architectural implications, as they directly influence the resulting code structure of Design Tokens.</p><p>For example, when we create a “<strong>text</strong>” Variable group with a “primary” color, it will generate the CSS variable [ text-primary ] on Dev Mode. This occurs because Figma uses group names with [ - ] to create the final variable name.</p><p>Consider naming conventions that enhance readability and consistency across your product’s Design Tokens. For reference, see <strong>Nathan Curtis</strong>’s comprehensive guide on <a href="https://medium.com/eightshapes-llc/naming-tokens-in-design-systems-9e86c7444676"><strong>Naming Tokens in Design Systems</strong></a>.</p><p>For example, “<strong>gray/25</strong>” transforms into the CSS variable [ --colors-neutral-gray-25 ] in Dev Mode.</p><figure><img alt="Diagram showing how Figma local variables (e.g., gray-25 to gray-500) are converted into CSS variable names such as — colors-neutral-gray-25 in Dev Mode, bridging design and development." src="https://cdn-images-1.medium.com/max/1024/1*QO1LxF8AKV_8i5zwcO2bCg.png" /><figcaption>CSS Variable Example</figcaption></figure><h4>Local Styles</h4><p><strong>Text Style</strong></p><figure><img alt="The left shows the Figma interface for creating text styles linked to design tokens; the right shows how these styles appear in Dev Mode, rendered as CSS variables." src="https://cdn-images-1.medium.com/max/1024/1*eF9p3BAB6tDJ80RkN6-GYw.png" /><figcaption>Text Styles</figcaption></figure><p>When creating Local Styles, it’s essential to link all style values to their corresponding Foundation Tokens. This critical connection serves two important purposes:</p><ol><li>It ensures Foundation Token values are accurately displayed in Dev Mode, maintaining consistency between design and development environments.</li><li>It enables engineers to efficiently locate Foundation Token values within the exported Design Tokens Code files, allowing them to establish Text Styles as Semantic Tokens. This streamlined process helps maintain the design system’s integrity throughout the development workflow.</li></ol><figure><img alt="Comparison of two text style setups: the left uses linked Foundation Tokens, generating CSS variables in Dev Mode; the right shows hardcoded values without token linkage." src="https://cdn-images-1.medium.com/max/1024/1*m0aWi8X6wcnaVVKeZH505w.png" /><figcaption>Text Styles in Dev Mode</figcaption></figure><p><strong>Effect styles</strong></p><figure><img alt="Illustration of how to create shadow effect styles in Figma. The left shows shadow property settings; the right displays predefined foundation tokens for shadow colors and opacity, ensuring consistency in the design system." src="https://cdn-images-1.medium.com/max/1024/1*rnjZv4H8iNBgKXzDfOIEeQ.png" /><figcaption>Shadow Effect Styles</figcaption></figure><p>Apply the same principle to Effect Styles: connect shadow effect colors to predefined shadow Foundation Tokens to maintain design system consistency.</p><p>Once you’ve completed organizing your Figma file according to the guidelines above, you’re ready to take the next step with Tokens Studio.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/320/0*JIi0w5FtQg_XZemu.gif" /></figure><p>🌟 Next Article <a href="https://medium.com/@mackyinling1215/from-design-to-code-ii-7a47036fb600"><strong>#4. From Design to Code (II)</strong></a></p><p><a href="https://medium.com/@mackyinling1215/design-system-concepts-and-establishing-basic-design-tokens-en-b1a974da0c16"><strong>#1. Design System Concepts and Establishing Basic Design Tokens</strong></a> | <a href="https://medium.com/@mackyinling1215/expanding-design-tokens-and-ui-components-en-2d74d9adf75e"><strong>#2.</strong> <strong>Expanding Design Tokens and UI Components</strong></a> | <em>#3. From Design to Code (I)</em> | <a href="https://medium.com/@mackyinling1215/from-design-to-code-ii-7a47036fb600"><strong>#4. From Design to Code (II)</strong></a></p><p>If you found this article helpful, please show your support with a clap and share it with friends who might be interested.</p><p>If you’d like to learn more about Design Systems, feel free to contact me!</p><p><a href="https://www.linkedin.com/in/yin-ling-mack/">LinkedIn</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=92fbef6de06d" width="1" height="1" alt=""><hr><p><a href="https://www.designsystemscollective.com/from-design-to-code-i-en-92fbef6de06d">From Design to Code (I)</a> was originally published in <a href="https://www.designsystemscollective.com/">Design Systems Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Expanding Design Tokens and UI Components]]></title>
            <link>https://www.designsystemscollective.com/expanding-design-tokens-and-ui-components-en-2d74d9adf75e?source=rss-a0521af3ea94------2</link>
            <guid isPermaLink="false">https://medium.com/p/2d74d9adf75e</guid>
            <category><![CDATA[code]]></category>
            <category><![CDATA[design-systems]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[figma]]></category>
            <category><![CDATA[web-design]]></category>
            <dc:creator><![CDATA[Yin-Ling Mack]]></dc:creator>
            <pubDate>Thu, 09 Jan 2025 13:47:16 GMT</pubDate>
            <atom:updated>2025-05-05T13:22:30.746Z</atom:updated>
            <content:encoded><![CDATA[<h4>Quickly Building a Design System from Scratch (2/4)</h4><figure><img alt="UI components from a design system, showcasing various states of CTA buttons, input fields, and notification cards with different visual and interaction styles." src="https://cdn-images-1.medium.com/max/1024/1*mHMc8AbON88dZCoDbXdeAA.png" /></figure><p>Language / 語言 : <em>English | </em><a href="https://medium.com/@mackyinling1215/design-tokens-and-ui-components-6fc68785fe4a"><strong>中文</strong></a></p><p><em>Quick Guide to Building a Design System Series:</em><br><a href="https://medium.com/@mackyinling1215/design-system-concepts-and-establishing-basic-design-tokens-en-b1a974da0c16"><strong>#1. Design System Concepts and Establishing Basic Design Tokens</strong></a> | <em>#2. Expanding Design Tokens and UI Components</em> | <a href="https://medium.com/@mackyinling1215/from-design-to-code-i-en-92fbef6de06d"><strong>#3. From Design to Code (I)</strong></a> | <a href="https://medium.com/@mackyinling1215/from-design-to-code-ii-7a47036fb600"><strong>#4. From Design to Code (II)</strong></a></p><blockquote>This series of articles will introduce how to quickly build a Design System from scratch, covering everything from establishing Design Tokens and UI Components to creating CSS Variants Code that engineers can use directly.</blockquote><p>In the previous article, I introduced the basic concepts of design systems and how to quickly establish design tokens, the smallest building blocks in a design system. I will write another article about creating these Design Systems and Design Tokens in Figma files when I have time. In this article, I will first introduce how to utilize these established design tokens to build our UI components.</p><p>Before building these UI components, let’s first introduce Component Tokens.</p><h3>Component Tokens</h3><p>In the previous article, we briefly introduced the three levels of Design Tokens:</p><ul><li><strong>Foundation Tokens</strong></li><li><strong>Semantic Tokens</strong></li><li><strong>Component Tokens</strong></li></ul><figure><img alt="A flowchart illustrating the hierarchy of design tokens from default values to foundation, semantic, and component tokens." src="https://cdn-images-1.medium.com/max/1024/1*Wm1yWXAU8T9XIeQK4FzPzw.jpeg" /><figcaption>Design Tokens Structure</figcaption></figure><h4>When do we need to create Component Tokens?</h4><figure><img alt="Illustration of when to use component tokens. The right side shows the recommended approach — using a dedicated dialog-radius token for specific components like dialogs. The left side shows a less ideal approach where all components share the same radius-sm, causing visual inconsistency." src="https://cdn-images-1.medium.com/max/1024/1*hGadoLoIcoV6YfYX2U3qow.png" /></figure><p>We can think about this from three perspectives. If a UI component meets these criteria, we can create dedicated Component Tokens for it:</p><ul><li><strong>Reusability and Consistency</strong>: <br>Suppose we have 10 different types of modal dialogs in our system. If each dialog directly uses the Semantic Token [ radius-sm ], it&#39;s not only prone to design errors but also difficult to ensure visual consistency across all dialogs. In this case, we can create a Component Token [ dialog-radius ] to uniformly manage the border radius settings for all dialogs. This not only ensures design consistency but also reduces maintenance complexity.</li></ul><pre>/* Not recommended: directly using Semantic Tokens in individual components */<br>:root {<br>  --spacing-4: 0.25rem;<br>  --radius-sm: var(--spacing-4, 0.25rem);<br>}<br><br>.dialog-account { border-radius: var(--radius-sm); }<br>.dialog-share { border-radius: var(--radius-sm); }<br>.dialog-submit { border-radius: var(--radius-sm); }<br><br>/* Recommended: using Component Tokens for unified management */<br>:root {<br>  --spacing-4: 0.25rem;<br>  --radius-sm: var(--spacing-4, 0.52rem);<br>  --dialog-radius: var(--radius-md, 0.25rem);<br>}<br><br>.dialog { border-radius: var(--dialog-radius, 0.25rem); }</pre><ul><li><strong>Extensibility: </strong><br>When these modal dialogs need to support different sizes, we might need corresponding different border radius sizes. In this case, we can create two Component Tokens: [ dialog-radius-sm ] and [ dialog-radius-md ]. This naming convention not only clearly expresses the component variant relationships, but also makes it easy to expand when we need to add other sizes (such as lg, xl) in the future.</li></ul><pre>:root {<br>  --dialog-radius-sm: var(--radius-sm);<br>  --dialog-radius-md: var(--radius-md);<br>}<br><br>.dialog-sm { border-radius: var(--dialog-radius-sm); }<br>.dialog-md { border-radius: var(--dialog-radius-md); }</pre><ul><li><strong>Maintainability</strong>: <br>The biggest advantage of using Component Tokens is centralized management. When we need to adjust the border radius of dialogs, we only need to modify the values of the two tokens [ dialog-radius-sm ] and [ dialog-radius-md ], and all dialogs using these tokens will automatically update, eliminating the need to modify the styles of each component individually. This significantly improves maintenance efficiency and reduces the likelihood of errors.</li></ul><pre>/* Before adjustment */<br>:root {<br>  --dialog-radius-sm: var(--radius-sm);  /* 4px */<br>  --dialog-radius-md: var(--radius-md);  /* 6px */<br>}<br><br>/* After adjustment */<br>:root {<br>  --dialog-radius-sm: var(--radius-xs);  /* 6px */<br>  --dialog-radius-md: var(--radius-sm);  /* 8px */<br>}</pre><p>For other cases, using Semantic Tokens alone is sufficient.</p><h3>How to create Component Tokens?</h3><p>First, let’s introduce the <strong>basic naming structure composition of Component Tokens</strong>:</p><ul><li><strong>component</strong>: component name (e.g., dialog, button)</li><li><strong>property</strong>: CSS property (e.g., radius, background)</li><li><strong>variant/state</strong>: variant or state (e.g., md, hover)</li></ul><pre>/* Basic naming structure */<br>--{component}-{property}-{variant/state}<br><br>/* Naming examples */<br>--button-radius-xs: var(--radius-xs, 0.25rem);<br>--button-bg-hover: var(--background-brand, #f0f9ff);<br>--dialog-radius-md: var(--radius-md, 0.5rem);</pre><p><strong>The Hierarchy of Design Tokens</strong></p><p>Here’s how Component Tokens establish relationships with Tokens from other levels:</p><pre>:root {<br>  /* Foundation Design Token: The most basic design values */<br>  --spacing-4: 0.25rem;<br>  --colors-brand-0: #f0f9ff;<br>  --spacing-4: 0.5rem;<br>  <br>  /* Semantic Token: Giving semantic names to foundation tokens */<br> --radius-xs: var(--spacing-4, 0.25rem);<br> --background-brand: var(--colors-brand-0, #f0f9ff);<br> --radius-md: var(--spacing-8, 0.5rem);<br>  <br>  /* Component Token: Settings for specific components */<br> --button-radius-xs: var(--radius-xs, 0.25rem);<br> --button-bg-hover: var(--background-brand, #f0f9ff);<br> --dialog-radius-md: var(--radius-md, 0.5rem);<br>}</pre><h3>How to Build UI Components?</h3><p>In the previous article, we introduced that UI components are like LEGO blocks that can be arranged and combined to create the interfaces we want. This componentized design approach ensures our system has:</p><ul><li><strong>Visual Consistency</strong>: All components follow the same design principles</li><li><strong>Reusability</strong>: Components can be reused across different pages, saving development time</li><li><strong>Flexible Composition</strong>: Designers and engineers can flexibly combine these components to create various page layouts</li><li><strong>Easy Maintenance</strong>: When design updates are needed, only the base components need to be modified, and all places using that component will be updated synchronously</li></ul><h3>Building UI Component Steps</h3><h4><strong>Step 1: Choose UI Kits</strong></h4><p>We can start with selected UI Kits, which provide a large number of pre-built components that can serve as our starting point.</p><figure><img alt="Selection of button components from an existing UI kit, showcasing different interaction states and style variations including primary, outline, text, and disabled buttons." src="https://cdn-images-1.medium.com/max/1024/1*Jb6GWZpueF60pdIhh_zDeg.png" /><figcaption>Pre-built button components in UI Kit</figcaption></figure><h4><strong>Step 2: Customize Components and Link Design Tokens</strong></h4><p>Modify the pre-built components according to project requirements and link them with our established Tokens. We can think from several perspectives to make our UI components better match the format needed by engineers:</p><figure><img alt="Customized button components using the brand’s primary color and linked to design tokens, showcasing various interaction states and styles such as filled, outlined, and disabled." src="https://cdn-images-1.medium.com/max/1024/1*rwNlnYlV_lT97l4e_L0AlQ.png" /><figcaption>Customize components to match the product style</figcaption></figure><p><strong>Token Type Selection:</strong></p><ul><li>Semantic Token</li><li>Component Token</li></ul><p><strong>Interaction State Management:</strong></p><ul><li>Whether there are validation states: default state (none), error state (error), success state (success)</li><li>How many basic states: default state (rest), mouse hover (hover), clicking (active), keyboard focus (focus)</li><li>Whether it’s in disabled state: true/false</li><li>Whether there are selection states: selected/deselected, checked/unchecked</li></ul><figure><img alt="Customized UI component states and properties, showing checkbox, tabButton, and input elements with interaction states (e.g., hover, focus), size options, badges, validation, and required settings." src="https://cdn-images-1.medium.com/max/1024/1*CagPi2c_yWFf-1ATJ6gnPw.png" /><figcaption>UI Components Settings</figcaption></figure><h4><strong>Step 3: Create New Components</strong></h4><p>Different products may have different requirements, but basic UI Kits mostly only contain fundamental components (such as buttons, dropdown menus). Therefore, we will need to create additional custom components that aren’t included.</p><figure><img alt="Creating a new component, including controls for setting width, height, padding, margin, and alignment." src="https://cdn-images-1.medium.com/max/1024/1*m6a10BUXxifpH-NEUeFgSA.png" /><figcaption>Create custom components according to different products</figcaption></figure><p>Once we have selected our UI components, we can begin preparing to export the Design into Code.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/490/0*RfiS_yuE0gybfKzx.gif" /></figure><p>🌟 Next Article <a href="https://medium.com/@mackyinling1215/from-design-to-code-i-en-92fbef6de06d"><strong>#3. From Design to Code (I)</strong></a></p><p><a href="https://medium.com/@mackyinling1215/design-system-concepts-and-establishing-basic-design-tokens-en-b1a974da0c16"><strong>#1. Design System Concepts and Establishing Basic Design Tokens</strong></a> | <em>#2. Expanding Design Tokens and UI Components</em> | <a href="https://medium.com/@mackyinling1215/from-design-to-code-i-en-92fbef6de06d"><strong>#3. From Design to Code (I)</strong></a> | <a href="https://medium.com/@mackyinling1215/from-design-to-code-ii-7a47036fb600"><strong>#4. From Design to Code (II)</strong></a></p><p>If you found this article helpful, please show your support with a clap and share it with friends who might be interested.</p><p>If you’d like to learn more about Design Systems, feel free to contact me!</p><p><a href="https://www.linkedin.com/in/yin-ling-mack/">LinkedIn</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2d74d9adf75e" width="1" height="1" alt=""><hr><p><a href="https://www.designsystemscollective.com/expanding-design-tokens-and-ui-components-en-2d74d9adf75e">Expanding Design Tokens and UI Components</a> was originally published in <a href="https://www.designsystemscollective.com/">Design Systems Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Design System Concepts and Establishing Basic Design Tokens]]></title>
            <link>https://www.designsystemscollective.com/design-system-concepts-and-establishing-basic-design-tokens-en-b1a974da0c16?source=rss-a0521af3ea94------2</link>
            <guid isPermaLink="false">https://medium.com/p/b1a974da0c16</guid>
            <category><![CDATA[figma]]></category>
            <category><![CDATA[design-systems]]></category>
            <category><![CDATA[code]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[web-design]]></category>
            <dc:creator><![CDATA[Yin-Ling Mack]]></dc:creator>
            <pubDate>Tue, 07 Jan 2025 16:42:37 GMT</pubDate>
            <atom:updated>2025-05-05T13:22:11.217Z</atom:updated>
            <content:encoded><![CDATA[<h4>Quickly Building a Design System from Scratch (1/4)</h4><figure><img alt="Example of a design system showing color scales for brand, success, warning, and error on the left, alongside UI components like form fields, buttons, and dropdowns on the right." src="https://cdn-images-1.medium.com/max/1024/1*uJeJtvVW8hktUhK6aYReVg.png" /></figure><p>Language / 語言 : <em>English | </em><a href="https://medium.com/@mackyinling1215/complete-guide-design-system-60777773d1b8"><strong>中文</strong></a></p><p><em>Quick Guide to Building a Design System Series:</em><br><em>#1. Design System Concepts and Establishing Basic Design Tokens</em> | <a href="https://medium.com/@mackyinling1215/expanding-design-tokens-and-ui-components-en-2d74d9adf75e"><strong>#2. Expanding Design Tokens and UI Components</strong></a> | <a href="https://medium.com/@mackyinling1215/from-design-to-code-i-en-92fbef6de06d"><strong>#3. From Design to Code (I)</strong></a> | <a href="https://medium.com/@mackyinling1215/from-design-to-code-ii-7a47036fb600"><strong>#4. From Design to Code (II)</strong></a></p><blockquote>This series of articles will introduce how to quickly build a Design System from scratch, covering everything from establishing Design Tokens and UI Components to creating CSS Variants Code that engineers can use directly.</blockquote><p>In real product development, teams often face design consistency, development efficiency, and cross-department collaboration challenges. Establishing a comprehensive Design System can effectively address these issues by providing teams with a unified design language and reusable component library.</p><h3>This article is suitable for readers who are:</h3><h4><strong>Product Designers / UX UI Designers who want to…</strong></h4><ul><li>Improve work efficiency and avoid repeatedly modifying similar UI components</li><li>Enhance product design consistency and establish a unified visual language</li><li>Collaborate more effectively with development teams</li></ul><h4><strong>Engineers who want to…</strong></h4><ul><li>Improve development efficiency and reduce time spent on repeatedly developing similar UI components</li><li>Manage and maintain UI component libraries more systematically</li><li>Ensure code consistency and reusability</li></ul><h4><strong>Product Managers (PMs) who want to…</strong></h4><ul><li>Improve the overall efficiency of design and engineering teams</li><li>Accelerate product development cycles</li><li>Ensure consistency in product experience</li></ul><h3>Core Concepts of Design Systems</h3><figure><img alt="Various LEGO bricks in different colors and shapes spread out, representing modularity and composability in design." src="https://cdn-images-1.medium.com/max/1024/1*LKoG92AH5VRpEfbAufugww.jpeg" /><figcaption>Image source：<a href="https://unsplash.com/photos/blue-red-and-yellow-lego-blocks-OSvN1fBcXYE">https://unsplash.com/photos/blue-red-and-yellow-lego-blocks-OSvN1fBcXYE</a></figcaption></figure><h4>What is Design System?</h4><p>It’s like a <strong>LEGO building system</strong> — we first create many basic components with similar design styles, then use these components to arrange and combine them into the interfaces we need. In the LEGO world, we have bricks of different sizes and shapes but with consistent style; similarly, in a <strong>Design System</strong>, we have various UI components like <strong>buttons</strong>, <strong>forms</strong>, and <strong>notifications</strong> that share the same <strong>design principles</strong>, <strong>visual style</strong>, and <strong>interaction patterns</strong>.</p><figure><img alt="UI components from a design system, showcasing various states of CTA buttons, input fields, and notification cards with different visual and interaction styles." src="https://cdn-images-1.medium.com/max/1024/1*SveDK6FksKDuIbNLb1uE1w.png" /><figcaption>UI components: Buttons, Text input, Notification</figcaption></figure><p>Just like LEGO bricks have standardized connection methods that allow all pieces to fit together perfectly, a Design System defines clear usage guidelines and interaction patterns for UI components. This ensures:</p><ul><li><strong>Visual Consistency</strong>: All components follow the same design guidelines</li><li><strong>Reusability</strong>: Components can be reused across different pages, saving development time</li><li><strong>Flexible Combination</strong>: Designers and engineers can flexibly combine these components to create various page layouts</li><li><strong>Easy Maintenance</strong>: When design updates are needed, only the base components need to be modified, and all instances using those components will be updated automatically</li></ul><p>This systematic approach not only improves development efficiency but also ensures that the product maintains a consistent user experience throughout its expansion.</p><h3>How do we begin building these UI components?</h3><p>The construction of these UI components follows the same logic as LEGO bricks: start with the most basic blocks. In a Design System, these basic blocks are called <strong>Design Tokens</strong>.</p><h4>Design Tokens are composed of three levels:</h4><p><strong>Foundation Tokens</strong></p><ul><li>Define all the basic values used in the product</li><li>Examples: color code [#007AFF], font size [16px], spacing value [8px]</li></ul><p><strong>Semantic Tokens</strong></p><ul><li>Give practical meaning to Foundation Tokens</li><li>Examples: primary background color [background-primary-color], body text size [body-text-size], padding distance [padding-4]</li></ul><p><strong>Component Tokens</strong></p><ul><li>Used to manage specific properties of complex UI components</li><li>Examples: primary button background color [button-primary-background], small button border radius [button-sm-radius]</li></ul><figure><img alt="A flowchart illustrating the hierarchy of design tokens from default values to foundation, semantic, and component tokens." src="https://cdn-images-1.medium.com/max/1024/1*Wm1yWXAU8T9XIeQK4FzPzw.jpeg" /><figcaption>Design Tokens Structure</figcaption></figure><p>Therefore, the first step in building a complete UI component library is properly defining these basic Design Tokens. This hierarchical structure not only makes the design system easier to maintain and expand but also ensures consistency across the entire product design.</p><p>For reference on how to name Design Tokens, you can check out <strong>Nathan Curtis</strong>’s article <a href="https://medium.com/eightshapes-llc/naming-tokens-in-design-systems-9e86c7444676"><strong>Naming Tokens in Design Systems</strong></a>.</p><h3>Figma File Structure</h3><p>Before setting up Design Tokens, we need first to consider the Figma file structure, which can be determined based on your company and team size. I would recommend separating Design Tokens and UI component files. This is because when we accidentally modify Design Tokens, the UI component files will show notifications about the Design Token changes. However, if everything is placed in the same file, we might accidentally change our tokens without noticing.</p><figure><img alt="Comparison of two Figma file structures. The left shows a recommended hierarchical setup separating design tokens, UI components, and component patterns; the right shows a mixed folder structure combining design tokens and UI components, which is less recommended." src="https://cdn-images-1.medium.com/max/1024/1*S3fYe4Kzcre4POfwIcbHAg.png" /><figcaption>Figma File Structure</figcaption></figure><h3>Establishing Basic Design Tokens</h3><p>There are two main approaches to building Design Tokens:</p><h4><strong>Starting from Scratch</strong></h4><ul><li>Suitable for teams with sufficient resources and time</li><li>Begin by defining product style and color systems</li><li>Requires longer planning and discussion time</li></ul><h4><strong>Modifying Existing UI Kits</strong></h4><ul><li>Suitable for small teams</li><li>Customize based on mature UI Kits</li><li>Can quickly establish a usable Design System in a shorter time</li></ul><h3>Using Existing UI Kits to Build a Company-Specific Design System</h3><p>How to choose UI Kits? There are several points we need to consider:</p><p><strong>Whether Foundation tokens include basic design elements:</strong></p><ul><li>Colors</li><li>Typography system (font-family, font-size, font-weight)</li><li>Spacing and sizing</li></ul><figure><img alt="Overview of Figma’s local variables interface, showing categorized settings for color, spacing, and typography." src="https://cdn-images-1.medium.com/max/1024/1*LSULPCazMkeIvzjIwnuB0w.png" /><figcaption>Foundation Tokens</figcaption></figure><p><strong>Quality of Semantic tokens:</strong></p><ul><li>Whether naming conventions are intuitive and easy to understand</li><li>Whether naming is consistent</li><li>Whether usage scenarios are clearly defined</li></ul><figure><img alt="Interface in Figma showing semantic design tokens, with colors on the left and corresponding spacing on the right." src="https://cdn-images-1.medium.com/max/1024/1*gypxlr5WznhcvK41EnDmNw.png" /><figcaption>Semantic Tokens</figcaption></figure><h3>Setting Up a Company-Appropriate Design Tokens Structure</h3><p>When organizing Figma’s Local Variables, you can create Collections based on these three layers of Tokens (Foundation Tokens, Semantic Tokens, and Component Tokens).</p><figure><img alt="Comparison of three different design token collection structures: UI kits, company-specific usage, and a more granular categorization, all including foundation, semantic, and component tokens." src="https://cdn-images-1.medium.com/max/1024/1*YuIYSf_GYLy1LONNJJnw2A.png" /><figcaption>UI Kits and Company-Appropriate Design Tokens Structure</figcaption></figure><p>When a company has Product A and Product B, and Product A has both Web and App versions (Android and iOS), organizing tokens in three collections makes it easier to manage all products under the company.</p><ul><li><strong>Foundation Tokens</strong> (pure design atoms unrelated to specific products): Colors, dimensions, etc. that will be used across all company products.</li><li><strong>Semantic Tokens</strong> (product or theme-related): At this collection, tokens begin to differentiate between company products. Product A will have one set of Semantic Tokens, Product B will have another set, and these tokens are all derived from Foundation tokens.</li><li><strong>Component Tokens</strong> (product-specific components): Since Product A has Web and App versions (Android and iOS), Component Tokens will be divided into 3 sets: one for Web, one for iOS, and one for Android.</li></ul><h3>Reference and Naming Conventions for Design Variables</h3><p>When we find that the Design tokens in our chosen UI Kit are incomplete or not intuitively named, we can reference mature frameworks like Tailwind CSS to improve and expand them.</p><p>Let’s use <strong>spacing tokens</strong> as an example:</p><h4>Referencing Tailwind CSS’s Spacing System</h4><ul><li>Minimum value: 0px</li><li>Maximum value: 384px</li><li>Base unit: 4px</li><li>Naming logic: Increments based on the base unit (e.g., p-1 represents 4px)</li></ul><h4>Real Project Example</h4><p>Here’s a spacing naming example based on a 4px grid system:</p><pre>/* Padding Tokens */<br>--system-padding-2px: var(--system-spacing-2, 2px);<br>--system-padding-1: var(--system-spacing-4, 0.25rem);    /* 4px */<br>--system-padding-1s: var(--system-spacing-6, 0.375rem);  /* 6px */<br>--system-padding-2: var(--system-spacing-8, 0.5rem);     /* 8px */<br>--system-padding-2s: var(--system-spacing-10, 0.625rem); /* 10px */<br>--system-padding-3: var(--system-spacing-12, 0.75rem);   /* 12px */<br>--system-padding-4: var(--system-spacing-16, 1rem);      /* 16px */<br>--system-padding-5: var(--system-spacing-20, 1.25rem);   /* 20px */<br>--system-padding-6: var(--system-spacing-24, 1.5rem);    /* 24px */<br>--system-padding-7: var(--system-spacing-28, 1.75rem);   /* 28px */<br>--system-padding-8: var(--system-spacing-32, 2rem);      /* 32px */<br>--system-padding-9: var(--system-spacing-36, 2.25rem);   /* 36px */<br>--system-padding-10: var(--system-spacing-40, 2.5rem);   /* 40px *</pre><p>Setting up these examples as local variables in <strong>Figma</strong>:</p><figure><img alt="Figma interface for managing semantic spacing variables, with spacing categories on the left and corresponding names and values (e.g., padding and gap) on the right." src="https://cdn-images-1.medium.com/max/1024/1*GqeF2Lq1MWu0mkg-eViQNw.png" /><figcaption>Local Variables in Figma</figcaption></figure><h3>Example Naming Principles</h3><ul><li><strong>Basic Rule</strong>: Uses 4px as the basic increment unit</li><li><strong>Special Value Handling</strong>: Can directly use px units (like system-padding-2px) or use specific suffixes (like 1s representing values between 1 and 2)</li><li><strong>Consistency</strong>: The entire Design tokens system should maintain unified naming logic, whether for basic or special values</li></ul><p>This naming system is not only easy to understand but also convenient for maintenance and expansion. It’s important to establish clear naming convention documentation within the team to ensure all members can understand and correctly use these tokens.</p><p>Once we’ve selected our UI Kits and established our basic Design tokens, we can begin preparing to build our UI components.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/0*o6csT7KWpU05eqjA.gif" /></figure><p>🌟 Next Article: <a href="https://medium.com/@mackyinling1215/expanding-design-tokens-and-ui-components-en-2d74d9adf75e"><strong>#2. Expanding Design Tokens and UI Components</strong></a></p><p><em>#1. Design System Concepts and Establishing Basic Design Tokens</em> | <a href="https://medium.com/@mackyinling1215/expanding-design-tokens-and-ui-components-en-2d74d9adf75e"><strong>#2. Expanding Design Tokens and UI Components</strong></a> | <a href="https://medium.com/@mackyinling1215/from-design-to-code-i-en-92fbef6de06d"><strong>#3. From Design to Code (I)</strong></a> | <a href="https://medium.com/@mackyinling1215/from-design-to-code-ii-7a47036fb600"><strong>#4. From Design to Code (II)</strong></a></p><p>If you found this article helpful, please show your support with a clap and share it with friends who might be interested.</p><p>If you’d like to learn more about Design Systems, feel free to contact me!</p><p><a href="https://www.linkedin.com/in/yin-ling-mack/">LinkedIn</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b1a974da0c16" width="1" height="1" alt=""><hr><p><a href="https://www.designsystemscollective.com/design-system-concepts-and-establishing-basic-design-tokens-en-b1a974da0c16">Design System Concepts and Establishing Basic Design Tokens</a> was originally published in <a href="https://www.designsystemscollective.com/">Design Systems Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>