Suggest an editImprove this articleRefine the answer for “How do pseudo-classes affect specificity?”. Your changes go to moderation before they’re published.Approval requiredContentWhat you’re changing🇺🇸EN🇺🇦UAPreviewTitle (EN)Short answer (EN)**Pseudo-classes** count as class-level selectors, so they increase specificity, adding +1 to the `class` column (for example `:hover`, `:focus`, `:nth-child()`). **Key point:** `:where()` is the exception, its specificity is always 0, even if it contains other selectors.Shown above the full answer for quick recall.Answer (EN)ImagePseudo-classes count as **class-level selectors**, so they **increase specificity**, adding +1 to the `class` column of the specificity formula. Simplified: | Selector type | Specificity | |---|---| | `#id` | 1,0,0 | | `.class`, `:hover`, `:focus`, `:nth-child()`, etc. | 0,1,0 | | `element` or `::pseudo-element` | 0,0,1 | So: - `:hover`, `:focus`, `:active`, `:nth-child()`, `:not()`, and other pseudo-classes → **increase specificity**, like a class - `:where()` is the exception, its specificity is always **0**, even if it contains other selectors **Conclusion:** most pseudo-classes make a selector stronger, as if you had added a class to it.For the reviewerNote to the moderator (optional)Visible only to the moderator. Helps review go faster.