A directory of resources inthe field of technical communication.

Articles>Web Design>Standards

101-124 of 134 found. Page 5 of 6.

About this Site | Advanced Search | Localization | Site Maps
 

« PREVIOUS PAGE 1 2 3 4 5 6  NEXT PAGE »

 

101.
#33388

Using Ajax for Creating Web Applications

In the past few years, developers could choose between two approaches when building a web application. The first approach was to create a screen-based system with very rich interactions using a sophisticated, powerful technology such as Java or Flash. The alternative approach was to create a page-based system using easier-to-learn core web standards like XHTML and CSS whose more basic capabilities force less-rich interactions. A new technological approach, dubbed Ajax, might just be the right mix between the two.

Porter, Joshua. User Interface Engineering (2005). Articles>Web Design>Standards>Ajax

102.
#33471

Web Content Accessibility Guidelines (WCAG) 2.0

Web Content Accessibility Guidelines (WCAG) 2.0 covers a wide range of recommendations for making Web content more accessible. Following these guidelines will make content accessible to a wider range of people with disabilities, including blindness and low vision, deafness and hearing loss, learning disabilities, cognitive limitations, limited movement, speech disabilities, photosensitivity and combinations of these. Following these guidelines will also often make your Web content more usable to users in general.

Caldwell, Ben, Michael Cooper, Loretta Guarino Reid and Gregg Vanderheiden. W3C (2008). Articles>Web Design>Accessibility>Standards

103.
#33472

A Personal Reflection on the WCAG 2.0 Publication

Let's work together as a community to make WCAG 2.0 a unifying force for web accessibility. There are so many websites and exciting new web applications being created today with accessibility barriers that make it difficult or impossible for some people with disabilities to use them. Let's change that, with WCAG 2.0.

Henry, Shawn Lawton. W3C (2008). Articles>Web Design>Accessibility>Standards

104.
#33685

WCAG 2.0 Checklist

A simple checklist that presents the principles and techniques of WCAG 2.0 in a user-friendly, understandable format. The language has been significantly changed and simplified from the official WCAG 2.0 specification to make it more easily tested and verified for web pages.

WebAIM (2009). Articles>Web Design>Accessibility>Standards

105.
#33787

DOM, SAX and Standards - Where Now?

It's been 7 years and three "levels" since the first W3C DOM activity. XML and the way it is used has changed vastly over that time. DOM itself has moved from an API to access and manipulate an in-memory tree with no concept of namespaces, to an end to end XML technology, where parsing, modification of the tree (with the ability to check for validity with a schema as you go) and serialization are all specified.

Reakes, Gareth, Alberto Massari, Lucian Holland and Neil Graham. IDEAlliance. Articles>Web Design>Standards>XML

106.
#33808

Five Ways to Instantly Write Better CSS

Sure, anyone can write CSS. Even programs are doing it for you now. But is the CSS any good? Here are five tips to start improving yours.

Davis, Trevor. NETTUTS (2009). Articles>Web Design>CSS>Standards

107.
#34000

What Are Web Standards and Why Should I Use Them?

Standards have so much to offer that we at The Web Standards Project (WaSP) consider it necessary to help you learn more about them. This document is merely a starting point; it will give you a solid understanding of what standards exist, why they do, and why you should care about them. Every time we create a piece of the Web, we contribute to the common information space that is the Web. We can build it up, or we can add weight that will tear it apart. The choice belongs to us; the consequences belong to everyone.

Web Standards Project (2009). Articles>Web Design>Standards>Education

108.
#34005

Browser Problems with the XML Prolog

Some browsers have difficulty upon encountering the XML Prolog. In some cases, the browser will render all the markup as text. In other cases, when a browser has some XML support, it might attempt to render the document as an XML tree. To avoid these problems, many practicing web professionals prefer to leave the prolog off. This table will help you make that decision by showing you which browsers have known problems with the XML prolog.

Web Standards Project (2007). Articles>Web Design>Standards>XML

109.
#34149

The Road to XHTML 2.0: MIME Types

Here's a dirty little secret: browsers aren't actually treating your XHTML as XML. Your validated, correctly DOCTYPE'd, completely standards compliant XHTML markup is being treated as if it were still HTML with a few weird slashes in places they don't belong (like
and ). Why? The answer is MIME types.

Pilgrim, Mark. XML.com (2003). Articles>Web Design>XHTML>Standards

110.
#34216

When Good Browsers Go Bad -- And They All Do

Jeffrey Zeldman must have thought he'd never live to see the day. Ten years after he co-founded the Web Standards Project, all of the major browser vendors have shown renewed commitment to supporting World Wide Web Consortium (W3C) standards in the last few years -- and they're following through. Those who lived through the browser wars of the '90s might think that hell has frozen over, were it not for one, small problem: Users still experience plenty of problems on the Web.

Mitchell, Robert L. Computerworld (2009). Articles>Web Design>Standards>Web Browsers

111.
#34616

New Accessibility Guidelines A "Welcomed Update"

The World Wide Web Consortium recently approved new accessibility guidelines. Passed in December 2008, the new "Web Content Accessibility Guidelines 2.0" is now the official recommendation for web accessibility for the disabled. This new WCAG 2.0 document, a welcomed update, replaces the WCAG 1.0 W3C recommendation of 1999. This article is part one in a series discussing the impact of WCAG 2.0 on your website.

Dolson, Joseph C. Practical eCommerce (2009). Articles>Web Design>Accessibility>Standards

112.
#34619

New Accessibility Guidelines Part IV: Robustness

