From HTML and CSS to accessibility, security and privacy

In 1989, Tim Berners-Lee proposed a linked information system at CERN. Over the following years, the foundations of the web took shape: servers, browsers, URLs, HTTP and HTML. The web was made publicly available beyond CERN in 1991. Early HTML primarily described the structure of simple documents and their links. It was not a complete design system—and was never meant to be one.

As use grew, a shared specification became increasingly important. The World Wide Web Consortium (W3C) was founded in 1994 to develop open web technologies. HTML 2.0 was published in 1995 as IETF RFC 1866; HTML 3.2 followed in 1997 as a W3C Recommendation. These milestones also show that web standards are shaped by different organizations, each with its own remit and process.

During the 1990s, Netscape Navigator and Microsoft Internet Explorer competed intensely. Alongside shared capabilities, browser vendors introduced proprietary extensions and interpreted features differently. Developers often had to add special cases and test repeatedly; the same page could behave differently from one browser to another. Competition accelerated development, but made compatibility harder.

CSS offered an important architectural idea: HTML describes the meaning and structure of content, while CSS describes its presentation. CSS1 became a W3C Recommendation in December 1996. Keeping structure and presentation distinct makes consistent styling, adaptation to different screen sizes and alternative presentations easier. It is not an absolute rule—HTML and CSS continue to evolve—but it remains a useful foundation for maintainable, accessible websites.

Starting in 1995, JavaScript brought programmable interaction to the browser: forms could be checked, interfaces updated and responses triggered by user input. The W3C did not standardize the language. Its core language specification is ECMAScript, first published by Ecma International in 1997 as ECMA-262. The distinction matters: JavaScript is the widely used language and runtime, while ECMAScript defines its standardized language foundation.

The Document Object Model (DOM) provided a programming interface for scripts to inspect and change a document's structure and content. DOM Level 1 became a W3C Recommendation in 1998. Together, the language, DOM and browser APIs make dynamic applications possible. Reliable interaction still requires developers to account for varying capabilities, loading states and input methods—and to avoid making essential content dependent on scripts alone.

As web applications became more complex, the early capabilities of HTML were no longer enough. Founded in 2004, WHATWG began work on the evolution of HTML; in 2007, the W3C established an HTML working group. HTML5 became a W3C Recommendation in 2014. Today, HTML is maintained as a continuously updated WHATWG Living Standard, while W3C and WHATWG collaborate on web technologies.

HTML introduced semantic elements such as <article> and <section>, native audio and video features, and capabilities for web applications into the standardization process. Semantics help browsers, search services and assistive technologies understand content. Mobile use, however, did not become possible through HTML5 alone: responsive CSS, flexible layouts, viewport configuration and capable browser APIs also play a part.

A modern standard must do more than make content visible in one browser. The Web Content Accessibility Guidelines (WCAG), developed by the W3C Web Accessibility Initiative, provide testable guidance for making content perceivable, operable and understandable to people with different sensory, motor and cognitive abilities. WCAG 2.2 became a W3C Recommendation in 2023. Good practice starts with semantic HTML, keyboard access, clear labels and sufficient contrast.

Security and privacy complement this work, but are not the same as HTML or CSS standards. Protocols such as TLS protect data in transit; secure implementation, updates and sensible access controls are also necessary. The General Data Protection Regulation (GDPR) is a law, not a technical web specification. Website teams should assess technical standards, legal obligations and concrete risks separately—and limit data collection to what is genuinely needed.

The history of the web shows that open standards do not prevent innovation; they provide a shared foundation for it. HTML, CSS, ECMAScript, the DOM, HTTP and WCAG come from different standardization processes. Together, they help make content available across devices, browsers and contexts. No single standard guarantees quality: careful implementation and ongoing testing matter just as much.

In practice, use semantic markup, build robust responsive layouts, test interactions with both mouse and keyboard, consider assistive technologies, protect data in transit and collect as little personal data as possible. Standards are not a box to tick once and forget. Following their development and testing with real users helps build a more interoperable, accessible and reliable web.