Web standards are the formal, non-proprietary
Web standards include many interdependent standards and specifications, some of which govern aspects of the Internet, not just the World Wide Web. Even when not web-focused, such standards directly or indirectly affect the development and administration of web sites and web services. Considerations include the interoperability, accessibility and usability of web pages and web sites.
Web standards consist of the following:
- Recommendations published by the
- Standards and "Living standards" published by the
- Standards published by the International Organization for Standardization (ISO), such as JPEG
More broadly, the following technologies may be referred to as "web standards" as well:
- Request for Comments (RFC) documents published by the Internet Engineering Task Force (IETF)
- The Unicode Standard and various Unicode Technical Reports (UTRs) published by the Unicode Consortium
- Name and number registries maintained by the Internet Assigned Numbers Authority (IANA)
Web standards are evolving specifications of web technologies.
The web standards movement
The earliest visible manifestation of the web standards movement was the Web Standards Project, launched in August 1998 as a grassroots coalition fighting for improved web standards support in browsers.
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 the World Wide Web Consortium; and progressive 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 "
The Web Standards movement pioneered by Glenn 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-heavy tag soup with light, semantic markup and progressive enhancement, with the goal of making web content "accessible to all".
When a web site or web page is described as complying with web standards, it usually means that the site or page has valid
When web standards are discussed, the following publications are typically seen as foundational:
- Recommendations for SVG) from W3C.
- Recommendations for stylesheets, especially Cascading Style Sheets (CSS), from W3C.
- Recommendations for Document Object Models (DOM), from W3C.
- Properly formed names and addresses for the page and all other resources referenced from it (URIs), based upon RFC 2396, from IETF.
- Proper use of
Work in the W3C toward the Semantic Web is currently focused by publications related to the Resource Description Framework (RDF), Gleaning Resource Descriptions from Dialects of Languages (GRDDL) and Web Ontology Language (OWL).
Standards publications and bodies
A W3C 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.
Non-standard and vendor-proprietary pressures
HTML 5 contains numerous "willful violations" of other specifications, in order to accommodate limitations of existing platforms.
Web Standards Compliance Testing
There are compliance tests both for HTML code generated by websites as well as for the faithful interpretation of HTML code by web browsers.
Compliance tests for website code
W3C offers online services to test websites directly for both web site developers, as well as for website users. These include:
- Markup Validation Service to check the markup (HTML, XHTML, …) of Web documents
- CSS Validation Service to check Cascading Style Sheets (CSS) and (X)HTML documents with style sheets
Compliance tests for web browsers
The Web Standards Project (WaSP), although development is officially inactive, continues to offer two levels of testing services for web browsers:
- "Mission - Web Standards Project". WaSP. Retrieved 2009-01-19.
- "W3C Technical Reports and Publications". W3C. Retrieved 2009-01-19.
- "WHATWG Standards". spec.whatwg.org. Retrieved 2020-11-22.
- "Ecma formal publications". Ecma. Retrieved 2009-01-19.,
- "Search for World Wide Web in ISO standards". ISO. Retrieved 2009-01-19.
- "IETF RFC page". IETF. Retrieved 2009-01-19.
- "Unicode Technical Reports". Unicode Consortium. Retrieved 2009-01-19.
- "IANA home page". IANA. Retrieved 2009-01-19.
- "Web Standards Mission". Archive.webstandards.org. Retrieved 2014-02-26.
- Zeldman, Jeffrey (2008-11-20). "Blue Beanie Day II". Zeldman on Web & Interaction Design. Retrieved 2020-04-21.
- Walker, Alissa (2009-11-30). "Why Is Your Web Designer Wearing a Blue Hat Today?". Fast Company. Retrieved 2020-04-21.
- "Web Content Accessibility Guidelines 1.0, W3C Recommendation 5-May-1999". W3C. 1999. Retrieved 2009-02-18.
- "HTML 5 - A vocabulary and associated APIs for HTML and XHTML - Compliance with other specifications". Retrieved 2017-06-29.