Dispatches From The Internets


E-Commerce Accessibility: Specifying UI Elements Using “Names”

For users relying on assistive technology such as screen readers, it’s … critically important to have programmatically determined names identifying various UI elements. … Doing so consistently with all interactive page elements will help ensure users using assistive technologies will be able to navigate through a site and complete a purchase successfully.

Could not have said it better myself. This article is chock full of excellent advice, not only on why names are important, but how to ensure your interactive components are properly named.




Bring Focus to the First Form Field with an Error

In a green field filled with only yellow flowers, a cute robot has found a single red flower, digital art

While filling out a long form the other day, I couldn’t figure out why it wasn’t submitting. Turns out I’d forgotten to fill in a field, but I didn’t know that because it had scrolled out of the viewport. This is a common problem on the web, but easily remedied with a little bit of JavaScript.




Equality vs. Equity

Pencil and watercolor illustration of an Indian man stepping off a city bus with a bag of groceries

Over the last few years, I’ve been quietly leading training efforts within Microsoft focused on leveling up folks’ allyship skills. There are a ton of really important lessons to be learned form the curriculum my team and I developed, but one folks ofter struggle with is the concept of “equality” as compared to “equity.”


When Equal Isn’t Equitable

This is an important insight from the Microsoft design research team regarding boosting the signal from historically excluded communities:

The trick is… the system is built on inequity, so finding customers who have been historically excluded means that you can’t expect to find them in the system itself.