The Best of the Internets

Will Your Toaster Become WCAG Compliant?

This is a really interesting look at the Internet of Things from the perspective of accessibility and how web standards may fit into it all.

While the applicability of WCAG 2.0 would need a high degree of interpretation to apply to a light bulb, web accessibility standards certainly apply to the browsers and apps that we use to centrally control it all. As this space continues to evolve, it’s vital that developers ensure that whatever devices control these products, accessibility is at the heart of them.


If you have problems understanding how nth-* selectors work in CSS, this visualizer may help you out.

The Trouble With Preprocessing Based on Future Specs

Lots of gold in this post from Chris Coyier. I agree with a lot of what he’s saying, but this passage really resonated with me:

[T]here are concepts that I think belong in an abstraction of a language and not the language itself. Variables could be an example here again. Preprocessor variables and native variables could co-exist and be useful in their own ways. If native CSS could do everything ever dreamed up in a preprocessor, it would be slow, complicated, and likely wouldn’t have seen the success that CSS has had as a language.

I could not agree more.

Windows 10 Upgrade Considerations for Screen Reader and Magnifier Users

The recommendation of IE over Edge may seem strange, but there’s a reason: Microsoft is changing APIs from MSAA (Microsoft Active Accessibility) to UIA (UI Automation) and it’s a work in progress. Consequently, the Microsoft Edge browser is not as accessible as the team would like it to be… yet. But, as Jacob Rossi covered in response to Steve Faulkner, it’s coming and the end result will be far better for folks who rely on assistive technology.