WCAG 2.2 readiness

WCAG 2.2 readiness is a targeted check of the site against the NEW success criteria added in version 2.2 relative to 2.1 (e.g. focus visibility, target size, input assistance, authentication without memory, etc.): where the site already conforms and where there are gaps. Honestly about the essence, this is key: this is a READINESS/gap analysis, not fixing. We show what needs work for 2.2; fixing is a separate scope. Honestly about the version relationship: WCAG 2.2 COMPLEMENTS 2.1 (adds criteria), not replaces it — so if you have not yet brought the site to 2.1 AA (803), it is more honest to start with the base, and 2.2 is the next step. We will say plainly if you first need a full 2.1 audit. Honestly about automation: as everywhere in accessibility, some new criteria are checked only manually and with real technologies, not an auto-test. Honestly about evolution: standards update (there will be new versions after 2.2) — 'readiness' is a snapshot for the current version, not a permanent status. Honestly about law: conformance reduces legal risk but is not equal to legal compliance and immunity from lawsuits (a lawyer). Honestly about access: access to the site is needed. An important boundary: this is 2.2 readiness (a gap analysis of new criteria); a full 2.1 AA audit is 803, fixes are 805-826. Picture this: instead of 'the new 2.2 requirements are out, and we do not know if we meet them' — a clear list of gaps for the new version. The base price starts from 18,000 ₽ (depends on the site size).

• A new version WCAG 2.2 is out — it is unclear whether you meet it.
• You do not know which criteria were added relative to 2.1.
• There are gaps against the new requirements, but they are not identified.
• You want to prepare in advance, not catch up with the standard later.

• Checking against the NEW WCAG 2.2 criteria (delta to 2.1)
• Identifying gaps against the new requirements
• Manual checking of criteria not covered by an auto-test
• Prioritization of improvements for 2.2
• An honest statement of whether a base 2.1 audit (803) is needed first
• Indicating boundaries (readiness ≠ fixed; not a legal guarantee)
• An estimate of the improvement scope
• Handover and review with you

• A clear list of gaps against the new WCAG 2.2 criteria
• It is clear what to improve for the new version
• Criteria checked only manually are accounted for
• A basis for improvements (fixes — separate)

• We compare the site with the new 2.2 criteria; collect access
• We identify gaps, manually check what an auto-test misses
• We prioritize, honestly mention the 2.1 base, review with you

• How does 2.2 differ from 2.1 and do I need it?

  WCAG 2.2 adds new criteria to 2.1 (e.g. focus visibility, target size, accessible authentication), without removing the old ones. If you have not yet brought the site to 2.1 AA, it is more honest to start with a base audit (803), and 2.2 readiness is the next step. We will say plainly what you need first.

• Is readiness already conformance?

  No. Readiness is a GAP analysis: where you already meet 2.2 and where you do not. Actually meeting the new criteria is a separate scope of work. We honestly separate: first see the gap, then deliberately close it.

• The standard will update again — is there a point?

  Yes, standards evolve, and 'readiness' is a snapshot for the current version, not a permanent status. But closing new criteria in advance is cheaper and calmer than catching up under pressure (e.g. market or legal requirements). We will honestly note that it is a process, not a one-off point.