Accessibility is not a feature. — ethanmarcotte.com
I care pretty deeply about accessible design. I wouldn’t call myself an accessibility specialist, mind you, but I’ve always felt that “designing for the web” means ensuring our work is accessible as broadly as possible. Not just accessible to differently-sized screens, but for people who might not browse the web like I do. Lately, I’ve been reflecting on some of the language I use to talk about ac
Left to our own devices. — ethanmarcotte.com
It’s easy, I think, to make the moral case for testing on old devices. There’s a more practical case, too. Recently, I was chatting with one of my clients, who was concerned how slowly their pages were loading for prospective customers in China. We talked about unreliable networks, perceived performance, and setting up a performance budget. And then we started talking a bit more generally about de
A working pattern library. — ethanmarcotte.com
Whether I’m designing a new site or auditing an existing one, nearly all my design projects from the last few years have culminated in a pattern library. But in my experience, the biggest challenge of modular design isn’t designing the patterns. It’s everything that comes after that. (That’s not to say designing in patterns is easy, mind.) Here’s the inimitable Alla Kholmatova, from her wonderful
1
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
Constrained CSS grids without <code>max-width</code>. — ethanmarcotte.com
Writing my accessibility statement. — ethanmarcotte.com
Bits. — ethanmarcotte.com
World wide wrist. — ethanmarcotte.com
AMPersand. — ethanmarcotte.com
Pattern patter. — ethanmarcotte.com
A bit more on container queries. — ethanmarcotte.com
