#webstandards

RFC 10008 gave HTTP a QUERY method in June 2026: safe and idempotent like GET, with a request body like POST. Almost nothing implements it yet.

Modern browsers are basically operating systems disguised as applications and binary size bloat is an...

I built 69 text-fragment links from my own production build and clicked each one in Chromium. All 48 prose quotes landed; 14 of 15 code-block quotes did not.

In a new post responding to a WHATWG discussion, Lea Verou pushes back on the framing that polyfilling is harmful, and defends it as the mechanism that lets browsers ship first.

For years, API developers have lived with an awkward choice. When a client wants to retrieve data,...

There is a meeting that happens in every engineering org, roughly once a quarter, forever. Someone is...

w3c issue 37 has 40+ comments debating how to standardize identity and authorization for ai agents...

w3c issue 37 is tracking how ai agents executing payments will impact the web's technical and...

Practical accessibility guide for developers: semantic HTML, ARIA labels (when and when not to use), keyboard navigation, screen reader testing, color contrast, and automated a11y testing in CI/CD.

69,000 bots. 165 million transactions. No shared trust layer between any of them. That's the...

Interop 2026 marks a pivotal shift: browsers are collaborating on shared web standards, reducing developer headaches and boosting user experiences. Forget polyfills; embrace the future of a unified web.

Semantic HTML is more than just writing “clean code.” It’s about giving meaning to your content. By...