Delay happens. The train is late, the flight is cancelled, the traffic is murder. Travel is the leading edge of entropy, and entropy is the universe’s final comment on the meaning of it all. If the universe is expanding and there are snow delays on Route 1, it’s not your fault that you’re 15 minutes late to the meeting, right?

Don’t be so quick to excuse yourself. If 80% of success is just showing up, 90% is showing up early.

It’s hard for the client to sympathize with your lateness when she, who had farther to travel, managed to make the meeting on time. No matter how well you tell your story about the newbie cab driver who thought you said 114th Street, the client still sat waiting for you for twenty minutes after denying herself a Starbuck’s so she would be on time. Everyone in the room is a grownup, and, on the surface, your lateness isn’t an issue. But although nothing will be said, somehow the meeting will not turn out as well as expected.

Of course the conference organizers care that you, their keynote speaker, spent the night in the airport because of a cancelled flight. As sensitive human beings, they’d love to upgrade your room to a suite, hire you a masseuse, and send you to bed. But as business people who spent the morning juggling their schedule and making impromptu excuses to attendees because their keynote speaker showed up late, they will never hire you again.

How can a client blame you for a cab driver’s mistake? How can a conference organizer hold you accountable for an airline’s cancelled flight?

They can do it because lateness is part of the order of things, and grownup professionals plan for it, just as they plan for budget shortfalls and extra rounds of revision.

If you plan to arrive early, then you are covered when circumstances beyond your control conspire to make you late.

This is simple and obvious but many otherwise brilliant professionals clearly don’t think about it. The result is that they often arrive late. It’s never their fault, and yet it’s always the same people who are late.

I’m a bleeding heart. If your pet turtle dies, I’ll give you a month’s paid vacation. But promptness is a duty we owe people who pay for our services. So here’s some free advice. Give yourself more time to arrive than you reasonably need. If you work uptown and you have a meeting downtown in two hours, head downtown now. If you’re speaking on the opposite side of the continent early Monday morning, fly out Saturday, not Sunday. That way, you’ll be where you’re supposed to be, no matter what obstacles the weather, the airlines, and the TSA throw your way.

Love means never having to say you’re sorry, but client services means apologizing every five minutes. Give yourself one less thing to be sorry for. Take some free advice. Show up often, and show up early.

Filed under: Free Advice, business

This post has earned 66 responses so far.

The first part of my post of 1 February was not an attack on Flash. It described a way of working with Flash that also supports users who don’t have access to Flash. I’ve followed and advocated that approach for 10 years. It has nothing to do with Apple’s recent decisions and everything to do with making content available to people and search engines.

It’s how our agency and others use Flash; we’ve published articles on the subject in our magazine, notably Semantic Flash: Slippery When Wet by Daniel Mall.

We do the same thing with JavaScript—make sure the site works for users who don’t have JavaScript. It’s called web development. It’s what all of us should do.

My point was simply that if you’re an all-Flash shop that never creates a semantic HTML underpinning, it’s time to start creating HTML first—because an ever-larger number of your users are going to be accessing your site via devices that do not support Flash.

That’s not Apple “zealotry.” It’s not Flash hate. It’s a recommendation to my fellow professionals who aren’t already on the accessible, standards-based design train.

THE SECOND PART OF MY POST wasn’t Flash hate. It was a prediction based on the way computing is changing as more people at varying skill levels use computers and the internet, and as the nature of the computer changes.

There will probably always be “expert” computer systems for people like you and me who like to tinker and customize, just as there are still hundreds of thousands of people who hand-code their websites even though there are dozens of dead-simple web content publishing platforms out there these days.

But an increasing number of people will use simpler computers (just as we’ve seen millions of people blog who never wrote a line of HTML).

THE THIRD PART OF MY POST wasn’t Flash hate. It was an observation that Google and Apple, as companies, have more to gain from betting on HTML5 than from pinning their hopes to Adobe. That’s not a deep insight, it’s a statement of the obvious, and making the statement doesn’t equate to hating Adobe or swearing allegiance to Google and Apple—any more than stating that we’re having a cold winter makes me Al Gore’s best friend.

(Although I like Gore, don’t get me wrong. I also like Apple, Google, and Adobe. My admiration for these companies, however, does not impede my ability to make observations about them.)

THE THIRD PART OF MY POST ALSO WASN’T a blind assertion that HTML5, with VIDEO and CANVAS, is ready to replace Flash today, or more adept than Flash, or more accessible than Flash. Flash is currently more capable and it is far more accessible than CANVAS.

We have previously commented on HTML5’s strengths and weaknesses (Exhibit A, Exhibit B, Exhibit C) and are about to publish a book about HTML5 for web designers. HTML5 is rich with potential; Flash is rich with capability and can be made highly accessible.

