Skip to content
SilktideHelp

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-checked

Success criteria where Silktide reports definite failures as errors.

24 of 86

Machine-assisted

Success criteria where Silktide points to content that may fail, as warnings for a person to confirm.

31 of 86

Guided review

Success criteria where Silktide asks a person to verify - honest when automation cannot decide.

LevelSuccess criteria✅ Machine-checked☑️ Machine-assisted🔍 Guided review
A3113117
AA241158
AAA317816
All levels86312431

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?

How we arrive at these figures

Figures are of the 86 success criteria in WCAG 2.2, Levels A through AAA. (WCAG 2.2 removed 4.1.1 Parsing; it is not counted.) Each criterion is counted once, at the strongest of its website checks:

  • 31 have at least one check that reports errors (machine-checked).
  • 24 have a check that reports warnings, but none that reports errors (machine-assisted).
  • 31 have only a review (guided review).
  • Together that is 86 of 86 - every WCAG 2.2 success criterion has at least one Silktide check.
  • Restricted to Level A + AA (the 55 criteria most laws reference): 24 machine-checked, 16 machine-assisted, 15 guided review.
  • The figures count Silktide's checks of web pages. PDF checks are listed in the rows they test but not counted, because PDFs are scored separately (see PDFs on your website). Counting them would move one criterion, 2.4.3 Focus Order, to machine-checked for PDFs only.
  • ARIA checks are listed in the rows they test (1.3.1 and 4.1.2) but not counted either. Counting them would change nothing: both criteria already have machine-checked WCAG checks.
  • An automated check on a criterion does not mean the whole criterion is machine-testable. Almost every criterion has failure modes only a human can find; the table below tells you which parts are automated.

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.

