Registering for school, paying bills, updating government documents—we conduct a significant part of our daily lives through web forms. So when simply typing in your name breaks a form, well, user experience, we have a problem. As our population continues to diversify, we need designs that accommodate a broader range of naming conventions. Aimee Gonzalez shows how cultural assumptions affect what we build on the web—and how fostering awareness and refining our processes can start to change that.
Showing your in-progress designs can be scary, but there’s no better way to keep your product in line with your users’ needs. Research and testing aren’t just boxes to be checked off; they’re methodologies to be integrated into the entire design process—and the more, and the more diverse, the merrier. Jessica Harllee explains how Etsy shares their work with users every step of the way—and the benefits (and surprises) that follow.
Everyone talks a lot about empathy, but distilling that theory-driven talk into practices for our day-to-day work can seem daunting. Susan Robertson shows how she’s been able to practice empathy for users as a developer.
Attracting—and keeping—new users is a delicate dance. Too many obstacles and people don’t sign up; too little interaction and they don’t come back. The ideal onboarding process turns potential users into loyal ones—by thoughtfully identifying new users, teaching them to use your product, and giving them a reason to return. Rick Pastoor shares his onboarding framework and what he’s learned about the difference between a good onboarding process and a great one.
Half of all web pages are in English, but only about 28 percent of people using the internet speak English as a first language. Fortunately, designing for non-native English speakers doesn’t have to come with a huge price tag. Senongo Akpem shares three straightforward strategies for making your sites and apps more usable for non-native speakers.
Between the intricacies of documentation and the risk of wielding too much power over the browser, WAI-ARIA can be daunting. For the dev uncertain on how to fold accessibility best practices into their daily workflow, Lyza Gardner sets out to summarize one category of roles—the landmark roles. They help user agents map out the territories on a page so the user can navigate them with greater ease, and they’re a great place to start getting familiar with ARIA’s part in assistive technology.
Displays that are more tiny than our lowest-size breakpoints require a more condensed range of type sizes. If you don’t already have in place a typographic system that can absorb the demands of this new context (watches, wearables, digital sticky notes, whatever), now might be the time to consider it. Matt Griffin was ready for anything because his site was simple and built to be future friendly.
If you’ve been treating “people with disabilities” as an edge case for your websites, consider this a reckoning. Web accessibility means that everyone can use the web. The job of a web designer isn’t to question the configurations, devices, and tools that users bring to the table; it’s to rise to the challenge of making a site work for anyone who wishes to use it. Anne Gibson makes the case for site testing, inclusivity, and a better way of thinking about people online.
The labels of version links are key to navigating international websites. Making sure they are clear and unambiguous can increase user happiness and make you stand out in a crowd.
We all want user research that provides reliable guidance for our teams. But bias is tricky—it’s often introduced unknowingly. How can we be sure that the results of guerrilla user research sessions are as impartial as possible? Alla Kholmatova has the answer: getting more collaborative in how we plan, lead, evaluate, and analyze our user research.