From 3393841522864cfa3e069588307acb807ca24ab1 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ga=C3=ABl=20Poupard?= Date: Wed, 8 Dec 2021 14:16:41 +0100 Subject: [PATCH] fix(typo): in accessibility.md Looks like a typo, am I wrong? Thanks for this content @erikkroes, it's really useful :heart: --- docs/blog/accessibility.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/blog/accessibility.md b/docs/blog/accessibility.md index 6b4c010b3..3800ebeb3 100644 --- a/docs/blog/accessibility.md +++ b/docs/blog/accessibility.md @@ -38,7 +38,7 @@ To summarize, these are three reasons to focus on accessibility in your design s ## The accessibility of Lion -Using Lion does not ensure an accessible outcome. Sorry, it doesn't work like that. What it does provide is a solid base for you to build your own design systems and/or components with. It covers things like keyboard accessibility, UX design and semantics but a bad visual design can still ruin a lot. You have the freedom to use Lion for a white-on-yellow set of components (but it probably won't be very usable for many). It's your responsibility to use what's provide, and build something that includes people. +Using Lion does not ensure an accessible outcome. Sorry, it doesn't work like that. What it does provide is a solid base for you to build your own design systems and/or components with. It covers things like keyboard accessibility, UX design and semantics but a bad visual design can still ruin a lot. You have the freedom to use Lion for a white-on-yellow set of components (but it probably won't be very usable for many). It's your responsibility to use what's provided, and build something that includes people. ### Implementation