# web-standards Published articles for web-standards. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## AI, Disruption, and Standards DevFeed: [AI, Disruption, and Standards]() Original publisher: [Read original article]() Author: L. Jeffrey Zeldman Published: 2026-09-10T16:12:17Z Content type: opinion Language: en Sources: [Jeffrey Zeldman]() Topics: [Artificial Intelligence](), [ai-governance](), [web-standards](), [Generative AI](), [MCP](), [a2ui](), [Accessibility]() Tags: [a2ui](), [accessibility](), [ai](), [ai-governance](), [appearances](), [architecture](), [best-practices](), [design](), [designers](), [ethics](), [formats](), [generative-ai](), [governance](), [mcp](), [open-source](), [standards](), [ux](), [video](), [web-standards](), [webstandards]() ### AI overview This article introduces a video panel on AI and standards featuring Jeffrey Zeldman and Patrick Neeman. The discussion connects lessons from the web standards movement to AI interfaces, focusing on fragmented user experiences, accessibility, interoperability, provenance, and the role of open-source and community efforts. ### Source excerpt Individually, we have very little power, but together we have a great deal of power. In response to a series of Medium articles by Patrick Neeman--like this one that addressed issues of AI governance, fairness, and standardization--publisher Louis Rosenfeld invited Patrick and me to come on his show and talk about AI and standards. A [...] The post AI, Disruption, and Standards appeared first on Jeffrey Zeldman Presents. ## How First Impressions Shape Client Choices and Views of the Web Industry DevFeed: [How First Impressions Shape Client Choices and Views of the Web Industry]() Original publisher: [Read original article]() Author: L. Jeffrey Zeldman Published: 2026-09-01T13:10:32Z Content type: opinion Language: en Sources: [Jeffrey Zeldman]() Topics: [web design](), [Web Development](), [CSS](), [web-standards]() Tags: [css](), [design](), [glamorous](), [my-glamorous-life](), [post](), [tech](), [technofascism](), [web](), [web-design](), [web-standards]() ### AI overview Jeffrey Zeldman reflects on encounters with rude or exploitative people in the web industry and argues that early impressions can foreshadow later conduct. He connects a past website-design negotiation to a former partner's role in changing Twitter's verification system. ### Source excerpt Why first impressions are often correct. Today's jerk is tomorrow's techno-fascist. The post Tales o' Tech: Suffering Fools appeared first on Jeffrey Zeldman Presents. ## Ebb, Meet Flow: Intrinsic Design in a Nutshell DevFeed: [Ebb, Meet Flow: Intrinsic Design in a Nutshell]() Original publisher: [Read original article]() Author: L. Jeffrey Zeldman Published: 2026-08-18T17:24:50Z Content type: opinion Language: en Sources: [Jeffrey Zeldman]() Topics: [Responsive Design](), [web design](), [Front end](), [web-standards]() Tags: [authoring](), [best-practices](), [css](), [design](), [essentials](), [responsive](), [responsive-design](), [responsive-web-design](), [rwd](), [standards](), [state-of-the-web](), [the-essentials](), [the-profession](), [type](), [typography](), [usability](), [user-experience](), [ux](), [w3c](), [web-design](), [web-design-history](), [web-standards](), [webdesign](), [webtype]() ### AI overview This article explains intrinsic or fluid responsive design: define type scales for small and large screens, then let the browser interpolate between them according to viewport width. It connects the approach to earlier ideas about designing for the web's natural ebb and flow and to the development of Responsive Web Design through improved web standards and browser support. ### Source excerpt In 2020, the gifted makers of websites at Clearleft shared methods to achieve fluid responsive design. "Utopian" web design was (and still is) their half-kidding name for this approach, which Apple's Jen Simmons, working indendently, called "intrinsic design." Instead of chasing an ever-changing number of fixed breakpoints, utopian or intrinsic design follows the web's intrinsic [...] The post Ebb, Meet Flow: Intrinsic Design in a Nutshell appeared first on Jeffrey Zeldman Presents. ## Experimenting with the proposed Cross-Origin Storage API in Transformers.js DevFeed: [Experimenting with the proposed Cross-Origin Storage API in Transformers.js]() Original publisher: [Read original article]() Author: Thomas Steiner Published: 2026-06-23T00:00:00Z Content type: tutorial Language: en Sources: [Hugging Face - Blog]() Topics: [AI, ML & Data Engineering]() Tags: [ai-models](), [announcement](), [api](), [artificial-intelligence](), [asr](), [browser](), [cache](), [chrome](), [chrome-extension](), [cos](), [cross-origin-storage](), [inference](), [javascript](), [on-device](), [open-source](), [storage](), [transformers](), [transformers-js](), [wasm](), [web](), [web-apps](), [web-developers](), [web-standards](), [webassembly]() ### AI overview A tutorial that uses Transformers.js browser inference examples to examine duplicate model and WebAssembly downloads across origins and the proposed Cross-Origin Storage API. ### Source excerpt We're on a journey to advance and democratize artificial intelligence through open source and open science. ## A Partial Visual History of zeldman.com DevFeed: [A Partial Visual History of zeldman.com]() Original publisher: [Read original article]() Author: L. Jeffrey Zeldman Published: 2026-06-04T14:35:27Z Content type: opinion Language: en Sources: [Jeffrey Zeldman]() Topics: [Web Development](), [Website](), [HTML](), [layout](), [web-standards]() Tags: [design](), [history](), [html](), [redesign](), [web-standards]() ### AI overview Jeffrey Zeldman reviews part of zeldman.com's visual history, from its 1995 launch through early HTML pages, table-based layouts, animated GIFs, and later server migrations, before discussing the site's current redesign. ### Source excerpt Look back in anchor tags: a partial review of my site's 31-year visual history before diving into the new design. The post Remembrance of zeldman.coms past appeared first on Jeffrey Zeldman Presents. ## April 2026 Baseline monthly digest DevFeed: [April 2026 Baseline monthly digest]() Original publisher: [Read original article]() Author: Jeremy Wagner GitHub LinkedIn Homepage Published: 2026-05-27T07:00:00Z Content type: news Language: en Sources: [web.dev: Blog]() Topics: [web-standards](), [Accessibility](), [Web platform](), [CSS](), [interoperability](), [Web Development]() Tags: [accessibility](), [article](), [css](), [developer](), [interoperability](), [web](), [web-platform](), [web-standards]() ### AI overview April 2026 Baseline digest covering newly available CSS capabilities, precision math utilities, structural semantic elements, Web API additions, and developer-community developments. It also explains how mature web-platform features and cross-browser interoperability can support more accessible web experiences. ### Source excerpt Read about various happenings with Baseline during April 2026. ## One Decade Later: Revisiting Five Front-End Kung Fu Moves DevFeed: [One Decade Later: Revisiting Five Front-End Kung Fu Moves]() Original publisher: [Read original article]() Published: 2026-04-30T23:26:34Z Content type: opinion Language: en Sources: [Ariya Hidayat]() Topics: [Front end](), [Web Development](), [JavaScript](), [Testing](), [test-coverage](), [ci](), [Instrumentation](), [ESLint](), [Git](), [web-standards]() Tags: [browser](), [code-coverage](), [continuous-integration](), [coverage](), [engineering](), [eslint](), [firefox](), [front-end](), [git-hooks](), [javascript](), [testing](), [web-standards]() ### AI overview A retrospective revisits front-end engineering techniques presented at a JavaScript meetup ten years earlier. It discusses git hooks, code complexity, code coverage, and cross-browser testing, explaining how common tools and modern workflows have changed their practical use. ### Source excerpt Exactly ten years ago, I gave a talk at the SF JavaScript meetup titled 5 Kung Fu Moves for Front-End Heroes. A full decade later, I found myself wondering: are these techniques still the secret sauce for modern front-end engineering, or have they been rendered obsolete by time? ## Squarespace & Web Standards: How We Helped Bring HTML Video & Audio Lazy Loading to Today's Browsers DevFeed: [Squarespace & Web Standards: How We Helped Bring HTML Video & Audio Lazy Loading to Today's Browsers]() Original publisher: [Read original article]() Author: Scott Jehl Published: 2026-03-30T21:00:00Z Content type: article Language: en Sources: [Squarespace](), [Squarespace Engineering Blog]() Topics: [web-standards](), [lazy loading](), [HTML](), [Web platform](), [WebKit](), [Chromium](), [Google Chrome](), [Firefox]() Tags: [browsers](), [chrome](), [chromium](), [firefox](), [html](), [lazy-loading](), [standards](), [web-standards]() ### AI overview Squarespace engineers describe how they helped add lazy loading for HTML video and audio to the HTML Standard. They contributed proposed implementations for Firefox and WebKit, worked with Chromium developers on a Google Chrome implementation, and added automated testing. ### Source excerpt At Squarespace, many of our core products are built on web standards, and our engineers are constantly pushing the boundaries of the web's capabilities. Occasionally, those boundaries reveal a limitation: an opportunity for the web's native capabilities to grow. This post is the story of how we found such an opportunity to work with the standards community to improve the web in a way that we - and everyone who uses it - can benefit. ## Announcing TypeScript 6.0 DevFeed: [Announcing TypeScript 6.0]() Original publisher: [Read original article]() Author: Daniel Rosenwasser Published: 2026-03-23T16:34:10Z Content type: release Language: en Sources: [TypeScript]() Topics: [TypeScript](), [JavaScript](), [Compiler](), [Go](), [Tooling](), [web-standards](), [npm](), [Visual Studio Code]() Tags: [code](), [features](), [javascript](), [release](), [tooling](), [types](), [typescript](), [updates](), [web-standards]() ### AI overview TypeScript 6.0 is announced as a bridge release between TypeScript 5.9 and the upcoming TypeScript 7.0. The article highlights alignment work, type-checking changes, import assertion deprecations, updated DOM types, and the transition toward a Go-based compiler and language-service codebase. ### Source excerpt Today we are excited to announce the availability of TypeScript 6.0! If you are not familiar with TypeScript, it's a language that builds on JavaScript by adding syntax for types, which enables type-checking to catch errors, and provide rich editor tooling. You can learn more about TypeScript and how to get started on the TypeScript [...] The post Announcing TypeScript 6.0 appeared first on TypeScript. ## Web Standards and the Fall of the House of Iamus DevFeed: [Web Standards and the Fall of the House of Iamus]() Original publisher: [Read original article]() Author: Alex Russell Published: 2025-09-21T00:00:00Z Content type: opinion Language: en Sources: [Alex Russell]() Topics: [web-standards](), [browsers](), [interoperability](), [Chromium]() Tags: [apple](), [browsers](), [chromium](), [interoperability](), [standards](), [web](), [web-standards](), [webdev]() ### AI overview This commentary argues that web standards and Working Groups generally document, refine, and spread designs that have already demonstrated value rather than determining what browsers may ship. It concludes that responsible feature development depends on thoughtful launch processes, not prior consensus. ### Source excerpt Photo by Photo by Artan Sadiku Commentary about browsers and the features they support is sometimes pejorative towards pre-standardisation features. Given Apple's constriction of Mozilla's revenue stream and its own strategic under-funding of WebKit, this usually takes the form "Chromium just ships whatever it wants." This is true, of course, but not in the way commenters intend; and not only because Blink's rigorous launch process frequently prevents unvalidated designs from shipping. Except for iOS, where Apple attempts to hide its role in undermining the competitive foundation of web standards, every vendor always ships "whatever it wants." That is the point of voluntary standards, and competition is the wind in those sails. Working Groups don't gate what browsers ship, nor do they define what's useful or worthy. There are no seers; no Delphic oracles that fleetingly glimpse a true logos. Working Groups do not invent the future, nor do they hand down revealed truths like prophets of the House of Iamus. In practice, they are thoughtful historians of recent design expeditions, critiquing, tweaking, then spreading the good news of proposals that already work through Web Standards ratified years after features first ship, serving to licence designs liberally to increase their spread. In the end, this is the role of standards and the Working Groups that develop them: to license patents that read on existing designs, reducing risks to implementers who adopt them. Anyone who tries to convince you otherwise, or invites you to try your hand at invention within a chartered Working Group, does not understand what those groups are designed to do. Sadly, this includes some folks who spend a lot of time in them. Contents Terminology Traps Standardisation != Interoperability Standardisation != Responsibility What Working Groups Really Do Chartered Working Groups Are Not Design Venues The Role of Incubation No Prophecies, Only Engineering Complaints about certain engines leading ## Celebrating 20 years of MDN DevFeed: [Celebrating 20 years of MDN]() Original publisher: [Read original article]() Author: joe-walker Published: 2025-07-23T00:00:00Z Content type: article Language: en Sources: [MDN Blog]() Topics: [Interop2027]() Tags: [collaboration](), [community](), [contributors](), [developers](), [docs](), [documentation](), [ecosystem](), [firefox](), [github](), [mozilla](), [open](), [platform](), [web](), [web-developers](), [web-platform](), [web-standards]() ### AI overview MDN marks its 20th anniversary, reflecting on its evolution from a community wiki into a broad resource for web developers and web-platform documentation. The article thanks its contributors and celebrates collaboration across the open web. ### Source excerpt MDN turns 20! Let's look at how we started, how MDN became the most trusted resource for web developers, the impact it's had on the open web, and yes, there's cake, too. ## Remixing Shopify's Admin: How We Made It 30% Faster and AI-Ready DevFeed: [Remixing Shopify's Admin: How We Made It 30% Faster and AI-Ready]() Original publisher: [Read original article]() Author: Craig Brunner Published: 2025-06-30T18:09:52Z Content type: article Language: en Sources: [Shopify Engineering](), [Shopify Engineering - Shopify Engineering]() Topics: [App](), [web-standards]() Tags: [ai](), [architecture](), [remix](), [routing](), [scale](), [shopify](), [typescript](), [web-standards]() ### AI overview Shopify describes rebuilding its Admin application with Remix to improve page-load performance, unify route information, and support large-scale collaboration across many teams. ### Source excerpt Learn how we just made Shopify's Admin 30% faster while setting it up for AI superpowers. We overhauled admin.shopify.com, transforming the system that supports 67 million daily page views and empowers merchants in managing their businesses. ## The Wax and the Wane of the Web DevFeed: [The Wax and the Wane of the Web]() Original publisher: [Read original article]() Author: by Ste Grainer Published: 2024-02-29T14:45:00Z Content type: opinion Language: en Sources: [A List Apart: The Full Feed]() Topics: [Web Development]() Tags: [browsers](), [css](), [design](), [developers](), [hacks](), [state-of-the-web](), [state-of-the-web-web-strategy](), [web](), [web-standards](), [web-strategy]() ### AI overview A reflective article on the web's recurring shifts in design and development practices. It contrasts early table-based layouts, font tags, spacer GIFs, and CGI scripts with the rise of web standards and broader CSS adoption. ### Source excerpt I offer a single bit of advice to friends and family when they become new parents: When you start to think that you've got everything figured out, everything will change. Just as you start to get the hang of feedings, diapers, and regular naps, it's time for solid food, potty training, and overnight sleeping. When you figure those out, it's time for preschool and rare naps. The cycle goes on and on. The same applies for those of us working in design and development these days. Having worked on the web for almost three decades at this point, I've seen the regular wax and wane of ideas, techniques, and technologies. Each time that we as developers and designers get into a regular rhythm, some new idea or technology comes along to shake things up and remake our world. How we got here I built my first website in the mid-'90s. Design and development on the web back then was a free-for-all, with few established norms. For any layout aside from a single column, we used table elements, often with empty cells containing a single pixel spacer GIF to add empty space. We styled text with numerous font tags, nesting the tags every time we wanted to vary the font style. And we had only three or four typefaces to choose from: Arial, Courier, or Times New Roman. When Verdana and Georgia came out in 1996, we rejoiced because our options had nearly doubled. The only safe colors to choose from were the 216 "web safe" colors known to work across platforms. The few interactive elements (like contact forms, guest books, and counters) were mostly powered by CGI scripts (predominantly written in Perl at the time). Achieving any kind of unique look involved a pile of hacks all the way down. Interaction was often limited to specific pages in a site. The birth of web standards At the turn of the century, a new cycle started. Crufty code littered with table layouts and font tags waned, and a push for web standards waxed. Newer technologies like CSS got more widespread adoption by browsers make ## A Chain Reaction DevFeed: [A Chain Reaction]() Original publisher: [Read original article]() Published: 2023-12-11T00:00:00Z Content type: article Language: en Sources: [Dan Abramov]() Topics: [Web Development](), [web-standards](), [CSS](), [Tailwind CSS](), [Code](), [browser]() Tags: [browser](), [code](), [css](), [tailwind](), [web-development](), [web-standards]() ### AI overview The article explains how shared names and layered abstractions make complex web behavior understandable. It connects JSX, HTML-like concepts, CSS, Tailwind classes, browser implementations, operating systems, and web standards to the process of displaying content on a screen. ### Source excerpt The limits of my language mean the limits of my world. ## Humility: An Essential Value DevFeed: [Humility: An Essential Value]() Original publisher: [Read original article]() Author: by Justin Dauer Published: 2023-06-22T13:00:00Z Content type: article Language: en Sources: [A List Apart: The Full Feed]() Topics: [web design](), [HTML](), [JavaScript](), [browser](), [web-standards](), [Accessibility]() Tags: [browser](), [design](), [html](), [javascript](), [web-design](), [web-standards]() ### AI overview This chapter presents humility as an essential value for designers and describes a personal journey from graphic design into web design. It discusses learning HTML and JavaScript to understand how design decisions are rendered in browsers, while reflecting on creativity, connection, usability, accessibility, and the evolving practices of early web design. ### Source excerpt Humility, a designer's essential value--that has a nice ring to it. What about humility, an office manager's essential value? Or a dentist's? Or a librarian's? They all sound great. When humility is our guiding light, the path is always open for fulfillment, evolution, connection, and engagement. In this chapter, we're going to talk about why. That said, this is a book for designers, and to that end, I'd like to start with a story--well, a journey, really. It's a personal one, and I'm going to make myself a bit vulnerable along the way. I call it: The Tale of Justin's Preposterous Pate When I was coming out of art school, a long-haired, goateed neophyte, print was a known quantity to me; design on the web, however, was rife with complexities to navigate and discover, a problem to be solved. Though I had been formally trained in graphic design, typography, and layout, what fascinated me was how these traditional skills might be applied to a fledgling digital landscape. This theme would ultimately shape the rest of my career. So rather than graduate and go into print like many of my friends, I devoured HTML and JavaScript books into the wee hours of the morning and taught myself how to code during my senior year. I wanted--nay, needed--to better understand the underlying implications of what my design decisions would mean once rendered in a browser. The late '90s and early 2000s were the so-called "Wild West" of web design. Designers at the time were all figuring out how to apply design and visual communication to the digital landscape. What were the rules? How could we break them and still engage, entertain, and convey information? At a more macro level, how could my values, inclusive of humility, respect, and connection, align in tandem with that? I was hungry to find out. Though I'm talking about a different era, those are timeless considerations between non-career interactions and the world of design. What are your core passions, or values, that transcend medium? It's ## MWC 2014, Firefox OS Success, and Yet More Web API Evolution DevFeed: [MWC 2014, Firefox OS Success, and Yet More Web API Evolution]() Original publisher: [Read original article]() Author: Brendan Eich Published: 2014-03-08T18:58:11Z Content type: opinion Language: en Sources: [Brendan Eich]() Topics: [Firefox](), [Web APIs](), [Mozilla](), [Mobile](), [web-standards]() Tags: [cordova](), [firefox](), [mobile](), [mozilla](), [uncategorized](), [web-apis](), [web-standards]() ### AI overview A commentary on Mozilla's Firefox OS activities at Mobile World Congress 2014, including a planned $25 smartphone for emerging-market retail channels, a growing device portfolio, and PhoneGap/Cordova support. It also reviews Web APIs being developed or standardized for smartphones and other devices. ### Source excerpt Just over a week ago, I left Barcelona and Mobile World Congress 2014, where Mozilla had a huge third year with Firefox OS. We announced the $25 Firefox OS smartphone with Spreadtrum Communications, targeting retail channels in emerging markets, and attracting operator interest to boot. This is an upgrade for those channels at about the ... Continue reading "MWC 2014, Firefox OS Success, and Yet More Web API Evolution" ## Moving The Web Forward DevFeed: [Moving The Web Forward]() Original publisher: [Read original article]() Author: Paul Irish Published: 2011-12-04T03:33:00Z Content type: article Language: en Sources: [Paul Irish]() Topics: [Web](), [Web platform](), [GitHub](), [frontend development](), [Front end](), [IRC](), [jQuery](), [Boilerplate]() Tags: [community](), [contribute](), [developers](), [development](), [frontend](), [frontend-development](), [github](), [html5](), [open](), [platform](), [project](), [repo](), [resources](), [standards](), [team](), [web](), [web-platform](), [web-standards](), [writeup]() ### AI overview The article introduces Move the Web Forward, an initiative that helps people channel their interest into practical contributions to the web community and web platform. It describes the initiative's collaborative creation through design, frontend development, IRC, etherpad, and GitHub, and highlights examples of participants contributing to web standards, Firefox, BuddyPress, and documentation. ### Source excerpt This Wednesday, me and a ragtag team of like-minded developers launched Move the Web Forward, an initiative to direct people's passions into productive efforts that assist not only the web community but the entire web platform. People often feel the need to "give back", but when it comes to contributing it's a challenge to find the right place. This is something I've seen happen firsthand in the jQuery and HTML5 Boilerplate communities. The MWF effort was inspired by a tweet by WebKit extraordinaire Dimitri Glazkov. If you want to help out with Web standards, you could wear a blue beanie once a year. Or you could start hacking on WebKit/Gecko. -- Dimitri Glazkov (@dglazkov) December 29, 2010 Me and Divya started brainstorming on an etherpad. We rounded up some folks on Google+ and IRC and started collecting a lot of excellent resources. Soon after a design was in the making and we started working in an open repo on github... At this point, I want to call out Mat Marquis aka @wilto, in particular, for really taking early ownership of this project and spearheading the design and frontend development. His efforts really made the site communicate its content effectively. Naturally the site is on github if you'd like to contribute. We have a few issues open that we'll be improving the site with. (Also, let me just say for projects like this, a cron job to pull latest from Github makes for such a relaxing workflow.) Thanks to Divya, Mat, Aaron Forsander, Connor Montgomery, Stephanie Rewis (great writeup!), Nicolas Gallagher, Addy, and all these awesome folk. Truly a socially developed site; everyone collaborating on IRC, etherpad and github (with as many having commit rights as possible). Fun project to work on and I hope to see everyone find the right place for them to get more involved in actively making the web as awesome as you want it to be. 2011.12.02: #movingwebforward in action! Beyond all the people who signed up (with the avatars) on the site to commit to things..