Web Standards Quotes

At one point, CERN was toying with patenting the World Wide Web.

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

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.

Anyone who slaps a 'this page is best viewed with Browser X' label on a Web page appears to be yearning for the bad old days, before the Web, when you had very little chance of reading a document written on another computer, another word processor, or another network.

Publishing a protocol under the name Atom that tries to capture all of the prior art in this stage and might provide a good basis for winding down the syndication wars.

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.

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.

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!

What we now call the browser is whatever defines the web. What fits in the browser is the World Wide Web and a number of trivial standards to handle that so that the content comes.

Google is making a huge investment in developing the Ajax approach.

For most of the '90s and the first part of this decade, content providers who wanted to publish online only needed to worry about the graphical web browser.

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

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.

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

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.

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.

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

I taught myself HTML.

If you use the original World Wide Web program, you never see a URL or have to deal with HTML. That was a surprise to me - that people were prepared to painstakingly write HTML.

Ajax is an important development for Web applications, and its importance is only going to grow.

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.

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 at The Web Standards Project turned everything on its head. We said browsers should support the same standards instead of competing to invent new tags and scripting languages. We said designers, developers, and content folks should create one site that was accessible to everyone.