Free Your Embedded Data With SearchMonkey

Arguing for web standards and semantically clean and rich websites is an uphill battle. For years we had to deal with browsers that needed us to mess around with HTML just to display a document in several columns and the visual outcome was much more important than the structure.

Heilmann, Christian. Digital Web Magazine (2008). Articles>Web Design>Standards>HTML

Understanding Progressive Enhancement

Since 1994, the web development community has beaten graceful degradation’s drum. A carry-over from the engineering world, the concept was, at its core, about giving the latest and greatest browsers the full-course meal experience while tossing a few scraps to the sad folk unfortunate enough to be using Netscape 4. It worked, sure, but it didn’t really match Tim Berners-Lee’s original vision for a universally accessible web. At SXSW in 2003, Steve Champeon and Nick Finck gave a presentation titled “Inclusive Web Design For the Future.” There, they unveiled a blueprint for this new way of approaching web development. Steve also gave it a name: progressive enhancement.

Gustafson, Aaron. List Apart, A (2008). Articles>Web Design>Standards

jQuery and JavaScript Coding: Examples and Best Practices

When used correctly, jQuery can help you make your website more interactive, interesting and exciting. This article will share some best practices and examples for using the popular JavaScript framework to create unobtrusive, accessible DOM scripting effects. The article will explore what constitutes best practices with regard to Javascript and, furthermore, why jQuery is a good choice of a framework to implement best practices.

Smashing (2008). Articles>Web Design>Standards>JavaScript

Mobile Web Best Practices 1.0

This document specifies Best Practices for delivering Web content to mobile devices. The principal objective is to improve the user experience of the Web when accessed from such devices. It is primarily directed at creators, maintainers and operators of Web sites. Readers of this document are expected to be familiar with the creation of Web sites, and to have a general familiarity with the technologies involved, such as Web servers and HTTP. Readers are not expected to have a background in mobile-specific technologies.

W3C (2008). Articles>Web Design>Wireless Web>Standards

sIFR 2.0: Rich Accessible Typography for the Masses

Over the last several months, a small group of web developers and designers have been hard at work perfecting a method to insert rich typography into web pages without sacrificing accessibility, search engine friendliness, or markup semantics. The method, dubbed sIFR (or Scalable Inman Flash Replacement), is the result of many hundreds of hours of designing, scripting, testing, and debugging.

Davidson, Mike. Mike Industries (2008). Articles>Web Design>Typography>Standards

WCAG and the Myth of Accessibility

Kevin Leitch explains why he feels that the Web Content Accessibility Guidelines have failed in their mission to ensure that web content is accessible to all.

Leitch, Kevin. Juicy Studio (2004). Articles>Web Design>Accessibility>Standards

Creating Semantic Structure

Despite the nature of the Web and the vast change in its role from a structural medium to a visual media, it is still important that Web content be designed with proper structure. With better support for Cascading Style Sheets in recent versions of Web browsers, developers can change the appearance of structural elements to meet their design and visual preferences.

WebAIM (2006). Articles>Web Design>Standards

How to Meet WCAG 2.0

A customizable quick reference to Web Content Accessibility Guidelines 2.0 requirements (success criteria) and techniques.

W3C (2008). Articles>Web Design>Accessibility>Standards

About Web Standards

The World Wide Web Consortium (W3C), along with other groups and standards bodies, has established technologies for creating and interpreting web-based content. These technologies, which we call 'web standards', are carefully designed to deliver the greatest benefits to the greatest number of web users while ensuring the long-term viability of any document published on the Web. Designing and building with these standards simplifies and lowers the cost of production, while delivering sites that are accessible to more people and more types of Internet devices. Sites developed along these lines will continue to function correctly as traditional desktop browsers evolve, and as new Internet devices come to market.

Web Standards Group (2006). Articles>Web Design>Standards

Introduction to Device Independence, Part 1

In the past three to four years the number of different kinds of devices that can access the Web has increased significantly. And they have a wide variety of different capabilities: smart phones, mobile phones, voice response systems, PDAs, and even microwave ovens can access the Web. The mission of the Device Independence activity of the W3C is to avoid fragmentation of the Web into spaces that are accessible only from certain types of devices.

Mikhalenko, Peter. XML.com (2004). Articles>Web Design>Standards

Web Standards Checklist

The term web standards can mean different things to different people. For some, it is 'table-free sites', for others it is 'using valid code'. However, web standards are much broader than that. A site built to web standards should adhere to standards (HTML, XHTML, XML, CSS, XSLT, DOM, MathML, SVG etc) and pursue best practices (valid code, accessible code, semantically correct code, user-friendly URLs etc). In other words, a site built to web standards should ideally be lean, clean, CSS-based, accessible, usable and search engine friendly.

Weakley, Russ. Max Design (2004). Articles>Web Design>Standards>Semantic

Converting Your Team

I’d like to share some of the things I’ve done (and still do) to get the team I work with to start using web standards. Maybe it will help someone who is in the position I was a while back.

456 Berea Street (2004). Articles>Web Design>Standards>Collaboration

