Standards coverage
Every success criterion of 2.2 - all 86 of them, up to - plus conformance and Silktide's own best-practice checks, and how Silktide covers each one.
This page is about testing websites. For PDFs found on your website, see PDFs on your website.
How much does Silktide cover?
Silktide has a check for every one of the 86 success criteria. What that check can do depends on the criterion:
31 of 86
Machine-checkedSuccess criteria where Silktide reports definite failures as errors.
24 of 86
Machine-assistedSuccess criteria where Silktide points to content that may fail, as warnings for a person to confirm.
31 of 86
Guided reviewSuccess criteria where Silktide asks a person to verify - honest when automation cannot decide.
| Level | Success criteria | ✅ Machine-checked | ☑️ Machine-assisted | 🔍 Guided review |
|---|---|---|---|---|
| A | 31 | 13 | 11 | 7 |
| AA | 24 | 11 | 5 | 8 |
| AAA | 31 | 7 | 8 | 16 |
| All levels | 86 | 31 | 24 | 31 |
Level A and AA together, the 55 criteria most accessibility laws cite: 24 machine-checked, 16 machine-assisted, 15 guided review.
No automated tool - Silktide's or anyone else's - can test all of WCAG. Most success criteria hinge on human judgment: whether alternative text is appropriate, whether a page works with a real keyboard, whether an error message actually helps. What automation can do is find the definite failures, flag the likely ones, and make sure the judgment calls are never silently skipped. That is how this page is organized - three separate columns, never rolled into one inflated percentage.
Having a check for every criterion is not the same as testing every criterion automatically. Passing every Silktide check does not, on its own, show that a website conforms to WCAG; see If I score 100%, am I fully accessible?
Coverage levels
- ✅ Machine-checked - Silktide finds these failures automatically and reports them as errors. High confidence; fix them without second-guessing the tool.
- ☑️ Machine-assisted - Silktide reports content that may fail as warnings, pointing to the specific elements or pages involved. The evidence is real, but the verdict needs a person.
- 🔍 Guided review - automation cannot decide this criterion. Silktide adds a review to each page it applies to, saying exactly what a person should verify, so it is never silently skipped.
- ❌ Not covered - Silktide has no check for this criterion. No WCAG 2.2 criterion is in this state today.
Where a criterion has checks at several levels, the table shows the strongest. Follow the check links for exactly what each one tests, and its limits.
WCAG 2.2 coverage
Each criterion links to the official W3C explanation. Since is the WCAG version that introduced it - testing against WCAG 2.2 includes everything from 2.0 and 2.1 except 4.1.1 Parsing, explained below the table. Within a row, checks are listed strongest first: errors, then warnings, then reviews, then ARIA and PDF checks that test the same criterion.
WCAG 2.2 removed 4.1.1 Parsing as obsolete, so it is not one of the 86 and is not counted in the figures above. Silktide still runs its two 4.1.1 checks - Duplicate IDs and Semantic lists - because the problems they find still break . They count toward WCAG 2.0 and 2.1 only: when you test against WCAG 2.2, they are not part of your WCAG results, your score or your Guidelines view.
Reading this honestly
The caveats behind the table:
- No score proves conformance. A website can pass every Silktide check and still fail WCAG, because most criteria have failure modes only a person can find. Conformance is a claim your organization makes after testing that includes people, not a result any automated tool can hand you.
- A ✅ or ☑️ row covers that criterion's machine-detectable failures, not the whole criterion. 2.1.1 Keyboard is the clearest example: Silktide flags elements with mouse-only event handlers, but proving a whole page works with a keyboard requires using one. The same applies to 1.4.1 Use of Color, where Silktide tests link contrast but cannot judge a chart that relies on color alone.
- Quality judgments are prompted, not decided. Silktide reliably finds an image with missing alternative text (error). Whether existing is appropriate is a review prompt, not a machine verdict.
- Guided review is a workflow, not a test result. A 🔍 criterion passes no audit by itself. Its value is completeness: every applicable criterion appears in your Guidelines view with something recorded against it - an automated result, a review decision, or an open prompt - so nothing falls through the cracks. Testing that still needs a person is what a manual audit is for.
- Silktide's web accessibility checks do not yet use AI judgment. The checks here are deterministic. When that changes, this page will change.
What we don't cover yet
Every WCAG 2.2 success criterion - all 86, Levels A through AAA - has at least a guided review in Silktide. There is no uncovered criterion today.
That does not mean every criterion is fully machine-testable. 31 criteria have only a guided review - 7 at Level A, 8 at AA and 16 at AAA - because no mainstream tool, including Silktide, can decide them automatically. Follow each check's help page for exactly what a person must verify.
If a criterion's automated coverage is thinner than you need, tell us - the table above is exactly what we use to prioritize deeper checks.
ARIA coverage
Silktide tests 1.2 usage separately from WCAG, because broken ARIA can make a page less accessible than no ARIA at all. Most ARIA rules also test a WCAG criterion (usually 4.1.2 or 1.3.1), so they are listed in that criterion's row above too. Their results count toward ARIA in your Accessibility score, not toward a WCAG level.
| Silktide check | ARIA rule | Also tests WCAG | Coverage |
|---|---|---|---|
| Invalid ARIA role | aria-valid-role | 4.1.2 | ✅ Machine-checked |
| Missing required ARIA attribute | aria-required-attr | 4.1.2 | ✅ Machine-checked |
| Invalid ARIA attribute value | aria-valid-attr-value | 4.1.2 | ✅ Machine-checked |
| Presentation role on interactive element | aria-presentation-misuse | 4.1.2 | ✅ Machine-checked |
| Prohibited ARIA attribute | aria-allowed-attr | 4.1.2 | ✅ Machine-checked |
| Conflicting ARIA role | aria-conflicting-role | 4.1.2 | ✅ Machine-checked |
| Missing ARIA child role | aria-required-children | 1.3.1 | ✅ Machine-checked |
| Missing ARIA parent role | aria-required-parent | 1.3.1 | ✅ Machine-checked |
| Missing aria-activedescendant ID | aria-valid-idref-activedescendant | 1.3.1 | ✅ Machine-checked |
| Missing aria-controls ID | aria-valid-idref-controls | 1.3.1 | ✅ Machine-checked |
| Missing aria-details ID | aria-valid-idref-details | 1.3.1 | ✅ Machine-checked |
| Missing aria-errormessage ID | aria-valid-idref-errormessage | 1.3.1 | ✅ Machine-checked |
| Missing aria-flowto ID | aria-valid-idref-flowto | 1.3.1 | ✅ Machine-checked |
| Missing aria-owns ID | aria-valid-idref-owns | 1.3.1 | ✅ Machine-checked |
| Nested aria-hidden | aria-hidden-nested | - | ✅ Machine-checked |
| Deprecated ARIA attribute | aria-deprecated-attr | - | ☑️ Machine-assisted |
Best practices beyond the standards
Some things hurt real users without failing any WCAG criterion. Silktide tests these at its own discretion; they count toward Accessibility best practice in your Accessibility score, not toward WCAG conformance:
| Silktide check | Coverage | What it catches |
|---|---|---|
| Accessibility overlay | ✅ Machine-checked | Third-party overlay widgets that claim to fix accessibility and routinely make it worse. |
| Title attribute labeling | ☑️ Machine-assisted | Controls labeled only by title attributes, which most assistive technology handles poorly. |
| Small desktop text | ✅ Machine-checked | Body text rendered too small to read comfortably, even where contrast passes. |
| Icon-only control | ☑️ Machine-assisted | Buttons and links that are only an icon, with no accessible name. |
| Modal focus trap | 🔍 Guided review | Modal dialogs that fail to trap focus while open or restore it on close. |
PDFs on your website
PDFs found while testing your website get their own accessibility checks: tagging, headings, lists, tables, image alternative text, titles, tab order, link descriptions and language. These are the PDF checks in the WCAG table above, plus a few checks that test no WCAG criterion. Their results count toward PDF accessibility in your Accessibility score, separately from the WCAG figures on this page. See PDFs for how they surface in the Accessibility module.
Related
- Accessibility guidelines - this same coverage, applied to your website with evidence per requirement.
- Manual audits - ask Silktide's specialists to test what automation cannot.
- Checks - every Silktide check, with its standard.
- If I score 100%, am I fully accessible? - what a perfect score does and does not mean.
- What is Silktide's position on WCAG 3.0? - why this page, and Silktide's scores, stay on WCAG 2.2.