Topics: Code: HTML5

Responsive Images and Web Standards at the Turning Point

by Mat Marquis

Issue 351May 15, 2012

Responsible responsive design demands responsive images—images whose dimensions and file size suit the viewport and bandwidth of the receiving device. As HTML provides no standard element to achieve this purpose, serving responsive images has meant using JavaScript trickery, and accepting that your solution will fail for some users.

Then a few months ago, in response to an article here, a W3C Responsive Images Community Group formed—and proposed a simple-to-understand HTML picture element capable of serving responsive images. The group even delivered picture functionality to older browsers via two polyfills: namely, Scott Jehl’s Picturefill and Abban Dunne’s jQuery Picture. The WHATWG has responded by ignoring the community’s work on the picture element, and proposing a more complicated img set element.

Which proposed standard is better, and for whom? Which will win? And what can you do to help avert an “us versus them” crisis that could hurt end-users and turn developers off to the standards process? ALA’s own Mat Marquis explains the ins and outs of responsive images and web standards at the turning point.

Say No to Faux Bold

by Alan Stearns

Issue 350May 8, 2012

Browsers can do terrible things to type. If text is styled as bold or italic and the typeface family does not include a bold or italic font, browsers will compensate by trying to create bold and italic styles themselves. The results are an awkward mimicry of real type design, and can be especially atrocious with web fonts. Adobe’s Alan Stearns shares quick tips and techniques to ensure that your @font-face rules match the weight and styles of the fonts, and that you have a @font-face rule for every style your content uses. If you’re taking the time to choose a beautiful web font for your site, you owe it to yourself and your users to make certain you’re actually using the web font — and only the web font — to display your site’s content in all its glory.

Dive into Responsive Prototyping with Foundation

by Jonathan Smiley

Issue 348April 10, 2012

There are hundreds of devices out there right now that can access the full web, as Steve Jobs once put it. They come with different capabilities and constraints, things like input style or screen size, resolution, and form. With all these devices set to overtake traditional desktop computers for web traffic next year, we need tools to help us build responsively. Jonathan Smiley shows how to dive into responsive design using Foundation, a light front-end framework that helps you rapidly build prototypes and production sites.

The Vendor Prefix Predicament: ALA’s Eric Meyer Interviews Tantek Çelik

by Eric Meyer, Tantek Çelik

Issue 344February 14, 2012

During a public meeting of the W3C CSS Working Group, Mozilla web standards lead Tantek Çelik precipitated a crisis in Web Standards Land when he complained about developers who misunderstand and abuse vendor prefixes by only supporting WebKit’s, thereby creating a browser monoculture. Tantek’s proposed solution—having Mozilla pretend to be WebKit—inflamed many in the standards community, especially when representatives from Opera and Microsoft immediately agreed about the problem and announced similar plans to Mozilla’s. To get to the bottom of the new big brouhaha, exclusively for A List Apart, our Eric Meyer interviews Tantek on Mozilla’s controversial plan to support -webkit- prefixed properties.

Every Time You Call a Proprietary Feature “CSS3,” a Kitten Dies

by Lea Verou

Issue 344February 14, 2012

Any -webkit- feature that doesn’t exist in a specification (not even an Editor’s draft) is not CSS3. Yes, they are commonly evangelized as such, but they are not part of CSS at all. This distinction is not nitpicking. It’s important because it encourages certain vendors to circumvent the standards process, implement whatever they come up with in WebKit, then evangelize it to developers as the best thing since sliced bread. In our eagerness to use the new bling, we often forget how many people fought in the past decade to enable us to write code without forks and hacks and expect it to work interoperably. Lea Verou explains why single-vendor solutions are not the same as standards and not healthy for your professional practice or the future of the web.

Forward Thinking Form Validation

by Ryan Seddon

Issue 314September 21, 2010

When users complete a form to buy your product or sign up for your service, you want to reduce mistakes and guide them to success. Now, with HTML5 form input types and attributes, you can set validation constraints to check user input. With CSS3’s new UI pseudo-classes, you can style validation states to make form completion quick and effortless.

Apps vs. the Web

by Craig Hockenberry

Issue 312August 17, 2010

There's an app for that, and you're the folks who are creating it. But should you design a web-based application, or an iPhone app? Each approach has pluses and minuses—not to mention legions of religiously rabid supporters. Apple promotes both approaches (they even gave the web a year-long head start before beginning to sell apps in the store), and the iPhone's Safari browser supports HTML5 and CSS3 and brags a fast JavaScript engine. Yet many companies and individuals with deep web expertise choose to create iPhone apps instead of web apps that can do the same thing. Explore both approaches and learn just about everything you'll need to know if you choose to create an iPhone app—from the lingo, to the development process, to the tricks that can smooth the path of doing business with Apple.

Taking Advantage of HTML5 and CSS3 with Modernizr

by Faruk Ateş

Issue 308June 22, 2010

Years ago, CSS browser support was patchy and buggy, and only daring web designers used CSS for layouts. Today, CSS layouts are commonplace and every browser supports them. But the same can't be said for CSS3 and HTML5. That's where Faruk Ateş’s Modernizr comes in. This open-source JavaScript library makes it easy to support different levels of experiences, based on the capabilities of each visitor’s browser. Learn how to take advantage of everything in HTML5 and CSS3 that is implemented in some browsers, without sacrificing control over the user experience in other browsers.

A Brief History of Markup

by Jeremy Keith

Issue 305May 4, 2010

Hot off the presses! In his brand new, brief book for people who make websites, HTML5 For Web Designers, Jeremy Keith cuts through the confusion surrounding the web's new markup language and presents what every accessibility- and standards-focused web designer and developer needs to know about it—from semantics to strategy. Not only is HTML5 For Web Designers a great, fast read, it is also our first A Book Apart publication. To celebrate, A List Apart proudly presents all of "Chapter One: A Brief History of Markup." Enjoy!

Get Ready for HTML 5

by J. David Eisenberg

Issue 291September 1, 2009

Ready or not, here it comes. Despite the confusion surrounding its evolution, real-world HTML 5 is right around the corner. Longtime ALA contributor J. David Eisenberg returns to get us all up to speed on the markup we’re about to be writing.

Semantics in HTML 5

by John Allsopp

Issue 275January 6, 2009

The BBC's dropping of hCalendar because of accessibility and usability concerns demonstrates that we have pushed the semantic capability of HTML far beyond what it can handle. The need to clearly and unambiguously add rich, meaningful semantics to markup is a driving goal of the HTML 5 project. Yet HTML 5 has two problems: it is not backward compatible because its semantic elements will not work in 75% of our browsers; and it is not forward compatible because its semantics are not extensible. If "making up new elements" isn't the solution, what is?

A Preview of HTML 5

by Lachlan Hunt

Issue 250December 4, 2007

Who's afraid of HTML 5? Not Lachlan Hunt! As both a front-end web developer and a contributor to HTML 5, he tells us what we can expect from the emerging markup specification, whose goals include more flexibility and greater interoperability.