The advent of responsive design and HiDPI (or “Retina”) devices has created a real challenge for web developers: We need a way to provide multiple images to accommodate a variety of window sizes and resolutions.
A lot has changed with web typography. We are no longer forced to use a handful of “web safe” fonts or complicated image replacement tricks in order to set beautiful type. This presentation goes over how to learn about type, how properly markup type and how to style it.
In this presentation, we cover Responsive Web Design, going from a basic overview of the concept to common design patterns and pitfalls. This was presented at the April 24, 2012 Web Developers Group Meeting.
Web design is a field prone to major shifts. For the last few years, the advent of the mobile web has commanded our attention. We must now assume that almost any site we produce will be viewed on a variety of devices—from phones, to tablets, to traditional desktops.
I believe the next major development will be high-definition displays, and this is a shift we should begin preparing for as soon as possible.
When developing a dropdown menu for your site, it’s important not to assume that all your visitors will be navigating with a mouse. Some might be using the keyboard exclusively to navigate your website.
Fortunately, enabling keyboard access is a relatively simple task.
Color vision deficiency, or color blindness, is a very common disease that affects about 8% of the population. For the MU home page that equals about 5,000 visitors a day. That’s a significant number of users, so it’s important that we add a color blind test to our regular set of accessibility checks.
We had a great discussion regarding web fonts and the future of typography on the web at our monthly Mizzou Web Developers meeting this week. Afterward, designer extraordinaire Josh Hughes sent an e-mail to the listserv outlining some of the basics. I present it to you, kind reader, in its entirety.
@font-face is all the rage in the CSS world these days and I’ve been dying to give it a whirl. This entry won’t discuss the best practices in terms of CSS syntax or the ins-and-outs of @font-face; that has been done in numerous other places which I will link to at the bottom of this entry. I’d rather focus on a specific Windows-related issue.