Silktide tests websites using WCAG 2.2 (Web Content Accessibility Guidelines) by default. These guidelines define how to make digital content more accessible for people with disabilities, and staying up to date helps ensure your websites meet the latest standards.
Below, we’ve answered some common questions to help you understand what this change means and how it affects your accessibility testing.
What is WCAG 2.2?
WCAG 2.2 is the latest version of the international standard for digital accessibility, published by the W3C. It builds on WCAG 2.1 by introducing new success criteria focused on improving accessibility for users with cognitive disabilities, low vision, and limited motor control.
What’s new in WCAG 2.2?
WCAG 2.2 adds nine new success criteria, with improvements around:
Focus appearance
Target size for touch inputs
Authentication experiences, such as reducing reliance on cognitive tests
Silktide reflects these updates in your accessibility checks; we clearly highlight which checks are specific to WCAG 2.2.
Why has Silktide switched to WCAG 2.2 by default?
We want to ensure you're testing against the most up-to-date accessibility standards; WCAG 2.2 is now the latest official version. By making WCAG 2.2 the default, Silktide helps you stay aligned with industry best practice and prepare for future legal requirements.
Do I need to do anything differently in Silktide?
No action is required. All accessibility testing in Silktide is automatically based on WCAG 2.2. If you're already reviewing your accessibility results, you’ll simply see some new checks included in your reports.
Do I have to meet WCAG 2.2 if I’m only legally required to meet WCAG 2.1 or 2.0?
That depends on your region and specific legal requirements; some regulations reference earlier WCAG versions. However, from an ethical and inclusive design perspective, aiming for WCAG 2.2 is strongly recommended. The new success criteria help remove barriers for a broader group of users and demonstrate your commitment to digital accessibility.
How do I know which checks are specific to WCAG 2.2?
Silktide clearly labels checks that are unique to WCAG 2.2. You can also use filters to view results by WCAG version or success criteria level, helping you track your progress more easily.
Will this affect my compliance reports or scoring?
In most cases, the impact will be minor. Most of the existing criteria remain unchanged, and any changes to scoring or reports will reflect only the additional checks introduced in WCAG 2.2. These are clearly marked, so you can track them separately if needed.