Frontend development is a field that changes daily, and to stay up-to-date, I need a steady source of new information. One way I do this is through newsletters.
Read more
of 12 newsletters for frontend developers
→
The description list (<dl>) is a magical element that can be used to mark up anything from dictionary entries to recipes. So, what’s so special about it?
Reading is a great way to learn, but it’s also a fantastic way to open yourself up to new ideas and experiences. As a developer, I believe reading is important to my continued growth and advancement. If you believe that too, you might enjoy these ten books that I find particularly interesting.
Read more
of 10 interesting books for developers
→
If you didn’t already know, your CSS can influence screen readers. One of the most surprising things to me was learning that VoiceOver removes list semantics from uls and ols when list-style-type: none is applied to them.
I wanted to share what my typical accessibility testing sessions look like. This is a quick over, but I hope you find it helpful (and if you haven’t done so yet, check out some accessibility quick wins I wrote about).
I sometimes give talks on Web accessibility, and one of the top questions I get is: What can I do right now to make my website more accessible? When I began practicing accessibility, I would’ve probably talked about WAI-ARIA authoring practices, and adding aria roles, and managing focus with JavaScript. That’s certainly true for more complex UI, but most of us aren’t building Twitter.
When I was first learning about accessibility on the Web, I stumbled across WebAIM (Web Accessibility In Mind), a fantastic resource for all things accessibility.