ayo/lion
1
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

fix(typo): in accessibility.md

Browse source 
Looks like a typo, am I wrong?

Thanks for this content @erikkroes, it's really useful ❤️
This commit is contained in:
Gaël Poupard 2021-12-08 14:16:41 +01:00 committed by GitHub
parent 30805edf12
commit 3393841522
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
docs/blog/accessibility.md
View file

@ -38,7 +38,7 @@ To summarize, these are three reasons to focus on accessibility in your design s
## The accessibility of Lion ## 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 ### Implementation