The fourth principle of the Web Content Accessibility Guidelines requires new web documents to be “robust.” Robustness, future-proofing, user-agent independence, accessibility-supported: All are terms that suggest the same basic idea that your documents should follow standard, supported models for web document types. In many ways, this is the simplest and most testable requirement of the WCAG, but the details can be quite complicated.

Dolson, Joseph C. Practical eCommerce (2009). Articles>Web Design>Accessibility>Standards

113.
#34642

Adopting WCAG 2

It is six months since the release of WCAG 2.0 and I thought it might be interesting to see how extensively it has been adopted as a bench mark for determining web content accessibility. Over this time, I have felt that the rate of adoption has been relatively slow and the number of countries and other regulatory authorities now using WCAG 2 is lower than I expected.

Hudson, Roger. DingoAccess (2009). Articles>Web Design>Accessibility>Standards

114.
#34674

Understanding 'aside'

HTML 5 offers a new element to mark additional information that can enhance an article but isn’t necessarily key to understanding it. However, in the interpretation of 'aside' there lies confusion as to how it can be used, and with that there is demand for the Doctor to step up and clear the air. In this article I will look at what 'aside' was created for, including sample uses and how not to use this useful, misunderstood element.

HTML 5 Doctor (2009). Articles>Web Design>Standards>HTML5

115.
#34688

Yes, You Can Use HTML 5 Today!

The blogosphere was jerked into excitement when Google gave a sneak preview of its new service, Google Wave. Only the select few have an account, but there’s an 80-minute video about it on YouTube for the rest of us. The service is an HTML 5 app, and so HTML 5 has gone from being too far away to care about to today’s hot topic.

Lawson, Bruce. SitePoint (2009). Articles>Web Design>Standards>HTML5

116.
#34689

HTML 5: Now or Never?

Here at SitePoint, we have started thinking about HTML 5, and whether or not the time is right to publish a book about it. To help us decide, we asked a number of web luminaries what they thought. Their answers were both varied and interesting. Take a look and decide for yourself: is it time you started learning about HTML 5?

Yank, Kevin. SitePoint (2009). Articles>Web Design>Standards>HTML5

117.
#34737

Recommended List of DTDs You Can Use in Your Web Document

When authoring document is HTML or XHTML, it is important to Add a Doctype declaration. The declaration must be exact (both in spelling and in case) to have the desired effect, which makes it sometimes difficult. To ease the work, below is a list of recommended declarations that you can use in your Web documents.

W3C (2007). Articles>Web Design>Standards>XHTML

118.
#35005

A Whole Lotta HTML5 Love

With the flurry of HTML5 tweets this past month, I felt it was somewhat easier to park some of them in a blog post. Retweeting was adding to the confusion for a non-HTML5 person like me.

STC AccessAbility SIG (2009). Articles>Web Design>Standards>HTML5

119.
#35006

Misunderstanding Markup: XHTML 2/HTML 5 Comic Strip

Now that the development of XHTML 2 is discontinued, should we stick to XHTML 1.0 or move forward to HTML 5 or better prefer the old HTML 4? Let’s set things straight once and for all. In this post we are trying to clear up the confusion, explain what is what and describe what markup language you can use for your web-sites.

Colbow, Brad. Smashing (2009). Articles>Web Design>Standards>HTML5

120.
#35050

Why is HTML Suddenly Interesting?

Today the HTML conversation is reborn. Standards development around HTML seems to actually have a chance of influencing user experience in the browser, and Microsoft itself is participating in the HTML 5 conversation despite still holding roughly two-thirds of the browser market. While Microsoft's market share is only slowly eroding, developer mindshare seems to have shifted decisively to the band of WHATWG upstarts, Microsoft's competitors.

St. Laurent, Simon. O'Reilly and Associates (2009). Articles>Web Design>Standards>HTML5

121.
#35152

Ten Ways To Make Your XHTML Site Accessible Using Web Standards

Let’s take a look at 10 ways to improve the accessibility of your XHTML website by making it standards-compliant. We’ll go the extra mile and include criteria that fall beyond the standards set by the W3C but which you should follow to make your website more accessible. Each section lists the criteria you need to meet, explains why you need to meet them and gives examples of what you should and shouldn’t do.

Irigoyen, Michael. Smashing (2009). Articles>Web Design>Accessibility>Standards

122.
#35153

Why Apple is Betting on HTML 5: A Web History

To get an accurate picture of why HTML 5 matters and how its adoption will change the future of the web and software in general, you have to take a look at the squabbling drama of contention that HTML 5 is emerging from as industry rivals work to achieve a new level of consensus on how the web should work.

Dilger, Daniel Eran. AppleInsider (2009). Articles>Web Design>Standards>HTML5

123.
#35160

Video Introduction to HTML 5

Are you interested in HTML 5 and what's coming down the pipeline but haven't had time to read any articles yet? We've put together an educational Introduction to HTML 5 video that goes over many of the major aspects of this new standard. In the video we also crack open the HTML 5 YouTube Video prototype to show you some of the new HTML 5 tags, such as nav, article, etc.

Google (2009). Articles>Web Design>Standards>HTML5

124.
#35164

Get Ready for HTML 5

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.

Eisenberg, J. David. List Apart, A (2009). Articles>Web Design>Standards>HTML5

125.
#35167

How to Read W3C Specs

If you’re working with the latest technology, there may not be any user reference material at all; the only documentation available is the specification. In such a case, learning to read the spec is a necessity, not a luxury.

Eisenberg, J. David. List Apart, A (2009). Articles>Web Design>Standards>Specifications

 
« PREVIOUS PAGE  |  NEXT PAGE »

There are 11 readers currently online: 1 registered user and 10 guests. Register.Follow us on: TwitterFacebookRSSPost about us on: TwitterFacebookDeliciousRSSStumbleUpon