Web standards are the formal, non-proprietarystandards and other technicalspecifications that define and describe aspects of theWorld Wide Web. In recent years, the term has been more frequently associated with the trend of endorsing a set of standardizedbest practices for buildingweb sites, and a philosophy ofweb design and development that includes those methods.[1]
Web standards include many interdependent standards and specifications, some of which govern aspects of theInternet, not just the World Wide Web. Even when not web-focused, such standards directly or indirectly affect the development and administration of web sites andweb services. Considerations include theinteroperability,accessibility andusability of web pages and web sites.
Web standards consist of the following:
More broadly, the following technologies may be referred to as "web standards" as well:
Web standards are evolving specifications of web technologies.[10] Web standards are developed bystandards organizations—groups of interested and often competing parties chartered with the task of standardization—not technologies developed and declared to be a standard by a single individual or company. It is crucial to distinguish those specifications that are under development from the ones that already reached the final development status (in case ofW3C specifications, the highest maturity level).
The earliest visible manifestation of the web standards movement was theWeb Standards Project, launched in August 1998 as a grassroots coalition fighting for improved web standards support in browsers.[11]
The web standards movement supports concepts of standards-based web design, including the separation of document structure from a web page or application's appearance and behavior; an emphasis on semantically structured content that validates (that is, contains no errors of structural composition) when tested against validation software maintained by theWorld Wide Web Consortium; andprogressive enhancement, a layered approach to web page and application creation that enables all people and devices to access the content and functionality of a page, regardless of personal physical ability (accessibility), connection speed, and browser capability.
Prior to the web standards movement, many web page developers used invalid, incorrect HTML syntax such as "table layouts" and "spacer" GIF images to create web pages — an approach often referred to as "tag soup". Such pages sought to look the same in all browsers of a certain age (such asMicrosoft Internet Explorer 4 andNetscape Navigator 4), but were often inaccessible to people with disabilities. Tag soup pages also displayed or operated incorrectly in older browsers, and required code forks such asJavaScript forNetscape Navigator and JScript forInternet Explorer that added to the cost and complexity of development. The extra code required, and the lack of a caching page layout language, made web sites "heavy" in terms of bandwidth, as did the frequent use of images as text. These bandwidth requirements were burdensome to users in developing countries, rural areas, and wherever fast Internet connections were unavailable.
The Web Standards movement pioneered byGlenn Davis, George Olsen,Jeffrey Zeldman, Steven Champeon, Todd Fahrner,Eric A. Meyer,Tantek Çelik, Dori Smith,Tim Bray, Jeffrey Veen, and other members of the Web Standards Project replaced bandwidth-heavytag soup with light, semantic markup andprogressive enhancement, with the goal of making web content "accessible to all".[12]
The Web Standards movement declared thatHTML,CSS, andJavaScript were more than simply interesting technologies. "They are a way of creating Web pages that will facilitate the twin goals of sophisticated and appropriate presentation and widespread accessibility."[12] The group succeeded in persuadingNetscape,Microsoft, and other browser makers to support these standards in their browsers. It then set about promoting these standards to designers, who were still usingtag soup,Adobe Flash, and other proprietary technologies to create web pages.
In 2007, Douglas Vos initiated theBlue Beanie Day, inspired by Jeffrey Zeldman, who is shown with a blue cap on the book cover of his 2003 bookDesigning with Web Standards.[13] Since then, the30 November is the annual international celebration of web standards andweb accessibility.[14]
When a web site or web page is described as complying with web standards, it usually means that the site or page has validHTML,CSS andJavaScript. The HTML should also meetaccessibility andsemantic guidelines. Full standard compliance also covers proper settings forcharacter encoding, validRSS or validAtom news feed, validRDF, validmetadata, validXML, valid object embedding, valid script embedding, browser- and resolution-independent codes, and proper server settings.
When web standards are discussed, the following publications are typically seen as foundational:
Web accessibility is normally based upon theWeb Content Accessibility Guidelines[17] published by the W3C'sWeb Accessibility Initiative.
Work in the W3C toward theSemantic Web is currently focused by publications related to theResource Description Framework (RDF),Gleaning Resource Descriptions from Dialects of Languages (GRDDL) andWeb Ontology Language (OWL).
AW3C recommendation is a specification or set of guidelines that, after extensive consensus-building, has received the endorsement of W3C members and the director.
An IETF Internet Standard is characterized by a high degree of technical maturity and by a generally held belief that the specified protocol or service provides significant benefit to the Internet community. A specification that reaches the status of Standard is assigned a number in the IETF STD series while retaining its original IETF RFC number.
HTML 5 contains numerous "willful violations" of other specifications, in order to accommodate limitations of existing platforms.[18]
There are compliance tests both for HTML code generated by websites as well as for the faithful interpretation of HTML code by web browsers.
W3C offers online services to test websites directly for both web site developers, as well as for website users. These include:
TheWeb Standards Project (WaSP), although development is officiallyinactive, continues to offer two levels of testing services for web browsers:
