kb/data/developer.mozilla.org/en-US/docs/Glossary/Web_standards-0.md

12 KiB

title chunk source category tags date_saved instance
Web standards - Glossary | MDN 1/3 https://developer.mozilla.org/en-US/docs/Glossary/Web_standards reference web, html, css, javascript, documentation 2026-05-05T05:49:23.652432+00:00 kb-cron

MDN HTML HTML: Markup language

HTML reference

HTML guides

Markup languages

CSS CSS: Styling language

CSS reference

CSS guides

Layout cookbook

JavaScriptJS JavaScript: Scripting language

JS reference

JS guides

Web APIs Web APIs: Programming interfaces

Web API reference

Web API guides

All All web technology

Technologies

Topics

Learn Learn web development

Frontend developer course

Learn HTML

Learn CSS

Learn JavaScript

Tools Discover our tools

About Get to know MDN better

Blog

  1. Glossary
  2. Web standards

Web standards

Web standards are rules established by international standards bodies that define how the Web works (and which sometimes control the Internet as well). Several standards bodies are responsible for defining different aspects of the Web, and all the standards must coordinate to keep the Web maximally usable and accessible. Web standards also must evolve to improve the current status and adapt to new circumstances. This non-exhaustive list gives you an idea of which standards websites and network systems must conform to:

  • IETF (Internet Engineering Task Force): Internet standards (STD), which among other things govern set-up and use of URIs, HTTP, and MIME
  • W3C : specifications for markup language (e.g., HTML), style definitions (i.e., CSS), DOM, accessibility
  • IANA (Internet Assigned Numbers Authority): name and number registries
  • Ecma Intl.: scripting standards, most prominently for JavaScript
  • ISO (International Organization for Standardization): standards governing a diverse array of aspects, including character encodings, website management, and user-interface design

In this article

Opposing standards

Occasionally, the members of a standards body may disagree with how a feature is developing, and some may oppose it. This means that technology implementers (for example web browser vendors) who disagree with the feature in its current form are unlikely to ever implement it. Vendors that do agree with the feature usually still implement it so that it is available to experiment with and provide feedback on. This enables interested parties to build use cases and demonstrate the issues with the feature, hopefully working toward reaching a consensus on a future version. Standards body members often publish a record of their position on different standards, for reference. For example, see Mozilla Specification Positions and WebKit Standards Positions.

See also