Whether you contribute to the user experience, development, or strategy of your website, you have a business, ethical, and (in many cases) legal responsibility to make your site accessible. And an equally compelling duty to your stakeholders, creativity, and career to achieve accessibility without sacrificing one whit of design or innovation. So what’s a site and application maker to do? For starters, read this book! We are thrilled to present an exclusive excerpt from Chapter 5 of A Web for Everyone: Designing Accessible User Experiences by Sarah Horton and Whitney Quesenbery, available now from Rosenfeld Media—and with a 20 percent discount for ALA readers, even.
More from A List Apart
We’re obsessive about collecting input from a wide range of potential users and stakeholders. But with such an onslaught of feedback, there’s always a risk of having your motivation and faith in humanity sucked right out of you. Sometimes, you just need calm critique from the few people who really get you. So which kind of feedback is best? The answer is both.
From the Blog
Part of getting comfortable with the command line is making it your own. Small customizations, shortcuts, and time saving techniques become second nature once you spend enough time fiddling around in your terminal. Since Git is my Version Control System of choice (due partially to its incredible popularity via GitHub), I like to spend lots of time optimizing my experience there.
I recently read Greg Smith’s piece on Bocoup's blog about how they think about time tracking, including all the fascinating data about how your brain works to solve problems. It interested me a lot, since I've been thinking about not just how I track projects, but also how I structure my day as a freelancer.