Each CSS property is resolved against the Baseline dataset behind MDN and caniuse. Flagged when a desktop engine does not support it. Mobile-only gaps are excluded - `cursor` is absent from iOS Safari by design, not omission.
- Free, no signupNo account, no card
- No AI in the score986 deterministic rules
- Nothing publishedYour scans stay yours
- Answers in secondsQuick scan, no browser
How this rule is weighted
- Importance
- 5 / 10
- How much this matters relative to other rules.
- Confidence
- RESEARCH
- Backed by large-sample study or industry research, not a specification.
- Severity
- warning
- How the finding is presented when it fails.
- Scoring
- Counts
- A failure costs points in its category.
Impact is importance multiplied by the confidence tier’s weight — SPECIFICATION 1.0, RESEARCH 0.7, EMERGING 0.3, EXPERIMENTAL 0.1. Two rules backed by the same class of evidence therefore always carry the same weight, which is what makes the score reproducible rather than hand-tuned.
What produces this finding
Built at scan time by browser support data, not from our static registry. That engine evaluates its whole rule set in one pass, so this check cannot be run on its own — it runs as part of a scan.
Questions about this rule
- Does CSS_BASELINE_LIMITED affect my score?
- Yes. It is an importance 5 rule at RESEARCH confidence, so a failure costs 5 × 0.7 points of impact in the CSS category before that category is normalised to 100.
- What does RESEARCH confidence mean?
- Backed by large-sample study or industry research, not a specification. Confidence is a declared tier rather than a per-rule number, so every rule backed by the same class of evidence carries the same weight - which is what makes the score reproducible instead of hand-tuned.
- How do I check CSS_BASELINE_LIMITED on my own site?
- This rule is produced by browser support data during a scan. browser support data evaluates its whole rule set in one pass, so this check cannot be run on its own - run the CSS checker and it is included.
Tags
- css
- baseline
- browser-support
Related CSS rules
- Stylesheets parse without errorsEvery inline and linked stylesheet is parsed. A parse error means the browser discarded a declaration or a whole rule at load time, so styling that looks correct in the source never applied.CSS_W3C_PARSE_ERROR
- Declaration values match their property grammarEach value is matched against the property's formal grammar from the CSS specifications. A value that does not match is dropped at parse time, so the declaration has no effect even though the property name is correct.CSS_W3C_INVALID_VALUE
- Declarations use real CSS propertiesEach property name is checked against the machine-readable index of properties defined in the CSS specifications. An unknown property is almost always a typo no browser will honour.CSS_W3C_UNKNOWN_PROPERTY
- No CSS expression() usageA legacy Internet Explorer feature that executes JavaScript from CSS - both obsolete and a script-injection vector.CSS_NO_EXPRESSION
- No sub-legible font sizesText below about 3px is invisible to a human but fully indexable. Whether or not it is deliberate, it matches the keyword-stuffing pattern that ranking systems demote for.CSS_NO_INLINE_FONT_SIZE_TINY
- Stylesheet respects reduced-motion preferencesVestibular disorders make large-motion animation genuinely painful. The operating system already exposes the user's preference; honouring it is a two-line media query.CSS_PREFERS_REDUCED_MOTION