Earlier this week, we learned about designing safe animations for those living with motion sensitivity. Today, Val Head shares additional resources for creating more accessible animations.
For millions of people with vertigo and inner ear problems, large-scale web animations can trigger nausea, migraines, and dizziness. To make websites accessible for everyone, we don’t need to eliminate animation; we need to apply it more thoughtfully. Val Head walks us through some of the challenges posed by vestibular disorders and provides guidelines for designing with motion sensitivity in mind.
The dog days are upon us—but instead of giving up in the summer swelter, take heart! We’ve got an extra-special reading list of bright, insightful brainfood. ALA’s third annual summer reader explores what’s been on the web industry’s mind lately, from accessibility to performance, from CSS techniques to web type, from mentorship to more collaborative approaches. It’s a list as cool and fancy as a watermelon-basil popsicle. Yeah, that does sound good, doesn’t it? Kick back, chill out, and get to reading.
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.
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.
Getting plurals right in localization is a tricky prospect—each language has its own rules, and exceptions within those rules. How can we scale our websites and apps to respond to our global audience? Tingan Ho shows us how MessageFormat lessens some common pain points in the pluralization process.
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.
If economics is “the dismal science,” accessibility has long been the least loved branch of web design and development—and the least specified client requirement. Type and grids (especially the flexible variety) have fans aplenty. CSS, Sass, and frameworks draw huge, passionate crowds. But even die-hard front-enders and dedicated followers of best practices seem to wilt in the face of today’s greatly improved accessibility techniques. As a result, while most of us have kept up with the emerging methods, technologies, and challenges of multi-device design and development, essential and well supported specs like WAI-ARIA remain woefully under-implemented. Even the best of us seem to consider accessibility something to be done at the end of the job. Andrew Hoffman explains the advantages and necessity of an “accessibility first” approach.
The social events surrounding conferences are an integral part of the experience—and they mostly involve getting together over drinks. But as the industry becomes more inclusive, we gain more people for whom drinking isn’t a good option. It’s time to add more ways to party and meet up that give us a chance to network with all of our peers—and maybe even leave us feeling up for that second-day morning workshop.
Though some decry flat user interfaces as pure fashion, or as the obvious response to skeuomorphic trends, many designers have embraced the flat approach because the reduction in visual styling (such as gradients, drop shadows, and borders) creates interfaces that feel simpler and cleaner. Trouble is, most flat UIs are built with a focus on the provision of content, with transactional components (i.e., forms) receiving very little attention. So what happens when flat UIs and forms collide? User experiences can, and often do, suffer. Keep your flat forms from failing by using controlled redundancy to communicate difference.