<?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 Thomas Michel on Medium]]></title>
        <description><![CDATA[Stories by Thomas Michel on Medium]]></description>
        <link>https://medium.com/@thomasmichel?source=rss-8032ee484735------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*htV2HtwJF8MgdH9vFyi3Ug.jpeg</url>
            <title>Stories by Thomas Michel on Medium</title>
            <link>https://medium.com/@thomasmichel?source=rss-8032ee484735------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 04:22:53 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@thomasmichel/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[The Great Color Migration: how we shipped WCAG rules at scale — without freezing the roadmap]]></title>
            <link>https://medium.com/@thomasmichel/the-great-color-migration-how-we-shipped-wcag-rules-at-scale-without-freezing-the-roadmap-5032a01c3b00?source=rss-8032ee484735------2</link>
            <guid isPermaLink="false">https://medium.com/p/5032a01c3b00</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[accessibility]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design-systems]]></category>
            <category><![CDATA[wcag]]></category>
            <dc:creator><![CDATA[Thomas Michel]]></dc:creator>
            <pubDate>Mon, 22 Sep 2025 07:04:58 GMT</pubDate>
            <atom:updated>2025-09-22T07:04:58.023Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3LU-Q-1ZQujV5tFPrhw43A.jpeg" /></figure><h3>The Great Color Migration: how we shipped WCAG rules at scale — without freezing the roadmap</h3><p><em>I’m Thomas Michel, Principal Designer at </em><a href="https://payfit.com/"><em>PayFit — a payroll and HRIS platform</em></a><em>. Over the past months I led a system-wide color migration to meet the European Accessibility Act while strengthening our brand identity. This is the behind-the-scenes story: what we changed, the tools we used, and the trade-offs that made it shippable.</em></p><p>I remember the Slack ping that kicked this off.</p><p>“EAA is now in force. Are we fully compliant?”</p><p>For context, the European Accessibility Act (EAA) came into effect in June 2025. While SaaS products like ours aren’t necessarily in the first enforcement wave, we chose to <strong>prepare now</strong> and treat <strong>WCAG 2.1 AA</strong> as our baseline across key surfaces. That reduces risk, serves users better, and aligns with our accessibility convictions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tnrA__XxrnT8r_fv1-erxw.png" /><figcaption>Current Colors used in our Design System</figcaption></figure><p>At PayFit, “<strong>Unity”</strong> is our current design system — created about two years ago. It hasn’t reached <strong>every</strong> corner of the app yet, but it will gradually replace our previous design system called “<strong>Midnight”</strong>. Unity favored neutral, accessibility-leaning defaults but still had AA gaps; Midnight prioritized vibrancy over contrast.”</p><p>Here, I was asked to lead a color revamp as Principal Designer: make Unity <strong>truly accessible</strong> and <strong>visually more confident</strong>. No feature freeze. No dramatic big-bang redesign. Just a deep, careful update to the foundation of… everything.</p><h3>Chapter 1 — Setting the brief before the hex</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*InaAt8kLFdyVMBaNTilHQg.png" /><figcaption>Screenshot of our Figjam board to define the first rules of changements</figcaption></figure><p>Before touching a single token, we set a <strong>human brief</strong> that would outlive any argument about our palette taste:</p><blockquote><strong><em>Our palette should be about:</em></strong><em> Trust, Confidence, Calm, Modern, Bright</em></blockquote><blockquote><strong><em>It should not be:</em></strong><em> Boring, Playful, Low-energy, Basic</em></blockquote><p>We ran <strong>two async color workshops</strong> in Figma with 4 designers from our Craft Guild <em>(Craft guild is an internal team of few product designer who want to work on side-subjects related to visual elements)</em>. The goal wasn’t “pick a pretty blue”, alongside the emotional brief, we captured working rules like:</p><ul><li><strong>Saturation envelopes</strong> for statuses so states read instantly without shouting.</li><li><strong>Greys that carry hierarchy</strong> (content, surfaces, separators) without flattening pages.</li><li><strong>Warmth vs. neutrality</strong> for brand expression without drifting into “playful.”</li><li><strong>State visibility</strong> across backgrounds (paper, cards, interactive zones).</li></ul><p>Each designer proposed a candidate palette under the same constraints; my job was to merge the strongest ideas into something <strong>systemic.</strong></p><p>A quick word on <strong>Unity’s architecture</strong>: <em>primitives → semantics → components.</em> It was the prevailing best practice when Unity was created, and for good reasons. It gives you leverage: change the <strong>intent</strong> (semantics), and dozens of surfaces improve together. <a href="https://designsystem.backbase.com/design-tokens"><em>Want to know more? Here is a good recap of this methodology.</em></a></p><h3>Chapter 2 — Audit reality, not theory</h3><p>We started with what users actually see. We pulled elements from the <strong>existing Figma library</strong>, then built a FigJam wall of <strong>real product screenshots</strong>. Three patterns emerged:</p><ul><li>too many <strong>very dark</strong> tones,</li><li>not enough <strong>saturation where states matter</strong>,</li><li>places where <strong>semantic intent</strong> didn’t match the visual result</li></ul><p>The goal wasn’t just “pass WCAG.” It was to <strong>refresh Unity’s character</strong> — less gloomy, more <strong>calmly confident</strong> — and to re-wire intent so one semantic change could uplift 30 places at once.</p><h3>Chapter 3 — How we built (and validated) the palette</h3><p>I split the work in two tracks: <strong>palette construction</strong> and <strong>system validation</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fY6pq88tp04C8aHjLZIEcQ.png" /><figcaption>Screenshot of my Figma board with color intent</figcaption></figure><p>I <strong>generated</strong> dozens of candidate palettes and killed the weak ones fast. Guided by our brief (<em>trust, confidence, calm; not playful</em>), I seeded core hues from brand needs and a 12-step shades, then used palette generators to build shade ladders and tune <strong>luminance gaps</strong>. Each candidate went through a 5-minute gate on the <strong>critical cases</strong>: body text on common surfaces, disabled text, input borders, focus rings, badge fills, and button. Anything that failed <strong>WCAG AA</strong> or felt <strong>visually heavy</strong> in forms/tables was tweaked or discarded. I tracked versions in FigJam (v1.0, v1.1…), kept what held up in real components, and only continued with the best one into the DS sandbox.</p><p><strong>Few Palette generator I used</strong></p><ul><li><a href="https://www.colorsandfonts.com/color-tools/color-converter/">Colors Converter (quick hex/HSL sanity)</a></li><li><a href="https://colorkit.co/color-shades-generator/">ColorKit — shades generator</a></li><li><a href="https://noeldelgado.github.io/shadowlord/">Shadowlord — relative luminance</a></li></ul><p><strong>Fast contrast checkers</strong></p><ul><li><a href="https://accessibleweb.com/color-contrast-checker/">Accessible Web Color Contrast Checker</a></li><li><a href="https://www.figma.com/community/plugin/748533339900865323">Figma Contrast plugin</a></li></ul><p>When WCAG rules felt fuzzy, I used <strong>Perplexity</strong> (and <strong>ChatGPT</strong>) to clarify edge cases, then wrote a short rule-of-thumb for the team (e.g., documented exceptions for <strong>non-text</strong> table lines to control visual weight).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2UDKS3nR1WOR538PEO7GFA.png" /><figcaption>Logic of Semantics applied into our Design System</figcaption></figure><h3>Chapter 4 —<strong> System validation (where the truth lives):</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aTX_ceSkIQOWH-ATPm8EgQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KsDsKu6loCzsteH3DDLYPw.png" /><figcaption>Used “Contrast” Figma plugin to check ratios + <a href="https://www.perplexity.ai/">Perplexity.a</a>i to deep dive on WCAG AA rules</figcaption></figure><ul><li>I created a <strong>“Color Test” branch</strong> into Unity Figma library. In this sandbox, we swapped primitives/semantics and let components <strong>auto-update</strong>.</li><li>Then, the unglamorous part: <strong>open each component, one by one</strong>. Look. Measure. Log.</li></ul><blockquote>A focus ring that looked perfect in isolation could swamp a quiet page.</blockquote><h3>Chapter 5— The “tricky” players: forms and tables</h3><p>These two are especially sensitive: even small contrast updates can change how a whole page reads.</p><h4>Forms (fields, borders, focus, helper text)</h4><p><strong>WCAG AA is deliberately strict.</strong> It asks for <strong>4.5:1</strong> on body text and <strong>3:1</strong> on <strong>non-text</strong> UI elements (like input borders and focus indicators). In practice, that’s a <strong>visibly higher contrast</strong> than many modern SaaS UIs use by default. The result? Form controls <strong>pop harder</strong>, pages can feel <strong>denser</strong>, and the first visual impression is “a bit too loud.”</p><p>We tested lighter treatments (0.5px borders, filled inputs, spacing tweaks, alternate neutrals) while staying within AA. Ultimately we optimized for <strong>accessibility by default</strong>: strict AA on form primitives and clear focus.</p><p><strong>Shipped:</strong> strict AA on form elements; <strong>border token bumped</strong> (e.g., L7 → L8), <strong>clear focus</strong> states, and <strong>labels/helper text</strong> always within ratio. The initial “contrast shock” fades after a few days—reliability stays.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wVykS9RHxOaW98CGdtF8bA.png" /></figure><h4>Tables (non-text UI)</h4><ul><li>Same approach: we ran <strong>a lot of tests</strong>, then decided to <strong>adapt design and rule</strong> with <strong>pragmatic trade-offs</strong>.</li><li>Shipped: <strong>text, icons, interactive states</strong> meet AA; <strong>headers/selected rows</strong> use stronger separators; <strong>regular separators</strong> are <strong>subtle</strong> (below strict 3:1 where allowed) so <strong>data</strong> — not the grid — gets the attention.</li></ul><h3>Chapter 6— What actually changed under the hood</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7IDpWy7UvuibaxY8gSa5fg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DTCXQJk4nC419xOtGJ9Z9g.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UlXRWlcC3i4B5BEmjOviyQ.png" /></figure><ul><li><strong>Neutral content</strong> gained <strong>headroom</strong> over standard backgrounds → body text reads more confidently across surfaces.</li><li><strong>Field borders</strong> stepped up (e.g., L7 → L8) to hit AA consistently in neutral UIs.</li><li><strong>Danger action</strong> hue/value shifted (we moved from an orange lineage to <strong>yellow</strong>), and <strong>labels flipped to black</strong> to keep contrast honest on the new ramps.</li><li>We rebalanced the <strong>greyscale</strong> so separators and surfaces carry hierarchy without flattening pages.</li><li>We introduced <strong>three new accent scales</strong> (Yellow, Teal, Pink) to widen expression</li><li>We updated +30 components to bring more UI and attention to details (by picking different color values on some parts of it).</li></ul><h4><strong>In number:</strong></h4><ul><li><strong>89%</strong> of primitives refreshed</li><li><strong>58%</strong> of semantic tokens refreshed</li><li><strong>96</strong> hue shifts</li></ul><p>Downstream, this meant <strong>real component work</strong> too</p><h3>Chapter 7— Handoff that made engineering faster</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VQu75nrZIVaLuhFDsFuUtA.png" /><figcaption>Screenshot of the specs made with ChatGPT &amp; .JSON imports (within 5min)</figcaption></figure><p>To make the work <strong>easier to implement</strong>, I used <a href="https://www.figma.com/community/plugin/1263743870981744253/design-tokens-manager"><strong>Design Tokens Manager plugin</strong></a><strong> </strong>to export <strong>old vs. new JSON</strong> and generated clear diff tables with GPT. Engineers got <strong>actionable data.</strong></p><pre>// before<br>{<br>  &quot;content.neutral.default&quot;: &quot;{primitive.gray.L1}&quot;,<br>  &quot;border.field.default&quot;: &quot;{primitive.gray.L7}&quot;,<br>  &quot;action.primary.fg&quot;: &quot;{primitive.white}&quot;<br>}<br>// after<br>{<br>  &quot;content.neutral.default&quot;: &quot;{primitive.gray.L5}&quot;,<br>  &quot;border.field.default&quot;: &quot;{primitive.gray.L8}&quot;,<br>  &quot;action.primary.fg&quot;: &quot;{primitive.black}&quot;<br>}</pre><p>We structured the JIRA Epic as a simple, reviewable sequence: <strong>primitives → semantics → component fixes</strong>. On the design side, the library updates propagated changes so designers didn’t have to chase manual edits in product files.</p><h3>Chapter 8— Rollout: quiet by design</h3><p>We <strong>spent a full month in joint QA across design and engineering</strong> <em>before</em> shipping to production — on purpose, to de-risk the release. Practically, that meant a DS sandbox in Figma, <a href="https://chromatic.com/"><strong>Chromatic</strong></a> <em>(for visual regression on our Storybook)</em> watching for pixel-level diffs, daily Slack loops to confirm intended changes, and a living Notion changelog explaining what changed, why, and what to check. That one-month dress rehearsal let us ship the final update as a <strong>quiet, one-shot merge</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2hSyC9GXQ12TNkmQpj2v_Q.png" /><figcaption>Screenshot of the Slack communication I made to announce new changements</figcaption></figure><blockquote>A week in, the feedback that mattered was practical: <strong>forms felt clearer</strong>, status colors read <strong>more intentionally</strong>, and Unity lost the “too dark / too serious” vibe without tipping into playful.</blockquote><p>We moved compliance from “should” to <strong>non-negotiable</strong>, aligning Unity with EAA/WCAG AA and removing real risk. Visually, Unity shifted from <strong>safe/dark/flat</strong> to a calmer, more <strong>confident</strong> voice.</p><h3>What I wish I’d known (so you don’t have to)</h3><ul><li><strong>Do the learning first.</strong> There are subtle trade-offs between a11y and visual lightness. Reading, benchmarking (Radix, Spectrum), and writing your <strong>red lines</strong> early saves weeks of “accessibility discovery” later.</li><li><strong>Explain decisions like a system owner.</strong> If a choice looks like taste, it gets debated like taste. Tie calls to <strong>WCAG, semantics, and UX outcomes</strong>.</li><li><strong>Prototype inside the design system.</strong> The <strong>Figma “Color Test”</strong> branch was the real MVP. Component auto-updates expose relationships you simply cannot see in a single page mock.</li><li><strong>Write your exceptions.</strong> Especially for <strong>non-text</strong> elements. Pragmatism is great; <strong>explicit pragmatism</strong> is better. Document when/why you deviate so the team can repeat it safely.</li><li><strong>Exported.</strong> <strong>JSON before/after</strong> lowers review friction and makes engineering faster. Pair it with a short checklist and a Chromatic screenshots review for confidence.</li></ul><blockquote>In short: we didn’t ship a new look — we strengthened the <strong>foundation</strong>. Unity is now more <strong>accessible</strong>, more <strong>coherent</strong>, and more <strong>on-brand</strong>.</blockquote><p>If this was useful, share it — and feel free to reach out to compare notes.</p><h4><strong>Connect with me</strong></h4><ul><li><strong>Portfolio</strong> — <a href="http://thomasmichel.me/">thomasmichel.me</a></li><li><strong>LinkedIn</strong> — <a href="https://www.linkedin.com/in/michelt/">https://www.linkedin.com/michelt/</a></li><li><strong>X (Twitter)</strong> — <a href="https://x.com/thomasmichel_">https://x.com/thomasmichel_</a></li><li><strong>Dribbble</strong>— <a href="https://dribbble.com/thomasmichel">https://dribbble.com/thomasmichel</a></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RhhFuT7uGw0cz3MXmBAudA.png" /><figcaption>Thanks for reading 🖤</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5032a01c3b00" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Creative Day Initiative]]></title>
            <link>https://medium.com/mention-design/monthly-creative-day-a2b8aa8f43e2?source=rss-8032ee484735------2</link>
            <guid isPermaLink="false">https://medium.com/p/a2b8aa8f43e2</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[motivation]]></category>
            <category><![CDATA[creative]]></category>
            <category><![CDATA[design-teams]]></category>
            <dc:creator><![CDATA[Thomas Michel]]></dc:creator>
            <pubDate>Fri, 01 Sep 2017 08:54:29 GMT</pubDate>
            <atom:updated>2017-12-27T22:33:13.462Z</atom:updated>
            <content:encoded><![CDATA[<h4>A day where designers can work on whatever they want as long as it is not related to the company.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BOh-yAjw-ZD8SP-rl8-pmA@2x.jpeg" /></figure><p>As designer you always need to be inspired, in fact that’s part of your job. But time to time the inspiration can go away and you start feeling unable to get something out. This situation happens very often for creators, at least 1 time each quarter for my part. As Lead Designer (at <a href="https://mention.com/">Mention.com</a>) this issue remains a priority to keep everyone in the team inspired. To do so I decided to take several initiatives, including the setup of a <strong>Creative Day. </strong>But what is a Creative Day? Well it is the same principle as a <em>level-up</em>, where designers can work on the subject of their choice in order to improve their knowledge. Here is a couple of insights that we gathered at Mention👇</p><blockquote>‘’You can only grow if you are willing to feel awkward or uncomfortable while trying something new.’’</blockquote><h3>Subjects</h3><p>The main goal of a Creative Day is therefore to get out of the comfort zone. Designers can work on whatever they want as long as it’s not a company’s project. Here is few examples of projects we’ve been working on:</p><ul><li>Redesign a website or an app</li><li>Explore a new tool/dev language</li><li>Create design ressource (icons/freebies…)</li><li>Improve wireframes skills</li><li>Or even … publish a Blog post (you got me!)</li></ul><h3>Milestones</h3><h4>9:30AM — Team kickoff</h4><p>The day start with a small kickoff to remain the millestones and objectives of the day. Then everyone takes few minutes to explain their project and the goal they want to achieve. (eg: being able to do a simple After Effect animation at the end of the day).</p><h4>9:45AM — Research/Executions</h4><p>Right after the kickoff designers start to do some research in order to organize their journey. Once ideas are clear &amp; precise everyone starts to work on their own to be as autonomous as possible.</p><h4>12AM — Project Update</h4><p>Each designer present their progress and ask for feedbacks if needed. This is usually the time where designers interact with each other about the problems encountered etc …</p><h4>6PM — Project Presentation</h4><p>At the end of the day we’re doing a small <strong>keynote</strong> where designers present a <strong>10min</strong> speech recalling their day and project. The interest of this presentation is to see how everyone managed their time but also to ask about the way they resolved issues and what they learned on the way. Another positive point is that people outside the design team attend to this presentation and ask quesitons from an <em>exterior</em> point of view. It’s not about presenting “his day”, it’s about sharing. A moment where everyone interact and learn something new.</p><h3>Results</h3><p>Here are some results from our first creative day. If you want to have a look:</p><ul><li>Order recap ⌚️ <a href="https://dribbble.com/shots/3946543-Order-Recap">https://dribbble.com/shots/3946543-Order-Recap</a></li><li>Nasa iOS redesign <a href="https://dribbble.com/shots/3552216-Nasa-Redesign">https://dribbble.com/shots/3552216-Nasa-Redesign</a></li><li>Exploring Framer prototyping tool</li><li>Fubiz iOS redesign</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wJnRqLRR-8v_WsRr2IqtrQ@2x.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SdHfVNmi0dPqmgyCgo1GKA@2x.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SXtv8bNnQpj7ZD1AOMHyhw@2x.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*o6qRjDIxXdAsjosE_VxKpQ@2x.jpeg" /></figure><h3>Day Insights</h3><p>So, what should we remember from a day like this? One thing I can confirm is that a Creative Day lets you learn something and get out of your comfort zone. Whether on a new skill, a tool or even on yourself. It helps you grow.</p><p>As I said from the beginning of this article you could feel “no longer inspired” by being in a company, mostly because of guidelines and legacy design. With this type of day you can therefore get out of these constraints by working on something which is not in your daily routine. It’s all about you learning/working on something different, at the rhythm you want.</p><blockquote>But what is the next step to get even more inspired? I’m currently working on a collection called “D Series” where I will be posting about other initiatives. Stay tuned …</blockquote><p>If you want to be the first to know about new content I’m posting, follow me on <a href="http://twitter.com/thomasmichel_">Twitter</a> or on <a href="https://dribbble.com/thomasmichel">Dribbble</a>.</p><p>Special thanks to <a href="https://twitter.com/CyrilCnt">Cyril Canete</a> for the help on this article ✌️</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a2b8aa8f43e2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/mention-design/monthly-creative-day-a2b8aa8f43e2">Creative Day Initiative</a> was originally published in <a href="https://medium.com/mention-design">Mention Design</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>