<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Design Systems on Ismael Ramos — Frontend Architect &amp; Product Engineer</title><link>https://www.ismaelramos.dev/pillars/design-systems/</link><description>Recent content in Design Systems on Ismael Ramos — Frontend Architect &amp; Product Engineer</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 05 Dec 2024 00:00:00 +0000</lastBuildDate><atom:link href="https://www.ismaelramos.dev/pillars/design-systems/index.xml" rel="self" type="application/rss+xml"/><item><title>Accessibility by default in a financial product at scale</title><link>https://www.ismaelramos.dev/case-studies/accessibility-implementation/</link><pubDate>Tue, 10 Sep 2024 00:00:00 +0000</pubDate><guid>https://www.ismaelramos.dev/case-studies/accessibility-implementation/</guid><description>Turning accessibility from an audit checklist into a property of the design system — so a platform serving millions across 20+ countries stays usable for keyboard, screen-reader and assistive-tech users by default.</description></item><item><title>A cross-team component library in LitElement</title><link>https://www.ismaelramos.dev/case-studies/cross-team-component-library/</link><pubDate>Thu, 05 Dec 2024 00:00:00 +0000</pubDate><guid>https://www.ismaelramos.dev/case-studies/cross-team-component-library/</guid><description>Building a framework-agnostic component library that ships into Angular apps, AEM-rendered pages and sibling products — so accessibility, theming and product polish stay consistent across teams in different countries.</description></item></channel></rss>