YohanYukiㆍ요한・謝雪
Things are going well in my attempt to create a modern website boilerplate.

Features:
- a11y / accessibility
- Semantic HTML (a11y)
- No FontIcons (a11y)
- IndieWeb
- Webmention
- Microformats
- Latest, widely supported CSS
- No code and practices from the old days. (Like a whole page of CSS resets and normalizations.)
- BEM methodology
YohanYukiㆍ요한・謝雪
Font Icons are bad for a11y (accessibility). Never ever use them again.
YohanYukiㆍ요한・謝雪
The best way is to use SVG icons.
YohanYukiㆍ요한・謝雪
You won't realise how bad a website, or mobile app, is when it comes to a11y until you, or a love one, needs it.
YohanYukiㆍ요한・謝雪
FontIcons are in the Top 5, if not the No.1, anti-a11y feature ever created.
YohanYukiㆍ요한・謝雪
People with Dyslexia find it hard to see font icons and make sense of it.
YohanYukiㆍ요한・謝雪
Screen readers don't skip font icons, they READ it. Imagine hearing something like, “unknown letter Facebook”. Screen readers don't read it as, “Facebook Icon, Facebook”.
YohanYukiㆍ요한・謝雪
Screen readers are used by a lot of people, for whatever reason. Yes, primarily by those with eye disability, but also by those who loves to do things by “voice”.
YohanYukiㆍ요한・謝雪
NoToDiscrimination Stop using Font Icons today!
載入新的回覆