Developing With Web Standards

This document attempts to explain how and why using web standards will let you build websites in a way that saves time and money for developers and provides a better experience for visitors. Also discussed are other methods, guidelines and best practices that will help produce high-quality websites that are accessible and usable to as many people and browsing devices as possible.

Johansson, Roger. 456 Berea Street (2008). Articles>Web Design>Standards

The Effect of Web Standards on Users

The current crop of web standards (XTHML & CSS) have had a dramatic effect on the work of the web designers who have adopted them. Writers of the best kinds have trumpeted the benefits of these standards over the coding practices that had become second nature to most (image spacers, anyone?).

Porter, Joshua. Bokardo (2008). Articles>Web Design>Standards

Who Cares How Pretty Web Sites Are?

A few weeks back, I wrote about why I think web standards are difficult to learn. I wrote that because I was spending 80% of my time getting my code into XHTML 1.0 and styling it with CSS so that it rendered consistently across 5 or 6 browsers. What was I doing the other 20% of the time? Creating content, of course. I was putting together what a huge percentage of my site visitors come for. When I thought about it in these terms (time spent), I felt like styling with CSS was a lot of work for comparatively little gain. After all, people will still be able to find the site, read the content, and click on the links, whether or not I’ve styled it.

Porter, Joshua. Bokardo (2008). Articles>Web Design>Standards>Usability

Some Reasons Why Web Standards Are Difficult to Learn

It seems like the box model shouldn’t be difficult to learn, but it is. I’m not sure why, but I think it may have to do with complexity that arises when you have boxes within boxes. At that point, it becomes an exercise of adding margin here, taking away padding there, and setting margins and paddings to 0 over there. Combine that with floating and positioning: relative, absolute, fixed, and it gets hard to know where the spacing between objects comes from, even when you’re working in standards-supporting browser like Mozilla. On top of this you have the box model hack…which only complicates things further. Even browsers get the box model wrong.

Porter, Joshua. Bokardo (2008). Articles>Web Design>Standards>CSS

Are Designers Focused Enough on User Needs?

I find that many designers give much more of their time to learning the latest standards trick than learning the latest “designing for users” trick. Here are a few reasons why this may be so.

Porter, Joshua. Bokardo (2008). Articles>Web Design>Standards>User Centered Design

The Sagacity in Validation

In one of my introductory articles I stated that I do not care much for validation, yet I use well-formed XHTML 1.0 Strict (no less) as my preferred standard and CSS for layout purposes. If so, why on earth would I claim not to care about, or ignore, validation?

Hilhorst, Didier P. Nundroo (2004). Articles>Web Design>Standards>XHTML

Web Design Going in the Wrong Direction?

There’s way too much talk about CSS and XHTML and Standards and Accessibility and not enough talk about people. CSS and Standards Compliant Code are just tools — you have to know what to build with these tools.

Signal vs. Noise (2004). Articles>Web Design>Standards>XHTML

Web Development Mistakes

When I visit a website, especially if it’s the site of a competitor or a prospective client, I like viewing source and take a look at what’s under the hood. It’s one of my not-so-secret obsessions. And I am way too often absolutely disgusted by what I see. The web is overflowing with sites that use horribly invalid, broken, and inaccessible markup.

456 Berea Street (2004). Articles>Web Design>Standards>XHTML

Web Standards For Business

This article highlights the benefits of using Web standards for business sites (Internet, intranet and extranet sites). It is aimed at stakeholders from the marketing, communication and IT departments.

Nonnenmacher, François. Web Standards Project (2003). Articles>Web Design>Standards

Les Standards Web Pour L'Entreprise

Les standards du Web apportent aussi leur lot d’avantages aux sites d’entreprise, Internet, intranet et extranet. Voyons comment les décideurs marketing, communication et informatique pourront tirer parti de l’utilisation des standards au sein de leur entreprise.

OpenWeb (2003). (French) Articles>Web Design>Standards

Why Standards Harmonization is Essential for Web Accessibility

This document introduces the concept of harmonization and causes of fragmentation in the area of Web accessibility standards, and examines the impact of harmonization and fragmentation on Web developers, tool developers, and organizations. It also suggests action steps for promoting Web accessibility standards harmonization.

W3C (2006). Articles>Web Design>Standards>Collaboration

UTF-8: The Secret of Character Encoding

Character encoding and character sets are not that difficult to understand, but so many people blithely stumble through the worlds of programming without knowing what to actually do about it, or say "Ah, it's a job for those internationalization experts." No, it is not! This document will walk you through determining the encoding of your system and how you should handle this information. It will stay away from excessive discussion on the internals of character encoding.

HTML Purifier (2005). Articles>Web Design>Standards>Language

Creating Bulletproof and Easy to Complete Web Forms

Effective form design is a great way to boost conversion rates. Jason Fried and Matthew Linderman share with us the secret of how to create attractive and functional forms.

Fried, Jason and Matthew Linderman. Peachpit Press (2004). Articles>Web Design>Standards>Forms