Jeffrey Zeldman Quotes

IT professionals have a responsibility to understand the use of standards and the importance of making Web applications that work with any kind of device.

Many thought it was a fool's errand - that the browser companies were never going to listen to us. Others argued that, 'Users don't care if you use Web standards.' Well, of course they don't. They just know that your site works better.

Because the competitive landscape of the web is such that the site which looks and works best gets the most traffic, developers and designers put a premium on the presentation of that content and let structural markup take a back seat.

Our old site did not have very good support for the disabled, but our new site should soon have much better support. With all of our content in divs now, we can hide all but the relevant chunks of content and navigation with a simple alternate CSS file.

I'm just loving BlueGriffon Editor! XML, HTML5, CSS, ARIA, SVGEdit all built in.

Everybody who runs a Web site knows we're not assured of compatibility, and we could end up with a split.

We're actually helping advance HTML5 in some very concrete ways, such as Edge, which is in beta.

We found a way to make things look great to the human eye through the window of a graphical web browser without worrying about what everything looked like under the hood.

It's not about HTML 5 vs Flash. They're mutually beneficial. The more important question is the freedom of choice on the web.

I think HTML5 is one area where Mozilla has done very poorly at actually communicating what we have done.

Even if it's not always the best markup, what are Facebook and Twitter? They're web standards with some scripts. They may not validate, but they're still CSS layouts and simple markup, and that's great!

Validation is easy - you run your site through a validator, and it's either valid or it isn't. The rest of the stuff, such as whether my logo or the biggest headline should be the h1 in my HTML, isn't so easy and is subject to interpretation.

In '93 to '94, every browser had its own flavor of HTML. So it was very difficult to know what you could put in a Web page and reliably have most of your readership see it.

The Mobile Web Initiative is important - information must be made seamlessly available on any device.

The code core of the 2001 browser upgrade campaign was the first instance of capability detection in place of browser detection.

Writing old school HTML code was never very much fun but now it's getting downright tedious for most people.

The Internet didn't become usable until Netscape because that gave the average person a user interface that was intuitive, simple, friendly - this made it accessible.

I certainly am interested in accessibility, clarity, and immediacy.

I vertically center things in tables a lot, and the fact that there is no way to control vertical positioning in divs affects the way we do things across the board.

Flash and HTML have co-existed, and they're going to continue to co-exist.

Now that digital lifestyle devices, tablets, wireless phones, and other Internet appliances are beginning to come of age, we need to worry about presenting our content to these devices so that it is optimized for their display capabilities.

If someone had protected the HTML language for making Web pages, then we wouldn't have the World Wide Web.

Despite demand, the BlackBerry avoided offering generalized web browsing support.

At Adaptive Path, we've been doing our own work with Ajax over the last several months, and we're realizing we've only scratched the surface of the rich interaction and responsiveness that Ajax applications can provide.

I'd like to be able to design as easily as if I was using Photoshop. I'd like to be able to create a multicolumn layout and control source order without having to do advanced mathematics or hire Eric Meyer or Dan Cederholm to figure out the CSS, because I can't.