CSS Working Group publishes June CSS Snapshot 2026

The CSS Working Group published a June 22 edition of CSS Snapshot 2026, collecting the specifications that define the state of CSS and classifying modules by stability. The W3C Group Note explicitly says its primary audience is implementers and that inclusion reflects specification maturity rather than browser adoption.

The snapshot is a map of specification confidence

CSS is developed as many modules instead of one monolithic “CSS version.” The snapshot groups stable specifications into the official definition, identifies reliable Candidate Recommendations, lists fairly stable modules with limited implementation experience, and calls out areas with rough interoperability.

That structure prevents two common mistakes. A recently edited module is not automatically unsafe to study, and a mature specification is not automatically available to every user. For example, the note lists established foundations alongside newer modules such as View Transitions, while separately describing transitions, animations, and other widely deployed areas whose details still have interoperability work.

The document also explains W3C stages. A Working Draft is a design phase; Candidate Recommendation emphasizes tests and independent implementations; Recommendation is the maintenance stage. A Group Note itself is not a W3C-endorsed Recommendation, a status the snapshot states directly.

Pair standards status with runtime data

Architecture records should cite the specification for semantics and a compatibility source for deployment decisions. A design-system proposal that says “the spec is stable” still needs the project’s browser matrix, usage data, and a fallback assessment. Conversely, a feature with uneven implementation can be viable as progressive enhancement when unsupported browsers retain usable output.

Use the snapshot during standards review: locate the module, read its stability category, then test the exact properties and values in supported engines. Avoid shorthand claims such as “CSS 2026 support,” because CSS has no traditional monolithic version and browsers ship features incrementally. The concrete next step is to add specification status and observed browser support as separate fields in frontend decision records.