Success criterionLevelSinceCoverageSilktide checks
1.1.1 Non-text ContentA2.0✅ Machine-checkedAdjacent links · Duplicate alt text · Image button alt text · Image in link alt text · Missing alt text · Title on empty alt text · Decorative images · Submit button alt text · Appropriate alt text · PDF image alt text · PDF text mapping
1.2.1 Audio-only and Video-only (Prerecorded)A2.0☑️ Machine-assistedText alternative for prerecorded audio · Text alternative for prerecorded video
1.2.2 Captions (Prerecorded)A2.0✅ Machine-checkedCaptions for prerecorded audio / video
1.2.3 Audio Description or Media Alternative (Prerecorded)A2.0☑️ Machine-assistedDescriptions or text alternatives for prerecorded media
1.2.4 Captions (Live)AA2.0☑️ Machine-assistedCaptions for live audio
1.2.5 Audio Description (Prerecorded)AA2.0☑️ Machine-assistedDescriptions for prerecorded media
1.2.6 Sign Language (Prerecorded)AAA2.0☑️ Machine-assistedSign language for prerecorded media
1.2.7 Extended Audio Description (Prerecorded)AAA2.0☑️ Machine-assistedExtended descriptions for prerecorded media
1.2.8 Media Alternative (Prerecorded)AAA2.0☑️ Machine-assistedText alternative for prerecorded media
1.2.9 Audio-only (Live)AAA2.0☑️ Machine-assistedAlternative text for live audio
1.3.1 Info and RelationshipsA2.0✅ Machine-checkedAvoid labels on non-labelable controls · Cell headers · Dialog labels · Field labels · Fieldset grouping · Fieldset legends · Heading text · Identical table summary and caption · Missing ARIA description IDs · Missing ARIA label IDs · Missing H1 · Obsolete scope attribute · Semantic links · Semantic lists · Table header IDs · Table headers · Table heading scopes · Unique label associations · Valid label IDs · Valid label IDs for fragments · Potential headings · Summaries for tables · Missing ARIA child role · Missing ARIA parent role · Missing aria-activedescendant ID · Missing aria-controls ID · Missing aria-details ID · Missing aria-errormessage ID · Missing aria-flowto ID · Missing aria-owns ID · PDF content tagging · PDF heading order · PDF lists · PDF tables · PDF tagging
1.3.2 Meaningful SequenceA2.0🔍 Guided reviewMeaningful sequence (HTML)
1.3.3 Sensory CharacteristicsA2.0🔍 Guided reviewSensory characteristics
1.3.4 OrientationAA2.1✅ Machine-checkedOrientation lock
1.3.5 Identify Input PurposeAA2.1✅ Machine-checkedProgrammatic field purpose
1.3.6 Identify PurposeAAA2.1🔍 Guided reviewIdentify purpose
1.4.1 Use of ColorA2.0✅ Machine-checkedLink contrast
1.4.2 Audio ControlA2.0☑️ Machine-assistedRequired audio controls
1.4.3 Contrast (Minimum)AA2.0✅ Machine-checkedText contrast · Text contrast over images
1.4.4 Resize TextAA2.0✅ Machine-checkedPinch-to-zoom enabled
1.4.5 Images of TextAA2.0🔍 Guided reviewText information
1.4.6 Contrast (Enhanced)AAA2.0✅ Machine-checkedHigh text contrast
1.4.7 Low or No Background AudioAAA2.0🔍 Guided reviewBackground audio
1.4.8 Visual PresentationAAA2.0🔍 Guided reviewUser control of text
1.4.9 Images of Text (No Exception)AAA2.0🔍 Guided reviewImages of text
1.4.10 ReflowAA2.1✅ Machine-checkedMobile horizontal scrolling · Mobile zoom and scrolling · Why does Silktide test with an iPhone 5?
1.4.11 Non-text ContrastAA2.1✅ Machine-checkedForm control contrast
1.4.12 Text SpacingAA2.1✅ Machine-checkedText spacing
1.4.13 Content on Hover or FocusAA2.1🔍 Guided reviewContent on hover or focus
2.1.1 KeyboardA2.0☑️ Machine-assistedKeyboard support
2.1.2 No Keyboard TrapA2.0🔍 Guided reviewApplet or plugin focus
2.1.3 Keyboard (No Exception)AAA2.0🔍 Guided reviewKeyboard (no exception)
2.1.4 Character Key ShortcutsA2.1✅ Machine-checkedAccesskey attribute · Character key shortcuts
2.2.1 Timing AdjustableA2.0✅ Machine-checkedDelayed meta refresh
2.2.2 Pause, Stop, HideA2.0🔍 Guided reviewUnavoidable animation
2.2.3 No TimingAAA2.0🔍 Guided reviewNot timing dependent
2.2.4 InterruptionsAAA2.0🔍 Guided reviewPage interruptions
2.2.5 Re-authenticatingAAA2.0🔍 Guided reviewTime limited data loss
2.2.6 TimeoutsAAA2.1🔍 Guided reviewSession timeout
2.3.1 Three Flashes or Below ThresholdA2.0🔍 Guided reviewFlashing content (A)
2.3.2 Three FlashesAAA2.0🔍 Guided reviewFlashing content (AAA)
2.3.3 Animation from InteractionsAAA2.1🔍 Guided reviewAnimation from interactions
2.4.1 Bypass BlocksA2.0✅ Machine-checkedFrame title · Missing anchor · Skip to content · Frame titles
2.4.2 Page TitledA2.0✅ Machine-checkedMissing title · Appropriate page title · PDF display title · PDF title
2.4.3 Focus OrderA2.0☑️ Machine-assistedFocus order · PDF tab order
2.4.4 Link Purpose (In Context)A2.0✅ Machine-checkedLink purpose · Links with different destinations · PDF link descriptions
2.4.5 Multiple WaysAA2.0🔍 Guided reviewMultiple ways to access a page
2.4.6 Headings and LabelsAA2.0🔍 Guided reviewAppropriate headings and labels
2.4.7 Focus VisibleAA2.0✅ Machine-checkedVisible focus
2.4.8 LocationAAA2.0🔍 Guided reviewLocation
2.4.9 Link Purpose (Link Only)AAA2.0🔍 Guided reviewLink purpose (link only)
2.4.10 Section HeadingsAAA2.0🔍 Guided reviewSection headings
2.4.11 Focus Not Obscured (Minimum)AA2.2✅ Machine-checkedFocus not obscured
2.4.12 Focus Not Obscured (Enhanced)AAA2.2✅ Machine-checkedFocus not partly obscured
2.4.13 Focus AppearanceAAA2.2✅ Machine-checkedClear focus
2.5.1 Pointer GesturesA2.1🔍 Guided reviewPointer gestures
2.5.2 Pointer CancellationA2.1☑️ Machine-assistedPointer cancellation
2.5.3 Label in NameA2.1✅ Machine-checkedLabel in name
2.5.4 Motion ActuationA2.1☑️ Machine-assistedMotion actuation
2.5.5 Target Size (Enhanced)AAA2.1✅ Machine-checkedLarge enough controls
2.5.6 Concurrent Input MechanismsAAA2.1☑️ Machine-assistedConcurrent input
2.5.7 Dragging MovementsAA2.2🔍 Guided reviewDrag and drop alternative
2.5.8 Target Size (Minimum)AA2.2✅ Machine-checkedInteractive component distance
3.1.1 Language of PageA2.0✅ Machine-checkedInvalid language for page · Page language · PDF language
3.1.2 Language of PartsAA2.0✅ Machine-checkedInvalid language for part of page
3.1.3 Unusual WordsAAA2.0🔍 Guided reviewDefinitions of unusual words
3.1.4 AbbreviationsAAA2.0🔍 Guided reviewIdentifiable abbreviations
3.1.5 Reading LevelAAA2.0✅ Machine-checkedEasy to understand content
3.1.6 PronunciationAAA2.0✅ Machine-checkedRP and RT elements
3.2.1 On FocusA2.0🔍 Guided reviewOn focus
3.2.2 On InputA2.0✅ Machine-checkedForm submit button
3.2.3 Consistent NavigationAA2.0🔍 Guided reviewConsistent navigation
3.2.4 Consistent IdentificationAA2.0🔍 Guided reviewConsistent identification
3.2.5 Change on RequestAAA2.0✅ Machine-checkedExplain opening new tabs
3.2.6 Consistent HelpA2.2☑️ Machine-assistedConsistent help
3.3.1 Error IdentificationA2.0☑️ Machine-assistedError identification
3.3.2 Labels or InstructionsA2.0☑️ Machine-assistedForm instructions
3.3.3 Error SuggestionAA2.0☑️ Machine-assistedSuggested form corrections
3.3.4 Error Prevention (Legal, Financial, Data)AA2.0☑️ Machine-assistedError prevention mechanism (AA)
3.3.5 HelpAAA2.0☑️ Machine-assistedContext-sensitive help
3.3.6 Error Prevention (All)AAA2.0☑️ Machine-assistedError prevention mechanism (AAA)
3.3.7 Redundant EntryA2.2☑️ Machine-assistedRedundant entry
3.3.8 Accessible Authentication (Minimum)AA2.2☑️ Machine-assistedAccessible login
3.3.9 Accessible Authentication (Enhanced)AAA2.2☑️ Machine-assistedAccessible login (no exception)
4.1.2 Name, Role, ValueA2.0✅ Machine-checkedScreen reader links · Conflicting ARIA role · Invalid ARIA attribute value · Invalid ARIA role · Missing required ARIA attribute · Presentation role on interactive element · Prohibited ARIA attribute
4.1.3 Status MessagesAA2.1🔍 Guided reviewStatus messages

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 checkARIA ruleAlso tests WCAGCoverage
Invalid ARIA rolearia-valid-role4.1.2✅ Machine-checked
Missing required ARIA attributearia-required-attr4.1.2✅ Machine-checked
Invalid ARIA attribute valuearia-valid-attr-value4.1.2✅ Machine-checked
Presentation role on interactive elementaria-presentation-misuse4.1.2✅ Machine-checked
Prohibited ARIA attributearia-allowed-attr4.1.2✅ Machine-checked
Conflicting ARIA rolearia-conflicting-role4.1.2✅ Machine-checked
Missing ARIA child rolearia-required-children1.3.1✅ Machine-checked
Missing ARIA parent rolearia-required-parent1.3.1✅ Machine-checked
Missing aria-activedescendant IDaria-valid-idref-activedescendant1.3.1✅ Machine-checked
Missing aria-controls IDaria-valid-idref-controls1.3.1✅ Machine-checked
Missing aria-details IDaria-valid-idref-details1.3.1✅ Machine-checked
Missing aria-errormessage IDaria-valid-idref-errormessage1.3.1✅ Machine-checked
Missing aria-flowto IDaria-valid-idref-flowto1.3.1✅ Machine-checked
Missing aria-owns IDaria-valid-idref-owns1.3.1✅ Machine-checked
Nested aria-hiddenaria-hidden-nested-✅ Machine-checked
Deprecated ARIA attributearia-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 checkCoverageWhat it catches
Accessibility overlay✅ Machine-checkedThird-party overlay widgets that claim to fix accessibility and routinely make it worse.
Title attribute labeling☑️ Machine-assistedControls labeled only by title attributes, which most assistive technology handles poorly.
Small desktop text✅ Machine-checkedBody text rendered too small to read comfortably, even where contrast passes.
Icon-only control☑️ Machine-assistedButtons and links that are only an icon, with no accessible name.
Modal focus trap🔍 Guided reviewModal 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.

Last updated

Was this page helpful?