WCAG 2.2 CSS Lint - Focus & Target Size

WCAG 2.2 became a W3C Recommendation on 5 October 2023 and added five success criteria on top of WCAG 2.1. Three of them are decided almost entirely in CSS: 2.5.8 Target Size (Minimum), 2.4.11 Focus Not Obscured (Minimum) and 2.4.13 Focus Appearance. Stylesheet tooling and code assistants built on 2.1-era material do not look for them, so the rules pass review and the criteria fail.

This extension reads the stylesheet itself - not a rendered page - and reports the declarations that break a criterion, with the criterion number, its conformance level and the line.

What it checks

14 rules, covering 11 success criteria:

Using it

1. Open a .css or .scss file.
2. Command palette → WCAG 2.2 CSS Lint - Focus & Target Size: Check this file.

Findings open as a report next to the file. Two sample stylesheets ship in _fixtures/: dirty.css is 61 lines and returns 14 findings across 11 criteria; clean.css is the same component set after the fixes and returns none.

Free and licensed

Linting the open file is free and finishes the job on its own - all 14 rules, every criterion number, no watermark, no usage counter, no limit on how often you run it.

A licence key adds a different job: Sweep workspace and write report reads every stylesheet in the workspace in one pass and writes a dated criterion-by-criterion table (Markdown + CSV) - the paper record that sits behind an accessibility statement, with file and line for each criterion. Enter it with Enter licence key.

Full workspace sweep and report: free for 7 days from your first sweep, then a licence key.

$29 once - one licence key per person or team seat - 7-day full refund. An accessibility consultant reading one stylesheet by hand bills a $150-$250 hour.

Yardstick

An accessibility consultant reading one stylesheet by hand bills a $150-$250 hour; a third-party WCAG audit of a whole site is quoted in the thousands.

Scope

CSS is one layer. These rules read declarations and selectors, so they see what a stylesheet can decide on its own; contrast pairs that depend on computed inheritance, and anything decided in markup (labels, headings, aria), are outside them. A finding is a place to look with the criterion already identified, not a conformance claim.

Browser version

The same engine and the same 14 rules run as a page, with nothing to install: https://getreadystack.com/tools/wcag22-css-lint