That it is unstable on Mac and Linux is one reason Apple chose not to include it in its devices; that this omission will change the way some developers create web content is certain. If the first thing it does is encourage them to develop semantic HTML first, that’s a win for everyone who uses the web.

Carry on.

Filed under: Adobe, Apple, Flash, Google, Web Design, Web Design History, Web Standards, development

This post has earned 34 responses so far.

There is still no Wi-Fi on the northeast corridor Amtrak trains that carry hundreds of thousands of business travelers each day. So quit whining and get a USB 3G modem. It’s free with monthly service, which is tax-deductible. For the $60/month I pay Verizon, I can connect my laptop to the internet from any train, bus, boat, lounge, lobby, conference room, coffee shop, or just about any other environment to which modern business takes me.

Filed under: Free Advice, business, industry

This post has earned 18 responses so far.

Dan Benjamin and yours truly discuss the secret history of blogging, transitioning from freelance to agency, the story behind the web standards movement, the launch of A Book Apart and its first title, HTML5 For Web Designers by Jeremy Keith, the trajectory of content management systems, managing the growth of a design business, and more in the inaugural episode of the Pipeline.

Filed under: Acclaim, Advocacy, Appearances, CSS, Design, HTML, Interviews, The Profession, User Experience, Web Design, Web Design History, Web Standards, Zeldman, better-know-a-speaker, content, creativity, speaking

This post has earned 5 responses so far.

Lack of Flash in the iPad (and before that, in the iPhone) is a win for accessible, standards-based design. Not because Flash is bad, but because the increasing popularity of devices that don’t support Flash is going to force recalcitrant web developers to build the semantic HTML layer first. Additional layers of Flash UX can then be optionally added in, just as, in proper, accessible, standards-based development, JavaScript UX enhancements are added only after we verify that the site works without them.

As the percentage of web users on non-Flash-capable platforms grows, developers who currently create Flash experiences with no fallbacks will have to rethink their strategy and start with the basics before adding a Flash layer. They will need to ensure that content and experience are delivered with or without Flash.

Developers always should have done this, but some don’t. For those who don’t, the growing percentage of users on non-Flash-capable platforms is a wake-up call to get the basics right first.

Whither, plug-ins?

Flash won’t die tomorrow, but plug-in technology is on its way out.

Plug-in technology made sense when web browsing was the province of geeks. It was a brilliant solution to the question of how to extend the user experience beyond what HTML allowed. People who were used to extending their PC via third-party hardware, and jacking the capabilities of their operating system via third-party spell checkers, font managers, and more, intuitively grasped how to boost their browser’s prowess by downloading and updating plug-ins.

But tomorrow’s computing systems, heralded by the iPhone, are not for DIYers. You don’t add Default Folder or FontExplorer X Pro to your iPhone, you don’t choose your iPhone’s browser, and you don’t install plug-ins in your iPhone’s browser. This lack of extensibility may not please the Slashdot crowd but it’s the future of computing and browsing. The bulk of humanity doesn’t want a computing experience it can tinker with; it wants a computing experience that works.

HTML5, with its built-in support for video and audio, plays perfectly into this new model of computing and browsing; small wonder that Google and Apple’s browsers support these HTML5 features.

The power shifts

Google not only makes a browser, a phone, an OS, and Google Docs, it also owns a tremendous amount of video content that can be converted to play in HTML5, sans plug-in. Apple not only makes Macs, iPhones, and iPads, it is also among the largest retail distributors of video and audio content.

Over the weekend, a lot of people were doing the math, and there was panic at Adobe and schadenfreude elsewhere. Apple and Adobe invented modern publishing together in the 1980s, and they’ve been fighting like an old unmarried couple ever since, but Apple’s decision to omit Flash from the iPad isn’t about revenge, it’s about delivering a stable platform. And with HTML5 here, the tea leaves are easy to read. Developers who supplement Flash with HTML5 may soon tire of Flash—but Adobe has a brief but golden opportunity to create the tools with which rich HTML5 content is created. Let’s see if they figure that out.

Discussion has moved to a new thread.

Filed under: Accessibility, Adobe, Advocacy, Apple, Design, HTML, HTML5

This post has earned 182 responses so far.

Comments off.

m.nicewebtype.com is a light yet essential mobile site for people who design websites, love type, and struggle to keep up with the dizzying world of web fonts. In it, Tim Brown, author of Nice Web Type, creator of Web Font Specimen (what’s that?), and latterly type manager for Typekit, curates the Design Twitterverse to share the latest insights, innovations, quips, and controversies regarding everyone’s favorite new web design fetish.

Don’t leave home without it.

Filed under: Web Design, Web Standards, Websites, links, webtype

This post has earned 2 responses so far.

Dan Benjamin, creator of wonderful websites, apps, broadcasts, and platforms and longtime friend of A List Apart and your host, introduces a new venture.

