{"id":12374,"date":"2025-08-15T08:00:32","date_gmt":"2025-08-15T07:00:32","guid":{"rendered":"https:\/\/www.uxdesigninstitute.com\/blog\/?p=12374"},"modified":"2025-08-15T10:03:53","modified_gmt":"2025-08-15T09:03:53","slug":"building-accessible-design-systems","status":"publish","type":"post","link":"https:\/\/www.uxdesigninstitute.com\/blog\/building-accessible-design-systems\/","title":{"rendered":"Accessible design systems: why they matter and how to build one"},"content":{"rendered":"\n<h2><strong>What is an accessible design system?<\/strong><\/h2>\n<p><span style=\"font-weight: 400;\">A design system is a collection of reusable components, guidelines, and standards that teams follow to build consistent, cohesive products.\u00a0<\/span><\/p>\n<p><span style=\"font-weight: 400;\">It\u2019s a bit like a recipe book for a restaurant, ensuring every chef uses the same ingredients and follows the same steps to create signature dishes. That way, diners in the restaurant get the same great taste every time, no matter who\u2019s cooking.\u00a0<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Similarly, a design system contains all the building blocks needed to create websites and apps: things like buttons, icons, <\/span><a href=\"https:\/\/www.uxdesigninstitute.com\/blog\/guide-to-typography-design\/\"><span style=\"font-weight: 400;\">typography<\/span><\/a><span style=\"font-weight: 400;\">, colour palettes, and interaction patterns.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">That\u2019s design systems. <strong>So what about <\/strong><\/span><strong><i>accessible <\/i>design systems?<\/strong><\/p>\n<p><span style=\"font-weight: 400;\">Now let\u2019s imagine you want to bake a high-protein cake. You could follow a standard cake recipe and then try to add the protein afterwards\u2026or you could follow a recipe that already includes protein-rich ingredients.\u00a0<\/span><\/p>\n<p><span style=\"font-weight: 400;\">The second approach is much more reliable and straightforward (and it\u2019ll save you time).\u00a0<\/span><\/p>\n<p><span style=\"font-weight: 400;\">The same goes for accessibility. It\u2019s much more effective to bake accessibility into your designs from the very beginning than it is to try and bolt it on later.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">And that\u2019s exactly what an accessible design system does. It\u2019s just a normal design system, but with accessibility practices baked in. Every component is designed to be accessible by default, and that ultimately results in more consistently accessible products.\u00a0<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Rather than \u2018cooking from scratch\u2019 every time, you\u2019re referring back to your trusted recipe and stock of ingredients, ones that you know are inherently accessible and inclusive.\u00a0<\/span><\/p>\n<p><i><span style=\"font-weight: 400;\">Read also: <\/span><\/i><a href=\"https:\/\/www.uxdesigninstitute.com\/blog\/what-is-a-design-system\/\"><i><span style=\"font-weight: 400;\">What is a design system and why is it useful?<\/span><\/i><\/a><\/p>\n<table class=\"wp-list-table widefat fixed striped table-view-list posts\">\n<tbody id=\"the-list\">\n<tr id=\"post-11893\" class=\"iedit author-other level-0 post-11893 type-uxdipromotedcontent status-publish hentry\">\n<td class=\"shortcode column-shortcode\" data-colname=\"Shortcode\"><code class=\"highlight-shortcode\"><section id=\"promotion\" class=\"promotion-content-raw inlinepromo inlinepromo_professional-certificate-in-designing-for-accessibilityp-1 my-4\" style=\"\">\n\t<div class=\"w-container\">\n\t\t<div class=\"row align-items-center\">\n\t\t\t<div class=\"col-md-12 promotion-info\">\n                <a class=\"link-content\" href=\"https:\/\/www.uxdesigninstitute.com\/courses\/designing-for-accessibility?utm_campaign=blog_promo&amp;utm_source=blog&amp;utm_medium=blog_panel_text&amp;utm_content=inline\" style=\"\">\n                    <p>[GET CERTIFIED IN ACCESSIBLE DESIGN]<\/p>\n                    <span>Take our Professional Certificate in Designing for Accessibility<\/span>\n                <\/a>\n\t\t\t<\/div>\n\t\t<\/div>\n\t<\/div>\n<\/section>\n<\/code><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h2><strong>Why accessible design systems matter<\/strong><\/h2>\n<p><span style=\"font-weight: 400;\">Accessible design systems matter because <\/span><i><span style=\"font-weight: 400;\">accessibility <\/span><\/i><span style=\"font-weight: 400;\">matters.\u00a0<\/span><\/p>\n<p><span style=\"font-weight: 400;\">The <\/span><a href=\"https:\/\/www.who.int\/news-room\/fact-sheets\/detail\/disability-and-health\" target=\"_blank\" rel=\"noopener\"><span style=\"font-weight: 400;\">World Health Organization<\/span><\/a><span style=\"font-weight: 400;\"> estimates that 1 in 6 people worldwide live with a disability. Yet, in their analysis of the top 1 million website homepages, <\/span><a href=\"https:\/\/webaim.org\/projects\/million\/\" target=\"_blank\" rel=\"noopener\"><span style=\"font-weight: 400;\">WebAIM<\/span><\/a><span style=\"font-weight: 400;\"> found that over 94% had accessibility issues.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">The digital realm is nowhere near where it needs to be in terms of providing inclusive, user-friendly experiences to all and designers have a critical role to play in changing that.\u00a0<\/span><\/p>\n<p><strong>Designers and product teams must prioritise accessibility in order to:<\/strong><\/p>\n<ul>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Create products, services, and experiences that everybody can use and enjoy<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Ensure compliance with ever-tightening legal requirements (like the <\/span><a href=\"https:\/\/www.uxdesigninstitute.com\/blog\/european-accessibility-act-ux\/\"><span style=\"font-weight: 400;\">European Accessibility Act<\/span><\/a><span style=\"font-weight: 400;\">)<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Meet consumer expectations and keep up with competitors who are already leading the way with accessible and inclusive design<\/span><\/li>\n<\/ul>\n<p><span style=\"font-weight: 400;\">We need accessible design to close the accessibility gap, but it can\u2019t just be an afterthought or an add-on.\u00a0<\/span><\/p>\n<p><span style=\"font-weight: 400;\">It needs to be woven into the very fabric of the product, right down to every last detail. It needs to be a collective effort shared across product teams, and it needs to be consistent and ongoing.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">That\u2019s why accessible design systems are so important. They ensure that accessibility is a fundamental part of both the <\/span><a href=\"https:\/\/www.uxdesigninstitute.com\/blog\/product-design-process-guide\/\"><span style=\"font-weight: 400;\">product design process<\/span><\/a><span style=\"font-weight: 400;\"> and the product itself.\u00a0<\/span><\/p>\n<p><span style=\"font-weight: 400;\">When you build an accessible design system, you\u2019re embedding accessibility best practices into every component and guideline that shapes your product. This helps to create products that are consistently inclusive across every screen, page, or feature.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">From there, accessibility becomes scalable. No matter how big or complex the product grows, accessibility standards remain intact because they\u2019re embedded into the product\u2019s core \u2018recipe.\u2019\u00a0<\/span><\/p>\n<p><span style=\"font-weight: 400;\">With an accessible design system, you don\u2019t need to waste time fixing accessibility issues later on or making costly revisions, and you don\u2019t need to scramble to meet new accessibility laws and requirements. You\u2019re prioritising accessibility from the start and committing to it long-term.\u00a0<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Accessible design systems are an incredibly powerful tool, and they\u2019re a fundamental step towards more <\/span><a href=\"https:\/\/www.uxdesigninstitute.com\/blog\/what-is-accessible-design\/\"><span style=\"font-weight: 400;\">accessible design<\/span><\/a><span style=\"font-weight: 400;\">. So how do you build one?<\/span><\/p>\n<p><span style=\"font-weight: 400;\">We\u2019ll share our step-by-step guide shortly. But first, let\u2019s break down the key components you\u2019ll find in every accessible design system.\u00a0<\/span><\/p>\n<h2><strong>The key components of an accessible design system<\/strong><\/h2>\n<p><span style=\"font-weight: 400;\">To create an accessible design system, you\u2019ll need the following building blocks:<\/span><\/p>\n<h3><strong>Inclusive UI components<\/strong><\/h3>\n<p><span style=\"font-weight: 400;\">These are the interactive elements you use every day, like buttons, forms, navigation menus, and modals.\u00a0<\/span><\/p>\n<p><span style=\"font-weight: 400;\">In an accessible design system, these components are designed to be accessible right out of the box. That means they have clear focus indicators, support keyboard navigation, and include ARIA roles and attributes so they can be easily interpreted by screen readers.\u00a0<\/span><\/p>\n<h3><strong>Semantic structure and coding guidelines<\/strong><\/h3>\n<p><span style=\"font-weight: 400;\">Your design system should provide clear HTML and CSS guidelines that make sure everything is built with meaningful, semantic structure.\u00a0<\/span><\/p>\n<p><span style=\"font-weight: 400;\">This helps assistive technologies interpret your content correctly. Good documentation also makes it easier for your team to keep accessibility consistent across the board.<\/span><\/p>\n<h3><strong>Colour, contrast, and typography<\/strong><\/h3>\n<p><span style=\"font-weight: 400;\">An accessible design system uses colour palettes with sufficient contrast, scalable typography, and thoughtful spacing to ensure content is legible for users with varying visual abilities.<\/span><\/p>\n<h3><strong>Patterns and usability standards<\/strong><\/h3>\n<p><span style=\"font-weight: 400;\">In an accessible design system, reusable templates and interaction patterns are designed with accessibility in mind. This includes built-in support for keyboard navigation, screen readers, and other assistive technologies.<\/span><\/p>\n<h3><strong>Accessibility testing and maintenance\u00a0<\/strong><\/h3>\n<p><span style=\"font-weight: 400;\">Ongoing testing (both automated and with real users) is key to maintaining accessibility over time. A good design system includes guidelines and tools for validating accessibility and updating components as standards and user needs evolve.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Those are the building blocks. Now how do you bring them all together into a cohesive and repeatable design system? Let\u2019s take a look.\u00a0<\/span><\/p>\n<h2><strong>How to build an accessible design system (step-by-step)<\/strong><\/h2>\n<p><span style=\"font-weight: 400;\">Whether you\u2019re revising an existing design system or building one from scratch, here\u2019s how to prioritise and improve accessibility throughout.\u00a0<\/span><\/p>\n<h3><strong>1. Define accessibility standards from the start<\/strong><\/h3>\n<p><span style=\"font-weight: 400;\">Before you do anything else, set a clear benchmark for how you\u2019re defining and measuring accessibility. For example, you might build your design system to meet WCAG 2.2. Level AA requirements (that\u2019s what most products should be aiming for).\u00a0<\/span><\/p>\n<p><span style=\"font-weight: 400;\">At this stage, make sure you also consider legal requirements in your region. If you\u2019re in the European Union (or serving customers in the EU), for example, you\u2019ll need to comply with standards set out by the European Accessibility Act.\u00a0<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Whatever standard you\u2019re aiming for, document it. This gives everyone a shared target and will help you build your design system accordingly.\u00a0<\/span><\/p>\n<p><i><span style=\"font-weight: 400;\">Read also: <\/span><\/i><a href=\"https:\/\/www.uxdesigninstitute.com\/blog\/what-are-the-wcag-guidelines\/\"><i><span style=\"font-weight: 400;\">What are the Web Content Accessibility Guidelines (WCAG) and why are they so important?<\/span><\/i><\/a><\/p>\n<h3><strong>2. Audit your existing design system (or choose a proven framework to create a new one)<\/strong><\/h3>\n<p><span style=\"font-weight: 400;\">If you already have a design system in place, now\u2019s the time to review it. Look at your existing components and check how they perform when it comes to accessibility.\u00a0<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Are they keyboard accessible? Do they use semantic HTML? Is colour contrast sufficient? How do they behave with screen readers?<\/span><\/p>\n<p><strong>Here are some tools and techniques to help you with the audit:<\/strong><\/p>\n<ul>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><b>Automated checkers<\/b><span style=\"font-weight: 400;\"> like <\/span><a href=\"https:\/\/www.deque.com\/axe\/devtools\/\" target=\"_blank\" rel=\"noopener\"><span style=\"font-weight: 400;\">Axe DevTools<\/span><\/a><span style=\"font-weight: 400;\">, <\/span><a href=\"https:\/\/developer.chrome.com\/docs\/lighthouse\/overview\/\" target=\"_blank\" rel=\"noopener\"><span style=\"font-weight: 400;\">Lighthouse<\/span><\/a><span style=\"font-weight: 400;\">, or <\/span><a href=\"https:\/\/wave.webaim.org\/\" target=\"_blank\" rel=\"noopener\"><span style=\"font-weight: 400;\">WAVE<\/span><\/a><span style=\"font-weight: 400;\"> can quickly flag common accessibility issues.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><b>Keyboard testing<\/b><span style=\"font-weight: 400;\">: Try navigating your components using only the keyboard (Tab, Enter, and arrow keys). Can you access all interactive elements? Is the focus order logical and visible?<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><b>Screen reader testing<\/b><span style=\"font-weight: 400;\">: Use a screen reader like VoiceOver (Mac), NVDA (Windows), or TalkBack (Android) to check whether your components are announced properly and make sense when read aloud.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><b>Colour contrast checkers<\/b><span style=\"font-weight: 400;\"> like <\/span><a href=\"https:\/\/contrast-grid.eightshapes.com\/\" target=\"_blank\" rel=\"noopener\"><span style=\"font-weight: 400;\">Contrast Grid<\/span><\/a><span style=\"font-weight: 400;\"> or <\/span><a href=\"https:\/\/webaim.org\/resources\/contrastchecker\/\" target=\"_blank\" rel=\"noopener\"><span style=\"font-weight: 400;\">WebAIM\u2019s Contrast Checker<\/span><\/a><span style=\"font-weight: 400;\"> help ensure your text is readable against background colours.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><b>Semantic HTML review:<\/b><span style=\"font-weight: 400;\"> Inspect your code to make sure you\u2019re using semantic elements (like &lt;button&gt; instead of &lt;div&gt;) and appropriate ARIA attributes where necessary.<\/span><\/li>\n<\/ul>\n<p><span style=\"font-weight: 400;\">Once you\u2019ve identified where things fall short, map out a plan to improve accessibility across your components.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">If you\u2019re starting your design system from scratch, don\u2019t reinvent the wheel. Use a trusted system like the <\/span><a href=\"https:\/\/design-system.service.gov.uk\/\" target=\"_blank\" rel=\"noopener\"><span style=\"font-weight: 400;\">GOV.UK design system<\/span><\/a><span style=\"font-weight: 400;\"> or Google\u2019s <\/span><a href=\"https:\/\/m3.material.io\/\" target=\"_blank\" rel=\"noopener\"><span style=\"font-weight: 400;\">Material Design<\/span><\/a><span style=\"font-weight: 400;\"> as a foundation. These frameworks already include accessible components and patterns you can learn from and adapt.<\/span><\/p>\n<h3><strong>3. Build accessible components (or refactor existing ones)<\/strong><\/h3>\n<p><span style=\"font-weight: 400;\">As we outlined earlier, every accessible design system is made up of accessible components. So the next step is to either create your accessible components from scratch, or refactor existing components to make them more accessible.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Focus first on the elements users interact with most, especially those that often cause accessibility issues: buttons, links, forms, input fields, modals, navigation menus, and tabs.<\/span><\/p>\n<p><strong>As you go, keep these best practices in mind:<\/strong><\/p>\n<ul>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Use semantic HTML wherever you can<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Include clear labels (both visible labels and \u2018hidden\u2019 labels for screen readers)<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Make sure every component works with a keyboard<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Test with assistive tech, not just visually<\/span><\/li>\n<\/ul>\n<p><span style=\"font-weight: 400;\">Your components form the foundation of your design system, so take the time to get them right and make sure they\u2019re accessible by default.<\/span><\/p>\n<h3><strong>4. Create clear and accessible documentation\u00a0<\/strong><\/h3>\n<p><span style=\"font-weight: 400;\">A good design system doesn\u2019t only show how components should look and function. It also explains how to use them properly.\u00a0<\/span><\/p>\n<p><strong>Create clear documentation that guides people on how to build accessible experiences using the system and components you\u2019ve created. Include:<\/strong><\/p>\n<ul>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">A clear explanation of each component\u2019s accessibility features<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Examples of both correct and incorrect usage<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Live demos or code samples that show accessibility in action<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">General guidelines and best practices for accessibility<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">An accessibility checklist (we\u2019ve written an <\/span><span style=\"font-weight: 400;\">essential accessibility checklist for designers <a href=\"https:\/\/www.uxdesigninstitute.com\/blog\/accessibility-checklist-for-designers\/\">here<\/a>,<\/span><span style=\"font-weight: 400;\">\u00a0you can use it to guide you)<\/span><\/li>\n<\/ul>\n<p><span style=\"font-weight: 400;\">And remember: your documentation must be accessible, too. Use plain language, easily readable formatting, clear examples and content that makes sense for everyone, not just designers and developers.\u00a0<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Store your documentation in a shared space that everyone can access, and remember to update it regularly as your design system (and product) evolves.\u00a0\u00a0<\/span><\/p>\n<p><i><span style=\"font-weight: 400;\">Read also: <\/span><\/i><a href=\"https:\/\/www.uxdesigninstitute.com\/blog\/ux-documentation-tools\/\"><i><span style=\"font-weight: 400;\">The best UX documentation tools (and why you need them)<\/span><\/i><\/a><i><span style=\"font-weight: 400;\">.<\/span><\/i><\/p>\n<h3><strong>5. Establish processes for regular testing and maintenance<\/strong><\/h3>\n<p><span style=\"font-weight: 400;\">Accessibility isn\u2019t a one-time effort; it needs to be continuous and ongoing. Make sure you\u2019re regularly testing your components and keeping your design system up to date as standards evolve and your product changes.<\/span><\/p>\n<p><strong>Build accessibility checks into your team\u2019s workflows so they become part of the day-to-day process, not a separate task at the end. For example, you can:<\/strong><\/p>\n<ul>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Use automated tools like Axe, Lighthouse, or WAVE during development<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Test components manually using a keyboard and screen reader<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Run accessibility audits during major updates or new releases<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Encourage feedback from users with disabilities<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Assign accessibility champions to help embed best practices across teams<\/span><\/li>\n<\/ul>\n<p><span style=\"font-weight: 400;\">Keeping your design system accessible over time isn\u2019t just about fixing issues. It\u2019s also about building a culture of inclusion into how you design, build, and ship every day.<\/span><\/p>\n<h3><strong>Bonus tip:<\/strong><\/h3>\n<p><span style=\"font-weight: 400;\">Make building an accessible design system a collaborative effort across teams. Involve designers, developers, <\/span><a href=\"https:\/\/www.uxdesigninstitute.com\/blog\/what-does-a-ux-writer-do\/\"><span style=\"font-weight: 400;\">content designers<\/span><\/a><span style=\"font-weight: 400;\">, and accessibility specialists. This helps to create a shared understanding and sense of accountability around accessibility, which is crucial for ensuring your design system has maximum impact across the organisation.<\/span><\/p>\n<h2><strong>Avoid these common pitfalls when building your accessible design system<\/strong><\/h2>\n<p><span style=\"font-weight: 400;\">Even with the best intentions, there are some common mistakes that can limit the impact of your accessible design system. Here are some pitfalls to look out for, and how to avoid them:\u00a0<\/span><\/p>\n<h3><strong>Pitfall #1: Treating accessibility as an add-on<\/strong><\/h3>\n<p><span style=\"font-weight: 400;\">You already know that accessibility needs to be embedded in the design process from the very start, and that\u2019s why you\u2019re building an accessible design system.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">However, there\u2019s always the danger that people only refer to the system at the end of a project, using it as a checklist rather than a foundation or starting point.\u00a0<\/span><\/p>\n<p><span style=\"font-weight: 400;\">To avoid this, make sure your design system is positioned as a core, go-to resource that\u2019s part of everyday workflows, not something you only consult when the work is done.\u00a0<\/span><\/p>\n<h3><strong>Pitfall #2: Focusing only on visual design\u00a0<\/strong><\/h3>\n<p><span style=\"font-weight: 400;\">It\u2019s easy to assume that if something looks clean and clear, it must be accessible. But accessibility goes beyond how things look. Make sure your team is also testing how components behave, using a keyboard, navigating with a screen reader, and interacting with different states. A visually polished design isn\u2019t enough if users can\u2019t actually use it.<\/span><\/p>\n<h3><strong>Pitfall #3: A lack of knowledge and training around accessibility<\/strong><\/h3>\n<p><span style=\"font-weight: 400;\">An accessible design system is a great first step towards more accessible design. But if your team doesn\u2019t have the knowledge, skills, mindset, and confidence to prioritise and advocate for accessibility, it will only get you so far.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">To truly make an impact, pair your design system with ongoing skills development, be that through in-house workshops, peer-to-peer learning, or formal training.\u00a0<\/span><\/p>\n<p><span style=\"font-weight: 400;\">If you\u2019re serious about leveling up your approach to accessibility, check out the UX Design Institute\u2019s <\/span><a href=\"https:\/\/www.uxdesigninstitute.com\/courses\/designing-for-accessibility\"><span style=\"font-weight: 400;\">Professional Certificate in Designing for Accessibility<\/span><\/a><span style=\"font-weight: 400;\">.\u00a0<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Through self-paced modules, an expert-led curriculum, and practical exercises, you\u2019ll learn how to embed accessibility into your design process, from research and testing, right through to championing accessibility and getting stakeholder buy-in.\u00a0<\/span><\/p>\n<table class=\"wp-list-table widefat fixed striped table-view-list posts\">\n<tbody id=\"the-list\">\n<tr id=\"post-11893\" class=\"iedit author-other level-0 post-11893 type-uxdipromotedcontent status-publish hentry\">\n<td class=\"shortcode column-shortcode\" data-colname=\"Shortcode\"><code class=\"highlight-shortcode\"><section id=\"promotion\" class=\"promotion-content-raw inlinepromo inlinepromo_professional-certificate-in-designing-for-accessibilityp-1 my-4\" style=\"\">\n\t<div class=\"w-container\">\n\t\t<div class=\"row align-items-center\">\n\t\t\t<div class=\"col-md-12 promotion-info\">\n                <a class=\"link-content\" href=\"https:\/\/www.uxdesigninstitute.com\/courses\/designing-for-accessibility?utm_campaign=blog_promo&amp;utm_source=blog&amp;utm_medium=blog_panel_text&amp;utm_content=inline\" style=\"\">\n                    <p>[GET CERTIFIED IN ACCESSIBLE DESIGN]<\/p>\n                    <span>Take our Professional Certificate in Designing for Accessibility<\/span>\n                <\/a>\n\t\t\t<\/div>\n\t\t<\/div>\n\t<\/div>\n<\/section>\n<\/code><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h2><strong>The takeaway<\/strong><\/h2>\n<p><span style=\"font-weight: 400;\">Accessible design is about creating products and services that everybody can use. Ethically, it\u2019s the right thing to and from a business perspective, it\u2019s crucial for staying compliant and competitive.\u00a0<\/span><\/p>\n<p><span style=\"font-weight: 400;\">With an accessible design system, you can embed accessibility right into your design process and make sure it\u2019s a priority for everyone working on the product. Follow the steps we\u2019ve laid out in this guide to improve your existing design system or build a new one from scratch.\u00a0<\/span><\/p>\n<p><span style=\"font-weight: 400;\">And remember: accessibility is an ongoing effort, not a one-off checkbox. Keep learning and adapting your design practice as accessibility standards evolve.\u00a0<\/span><\/p>\n<p><strong>Want to learn more about accessible design? Check out:<\/strong><\/p>\n<ul>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><a href=\"https:\/\/www.uxdesigninstitute.com\/blog\/accessible-design-heather-hepburn\/\"><span style=\"font-weight: 400;\">Making accessibility real: practical insights from Skyscanner\u2019s Head of Accessibility, Heather Hepburn<\/span><\/a><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><a href=\"https:\/\/www.uxdesigninstitute.com\/blog\/user-experience-accessibility\/\"><span style=\"font-weight: 400;\">How to optimise your website for user experience accessibility<\/span><\/a><\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>One in six people, about 1.3 billion, live with a disability and face barriers to using digital products and services. While this gap is not new, stricter laws and growing awareness are making it harder to ignore. There is no single fix, but embedding accessibility into your design system is one of the most effective solutions. In this guide, we will explore why it matters and how to build one.<\/p>\n","protected":false},"author":22,"featured_media":12375,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"content-type":"","footnotes":""},"categories":[273],"tags":[],"class_list":["post-12374","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-how-to-guides"],"_links":{"self":[{"href":"https:\/\/www.uxdesigninstitute.com\/blog\/wp-json\/wp\/v2\/posts\/12374","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.uxdesigninstitute.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.uxdesigninstitute.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.uxdesigninstitute.com\/blog\/wp-json\/wp\/v2\/users\/22"}],"replies":[{"embeddable":true,"href":"https:\/\/www.uxdesigninstitute.com\/blog\/wp-json\/wp\/v2\/comments?post=12374"}],"version-history":[{"count":4,"href":"https:\/\/www.uxdesigninstitute.com\/blog\/wp-json\/wp\/v2\/posts\/12374\/revisions"}],"predecessor-version":[{"id":12379,"href":"https:\/\/www.uxdesigninstitute.com\/blog\/wp-json\/wp\/v2\/posts\/12374\/revisions\/12379"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.uxdesigninstitute.com\/blog\/wp-json\/wp\/v2\/media\/12375"}],"wp:attachment":[{"href":"https:\/\/www.uxdesigninstitute.com\/blog\/wp-json\/wp\/v2\/media?parent=12374"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.uxdesigninstitute.com\/blog\/wp-json\/wp\/v2\/categories?post=12374"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.uxdesigninstitute.com\/blog\/wp-json\/wp\/v2\/tags?post=12374"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}