After two years, it’s clear that awareness about Baseline is grown a lot. As one of the co-chair of the group that makes Baseline, Patrick wanted to take a pause and reflect on how Baseline is starting to show up in developer’s lives, but also how it can be perfected.

Piccalilli's resource offers insights, tutorials, and resources for frontend developers and web designers. Readers can learn about HTML, CSS, and JavaScript techniques, as well as design principles and accessibility. With articles, tutorials, and design showcases, Piccalilli provides  guidance and inspiration for creating modern and accessible web experiences.

Piccalilli

Baseline is a browser compatibility status system that categorizes web features into three stages: Not Baseline, Newly Available (supported across major browsers), and Widely Available (supported for 2.5+ years). While it provides a useful shortcut for assessing feature availability across Chrome, Firefox, Safari, and Edge, it has limitations—it doesn't account for all browsers, older versions, accessibility issues, or progressive enhancement strategies. The WebDX Community Group is actively improving Baseline by integrating accessibility data, mapping polyfills and best practices, and expanding browser coverage. Developers should treat Baseline as a starting point rather than a definitive decision-making tool, considering additional factors like specific browser requirements and accessibility before adopting features.

Perfecting Baseline

Baseline fills a gap but is also imperfect permalink

A term that stuck, and an interconnected catalog of features permalink