5 by 5 Studios is a new internet broadcasting network, home to shows like EE Podcast, Tack Sharp, The Dev Show, The Ruby Show, and Utility Belt, releasing new episodes every week.

As part of the launch, 5 by 5 announces two new shows hosted by Dan:

• The Pipeline, an interview show talking with designers, developers, writers, and entrepreneurs, brought to you by Campaign Monitor. Upcoming guests include Kottke, Storey,Vaynerchuk, Coudal, Mann, and Siracusa.
• The Conversation, brought to you by Shopify, is a live-streamed talk show featuring topical discussions, reviews, special guests, news with Christina Warren from Mashable, and your calls, all live.

NOTE: I’m pleased as punch to be the first Pipeline guest. Come hear us on Friday, January 29th, 2010.

Filed under: Authoring, Community, Design, Ideas, Publishing, content, industry, launches, links, podcasts

This post has earned 2 responses so far.

In a special double issue of A List Apart, for people who make websites, Shelley Powers takes a second look at SVG and likes what she sees. You may, too.

Many of us think of Scalable Vector Graphics (SVG) as an also-ran: fine for charts and tables, but not much else. Yet SVG can actually enhance a site’s overall design, and can be made to work in even the most stubborn browser.

In Part I, Shelley covers important basics of working with SVG, including browser support and accessibility.

In Part II, dig deeper into the technology behind using SVG for your site design. Explore how to incorporate SVG in a cross-browser friendly manner, including using SVGWeb to ensure that the SVG shows in Internet Explorer. And discover the unique characteristic that makes SVG ideal for page backgrounds: scalability.

Illustration: Kevin Cornell for A List Apart

Filed under: A List Apart, Design, Web Design, Web Standards, development

Comments off.

The deaths of Leslie Harpold and Brad Graham, in addition to being tragic and horrible and sad, have highlighted the questionable long-term viability of blogs, personal sites, and web magazines as legitimate artistic and literary expressions. (Read this, by Rogers Cadenhead.)

Cool URIs don’t change, they just fade away. When you die, nobody pays your hosting company, and your work disappears. Like that.

Now, not every blog post or “Top 10 Ways to Make Money on the Internet” piece deserves to live forever. But there’s gold among the dross, and there are web publications that we would do well to preserve for historical purposes. We are not clairvoyants, so we cannot say which fledgling, presently little-read web publications will matter to future historians. Thus logic and the cultural imperative urge us to preserve them all. But how?

The death of the good in the jaws of time is not limited to internet publications, of course. Film decays, books (even really good ones) constantly go out of print, digital formats perish. Recorded music that does not immediately find an audience disappears from the earth.

Digital subscriptions were supposed to replace microfilm, but American libraries, which knew we were racing toward recession years before the actual global crisis came, stopped being able to pay for digital newspaper and magazine descriptions nearly a decade ago. Many also (even fancy, famous ones) can no longer collect—or can only collect in a limited fashion. Historians and scholars have access to every issue of every newspaper and journal written during the civil rights struggle of the 1960s, but can access only a comparative handful of papers covering the election of Barack Obama.

Thanks to budget shortfalls and format wars, our traditional media, literature, and arts are perishing faster than ever before. Nothing conceived by the human mind, except Heaven and nuclear winter, is eternal.

Still, when it comes to instant disposability, web stuff is in a category all its own.

Unlike with other digital expressions, format is not the problem: HTML, CSS, and backward-compatible web browsers will be with us forever. The problem is, authors pay for their own hosting.

(There are other problems: the total creative output of someone I follow is likely distributed across multiple social networks as well as a personal site and Twitter feed. How to connect those dots when the person has passed on? But let’s leave that to the side for the moment.)

A suggestion for a business. Sooner or later, some hosting company is going to figure out that it can provide a service and make a killing (as it were) by offering ten-, twenty-, and hundred-year packets of posthumous hosting.

A hundred years is not eternity, but you are not Shakespeare, and it’s a start.

Filed under: Accessibility, Advocacy, Blogs and Blogging, Community, Formats, HTML, Ideas, Publications, Publishing, Respect, State of the Web, The Profession, W3C, business, content strategy, data, glamorous, industry, work, writing

This post has earned 58 responses so far.

Since 1998, A List Apart has sought to serve the international web design and development community with educational, insightful, and sometimes visionary articles on web standards, emerging ideas and technologies, and best practices in content, usability, and design.

One barrier has long prevented us from fulfilling our goal to the utmost. But today we transcend it. Introducing A List Apart Arabic—an authorized A List Apart publication. Thank you and congratulations to Mohammad Saleh Kayali and his partners.

Look for additional international A List Apart editions, coming soon.

Filed under: A List Apart, Accessibility, Happy Cog™, Publications, Publishing, development

This post has earned 21 responses so far.