FAQs
What are WCAG 2.2 guidelines?
WCAG 2.2 builds on earlier versions of the Web Content Accessibility Guidelines by extending requirements that support people who experience barriers online. The update introduces additional success criteria designed to strengthen navigation, improve visibility of interactive elements, and reduce obstacles in completing tasks such as filling out forms or using controls.
Rather than replacing WCAG 2.1, it expands the framework so organisations have clearer, more practical checkpoints to measure accessibility against. Meeting WCAG 2.2 AA means aligning with the most up-to-date global benchmark for digital accessibility.
Does my website need to be WCAG compliant?
Yes. While the exact legal requirement depends on your country, most organisations are expected to meet at least WCAG 2.1 AA today, with many already moving to WCAG 2.2 AA. Even where the law does not explicitly mandate WCAG, accessibility obligations often fall under broader equality or anti-discrimination laws. Our governance management support helps organisations put the right policies in place.
Does WCAG apply to software?
Yes, WCAG 2 was created for websites, but the principles extend to many types of digital products and software interfaces. Mobile applications, SaaS platforms, and interactive tools that behave like websites are all expected to meet the same accessibility standards. Organisations often apply WCAG as a universal benchmark for digital accessibility, not only for web pages.